Jump to section
You know the SOP binder. It lives on a shelf near the printer, three inches thick, last updated when the office still faxed things. Nobody reads it. When a new hire asks how to open a file, someone walks over and shows them, again, for the fortieth time. The binder failed not because the ideas were wrong but because it was built to be filed, not followed.
A standard operating procedure is worth writing only if someone will actually use it under pressure, at 4:45 on a Friday, with a client on hold. That is a high bar. Most procedures never clear it. The good news is that the fix is not more detail or a better template. It is less: shorter documents, tied to real tasks, stored where the work already happens.
Start with the task you explain most often
Do not sit down to "document the firm." That project has no end, and you will quit before you finish. Instead, pick the one thing you or your senior staff explain over and over. Opening a new matter. Sending a retainer. Booking a client into the calendar with the right reminders. Requisitioning a cheque from trust. If a task interrupts your day because only you know how to do it, that is your first SOP.
There is a simple test. Wait until the next time someone asks you how to do something, then write down exactly what you tell them. You have just drafted an SOP from memory, in the moment, with all the real caveats intact. The tasks that come up most are the ones where a written procedure buys back the most time.
Tip. Keep a running list on a sticky note for one week: every time you answer the same how-do-I question twice, add it. By Friday you will have your priority order, ranked by how much the questions annoy you.
One page, one owner, one outcome
Here is the rule that makes SOPs survive: one page, one owner, one outcome. If a procedure runs longer than a single page, it is either two procedures pretending to be one, or it has drifted into policy and philosophy. Split it or trim it.
One outcome means the document produces a finished thing. Not "understand the intake process" but "a new matter is open, conflicts are cleared, and the file is calendared." A reader should be able to look at the top of the page and know what will be true when they reach the bottom.
One owner means a named person, by role, is responsible for keeping it correct. Procedures without an owner rot silently. When the registry changes a filing rule, someone has to notice and update the page. That someone is the owner, and they should know it.
A procedure that takes longer to read than the task takes to do will never get read twice. The one-page rule
Write the steps a new hire could follow
The test for a good SOP is not whether you can follow it. You already know the task. The test is whether a competent person on their second day could follow it without stopping to ask a question. That means numbered steps, plain verbs, and no assumed knowledge.
Compare these two versions of a single step.
| Vague | Followable |
|---|---|
| Run the usual conflict search before opening. | Search the client name, all opposing parties, and any related businesses. If any match appears, stop and send it to the responsible lawyer before continuing. |
| Set up the file properly. | Create the matter, attach the signed retainer, and add the limitation period to the calendar with a reminder 30 days out. |
The vague column reads fine to you because you fill the gaps automatically. The new hire cannot. Write for the person who does not yet know what "the usual" means. Where a step depends on judgment, say so plainly and name who to ask. A good SOP is honest about where it stops being mechanical.
Two related procedures worth writing this way early are your conflict check and the way you track limitation periods, because both are the kind of task where a missed step is not a small mistake.
Store it where the work happens
An SOP saved in a shared drive folder called Procedures is an SOP nobody will find at the moment they need it. People do not go looking for instructions before they start a task. They start the task, hit the point of doubt, and want the answer right there.
So put the procedure next to the trigger. If opening a matter starts in your practice management system, the intake steps should be visible when someone opens a matter, not two clicks away in a document library. A firm running its files, calendar, and billing in one place like A1 CMS has a real advantage here, because the checklist can sit beside the button that starts the work. The closer the instruction is to the action, the more often it gets used.
Note. If your tools cannot embed a procedure, the next best thing is a single, linkable page per SOP, so you can paste the link into a task, an email, or a training note. One page, one link, no digging.
Update it the first time it breaks
Every SOP is wrong eventually. A form changes, a court moves to electronic filing, a step turns out to skip something important. The firms whose procedures stay trusted are not the ones who audit everything quarterly. They are the ones who fix the page the first time it fails.
Build the habit into the moment of failure. When someone follows the SOP and it leads them wrong, the fix is not to explain the real way in a hallway conversation. The fix is to edit the page, right then, while the gap is fresh, and tell the owner it changed. A procedure that gets corrected the moment it breaks builds credibility. Once people know it is current and accurate, they reach for it without being told to.
Start smaller than feels worthwhile. Pick the one task you are tired of explaining, write it on a single page a new hire could follow, and put it where that work begins. Do that five times over the next month and you will have replaced the ignored binder with a handful of procedures your firm actually runs on. That is the whole point: not a manual you can point to, but instructions your team reaches for on their own.
