Franchise SOP Development from the Field: The Coach's Harvest

Franchise SOP development is normally treated as a headquarters job, but much of the raw material is in the field. When three locations independently invent the same workaround, the manual has a gap and the fix already exists. The coach who notices the repetition and writes it up owns something headquarters cannot generate.

Headquarters has its own version of the work — find a location beating its band, interview the operator for the mechanism, publish a candidate standard — and I set that method out in capture franchise tribal knowledge. It depends on somebody at headquarters having time to go looking.

The field version starts from something only a coach has: the same problem seen solved three different ways in three different buildings.

The signal is repetition, not excellence

You are not looking for your best store. You are looking for the same invention twice.

A brand's morning delivery lands during the breakfast rush, so the manual's receiving sequence never quite works. One store began staging the pallet in the closed dining room and breaking it down after nine. A second had done the same and built a laminated card for it. A third had rearranged the walk-in so the receiving order matched the shelf order. None knew about the others, and each had taken roughly 20 minutes out of the worst part of the morning — one could show about $260 a month of reduced waste. Invented numbers, but the arithmetic an owner does on the back of an invoice.

That is a standard operating procedure with three independent trials already run. Headquarters could not have designed it, because headquarters does not know the delivery lands at the wrong time.

What convergent invention looks like on the ground:

• The same workaround. Two or more locations doing the identical thing the manual does not describe.
• The same discarded step. A step nobody at three sites performs, and each will tell you why if asked directly.
• The same locally bought object. A timer, a whiteboard, a second label printer. Somebody spending their own money is a complaint in physical form.
• The same question, repeated. Asked at four locations in a month, it is a gap in the manual rather than four confused operators.

One instance is interesting. The second is evidence. The third is a standard nobody has written yet.

Why coaches see this and still do not write it down

Coaches notice. Ask any field consultant about a fix they have seen at three stores and you get an answer in five seconds.

The visit template is part of the reason: a form built around exceptions has somewhere to record what was out of standard and nowhere to record what beat it. But the deeper reason is incentives. A coach is measured on visits completed, commitments closed and audit scores. Harvesting an SOP produces nothing measurable this quarter, and at the span most territories carry, unmeasured work loses every time — the squeeze described in franchise business consultant span of control, showing up as knowledge that never leaves the car park.

There is a political reason too. Publishing a workaround says the standard is wrong, and the person saying it out loud is the coach rather than the operator. If the brand-standards team is defensive, the coach carries the cost of the correction — a lesson most learn once.

And writing an SOP sounds like a project — template, review cycle, format. At the harvest stage it is four lines.

The four lines, written before you drive away

Do it while the detail is fresh. Anything postponed to Sunday becomes a summary, and the value is in the specifics.

1. The sequence, with every number said out loud. What happens, in what order, at what time, at what par level. "Stage the pallet in the dining room, break it down after nine" is usable; "they manage receiving better" is not.
2. What it replaced, and what breaks without it. The dropped step from the manual, and what the store does when the person who invented it is off.
3. Where else you have seen it. Store names and dates, which your route puts you in a position to supply and which turn an anecdote into three trials.
4. Who found it. Name and location, spelled correctly, for each instance.

Then two disciplines. Leave your reasoning out — you are filing evidence, and a note that argues reads as a campaign — and send it to a named person, not a shared mailbox. Where such a note should live has an unflattering answer at most brands: nowhere, which is the symptom in the franchise CRM vs management software diagnosis that no category owns.

Franchise SOP development survives only if credit is attached

This is what decides whether there is ever a second contribution. When a field-sourced fix reaches the network as "a best practice from the field", the operator who invented it stops volunteering, and so do the two who hear about it. Nobody complains; they simply have nothing to say at the next visit. Attribution is not a courtesy in franchise SOP development, it is the payment, and a store name in the header costs the brand nothing.

The strongest version names the mechanism after the place it came from. A brand where a procedure is known as the Kirkwood receiving order gets candidates offered to it unprompted, because operators can see what recognition looks like. It works partly because the goodwill is already there: in Franchise Business Review's survey of 26,000 franchisees across 330 brands, 86% would recommend their franchise to others and 82% say they enjoy operating their business. Naming someone inside a network like that is a reward, not an exposure.

The part of the job that follows you

Then the coach's own credit, which people are reluctant to raise. Ask for it plainly: your name on the harvest note, not on the standard. Claiming the invention is fatal — do it once and the network stops showing you anything — but recording who found and verified a mechanism is accurate, and it is the only durable evidence the role produced something.

Consider what a field career otherwise accumulates. Visit counts do not travel, and nobody in an interview has been impressed by a completion rate. Five adopted standards, each naming the operator who invented it and the coach who spotted the pattern, is a portfolio — roughly the difference between a field consultant and the person who ends up running field operations. It pays inside the role too: what a new owner needs first is the network's operating knowledge, not the manual's — much of what good support in a first quarter consists of.

None of this needs a programme or permission. It needs you to notice the second time you see something and write down who did it first — the least discussed reason to build a week around movement rather than the map, because franchise field visit routing that repeats the same rota shows you the same things.

Headquarters runs the other half of this job: harvesting what operators already know.