What worked at two locations quietly breaks at three

At one or two locations, you are the standard. At three, you cannot be in every operatory, and whatever was living in your head stops traveling. Standardization is how your judgment and your culture keep moving without you, framed as support for your staff, never surveillance.

Building something bigger than one chair

Opening a third location is a different ambition than running a practice. You are building a group: a shared standard of care with your name on it, a bench of location leaders you developed, careers for people who bet on you early, maybe a legacy that outlasts your own clinical years. The owners who get here are not chasing a bigger paycheck. They are builders, and the third location is where the building either becomes an organization or becomes a pile of practices.

The fear: it breaks quietly, and you find out late

Here is the fear, stated precisely: what worked at two locations quietly breaks at three, and nothing announces it. At one or two sites, you were the system. You were in the building most days, your standards traveled in your presence, and drift got corrected the same week it started. At three, the math fails. You cannot be in every operatory, and the location you are not standing in is running on whatever traveled without you.

Documentation drifts first: three sites develop three ideas of what a complete note looks like, and nobody sees it until claims from one location start bouncing.
The coverage conversation diverges: one front desk verifies before the visit, another verifies after, and patients get three different money experiences under one brand.
Problems surface as month-old numbers: without a shared standard, you learn about drift from a report, weeks after the habit set in, at the site you visit least.

None of this is a people failure. Your teams did not get worse. The system that held everything together (you, physically present) stopped scaling. That is the diagnosis, and it points directly at the fix.

People: you cannot clone yourself. Standardize instead

Standardization has a bad reputation because it is so often done as surveillance: dashboards pointed at staff, metrics used as scorecards, written processes deployed as evidence for blame. That version deserves its reputation, and it also fails, because people do not maintain systems that exist to catch them. The version that works is the opposite: standardization as support. A shared written standard is how your judgment travels to the operatory you are not in, and how a location leader can be confident they are doing it right without calling you.

Frame the standard as backup, not oversight: the written process is what lets a new hire at site three deliver site-one quality in week two, and what protects staff when a judgment call gets questioned later. Say that out loud, repeatedly.
Develop location leaders by giving them the standard: a leader with a written playbook can run their building with real authority. A leader without one can only relay your decisions, which is not leadership and does not scale.
Let sites improve the standard: a standard the locations can propose changes to is theirs. One handed down and frozen is yours, and it will be quietly ignored at the site you visit least.

Week-one move, costs nothing: have each location write down its version of one routine you believe is standard (say, how tomorrow's schedule gets verified). Owner: each location lead. First result: immediate, and usually humbling. The differences you find are your real standardization backlog, ranked by how much they surprised you.

Process and technology: one standard of documentation and coverage

Where should the shared standard start? Documentation and coverage, because they sit at the top of the metric chain: documentation quality feeds clean claims (in plain words: how often insurance pays the first time without kicking the claim back), and verification before the visit feeds case acceptance (of the dentistry recommended, how much actually gets scheduled). Standardize upstream and the downstream numbers converge across sites on their own.

This week (costs nothing): a one-page definition of a complete note, agreed with your clinicians across sites. Owner: your clinical lead. Cost band: time only. First result: 2 to 4 weeks, read through each site's end-of-day carried-notes count. Moves: documentation quality.
This week (costs nothing): coverage verified before the visit at every site, as a written checklist run on tomorrow's schedule. Owner: each front-desk lead. Cost band: time only. First result: within a month, tallied as cost-surprise conversations per week. Moves: cost surprises, then case acceptance.
This quarter (modest investment): a documentation layer that enforces the shared standard at every site, on top of whatever each location already runs. Owner: clinical lead plus location leads. Cost band: subscription plus onboarding time, piloted on one or two sites first. First result: within the pilot month, on the pilot sites' own baselines. Moves: documentation quality, clean claim rate.
This year (bigger commitment): org-level visibility, so drift surfaces as this week's signal instead of last month's report, and a named revenue-integrity owner at group level. Owner: you or your operations lead. Cost band: platform decision plus a role. First result: a quarter. Moves: clean claim rate, collections (how long earned money waits before it lands).

The technology constraint at three locations is blunt: your sites may not run the same practice-management system, and a forced migration is a rip-and-replace across three buildings at once. The standardization layer has to sit on top of what each site already runs. On write-back, demand honesty from any vendor, including us: Chairside writes notes natively to Dentrix G7 through the bridge; for Dentrix Enterprise, Eaglesoft, and Open Dental the finished note attaches as a document; NexHealth and Cloud9 integrations are read-only with no note write-back. A vendor vague on this table will be vague after you sign.

Prove it the way a builder proves things: pilot first

The three-question test from the series flagship applies with extra force at group scale, because a group-wide mistake costs three buildings. Time to first value in weeks, an owner on your team at every site, and nothing that breaks if you cancel. The pilot-first motion is how you run that test honestly: one or two flagship locations, their own 30-day baselines set before go-live, expansion on evidence rather than on a pitch.

Set the baseline before the pilot: carried notes per day and cost-surprise tallies at the pilot sites, for one week, on paper. Cost: nothing, and it makes the pilot's result yours instead of the vendor's.
Judge the pilot on the metric chain: documentation quality first, clean claim rate a month behind it, exactly as the map predicts. An upstream fix showing up downstream on schedule is what a working system looks like.
Expand one location at a time, with each site's lead owning the install: the rollout is also leadership development, which is the thing you were actually building.