How to Write a One-Page SOP: A Practical Guide
A one-page standard operating procedure is the sweet spot for small teams. It’s long enough to standardise a task that has to be done the same way every time, and short enough that people actually read it. If your team’s processes currently live in people’s heads, or in a 20-page manual nobody opens, this template is the reset button. The one-page limit is deliberate: it forces you to write down only what a competent person needs to do the job right.
When to Use This
Use this template for any task that is done more than once and needs to be done consistently: raising invoices, running month-end, onboarding a new starter, doing the weekly stock count, processing returns. If the task changes every time, it’s not an SOP candidate. If it’s done the same way weekly or monthly, it is.
Write the SOP for the person who will do the job when the usual person is on holiday, the covering colleague, the new hire, the temp. If they can’t follow it without calling someone, it’s not finished. Resist the temptation to document every edge case; a one-page SOP covers the normal run plus the two or three exceptions that actually happen. If your procedure genuinely doesn’t fit on one page, it’s probably two procedures, split it and write a second sheet.
How to Fill It Out
The header box. Start with the document title written as an action in active voice, “Raise a client invoice,” not “Invoicing procedure.” Add a document ID (a simple code like SOP-FIN-001 works for a small team), the version number (start at 1.0), the effective date, and the review cadence (annual is the default; write it down so it’s not forgotten). Name the organisation or team it applies to and the classification (usually “Internal Operations”).
Section 1: Purpose & Objectives. One or two sentences: why this procedure exists, what quality standard it protects, and the business problem it prevents. This is not decoration, it tells the reader why they should care. Write the problem it solves plainly: “To define the weekly process for reviewing billable hours, issuing client invoices, and reconciling payments by Friday afternoon, preventing delayed receivables.”
Section 2: Scope & Initiation Trigger. Two parts. Scope: which team, department, or software tools this applies to. Trigger: the exact event that starts the routine. “Weekly every Friday at 9:00 AM” is a trigger. “Monthly” is not, it’s a wish. A specific trigger is what turns a procedure into a habit, because the person responsible knows exactly when to start.
Section 3: Roles & Accountabilities. Name three roles: the procedure owner (the person who does the work), the approver (the manager who validates it and signs off), and the covering backup (the colleague trained to run it when the owner is absent). The backup is the part most teams skip, and it’s the part that matters most, an SOP with no named backup breaks the day the owner calls in sick. Fill in actual names and job titles, not “TBD.”
Section 4: Step-by-Step Procedure. The core of the document. List the steps in chronological order, one action per step, starting with a strong verb: open, export, review, draft, submit. For every step, add the expected result and how to verify it, this is what separates an instruction from a hope. “Submit invoice batch to manager for written approval” is the action; “Written sign-off received by email” is the verification. Aim for five to nine steps. If you’re past ten, something needs to be a sub-procedure.
Section 5: Exceptions & Error Recovery. Write down the two or three things that actually go wrong: missing information, a discrepancy above a threshold, the system being down. For each one, state exactly what to do, who to contact, by when, and whether to pause or continue. Set a clear escalation threshold: “If the variance exceeds $500 or 5%, pause and escalate to the approver immediately.” Without a threshold, people either escalate everything or nothing.
Section 6: Governance & Approval Sign-Off. The owner prepares the SOP, the manager approves it, and you record the approval date and the next scheduled review. A procedure that was never approved is a suggestion; this section makes it official. Delete the grey instruction text before you share the finished document.
Common Mistakes
1. Writing a manual instead of an SOP. The classic failure: twenty steps, three appendices, background history of the department. A one-page SOP assumes a competent reader. Include only what they need to do the task the way you need it done, and cut everything else.
2. No named backup. The SOP works perfectly until the owner is away, and then it might as well not exist. Naming a backup forces you to train that backup, that training is half the value of the whole exercise.
3. A vague trigger. “As needed” and “regularly” are not triggers. If nobody knows exactly when to start the procedure, it starts late or not at all. Give a day, a time, or a specific event.
4. Skipping the exceptions section. Teams always document the happy path. The first surprise, a system outage, a missing invoice, then gets handled ad hoc, and the ad-hoc handling becomes the new, undocumented procedure. Two or three planned exceptions keep that from happening.
Who Needs to Sign Off
The procedure owner drafts the SOP; their direct manager reviews and approves it. That’s the minimum. If the procedure crosses departments, finance approving operations’ numbers, for example, the other department’s lead should review it too, so nobody discovers a conflicting process later. The template’s sign-off table records both signatures, the approval date, and the next review date.
How Often to Review and Update
Review every SOP at least once a year, the template’s review cadence line is there to enforce this. But also update it the moment something real changes: new software, a new step, a new person in the owner role, a lesson learned from an exception that worked better than the written plan. An out-of-date SOP is worse than no SOP, because people follow it with confidence into the wrong outcome. When you update, bump the version number (1.0 to 1.1 for a small change, 2.0 for a rewrite) and reset the review date.
Download the free One-Page Small-Team SOP Master Template.