A standard operating procedure (SOP) turns a recurring task into a repeatable workflow that another person can follow with confidence. This guide explains how to write an SOP, provides a step-by-step SOP checklist, and includes an editable standard operating procedure template for documenting owners, inputs, decisions, exceptions, permissions, outputs, and completion evidence.
Overview
An SOP should answer five practical questions: what needs to happen, who is responsible, when each step occurs, what to do when conditions change, and how completion is verified. It is not a record of every action someone has ever taken. It is a usable business process checklist designed to produce a consistent result.
The best SOPs are specific without becoming difficult to maintain. A new team member should be able to use one with limited clarification, while an experienced process owner should be able to review it quickly and identify outdated steps. Start with one recurring process that has a clear beginning and end, such as approving an invoice, publishing an article, onboarding an employee, or reviewing a vendor.
Use this creation checklist before publishing an SOP:
- Define the process name and the result it should produce.
- Identify the process owner and the people who perform or approve the work.
- Mark the trigger, starting conditions, and expected completion point.
- List the inputs, tools, files, records, and permissions required.
- Write the main steps in the order they normally occur.
- Document decision points, exceptions, handoffs, and escalation routes.
- Define the output and the evidence that proves the process is complete.
- Test the procedure with someone who did not create it.
- Assign a review date and a clear location for the current version.
Checklist by scenario
1. Define the process before writing steps
Write a short purpose statement using an outcome rather than a vague activity. For example, “Prepare and approve a client invoice” is more useful than “Handle billing.” Record the trigger, such as an approved milestone or completed delivery, and define what counts as done.
Assign one process owner. The owner does not have to complete every step, but should be responsible for accuracy, access, training, and future updates. Also list contributors, approvers, and backup owners. If ownership changes, the SOP should make that transition visible rather than relying on informal knowledge.
2. Capture inputs, tools, and permissions
Before documenting actions, list what the operator needs to begin. Inputs may include a request form, source document, customer record, spreadsheet, approval, or system notification. Name the relevant tool or workspace and specify where the source material is stored.
Permissions deserve their own line. State whether the operator needs to view, edit, approve, export, or administer information. Avoid giving broad access merely because it is convenient. If a step requires an approver or a restricted system, record who can authorize it and what the operator should do if access is missing.
3. Write the normal path as observable actions
Number each step and begin with a clear verb: open, verify, compare, update, save, send, approve, or archive. Include the information needed to perform the action, but avoid instructions that depend on personal judgment without explanation.
For each step, consider adding:
- Action: What must the operator do?
- Location: Where does the action happen?
- Quality check: What should be confirmed before moving on?
- Evidence: What record, status, file, or message shows completion?
- Handoff: Who receives the work next?
For example, “Review the invoice” is incomplete. “Compare the invoice total with the approved quote, confirm the billing details, and mark the review field as complete” gives the operator a clearer path and a verifiable result. A related invoice process checklist can help when documenting quote approval, invoicing, and payment follow-up.
4. Add decision points and exceptions
Most workflows fail at the edges rather than in the normal sequence. Identify questions that change the next action: Is the amount above the approval limit? Is required information missing? Has the deadline passed? Is the request from an authorized person?
Document each decision in an if/then format. For example: “If the request is incomplete, return it to the requester with the missing fields identified. If the request is complete, continue to approval.” Include an escalation route for cases the operator cannot resolve. The aim is not to predict every possibility; it is to prevent common exceptions from becoming hidden work.
5. Test, publish, and train
Ask a person who did not write the SOP to follow it using a realistic example. Observe where they pause, ask questions, or interpret a step differently. Those moments indicate missing context or an unclear decision rule.
After testing, publish one controlled version in the team’s agreed knowledge base or workflow tool. Link related forms, templates, and reference files from the SOP rather than duplicating them. Tell affected staff what changed and when to use the procedure. For onboarding, pair the SOP with an employee onboarding checklist and a short practice task.
Editable standard operating procedure template
Process name: [Name of recurring process]
Purpose: [Result this process should produce]
Owner: [Role or person responsible for maintenance]
Operators: [Roles that perform the work]
Approver: [Role required to approve, if applicable]
Trigger: [Event or condition that starts the process]
Inputs: [Requests, records, files, data, or approvals needed]
Tools and permissions: [Systems, access levels, and locations]
Procedure: [Numbered actions with quality checks]
Decision points: [Questions that change the next step]
Exceptions and escalation: [Known variations and who resolves them]
Output: [Completed record, deliverable, approval, or status]
Completion evidence: [What proves the process is finished]
Version and effective date: [Version number and date]
Next review date: [Scheduled review]
What to double-check
| Area | Review question |
|---|---|
| Inputs | Can the operator identify every required document, data field, approval, or request before starting? |
| Outputs | Is the expected result defined in a way that someone can verify? |
| Exceptions | Does the SOP explain what to do when information is missing, late, duplicated, or outside normal limits? |
| Permissions | Does each role have the access it needs without relying on shared credentials or informal workarounds? |
| Completion evidence | Is there a saved record, status, approval, message, or other trace showing that the work was completed? |
| Handoffs | Does the next person know what they receive, when they receive it, and what action is expected? |
| Maintenance | Is one person accountable for reviewing the SOP when tools, roles, or business rules change? |
Keep the SOP and its related workflow in the same operating environment where practical. If a team uses task management software, link the procedure from the relevant task or team workflow template. If the process involves content, connect it to a content publishing checklist and editorial calendar. A procedure is easier to use when it appears at the point of work rather than in an isolated folder.
Common mistakes
- Writing for the expert: Experienced operators often skip the context that new staff need. Test the procedure with someone unfamiliar with the task.
- Describing intent instead of action: “Ensure accuracy” is a goal, not a step. State what to compare, inspect, or record.
- Ignoring exceptions: A procedure that only covers the happy path pushes difficult cases into private messages and inconsistent decisions.
- Using unclear ownership: “The team” is rarely accountable. Assign a role or named owner for each important handoff.
- Over-documenting: Excessive background can bury the action list. Put essential instructions first and link to supporting detail.
- Failing to control versions: Old copies create conflicting instructions. Mark the current version and archive or remove obsolete copies.
- Using AI without verification: AI can help organize notes, suggest headings, or identify missing questions, but a process owner must verify every step, permission, exception, and system reference before publication.
When to revisit
Review an SOP on a planned schedule and whenever the underlying workflow changes. A quarterly review is a practical starting point for important business processes, while low-risk procedures may need less frequent formal review. Revisit it before seasonal planning cycles, after a recurring error, when a tool or form changes, when responsibilities move between roles, or when a new approval or compliance requirement affects the work.
Use this short review checklist:
- Ask the process owner to confirm that the purpose and outcome are still correct.
- Run the current procedure from start to finish with a recent example.
- Check every link, field name, permission, form, and system reference.
- Compare the documented steps with how the team actually works.
- Review recent exceptions and add only the guidance that will prevent repeat confusion.
- Update the version, effective date, owner, and next review date.
- Notify operators and archive the previous version.
To begin today, choose one repeated task, complete the template, and test it with another person before documenting a second process. Once the procedure is reliable, connect it to your broader small business operations checklist so SOP review becomes part of normal workflow management rather than a one-time documentation project.