Law firm operations manual: how to write one people read

A law firm operations manual is the written record of how the firm runs: who does what, in which system, by when, and who owns each process. It usually covers structure and roles, client intake and onboarding, matter handling and supervision, finance, IT, data protection and risk. To be used, each section needs a named owner, a review date and short task-level pages.

Many firms have a manual, often called an office manual or procedures manual, written for an accreditation or an audit and then left to go out of date. This guide covers what to put in one, a template for each section that keeps it readable, and the ownership model that keeps it current. It is part of our guide to legal operations in a law firm. Nothing here is regulatory advice; your COLP should confirm what your firm's policies must contain.

Why does a law firm need an operations manual?

Three reasons, in rising order of importance.

• Regulation. The SRA Code of Conduct for Firms requires effective governance structures, arrangements, systems and controls (2.1), and an effective system for supervising clients' matters (4.4). It does not require a manual by name, but a firm has to be able to show its systems exist, and writing them down is the usual way.
• Continuity. When the practice manager is off sick or a partner retires, the knowledge that lived in their head leaves with them.
• Consistency. Two fee-earners handling the same matter type in two different ways means two different client experiences and two sets of risks.

What should a law firm operations manual include?

A practical table of contents for a small or mid-sized UK firm:

• 1. Structure and roles. The firm's legal structure, managers, the COLP, COFA, MLCO and MLRO and their deputies, and who supervises whom. See law firm structure in the UK.
• 2. The front door. How calls, emails and web enquiries are answered, in and out of hours, who owns call backs and within what time. See the law firm client intake process.
• 3. Onboarding. Conflict checks, ID and AML checks, client care letters and engagement terms. See conflict checks at intake.
• 4. Matter handling. File opening, key dates, templates, supervision and review, file closure and archiving.
• 5. Client communication. Update standards, response times, complaints handling.
• 6. Finance. Time recording, billing, client account procedures, reconciliations and sign-off. The SRA Accounts Rules require a client account reconciliation at least every five weeks, signed off by the COFA or a manager.
• 7. People. Recruitment, induction, training, leave and cover.
• 8. Technology and data. Systems, access, passwords policy, data protection, retention, breach reporting.
• 9. Risk and compliance. Risk register, breach reporting to the SRA, AML policies, business continuity.
• 10. Suppliers. Who provides what, contract dates, who manages each relationship.

How should each section of the manual be written?

The reason manuals go unread is that they are written as policy, when people need them as instructions. Use one short page per task, on this template:

• Title as a task. "Returning a missed call", not "Telephone policy".
• Owner. One named person, not a department.
• Last reviewed and next review date.
• When this applies. One sentence.
• Steps. Numbered, one action per step, naming the system and the person.
• Time limit. How quickly it must happen.
• What good looks like. One example.
• If it goes wrong. Who to tell.

A page that does not fit on one screen is probably two tasks. Link to the firm's formal policies from the task page rather than repeating them.

A worked example: one page from the manual

This page is invented for illustration, for a hypothetical firm.

• Task: Returning a missed call from an unknown number.
• Owner: Practice manager. Reviewed: September. Next review: March.
• When: Any call to the main line that was not answered, during or outside office hours.
• Step 1: Reception checks the missed-call log at 9am, 1pm and 4pm.
• Step 2: Every unknown number is called back within one working hour of the check.
• Step 3: If a new enquiry, record it in the intake log with the caller's matter type.
• Step 4: Pass to the duty fee-earner for that department, who calls back the same day.
• Time limit: First call back within one working hour.
• If it goes wrong: Tell the practice manager, who reports misses in the weekly numbers.

That page is short, testable and has an owner. Anybody can check whether it happened. That is the standard every page should meet.

Who should own the operations manual?

One person owns the manual as a whole, usually the operations or practice manager. Each page has its own owner, usually the person who does or supervises the task. The COLP should review sections that touch regulatory requirements, and the COFA the finance sections. The managing partner signs off the whole, and the partners should be seen to follow it.

How do you keep a law firm manual up to date?

This is the part most guides skip, and the part that decides whether the manual survives. From operations work outside law, three rules keep documentation alive:

