The Franchise Operations Manual: How to Document Processes

In an established business, many decisions are made without written instructions: the manager remembers the sequence of steps, and staff ask an experienced colleague. When the business model is passed on to franchisees, this habit becomes a risk. An operations manual should enable a partner to replicate the operation without the founder’s constant involvement. For a resilient franchise network, what matters is not the length of the document, but whether people can find an answer and carry out a specific task correctly.

1. Build the manual around day-to-day tasks

Start not with a contents page for a future book, but with a list of recurring situations at your own outlet. Trace the journey of an order, product or service: from the initial request through to completion of service and closing the shift. List periodic tasks separately, such as stocktaking, equipment maintenance and reconciling records.

Define where each process begins and ends. For example, ‘receiving a delivery’ starts when the goods arrive and ends when receipt is confirmed or discrepancies are recorded. ‘Working with suppliers’ is too broad a topic for a single procedure: it covers several tasks with different people responsible for them.

Create a working table covering:

• the process name and the event that triggers it;
• the person carrying it out and the staff member responsible for resolving disputed issues;
• the documents, equipment and access permissions required;
• the expected outcome;
• the consequences of an error.

Document processes first where mistakes affect safety, money or the outcome promised to the customer. There is little point starting with detailed stationery storage procedures if staff take payments or handle order cancellations inconsistently.

Organise materials by role. A shift supervisor needs a sequence of tasks for the shift; a manager needs decision-making procedures; and the outlet owner needs a list of management responsibilities. Everyone can use the same knowledge base, but the route to the relevant instructions should reflect each person’s work.

2. Use a consistent format for procedures

A good procedure answers ‘what should I do now?’, rather than simply explaining the brand’s values. Use the same structure for each process: purpose, conditions for starting, person responsible, sequence of actions, outcome and exceptions.

Describe observable actions. ‘Prepare the workstation to a high standard’ leaves plenty of room for interpretation. Instead, list what to check, where to find the acceptable limits and what to do if something falls outside them. If a step involves software, specify the relevant section of the interface and include an up-to-date screenshot without real customer data.

For example, a delivery receipt procedure might follow this sequence:

1. Find the order associated with the delivery.
2. Compare the items actually received with the accompanying documents.
3. Check the condition of the packaging and the acceptance requirements for the goods.
4. Record any discrepancies using the prescribed method.
5. Refer disputed issues to an authorised member of staff.
6. Record the quantity accepted in the stock management system.

This is only a framework: the specific checks depend on the goods and the mandatory requirements that apply to them. A general procedure must not replace technical documentation or safety requirements.

Every process should have a verifiable outcome. For receiving a delivery, this is not ‘the goods have been received correctly’, but a quantity recorded in the system and any discrepancies documented. It is also useful to specify which records confirm completion of the task and where staff should save them.

3. Describe exceptions and the limits of independent decision-making

The standard scenario rarely generates the most questions. The main burden on the franchisor arises when staff encounter a situation the manual does not cover: the software is unavailable, goods are damaged or the required specialist is not on site.

For each critical process, add a short ‘If something goes wrong’ section. Set out:

• when work can continue using a fallback procedure;
• when the operation must stop;
• whom to notify about the problem;
• what information to provide;
• who has authority to approve further action.

Do not stop at ‘contact the manager’. Specify the role of the person providing cover and what to do if no response is received. A fallback procedure must never permit breaches of mandatory requirements simply to speed up service.

Distinguish mandatory rules from recommendations. For example, the method used to record a transaction may be compulsory, while a convenient sequence for preparing non-critical materials may be a recommendation. This helps partners understand where consistency is required and where they have a choice. Do not turn the founder’s personal preferences into obligations for the whole network without a clear operational reason.

4. Test usability and clarify contractual status

Before handing over the manual, give an individual procedure to a member of staff who was not involved in writing it. Ask them to complete the task and note any points where they had to guess or ask colleagues. Test potentially hazardous operations under the supervision of a qualified specialist, without putting people or property at risk.

Observe the task being carried out rather than explaining the document verbally. Every necessary prompt reveals a gap. After the test, revise the text: add a condition, split a lengthy step or remove an ambiguous word. This test assesses the clarity of the procedure, not the commercial viability of the business model as a whole.

In Russia, commercial concession agreements—the legal framework commonly used for franchising—are specifically regulated by Chapter 54 of the Civil Code of the Russian Federation. Article 1031 requires the rights holder to supply the necessary technical and commercial documentation, provide information, and instruct the user and their employees. An operations manual helps fulfil this obligation, but does not replace the agreement itself.

Article 1032 of the Civil Code requires the user to follow the rights holder’s instructions and directions intended to ensure consistency in the nature, methods and conditions of use of the bundle of exclusive rights. Work with a lawyer to determine which sections of the manual are binding, how they relate to the agreement and which matters require a separate contractual provision. Do not attempt to introduce new fees or penalties through an operational procedure.

Practical takeaway: start with one frequently performed process. Describe who carries it out, the actions involved, the outcome and the exceptions, then test the document without verbal prompts. This format will provide the foundation for a manual that partners can genuinely use.