A network can look disciplined on paper and still underperform in practice. The usual cause is not a lack of process. It is that leaders have treated standard operating procedures versus flexibility as a choice between two opposing positions: enforce the system or trust local judgement. High-performing franchise and multi-site businesses do neither. They define where consistency is non-negotiable, then give capable people clear authority to respond to the conditions in front of them.

For franchise leaders, this is a commercial issue, not a philosophical one. Too much variation creates customer inconsistency, margin leakage, compliance exposure and an impossible workload for field teams. Too much prescription slows decisions, discourages ownership and causes teams to follow a process that no longer fits the operating reality. The objective is controlled adaptability.

Why the tension exists in franchise systems

Standard operating procedures exist for good reasons. A franchise brand depends on repeatability. Customers should receive a reliable product, service and experience whether they visit one location or another. Franchise partners need clarity about what good execution looks like. Head office needs visibility over performance and confidence that legal, safety, brand and financial controls are being followed.

The difficulty is that locations are not identical. A regional site may face different labour availability, seasonal demand or customer behaviour from a metropolitan site. A mature multi-unit operator may have stronger local management capability than a first-time franchisee. Supply interruptions, landlord issues, local competitors and unexpected staffing gaps all require decisions that cannot wait for a revised manual.

When procedures do not account for this reality, people tend to respond in one of two unhelpful ways. Some bypass the system quietly, creating hidden variation and weak accountability. Others wait for permission, even when the correct decision is obvious. Both responses reduce the speed and quality of execution.

Standard operating procedures versus flexibility: set the boundaries

The practical answer is to separate the work that must be standardised from the work where local discretion can improve the result. This requires more precision than telling operators to use common sense. Common sense differs between people, and it is difficult to coach, measure or defend after the fact.

Start with the non-negotiables. These are the activities where inconsistency creates material risk to customers, the brand or the business. Food safety, workplace safety, privacy, cash handling, employment obligations, approved suppliers, core product specifications and brand-critical customer interactions will often sit in this category. The procedure should be clear, current and easy to access. The consequence of non-compliance should also be understood.

Then identify areas where outcomes matter more than a single prescribed method. Local area marketing, roster adjustments within labour targets, community partnerships, recovery actions for a dissatisfied customer, and the order in which a manager tackles daily priorities may allow greater flexibility. The leader is accountable for an agreed result, but can choose the most appropriate path.

There is a third category that is often missed: decisions that require escalation. These may include an unbudgeted spend above a set threshold, a proposed deviation from a product standard, a serious people matter, a potential reputational issue or a decision likely to affect other sites. Clear escalation points stop local initiative becoming unmanaged risk.

A useful operating principle is simple: standardise the risk, not every action. If the risk is low and the local team has the capability to make a sound decision, prescribe the outcome and guardrails rather than every step.

Build procedures that help people perform

Many SOPs fail because they are written as compliance documents rather than operating tools. They are long, difficult to find, out of date or disconnected from the way work actually happens at site level. No amount of enforcement fixes a procedure that is impractical during a busy service period.

Effective procedures make the required action clear at the point of use. They explain the purpose of the standard, define the critical steps, state who is responsible and show what to do when normal conditions do not apply. They also distinguish between a mandatory control and a recommended practice. If everything is labelled essential, nothing is.

Frontline input matters here. The people completing the work can identify ambiguous steps, duplicated checks and conditions that the original process did not anticipate. Involving them does not mean handing over control of the standard. It means testing whether the standard can be executed consistently in a real operating environment.

For example, a procedure for opening a site may contain twenty steps, but only five may be genuinely critical to safety, security, trading readiness and brand presentation. The remaining tasks may still be valuable, but they can be sequenced according to staffing levels and local conditions. That distinction gives managers room to lead without compromising the business.

Flexibility requires capability and evidence

Flexibility is not permission to improvise without discipline. It works when leaders have the commercial judgement, information and confidence to act within agreed boundaries. Where capability is uneven, broad discretion can magnify inconsistency rather than solve it.

This is why field coaching should focus on decision quality, not merely procedure adherence. A field manager can ask: What outcome were you trying to achieve? Which standard applied? What options did you consider? What information supported the decision? What happened next? These questions develop judgement while making accountability visible.

Data should guide the conversation. If one location uses a different approach to rostering, local marketing or stock management, assess whether it improves labour productivity, customer measures, sales, waste or team stability. A variation that produces a measurable benefit and remains within the operating guardrails may be worth testing elsewhere. A variation that simply feels easier should not become informal policy.

The distinction is particularly important in mature networks. Experienced operators often develop practical improvements before head office sees the need. Treating every variation as defiance loses valuable learning. Treating every local success as a new network standard creates noise. The leadership task is to test, validate and scale what works.

Create a disciplined path for exceptions

A business that expects no exceptions is usually a business that does not know where its exceptions are occurring. People will find workarounds when the standard conflicts with reality. The better approach is to make exceptions visible, time-bound and reviewable.

An exception process does not need to be bureaucratic. It should state who can approve a variation, the duration of approval, the measures that will be monitored and the point at which the original standard will be restored, amended or formally replaced. This protects the network from permanent drift while giving operators a practical route to respond to genuine local conditions.

Consider a site affected by a temporary supply disruption. The operator may need approval to use an alternate product or modify a customer offer. The decision should record the customer and brand implications, the financial effect and a review date. Once the disruption passes, leaders can assess whether the response was an appropriate short-term exception or whether it exposed a weakness in the existing supply process.

This discipline also improves trust. Franchisees and site managers are more likely to raise issues early when they know an exception will receive a commercial response rather than an automatic rejection. Head office gains better visibility and can make decisions based on patterns rather than anecdotes.

Review standards where work actually happens

Procedures should not be reviewed only after a serious failure. Regular review is part of performance management, particularly when the business changes its technology, product range, customer proposition, supplier arrangements or workforce model. A process that was sound two years ago may now create unnecessary friction or risk.

Use operational reviews to look for recurring questions, repeated workarounds, avoidable approval requests and performance gaps between sites. These signals often show that the standard is unclear, overly rigid or insufficiently supported by training. They can also reveal where a procedure is being ignored because leaders have not reinforced its commercial importance.

The strongest review forums bring together operational leaders, franchisees or operators, field teams and relevant functional specialists. The discussion should remain grounded in evidence: what is happening, what risk does it create, what result is required and what change will make execution more reliable? This is where confidential peer environments can be valuable. Leaders can pressure-test a difficult decision with people who understand the operational consequences, rather than relying on generic management advice.

Australian Franchise Alliance is built around that kind of practical leadership conversation: commercially grounded, confidential and focused on better judgement under pressure.

The measure is better execution

The right balance will differ by sector, network maturity and the capability of the people responsible for delivery. A highly regulated health or food business will need tighter controls than a service model with fewer safety-critical processes. A new network may require more direction while leaders build confidence. A mature network may benefit from greater local experimentation, provided its governance is clear.

What should remain constant is the standard of accountability. People need to know which requirements cannot move, where they have authority to act and when they must involve others. They also need leaders who will listen when the written process no longer reflects the operating reality.

A procedure is valuable when it makes excellent execution easier. Flexibility is valuable when it helps capable people protect that execution in changing conditions. Give both a clear place in the operating model, and the network is better placed to respond quickly without losing control.