• Change the page in the same week as the process. Any change to how something is done is not finished until its page is updated. Make that part of the change, not a follow-up.
• Review by date, not by memory. Every page carries a next review date. The owner of the manual runs a monthly list of pages past their date.
• Test a page each month. Pick one page at random and check whether what it says actually happened last week. If it did not, either the page or the practice is wrong. Fix whichever it is.

Where should the manual live?

Wherever staff already look. A searchable intranet page, a shared folder of short documents, or a knowledge base in the firm's existing system are all fine. A single long document is the hardest to keep current and the hardest to search. Whatever you choose, make sure there is one version, and that printed copies say they may be out of date.

Which processes should you write down first?

Not all at once. Start with the processes where an error costs most and happens silently. For most firms that is the front door and onboarding, then key dates and supervision, then finance. Our guide to law firm efficiency lists ten places to look, and law firm workflow automation covers which documented processes are then worth automating.

Writing the front door page often shows that nobody covers the line at lunch or after hours. Cam, our AI Engagement Coordinator, takes calls on the firm's line at any hour, says it is an AI, asks the firm's own qualifying questions, books the call back and sends the firm a summary. If your manual has a gap there, we are happy to talk.

How do you get staff to use the operations manual?

Documentation that nobody opens is a common problem outside law too, and the fixes carry over.

• Answer questions with a link. When someone asks how to do something, send the page rather than the answer. If there is no page, write it and then send it.
• Use it in induction. New starters work through the pages for their role in the first week. Their questions show which pages are unclear.
• Make partners visible users. If partners follow the documented process, others will. If they do not, the manual becomes optional.
• Keep it findable. One link, bookmarked on every machine, with search.
• Celebrate corrections. Anyone who spots a page that is wrong and says so has improved the firm.

Law firm operations manual checklist

Use this to audit an existing manual in an afternoon:

• Does every page have a named owner who still works here?
• Does every page have a review date that has not passed?
• Are the COLP, COFA, MLCO and MLRO named, with deputies?
• Is there a page for what happens to calls and enquiries outside office hours?
• Is there a page for who covers a fee-earner in court or on leave?
• Does the finance section match how reconciliations are actually done and signed off?
• Could a new starter find the answer to "how do I open a matter?" in under a minute?
• Has any page been tested against what actually happened in the last month?

Any "no" is a page to write or fix. Start with the ones where an error would be silent, because those are the ones nobody will report.

Is an operations manual the same as a Lexcel office manual?

Firms working towards the Law Society's Lexcel practice management accreditation often maintain an office manual for it. The approach in this guide is compatible: short task pages with owners and review dates can sit under whatever headings an accreditation asks for. Check the current Lexcel requirements with the Law Society directly, as they are updated from time to time.

How long does it take to write an operations manual?

Longer than people hope if it is written all at once, and not long at all if it is written a page at a time. A realistic approach for a small or mid-sized firm is two or three pages a week, starting with the front door and onboarding. Within a few months, the processes that matter most are covered, each by the person who knows them best. Writing a page usually takes under an hour. Agreeing what the process should be is what takes the time, and that conversation is worth having anyway.

What should the front door section say?

This is the section most manuals leave vague, and the one where vagueness costs the most. At minimum it should state who answers the main line at each hour of the working day, including lunch; what happens to calls outside office hours; who returns missed calls and within what time; which questions are asked of a new enquiry; and who a new enquiry is passed to, by practice area. If any line of that reads "reception" or "whoever is free", name a person instead.

Frequently asked questions

Is an office manual required by the SRA? The SRA does not require a manual by name. It requires effective governance, systems and controls and an effective supervision system. A written manual is the usual way to show those exist. Ask your COLP what your firm needs.

How long should a law firm operations manual be? As short as possible. One screen per task, with links to formal policies, is easier to use and keep current than a long document.

How often should the manual be reviewed? Each page should carry its own review date, commonly every six or twelve months, and be updated whenever the process it describes changes.

What is the difference between a policy and a procedure? A policy says what the firm requires and why. A procedure says who does what, in which system, by when. Staff use procedures day to day, so the manual should lead with them.

Can we use a template operations manual? A template can suggest headings. The content has to describe how your firm actually works, or it will not be followed and will not show that your systems exist.