How to Write Standard Operating Procedures for a Small Law Firm

Try this at your own firm. Ask the attorney, the paralegal, and whoever answers the phone how a new matter gets opened. Don't let them confer.

If the answers match, you're ahead of most small firms. If they don't, you've found the problem, and it's more common than anyone likes to admit.

Most small firms run on habit. Somebody learned a way of doing things, taught it to the next person by showing them once, and the process has been drifting ever since. It works until that person goes on vacation, or gets sick, or leaves. Then a task that used to take ten minutes becomes a scavenger hunt.

Standard operating procedures, usually called SOPs, are the fix. The word sounds corporate. The reality is a short written document that says how a task gets done.

Start with what hurts, not what's complete.

The mistake is trying to document the entire firm at once. That's how SOP projects die in week two. Instead, start with the processes that currently cause trouble. A few good candidates:

  • Opening and closing a matter

  • Client intake and conflict checks

  • Deadline and calendar entry

  • Billing and invoicing

  • Handling incoming mail and e-filing notices

  • Onboarding a new employee

Pick one. Just one. Write it. Then pick the next.

Write it while someone does the task.

The cleanest SOPs come from watching, not remembering. Sit next to the person who does the task and write down what they actually do, step by step. People forget half of what they do on autopilot, and a document written from memory misses it.

Screenshots help a lot. So does a short screen recording for anything that lives in your software. A written step like "enter the matter in the system" means nothing to a new hire. A screenshot with the right field circled means everything.

Keep each procedure small.

A good SOP fits on one or two pages. If yours runs longer, it's probably two procedures pretending to be one. Break it up.

A simple structure works for almost everything:

  1. What this procedure is for, in one sentence

  2. Who is responsible for it

  3. When it happens

  4. The steps, numbered, in order

  5. What to do if something goes wrong

That last one is the part people skip, and it's the part that saves you. "If the conflict check turns up a hit, stop and notify the managing attorney before sending anything to the client." One sentence like that prevents a very bad week.

Use plain language.

Write the way you'd explain it to a smart person who started yesterday. No legalese, no shorthand only you understand. If a step needs a judgment call, say what the judgment depends on.

Make it easy to find.

An SOP nobody can locate is just a file. Put them all in one shared folder with clear names, and tell your team where it is. Link to them from the places people already work. If someone has to ask where the intake checklist lives, you've added friction instead of removing it.

Test it on someone who didn't write it.

Hand the draft to a person who doesn't know the task and ask them to follow it. Watch where they get stuck. Every place they hesitate is a gap in the document. Fix it, and test again if the gap was big.

Review them on a schedule.

Your software changes, your rules change, your preferences change. A procedure that was accurate two years ago might now point people to a button that no longer exists. Pick a date once or twice a year and skim through. Update what's out of date, delete what you no longer do.

One caution on compliance

SOPs are also useful for areas with real ethical weight, like trust accounting and confidentiality. If you write procedures for these, check them against your state's rules of professional conduct. A written process that's wrong is worse than a loose process that's right.

The payoff isn't paperwork. It's that the firm stops depending on one person's memory. New hires get up to speed faster, mistakes drop, and you stop being the answer to every question.

If your firm is ready to get its processes out of people's heads and onto paper, that's a large part of what we do. Take a look at our law firm support page to see how we approach intake, workflow, and administrative systems.

Moore Consulting Services helps small and boutique law firms nationwide build practical administrative systems.

Note: This post shares general operational information. Professional conduct rules differ by state, so check your jurisdiction's requirements before adopting any procedure that touches client funds, confidentiality, or supervision.

Next
Next

How to Build Your Law School List Without Guessing