CG Common Ground | Common Ground Systems
What we did and what it producedActive

The work, decision by decision

What the pattern actually fixes in place

  1. One folder and page template, shared across every room, so a new engagement's structure is a known quantity from the first day instead of a decision someone has to make again.
  2. One access standard. A password gate that fails closed on any error rather than open, so a misconfiguration hides a room instead of exposing it, checked directly against the running room rather than assumed correct because the code looks right.
  3. One layout, a client-facing view framed around the firm's own notes rather than a sales pitch, paired with a working surface for the team, so the same room serves both audiences without needing two separate builds.
  4. Two independent checks before any room is called live. A direct probe against the room itself (does the gate actually behave the way it is supposed to, for every page, from outside the room), and a separate read-back against the source material (does what the room actually says match what the underlying documents actually say). A room that looks live and is not is worse than no room at all, which is the reasoning behind checking it two different ways rather than one.

What it produced

The clearest proof that the pattern held rather than just sounding good in theory: seven private data rooms were built in parallel in a single day in June 2026, work that would have taken weeks under the original one-off approach. The pattern kept scaling from there, and the firm now runs more than ten gated data rooms on the same one standard, each one a working surface for the team and a client-facing view built around the firm's own notes, whether the room is for an active deal or an early diligence look.

What we kept, replaced and installed

We kept the actual decisions made under deadline on the first room, the folder shape, the gate design, the layout split between public narrative and private record, because none of those decisions were wrong, they just were not yet reusable. We replaced treating each new engagement as its own from-scratch build. We installed the template, the access standard, and the two-way check as a standing pipeline that a new room gets run through rather than reinvented against.

What it costs, and what we would watch

Refusing to let each new engagement invent its own system is the whole discipline, and it is a discipline that costs something real the first time a genuinely unusual engagement wants something the pattern was not built for: the temptation to bend the pattern quietly rather than decide deliberately whether this is a case that earns a real exception. What we would watch going forward, as the pattern keeps scaling past ten rooms: whether the two-way check (the direct probe and the source read-back) is actually run every time a new room ships, or whether volume starts to erode the discipline that made the pattern trustworthy in the first place. This room, and every one of its sibling rooms in this space, was built and checked the same way.

The result, in short

More than ten gated data rooms now run on one template, one access standard and one layout. The pattern's scaling test, seven rooms built in parallel in a single day, replaced what the original one-off approach would have spread across weeks. Every room, including this one, is checked two independent ways before it is called live.

A slice of the project list

A few related projects.