FirmFooting / Briefs / Systems & SOPs
Systems & SOPs · Published Jul 5, 2026
Law Firm SOPs: Procedures a Day-One Paralegal Can Follow
There is one test for whether a firm procedure is any good, and it is brutal in its simplicity: could a paralegal who started this morning run it without asking anyone a question? Most law firm procedures fail that test, because they were never really written down, they just live in someone's head. Here is how to write ones that pass, plus a free pack to start.
Jareer Ali·
Systems & field notes·
15 min read
A law firm SOP is a short written document for one recurring task: its trigger, its owner, the numbered steps, the exceptions, and a last-reviewed date. The test of a good one is whether a new hire could follow it without help. Most firm procedures fail that test because they live in someone's head, not on paper. Writing them well moves knowledge from a person into the firm, which is what protects the firm when that person is out.
Key takeaways
- The only test that matters: could a paralegal who started this morning run it without asking? If not, it is not really written down.
- An SOP has a fixed anatomy: title, purpose, trigger, owner, numbered steps, exceptions, links, last-reviewed date. Two pages, not twenty.
- SOPs fail for four reasons: too long, written by the wrong person, aspirational instead of actual, or never updated. All four are avoidable.
- Documentation is not busywork. Administrative and client-relations errors are over a third of malpractice claims, and the ABA calls them uniquely within a firm's control (2016-2019 Profile, via WSBA).
- Have the person who does the task write it. Authorship makes it accurate and makes them a champion instead of a subject.
- Write by watching the work happen, then test the draft on someone who does not know the task. The step they get stuck on is the one you assumed.
Most firms think they have procedures. What they have is Denise. The intake gets done a certain way because Denise does it a certain way, and if you asked her to write down how, she would produce half a page that skips the four things she does automatically without noticing she does them. Those four unnoticed things are the entire procedure. They are also what walks out the door the day Denise takes a vacation, and what a new hire spends three frustrating weeks reconstructing by trial and error. An SOP is just the act of getting those four things out of Denise's head and onto a page before you need them there.
This guide is about writing SOPs that actually work, which is a narrower and more useful topic than writing SOPs in general. Anyone can produce a document nobody follows. The goal here is procedures a day-one paralegal can run, because that is the only kind that protects the firm.
The day-one test
Before anything else, adopt the test, because it will tell you the truth about every procedure you write. The test is this: hand the SOP to a competent person who has never done this specific task, and ask them to complete it using only the document. Do not help. Do not clarify. Watch where they get stuck.
Every place they hesitate, ask a question, or guess is a defect in the SOP, not in them. It marks a step the author knew so well they forgot to write it. "Open the case in Docketwise" assumes they know which field holds the deadline, that they should check the notice date against it, that a certain status means something specific. The expert does all of this without conscious thought, which is exactly why the expert is the worst person to judge whether the SOP is complete. The newcomer is the only reliable instrument, because they cannot fill gaps with knowledge they do not have.
Why SOPs are risk control, not bureaucracy
Lawyers are rightly allergic to process for its own sake, so let me make the risk case rather than the tidiness case, because the risk case is the real one.
A firm without written procedures is a firm whose operations live in individual memories, and individual memories have three failure modes that no amount of talent overcomes: they leave on vacation, they leave the firm, and they get overloaded and drop a step. The claims data points straight at this. Administrative and client-relations errors together make up over a third of malpractice claims, and the ABA describes them as uniquely within a firm's control (2016-2019 Profile, via WSBA). Uniquely within your control is the operative phrase: these are not errors of legal judgment that require years of expertise to reduce. They are errors of execution, and execution is exactly what an SOP standardizes.
There is a sharper version of the point. Recall that as calendaring software spread, administrative errors fell, but procrastination and failure to react to a calendar actually rose, because a tool stores a date but does not make anyone act. TLIE's line, that a good system only avoids claims if it is used properly, is really a statement about procedure. The reminder fired; what was missing was a written, owned answer to "and then what happens." That answer is an SOP. This is the same reason the seventh control of a complete deadline system is a written procedure, covered in the pillar on law firm deadline management.
The anatomy of a followable SOP
A good SOP has a fixed skeleton. Use the same one every time, because consistency is itself a feature: once your team knows the shape, they can find what they need in any procedure without reading it top to bottom.
| Part | What it is, and why it earns its place |
|---|---|
| Title | What the procedure is, in plain words. "How a new USCIS notice becomes a tracked deadline," not "Notice Intake Protocol v3." |
| Purpose | One line on why this exists. It stops the procedure from being followed blindly when reality does not match. |
| Trigger | The exact event that starts it. "A notice arrives from a court or agency." Without a trigger, an SOP is a document nobody knows when to open. |
| Owner | The named role responsible. Not a person's name, a role, so it survives turnover. |
| Steps | Numbered, in order, one action each, in plain language. The heart of it. If a step has a sub-decision, make it explicit. |
| Exceptions | The real edge cases and how to handle them. "If the notice has no date, do X." Undocumented exceptions are where procedures break. |
| Links | The actual tools, templates, and screens used. A step that says "enter it in the system" should link to the system. |
| Last reviewed | A date. An SOP with no review date is a document of unknown reliability, and people rightly stop trusting it. |
Two of these do more work than their size suggests. The trigger is what connects a procedure to real life; a firm full of SOPs nobody knows when to use is no better off than a firm with none. And the exceptions section is where expert knowledge actually lives, because the happy path is usually obvious and the edge cases are what separate someone who knows the task from someone who does not. Spend your effort there.
The free Footing Assessment scores your deadline, intake, and client-communication systems in three minutes, and names the first crack to fix.
Take the Footing AssessmentThe four ways SOPs fail
Almost every useless SOP fails for one of four reasons. Name them, and you can avoid all four deliberately.
| Failure | What it looks like | The fix |
|---|---|---|
| Too long | Twenty pages nobody opens; the procedure is buried in prose | Two pages, numbered steps, ruthless cutting. One task per SOP |
| Wrong author | Written by a manager who does not do the task; describes an idealized version | The person who does the task writes it, in their words |
| Aspirational, not actual | Describes how work should be done, not how it is done; nobody follows it | Document the real process first; improve it as a separate step |
| Never updated | Written once, drifts out of date, quietly abandoned | A last-reviewed date and a scheduled review owner |
The most insidious is aspirational-not-actual, because it feels like the responsible thing to do. You sit down to write the intake SOP and, since you are writing it anyway, you document the intake process as it ought to be, with the extra check and the tidy handoff nobody actually does. Now the SOP describes a fiction, the team knows it describes a fiction, and they ignore it, along with any future SOP by association. Document reality first. You can improve the process next week, and when you do, update the SOP to match. An accurate description of a flawed process beats an aspirational description of a perfect one every time, because only the accurate one gets followed.
How to write one in an afternoon
Writing an SOP is smaller than it sounds if you write it by observing rather than imagining. The method is watch, capture, test.
- Watch the task get done, once, start to finish. The person who owns it does it normally while you write down every action, including the ones they do without mentioning. Ask "and then what" at every pause.
- Capture each step as one plain action. Number them. Resist combining; "check and enter and confirm" is three steps, and the newcomer needs all three.
- Mark the decisions. Wherever the task branches, write the condition explicitly. "If the notice was mailed, add three days" is the kind of thing experts do silently and newcomers cannot guess.
- List the exceptions you saw or know. Ask the owner "what makes this go weird" and write down every answer. This is the highest-value five minutes.
- Test it on someone who does not know the task. Hand over the draft, watch them run it, and every stumble marks a step to fix. Revise until they can complete it clean.
An afternoon of watch-capture-test produces a better SOP than a week of writing from memory, because memory omits exactly the automatic steps a newcomer most needs. And crucially, the person who owns the task should hold the pen, for the same reason it matters in docketing: authorship makes the document accurate, and it makes the owner a champion of the system rather than someone it was done to. The argument for that framing is in why your paralegal's memory is not a docketing system.
Keeping them alive
A written SOP is not a monument, it is a living document, and the difference decides whether it is worth anything a year from now. Three habits keep a library of procedures alive.
- Give each SOP a review owner and a review date. Someone is responsible for confirming it still matches reality, on a schedule. An unowned SOP decays into fiction the moment the process changes.
- Update on change, not just on schedule. When a tool changes or a step changes, the SOP updates that day, as part of making the change. An SOP that lags the process is worse than none, because it actively misleads.
- Keep them where the work happens. A procedure filed in a drive nobody opens is a procedure nobody follows. Link each SOP from the tool or the task it governs, so it is one click away at the moment of need. Where all of them live together is the operations manual, covered in the modern operations manual guide.
Do this and your firm's knowledge stops being a collection of individual memories and becomes an asset the firm owns, one that survives vacations, resignations, and busy weeks. That is the entire point of the exercise: not tidiness, but resilience.
Where to go next
- The Law Firm Operations Manual: Free Modern Template
Where all your SOPs live together as one living hub.
- Your Paralegal's Memory Is Not a Docketing System
Why the person who does the task should author the procedure.
- The Law Firm Deadline System: The Complete Guide
Where the written procedure is the seventh of seven controls.
- The Escalation Ladder: 7/3/1-Day Alarms That Reach a Second Human
An example task worth writing an SOP for.
- Billing and AR Task Cadence: Follow Up Without Awkwardness live
Firms let receivables age because chasing clients for money feels awkward. A follow-up cadence.
A diagnosis, not a pitch
See where your firm would slip first.
Take the free Footing Assessment for a read on where your systems have no second observer, or book the thirty-minute Risk Audit. One page, inside 24 hours, whether you hire us or not.
Frequently asked questions
What is a law firm SOP?
A law firm SOP, or standard operating procedure, is a short written document that describes exactly how one recurring task is done: what triggers it, who owns it, the steps in order, the exceptions, and when it was last reviewed. It exists so the task is performed the same way every time regardless of who does it, and so the knowledge lives in the firm rather than in one person's head.
How do you write an SOP a new paralegal can follow?
Write it by watching the task actually get done, capture each concrete step in plain language, name the owner and the trigger, list the real exceptions, and then test it by having someone who does not know the task try to follow it. If they can complete it without asking a question, it passes. If they get stuck, the gap they hit is the step you assumed and did not write down.
What should a law firm SOP include?
A title, a one-line purpose, the trigger that starts the procedure, the named owner, the numbered steps in the order they happen, the known exceptions and how to handle them, any links to the tools or templates used, and a last-reviewed date. Two pages is usually enough; longer than that and people stop reading it.
Why do most law firm SOPs fail?
Usually for one of four reasons: they are too long to read, they were written by someone who does not actually do the task so they describe an idealized version, they describe how the work should be done rather than how it is done, or they were written once and never updated so they no longer match reality. Each failure is avoidable, and the fix is to have the person who does the task write it and to review it on a schedule.
- ABA Standing Committee on Lawyers' Professional Liability, Profile of Legal Malpractice Claims (2016-2019), on administrative and client-relations errors. americanbar.org
- Risk Management by the Numbers, Washington State Bar Association. nwsidebar.wsba.org
- Scheduling errors and legal malpractice claims, Texas Lawyers' Insurance Exchange. tlie.org