Writing standard operating procedures for your practice
How to document the standard operating procedures that make your practice consistent, trainable and less dependent on any one person.
The knowledge that runs most practices lives in people's heads. How a particular return is prepared, which checks matter, how a client likes to be handled. That works until someone is on leave or leaves for good. Standard operating procedures capture that knowledge so the practice depends on process, not memory.
Start with your highest-frequency work
You cannot document everything at once, so start where the payoff is greatest. The jobs you do most often, and the ones most prone to error, deserve procedures first. A well-written procedure for a routine BAS or a standard company return pays back every time that job runs.
- Pick repeatable work. Procedures shine on tasks done again and again.
- Target error-prone steps. Where mistakes recur, a documented standard prevents them.
- Cover the handoffs. Steps that pass between people are where knowledge leaks.
Write for the person doing it next
A good procedure is written for a competent colleague who has not done this specific task before, not for an expert who already knows. Be concrete. List the steps in order, note the decisions and their triggers, and point to the source of any reference data. Vague procedures get ignored; specific ones get followed.
Keep them living, not laminated
The fastest way to kill an SOP library is to let it go stale. A procedure that no longer matches reality is worse than none, because it teaches the wrong thing. Assign ownership, review procedures on a schedule, and update them whenever the underlying work changes.
Attach procedures to the work
Procedures gather dust when they live in a folder nobody opens. They come alive when they sit beside the work they describe. In Finye, checklists and subtasks attach directly to the job, so the procedure is right there as the work happens rather than in a document someone has to remember exists. That proximity is what turns a written standard into actual practice.
Use SOPs to train and delegate
The real dividend of good procedures is faster onboarding and safer delegation. A new staff member with clear SOPs becomes productive far sooner, and a partner can hand over work confident it will be done to standard. Professional development guidance from Chartered Accountants ANZ supports this link between documentation and capability.
Keep procedures short and usable
A procedure nobody reads helps no one, and the surest way to make a procedure unreadable is to pad it. Aim for the shortest document that a competent colleague could actually follow. Use plain numbered steps, note the decisions and what triggers them, and cut anything that merely explains what an experienced person already understands. A tight, practical procedure gets used; an exhaustive treatise gets filed and forgotten.
Decide who owns each procedure, too. An SOP without an owner is an SOP that slowly drifts out of date until it actively misleads. Naming a person responsible for each one, and setting a simple review rhythm, keeps the library trustworthy. The moment a procedure no longer matches how the work is really done, it stops being a help and becomes a hazard, so ownership and regular review are not optional extras but the thing that keeps the whole library alive and worth consulting.
Standard operating procedures are how a practice becomes bigger than any individual in it. Document the work that matters most, keep it current, and attach it to the job, and your firm gains consistency and resilience it cannot get any other way. Read more in our practice series.