One-Page Small-Team SOP Master Template
A concise single-page standard operating procedure format covering purpose, ownership, steps, and exception handling.
Choose a design
The same document in 9 designs, same content and editable fields, different styling. Pick the design you like and download that version. Click any design to preview it larger before downloading. The Sample card shows a completed example, filled in with sample details.
Classic Navy
Executive Charcoal
Modern Minimal
Compact
Burgundy
Forest
Teal Professional
Warm Copper
Mono
Sample
Download this template
Choose the file you need, then download it. No sign-up, no payment.
What’s Included in This Resource
Every resource on The Office File provides a complete toolkit rather than an empty, unhelpful document shell:
- Editable Microsoft Word (.docx) 1-page template with tested typography and margin styles (38 KB)
- Completed real-world worked example in Word (.docx, 39 KB): Weekly Client Invoicing & Receivables Reconciliation
- Printable PDF version (73 KB)
Sample included: Worked Example: Weekly Client Invoicing & Payment Reconciliation. Demonstrates a complete billing routine for a 12-person creative agency: auditing weekly billable hours, drafting invoice records in accounting software, securing management sign-off, delivering final PDFs to clients, and reconciling 30-day receivables.
How to Use This Template
Follow these practical steps to customize and roll out this procedure with your team:
1. Name the procedure clearly
Give the procedure an active-voice title that says what it does (e.g., "Reconcile Weekly Client Invoices"), so staff can find and follow it at a glance.
2. Specify the trigger event
Write down the exact condition that starts this routine (e.g., "Every Friday at 9:00 AM" or "Upon receiving client agreement").
3. Write numbered, active steps
Use direct action verbs ("Open ledger", "Export invoice") so any covering staff member can follow the sequence effortlessly.
4. Clarify exception handling
State explicitly what the employee must do if a step fails or a dispute occurs (e.g., "If variance exceeds $250, notify Operations Director").
About This Template
A standard operating procedure turns tribal knowledge into a repeatable system. This SOP template documents the purpose, owner, step-by-step method, and exception handling for a routine process, so the work gets done the same way whether it is your best employee or a new hire doing it. That consistency is what lets a small business scale without chaos.
Standardizing routine workplace processes on a single printable page. It establishes who owns the procedure, what triggers it, who approves completed work, and what steps to take when an error or exception occurs, without needing a confusing 10-page corporate manual.
When to Use This Template
- Training new hires on a routine process without tying up a senior team member
- Reducing errors in high-stakes or safety-critical routine work
- Providing auditors or clients with evidence of controlled, repeatable processes
- Documenting tribal knowledge before a key employee leaves or goes on leave
- Ensuring consistent output when different people perform the same task
Key Sections Explained
Understanding what goes in each part of the document helps you fill it in correctly the first time:
Step-by-step procedure
The numbered steps in execution order, written as instructions to the person doing the work, not as a description of it.
Purpose and scope
Why this procedure exists and what it covers, and just as importantly, what it does not cover.
Exceptions and troubleshooting
What to do when things deviate: common problems, escalation paths, and who to call when the procedure does not fit.
Trigger and frequency
What starts this procedure and how often it runs, daily, per order, on request, or on a schedule.
Roles and responsibilities
Who owns the procedure, who performs it, and who approves the output. No ambiguity about accountability.
Frequently Asked Questions
When should an SOP be updated?
Whenever the process changes, after any incident the SOP should have prevented, and at least annually. Assign an owner and a review date so updates do not depend on someone remembering.
Who should write the SOP?
The person who actually does the work, reviewed by their manager. Procedures written by people who have never done the task tend to describe an idealised version that falls apart in practice.
How long should an SOP be?
As short as clarity allows. One page is ideal for routine tasks; complex procedures may need more, but if nobody reads past page two, the extra pages are fiction. Favour clear steps over comprehensive prose.
How do we get people to actually follow it?
Keep it practical, train from it, and reference it when correcting deviations. An SOP that contradicts how the work is really done will be ignored, fix the document or fix the process, but do not let them diverge.