A standard operating procedure (SOP) is only useful if people open it, follow it, and keep it current. The aim is a short document that answers one question: how do we do this task, the same way, every time? Here is a practical outline.
State the purpose and scope
Begin with one or two sentences on what the procedure is for, when it applies, and when it does not. “How we onboard a new tax client, from signed engagement letter to kickoff call” is easier to use than “Onboarding.”
Name an owner and the roles involved
Every procedure needs an owner who keeps it accurate, plus a list of the roles that take part. Use role names rather than individual names where you can, so the document survives staffing changes.
Write the steps in the order the work happens
Number the steps and start each with a verb. Say who does the step, what they need before starting, and what “done” looks like. If a step has a deadline, state it. Break any step that contains several separate actions into smaller ones.
Describe exceptions and escalation
Most procedures fail at the exceptions: the client who does not respond, the missing document, the item that needs a second opinion. Write down the common ones, who decides, and when to escalate. You do not need to cover every case, only the ones that come up often.
List tools, templates, and where records live
Link to the checklist, template, or folder used in the procedure, and say where the finished record is kept. This is the detail people most often ask about, and the first thing to go out of date.
Add a simple check
Include a brief way to confirm the work was done correctly, such as a review step or a short end-of-process checklist. Where useful, note one measure to watch, such as the time from start to finish.
Keep it short and easy to find
One to two pages is often enough. Store procedures in one known place, and give each a clear title and a “last reviewed” date. A long document nobody can find is no better than none.
Review it on a schedule
Set a review date, perhaps once a year or after a busy season, and ask the people who use the procedure what has changed. Update it when the work changes, not only on the schedule.
Where to start
Pick one task that is done often and that only one or two people know how to do well. Write it down with the person who does it, then test it with someone who does not. Our Succession & Transition Readiness and Business Process Optimization pages describe how we help with this, or you can contact us.
This article is general operational education. It is not tax, accounting, or legal advice.