How to Write a One-Page SOP for a Task You Repeat Every Week
☰ Table of Contents
A one-page SOP (standard operating procedure) is useful when the same task keeps taking different amounts of time, getting missed, or requiring you to explain it again. It turns a recurring job into a short, usable checklist, without creating a binder nobody opens. The goal is not to document everything. It is to make the next run easier and more consistent.
This guide shows a practical way to write a one-page SOP for a weekly task, from choosing what to document to testing the instructions with someone else. It works for solo operators and small teams using ordinary documents, notes, or project tools.
What belongs in a one-page SOP
Capture just enough for a capable person to complete the task safely and know when it is done. Include the trigger, owner, needed inputs, ordered steps, a check for completion, and what to do when something goes wrong. If a step requires a separate policy, form, or technical guide, link to it instead of copying it all.
A simple SOP is especially useful for work with a repeatable sequence, such as preparing a weekly newsletter, closing out invoices, publishing a new listing, or handing off a customer request. It is less useful for work that changes substantially every time. For broader systems, see our guide to a lean digital tools stack for a small business.
A five-step method to document a task
- Pick one recurring task. Choose something frequent enough to matter and stable enough to repeat. Avoid trying to document an entire department at once.
- Watch one real run. Note the actual sequence, tools, decisions, and common delays. Do not write from memory alone if the task has hidden steps.
- Write in action verbs. Use short instructions such as “Open the order queue” or “Compare the total with the receipt.” Put steps in the order they happen.
- Mark decision points. State what to do when a condition changes: “If the receipt is missing, pause and request it; do not guess the amount.”
- Test it cold. Ask someone who knows the basics to follow the page without coaching. Every question or hesitation shows where the instructions need clarification.
| Section | Useful prompt | Keep it concise |
|---|---|---|
| Purpose and trigger | What starts this task, and what should it achieve? | One sentence |
| Owner and inputs | Who does it, and what must be ready? | Role plus short list |
| Steps | What happens, in order? | Numbered actions |
| Quality check | How can someone confirm it is complete? | Observable result |
| Exceptions | When should they stop or ask for help? | Only common or risky cases |
A practical SOP example
Here is a compact outline for a weekly invoice follow-up. Adapt the steps to your own software and payment terms rather than copying them blindly.
Task: Review and follow up on overdue invoices each Monday.
Owner: Operations lead.
Before you start: Open the current invoice list and confirm the reporting period.
Steps: Filter to overdue invoices; verify each balance against the invoice record; check for a recent payment or dispute; send the approved reminder using the current template; record the date and outcome.
Done when: Every overdue invoice has a checked status and a dated note.
Stop and ask: If the customer disputes the amount, a payment is unassigned, or account details appear inconsistent, do not send a reminder until reviewed.
Last reviewed: [date] by [role].
This example deliberately points to an approved message template rather than embedding a potentially outdated copy. The person doing the work can find the source of truth and the procedure stays short.
How to keep it useful instead of stale
Give the document an owner and a review date. Review it when the software, policy, or handoff changes, and after a mistake reveals a missing instruction. A lightweight quarterly check is often enough for stable tasks; high-risk procedures need a schedule that matches the risk and any applicable rules.
Store it where the task happens, not in a folder only one person can find. Use a clear title, a version or last-reviewed date, and links to current forms. If your process uses several digital tools, our small-business tools guide can help reduce needless app-hopping.
What an SOP should not do
A one-page SOP is not a substitute for training, judgment, a safety procedure, or a legal requirement. Do not compress complex or hazardous work until essential warnings disappear. Link to the authoritative instructions and involve the responsible specialist where needed. It should also not become a dumping ground for every edge case; keep the normal path clear and document only exceptions that materially affect quality, safety, money, or customer trust.
One-page SOP FAQs
What does SOP stand for?
SOP means standard operating procedure. It is a documented set of instructions for carrying out a recurring task consistently.
How long should an SOP be?
For a straightforward recurring task, one page is a good constraint, not a rule. A complex or safety-critical process may require longer formal documentation.
Who should write the procedure?
Usually the person who performs the task, with review from its owner or subject-matter expert. Then test it with another capable person.
How often should I update it?
Update it when the process changes or a real run exposes a gap. Add an owner and review date so it does not quietly become obsolete.
Can I use a checklist instead of a full SOP?
Yes, when the task is simple and the steps need little explanation. Add context, decision points, or links when a checklist alone could lead to mistakes.
Should I include screenshots?
Only when a visual makes a step materially clearer. Keep images current and avoid screenshots containing customer data or credentials.
A small document that saves the next explanation
Start with one task that repeats, document what actually happens, and ask someone else to test the page. A useful SOP is the shortest version that lets the next person do the work and recognize when to stop. That is enough to make a recurring week a little less dependent on memory.
