One promise, many clinics: writing a franchise operating standard that travels

01

A manual is not a standard

A standard is what happens in the room when nobody is watching. The manual is only a claim about what should happen. The distance between the two is where the actual operating problem lives.

I would test a written standard by asking different teams to perform the same defined scenario. Observe where they interpret the instruction differently, then have the appropriate owner resolve the ambiguity. Approval of a document is only the start of that work.

Read that as a design finding rather than a criticism. If qualified people drift from a written procedure while calm, the procedure was never doing the work you thought it was. Something else was.

02

Separate the promise from the method

Start by sorting everything in the manual into two lists.

The promise is what the patient gets, and it does not vary. The qualified person named on the record performs the procedure. Consent is taken before payment, not alongside it. The price given in writing is the price charged. Every case produces a record the patient can take to their own doctor. A complication has a named owner and a defined response time.

The method is how a site delivers that, and it should vary. Staffing mix, appointment sequencing, which room does what, the local supplier, the language the counselling is delivered in, how the follow-up call gets made. A site in a small town with four staff cannot run the same choreography as a site with fourteen, and forcing it to try produces the worst outcome available, which is a site that fails the standard and hides it.

In a franchise system, clinical governance and commercial ownership may sit with different parties. I would make the authority for each decision explicit in the operating agreement and test how an unresolved issue reaches the right owner.

03

The four line standard

Here is the format I use, and it fits on one page per procedure.

The promise. One sentence saying what the patient gets. Written from the patient's side, not the operator's.

The trigger. When this applies, and just as importantly when it does not. Most standards are ignored because staff cannot tell whether today's case is one of the ones it covers.

The proof. The artefact this leaves behind. A signed form, a photograph set to a defined angle, a timestamped note, a returned call log. If the standard produces no artefact, you have written a preference.

The local part. An explicit line saying what the site decides for itself. Naming this is what stops the whole document being treated as advisory.

Monday morning version: take your ten most referenced procedures, rewrite each as those four lines, and archive the rest of the manual as reference rather than as standard. Ten pages that people can hold in their head will beat four hundred that they cannot. If a rule does not survive the rewrite, it was probably a preference wearing a uniform.

04

Proof beats inspection

The strongest argument for building evidence into the work is that self reported compliance is close to worthless.

Separate evidence that a checklist exists from evidence that its required steps were performed. A clinical reviewer should define what adequate completion means. Operations can then check records and, where appropriate and authorised, observe how the process is actually used.

The fix is not more auditors. It is choosing standards whose proof is a by-product of doing the work properly. A photograph taken at a fixed angle cannot be produced without positioning the patient. A consent form timestamped before the payment record cannot be back-dated in a system that locks entries. Build the evidence into the flow and most of your audit stops being a visit and starts being a query.

If your evidence of compliance is a tick from the person who was meant to comply, you have measured willingness to tick.

05

Let sites adapt, but make them ask

The same narrative review makes a second point worth stealing. Checklists work better when they are adapted to local conditions and existing workflow rather than imposed unchanged, because a step that duplicates something the team already does gets skipped, and skipping becomes normal.

So build a route for variation. A site that cannot meet a method files a short request: what it cannot do, why, what it proposes instead, and how it will still produce the proof. You approve or refuse in writing, with an expiry date. Two things then happen. Deviation becomes visible rather than hidden, and your central team finds out where the standard is unrealistic. The third or fourth identical request is not an exception. It is a drafting error, and the manual is what should change.

06

What you hold and what you do not

You do not control whether a franchisee cares. You do not control their landlord, their staff turnover, the local salary market, or the day a good manager resigns. You do not control whether the market rewards the standard you hold.

What you control is narrow and it is enough. Which promises are non-negotiable, and how few of them there are. Whether each one produces evidence without anybody being asked. What you do the first time a strong performing site breaks one, because the network reads that decision more carefully than it reads the manual. And whether you rewrite the standard when the exception requests keep telling you the same thing.