What an operations manual actually needs to contain
Many small firms either have no written operations manual or possess a long document that no one consults. The useful version sits between those extremes. It captures the recurring ways of working that keep the firm consistent-how client work is accepted, how progress is tracked, how invoices are raised, how complaints are handled, and how knowledge is passed when someone is absent. It is not a policy library or a legal text; it is a practical reference that a competent person can follow without constant supervision.
The test of a good manual is simple: can a new or temporary team member perform the core processes correctly by reading it, and can an experienced person use it to check that nothing has been forgotten?
Selecting the processes worth documenting
Not every activity deserves a written procedure. Focus on the sequences that are performed regularly, that affect client experience or cash flow, and that create risk when done inconsistently. Typical candidates include enquiry handling, proposal preparation, project kick-off, progress reporting, invoice generation, complaint response, and the end-of-engagement close-out. Processes that are performed once a year or that vary widely with each instance can remain informal.
For each selected process, record the trigger that starts it, the sequence of steps, the person or role responsible at each step, the tools or templates used, and the definition of "done." Avoid narrative essays; numbered or bulleted steps are easier to follow under time pressure.
Writing for the person who was not in the room
The most common failure in operations manuals is that they are written for the author rather than for a reader who lacks the author's background knowledge. Assume the reader has general professional competence but no firm-specific memory. Name the exact location of templates, the exact fields that must be completed, and the exact person or role who must be notified. Vague instructions such as "update the system" or "inform the team" force the reader to guess.
Include the reasons for any non-obvious steps. When people understand why a check exists, they are less likely to skip it when under pressure.
Keeping the manual short enough to be used
A manual that runs to dozens of pages is rarely opened. Aim for a document that can be scanned in a few minutes and that points to more detailed templates or checklists only when needed. Store the detailed templates separately and link to them from the manual. This structure keeps the core document lean while still providing depth where it is required.
Version control matters. Each time a process is improved, update the manual and record the date of the change. Old versions should be archived rather than deleted so that the history of how the firm worked remains available if needed.
Making the manual part of daily work rather than a shelf document
A manual that is consulted only during induction will drift out of date. Build short references to it into existing routines. When a new client is onboarded, the relevant section of the manual is checked. When a complaint arrives, the complaint process page is opened. When someone is about to take leave, the handover section is used. These small habits keep the content current and signal that the manual is a working tool.
Encourage team members to note any step that proved unclear or missing. A simple feedback route-an email address or a shared comment log-turns the manual into a living document rather than a static one.
Starting with the highest-friction processes
An operations manual does not need to be complete before it is useful. Begin with the two or three processes that currently generate the most rework, delay or inconsistency. Document those thoroughly, put them into use, and expand from there. Each completed section reduces a known source of friction and demonstrates the value of the exercise to the rest of the team.
Over time the manual becomes the firm's operational memory. It reduces dependence on any single person's knowledge, shortens the time needed to bring new people up to speed, and provides a stable base from which processes can be improved rather than reinvented.