The franchise operations manual: how to write procedures people can use

An established business often runs on knowledge that nobody has written down. The manager spots a problem at a glance, and staff know who to call. But when expanding into a franchise network, that collective memory is not enough. An operations manual should turn experience into specific steps that franchisees and their teams can find and follow correctly. It is not a company encyclopaedia, but a practical tool for everyday decisions.

1. Start with a list of situations, not a table of contents

A common first mistake is to open a blank document and write down the brand’s history, values and organisational chart. These may have their place, but they do not tell a member of staff how to start a shift or what to do if the till stops working.

First, work through a typical day at your premises. Record the tasks carried out before opening, while serving customers, during shift handovers and after closing. Add less frequent situations, such as receiving a delivery or dealing with equipment failure. For each one, identify who handles it and what the outcome should be.

Choose procedures for the first version using three criteria:

• Frequency: how often the task is repeated.
• Impact of an error: what happens if someone carries it out incorrectly.
• Reliance on experience: whether only a few people currently know the correct procedure.

Start with tasks where these criteria overlap. Documenting rarely needed administrative details can wait; clarifying the daily closing procedure cannot.

2. Use the same structure for every procedure

A consistent structure makes information easier to find and update. Readers should not have to work out afresh where to find responsibilities, required resources or troubleshooting advice every time they open a document. Each procedure should cover one complete task.

For example, use this structure:

• When to use the procedure: the triggering event or specific point in time.
• Who carries it out: the job role, not the name of the current employee.
• What is needed: equipment, access permissions and information required before starting.
• What to do: numbered steps in the order they are actually performed.
• How to confirm completion: a verifiable outcome and any record required.
• What to do if something differs from the expected situation: a safe next step and the role to contact.

Instead of writing ‘check that the work area is ready’, specify which items to check and what counts as an acceptable condition. Avoid vague terms such as ‘regularly’ if you need a check before every opening.

A photograph can show the correct equipment layout more effectively than a paragraph of text. However, it must match the equipment actually used. Where premises have different layouts or formats, clearly identify which one the procedure applies to.

3. Capture decision-making and the limits of each procedure

A simple list of steps works only when everything goes as expected. Valuable know-how often lies in recognising when the standard procedure is no longer enough. Add decision points to every important procedure.

For receiving a delivery, for example, it is not enough to write ‘accept the goods’. Explain how to check them against the order, record discrepancies and deal with visible damage. Distinguish between what staff may resolve themselves and when they must involve the person responsible. The specific rules must reflect the product range and the contractual terms of supply.

Do not create blanket instructions such as ‘always keep the business running’. Where health or safety is at risk, stopping work may be the correct outcome. The manual should not replace manufacturers’ technical instructions, mandatory training or statutory safety requirements.

It is also useful to explain briefly why a critical step matters. Staff are more likely to recognise an unusual situation if they understand the problem a rule is intended to prevent.

4. Separate working instructions from legal obligations

The Czech Republic has no specific law governing franchising and no mandatory government template for an operations manual. Franchise agreements are generally concluded as innominate contracts — contracts not governed as a specific contract type — under Section 1746(2) of Act No. 89/2012 Coll., the Civil Code. There is no special registration regime for franchise agreements.

Whether the manual is binding on the franchisee therefore depends on the contractual arrangements. Simply labelling a document ‘binding’ does not establish whether it has been properly incorporated into the contractual relationship. When drafting it, distinguish between mandatory operating standards, recommended working tools and illustrative examples.

The content must comply with generally applicable legislation. Depending on the nature of the business, this may include consumer protection, employment and hygiene requirements, or personal data protection rules. Instructions affecting the franchisee’s pricing or commercial decisions also require assessment under competition law. A manual is not a way to bypass restrictions that apply to the agreement itself.

5. Test clarity through individual tasks

Give the completed procedure to someone who does not know the task by heart but has the necessary qualifications. Ask them first to find the right document and then to carry out the task by following it. The author should not provide prompts along the way: every necessary prompt reveals something that needs to be added.

Record unclear terms, missing resources and steps in the wrong order. For higher-risk tasks, test under qualified supervision or use a simulation. Assign each procedure an owner, a version number and an effective date. Store old versions separately so the team cannot mistake them for current instructions.

Practical takeaway: Choose a few of the most important tasks, document them using a consistent structure and test whether the instructions work in practice. A shorter manual that people can genuinely work from is a better foundation than a lengthy document full of general statements.