Standard Operating Procedure (SOP) Template
A fill-in-the-blank structure for writing a standard operating procedure your team can actually follow, with an approval and revision trail built in.
Most SOPs fail for one reason: they describe what should happen instead of telling a specific person what to do, in what order, and what to do when it goes wrong.
Use this template for any repeatable task that affects quality, safety, cost, or the customer. Write one procedure at a time, test it once with the person who actually does the work, then publish it.
What's included
- Document control block (owner, version, effective date)
- Purpose, scope, and definitions
- Numbered step-by-step procedure
- Roles and responsibilities
- Records, references, and revision history
1. Document control
Fill this in first. Every page of a printed copy should identify its version.
- Procedure title:
- Procedure owner: (one named person, not a department)
- Applies to:
- Version:
- Effective date:
- Next review date:
- Approved by:
2. Purpose
One or two sentences. Why does this procedure exist and what does it protect?
Example: This procedure ensures every customer delivery is confirmed, photographed, and closed out the same day, so billing is accurate and disputes can be answered with evidence.
3. Scope
State where it starts and where it stops, and name anything it excludes.
- Starts when:
- Ends when:
- Does not cover: (link to the procedure that does)
4. Definitions
Define only the words your team uses differently from everyone else. Skip anything already obvious.
5. Procedure
One action per step. Start each step with a verb and name who does it.
- Receive the request and log it in the intake sheet the same business day.
- Confirm scope, site contact, and access window with the customer in writing.
- Check materials and equipment against the job list before leaving the shop.
- Perform the work and record start and end times.
- Document completion with photos and a signed work order.
- Close the ticket and send the invoice within two business days.
- Escalate any deviation to the procedure owner the same day.
6. Roles and responsibilities
| Role | Responsible for | | --- | --- | | Requestor | Submitting complete, accurate information | | Technician | Performing and documenting the work | | Procedure owner | Keeping this document current and training the team | | Manager | Approving exceptions |
(List the roles as a simple table or bullet list — the point is that every step above has one named owner.)
7. Records and references
- Records created by this procedure and where they are stored:
- Related procedures:
- Forms or templates used:
- Regulatory or customer requirements referenced:
8. Revision history
| Version | Date | Change | Author | | --- | --- | --- | --- | | 1.0 | | Initial release | |
How to use this template
- Copy the sections above into your own document.
- Draft the procedure with the person who does the work, not for them.
- Walk through it once on a live job and note anything missing.
- Publish version 1.0 with an effective date and a scheduled review.
- Review at least annually, and immediately after any incident, audit finding, or repeated error.
Document approval statement
Approved — published by the Wise DSP Command Plane
This document is approved for publication by the Wise DSP Command Plane. Document owner of record: Zeus Wise, Senior Agent / Owner. Version 1.0. Any change to its content requires re-approval before it is published again.
Published free by Wise DSP through SunArrow. Use and adapt these tools for your own business. Nothing here is legal, tax, or accounting advice — confirm requirements that apply to your business with a qualified professional.
