---
title: "Invariants and local choices: the only two lists a franchise standard needs"
description: "A franchise standard needs two lists: what never varies and what each site decides. The damage comes from the third list nobody admits to writing."
date: "2026-09-04"
updated: "2026-09-16"
topic: "Franchise operations"
canonical_url: "https://rolstonpaul.com/writing/invariants-and-local-choices-the-two-lists-a-standard-needs"
author: "Rolston Paul"
reading_time: "8 min read"
---

# Invariants and local choices: the only two lists a franchise standard needs

Author: Rolston Paul. Rolston Paul is an Operations Head based in New Delhi, India, focused on medical tourism and aesthetic medicine operations, writing about the clinical governance, patient coordination and operating standards India needs to earn international trust.
Published: 2026-09-04
Updated: 2026-09-16
Canonical: https://rolstonpaul.com/writing/invariants-and-local-choices-the-two-lists-a-standard-needs
Topic guide: https://rolstonpaul.com/topics/franchise-operations

A franchise standard needs two lists: what never varies and what each site decides. The damage comes from the third list nobody admits to writing.

A franchise standard needs two lists and nothing else. The first is invariants: the outcomes every site owes the customer, which hold in every country, on every bad day, at every site including the strongest one. The second is local choices: everything about the route, meaning staffing mix, sequencing, suppliers, room layout, the language the conversation happens in, the hours the doors are open. The sorting test is one question. If a difference changes what the customer was promised, it belongs on the invariant list. If it only changes how the promise was delivered, the site decides, and you write that down too.

Most networks already have both lists in some form. They also have a third, and that is the one doing the damage.

For an aesthetic medical travel service in India, I would place honest outcome communication and confirmed aftercare responsibility on the invariant list. Language, appointment timing and travel coordination can vary. Clinical plans must still be individual. The Operations Head's task is to protect those distinctions so that a consistent service never becomes a promise of identical surgical results.

## The third list is the one nobody admits to writing

Open any operating manual and read the verbs. A small number of clauses say must. A smaller number say the site may choose. The rest say should, or recommended, or wherever practical, or expected, or best practice.

An ambiguous rule is an unresolved decision. I would place it in a separate register with the person authorised to settle it and the evidence needed. Do not label it flexible merely because the manual fails to say who decides.

What follows is predictable. Every site reads the middle privately, guided by temperament and pressure. A conscientious manager treats should as must and slows down. A stretched manager treats should as optional and moves on. Both believe they are compliant, and neither is wrong, because the document never decided.

Then a complaint arrives and head office discovers it had an opinion after all. It enforces a should. The site that ignored that clause for two years is now in trouble for behaviour the manual permitted. That single event costs more than almost anything else a franchisor does, because afterwards the network reads the document as a mood rather than a rule.

## What functioning networks already do

I use the two-list model as a practical design method: protect the commitments the network must keep and state where local teams can choose their approach.

For each proposed local adaptation, ask whether it changes the patient promise, clinical requirements or the evidence the network needs. If it does, the relevant owner must review it. If it does not, explain the freedom clearly enough for a site to use.

A local improvement also needs a route back into the common standard. I would record the trial, the result and the decision about wider use rather than depend on an informal conversation.

That is the failure mode of the local list. You permit variation, the variation produces something better, and the discovery dies in the site that made it. If you are going to free the method, build a route home for what the method finds. One quarterly page where each site records what it changed and what happened is enough to start. Reading it is the hard part.

## How do you decide what is an invariant?

Four questions, and a rule has to pass all four. On Monday, take the ten clauses your network argues about most and run them through it.

Does a difference change the promise or only the route? If customers at two sites would describe what they were promised differently, that is an invariant. If they would describe the same promise arriving by different means, it belongs to the site.

Would you enforce it against your strongest site, in its worst week? This is the honest question. Every network has a site that carries the numbers and knows it. If you would quietly let that site off, the rule is not an invariant anywhere.

Does following it leave evidence somebody can check without a visit? An invariant that produces no artefact cannot be held, only asserted. If the only proof is a person saying yes, you have written an aspiration.

Can every site do it today, with the staff and equipment it actually has? If two sites physically cannot comply, you have three options and only three. Fund them so they can. Move the rule to the local list. Or accept that you are running a network with known non-compliance and say that out loud. What you must not do is leave the rule written and unmet, because that teaches every site that written rules are negotiable.

Anything failing a question moves to the local list or gets rewritten until it passes. Nothing stays in the middle.

> A rule you would not enforce against your strongest site is not a standard. It is an opinion with a document number.

## Local choices should be published, not merely tolerated

The second list usually gets treated as a residue, whatever the manual did not mention. That is a mistake, because silence is read differently by different people. A cautious franchisee reads an unmentioned thing as forbidden and asks permission for a decision that was always theirs. A confident one reads it as licence and changes something you would have refused.

So write the local list on purpose. Name the decisions each site owns outright. Name the ones it owns provided it tells you. Name the ones that need approval first. Three columns, and every operational decision your network makes should be findable in one of them.

That list is also what makes the invariants credible. A short list of things that never vary reads as serious precisely because it sits beside a long list of things the site is trusted to decide. A network that fixes everything is not signalling high standards. It is signalling that it cannot tell which of its rules matter.

## The brand does not carry the quality by itself

Expansion and quality need separate evidence. More sites or more patients can demonstrate reach; they do not by themselves establish the quality of care. I would review clinical governance and service capability alongside the expansion plan.

Which puts the weight back on the design. If the format does not deliver quality on its own, the two lists are what deliver it, and how you run them matters as much as where the line sits.

The governance process should allow local clinicians and operating teams to challenge a rule with evidence. Record the decision and its reasons. A standard is easier to maintain when people know how to improve it without quietly departing from it.

Read it as an operating instruction. The line between the two lists is a negotiation you hold every quarter, not a wall you build once.

## What is yours to decide, and what is not

You do not control how a franchisee reads a document you are not in the room for. You do not control the local labour market, the regulator who changed a rule in one country and not the others, the landlord, or whether a good site manager stays. You do not control the pressure that makes a busy team skip a step.

You control which promises are invariant and how few of them there are. You control whether each one leaves evidence without anybody being asked. You control whether the local list is written down or left to inference. You control what you do the first time your strongest site breaks an invariant, because the network learns more from that decision than from the manual. And you control whether the third list exists at all.

Delete the middle. Every clause then becomes either a rule you will enforce or a decision you have handed over, and both of those are honest. A network can run on either. It cannot run on a document that has not decided.

## Questions people ask

### What is the difference between franchise brand standards and local adaptation?

Brand standards are the outcomes every site owes the customer, and they do not vary anywhere. Local adaptation covers the route a site takes to get there: staffing mix, sequencing, suppliers, room layout, language, opening hours. The test is whether a difference changes what was promised or only how it was delivered. Promise changes are brand standards. Route changes belong to the site.

### How do you decide which franchise standards can be adapted locally?

Ask four questions of every rule. Does a difference change the promise or only the route. Would you enforce it against your strongest site in its worst week. Does following it leave evidence somebody can check without a visit. Can every site do it today with the staff and equipment it actually has. A rule that fails any of the four belongs on the local list.

### Why do franchise brand standards fail across multiple countries?

Usually because the document carries a third pile. Alongside the rules that never vary and the decisions each site makes freely sits a large set of clauses that are recommended, expected or encouraged. Nobody enforces those and nobody releases them, so each site quietly decides what they mean. Drift starts in that middle group, not in the rules people argue about openly.

---

Contact: info@rolstonpaul.com