Template preview · Operations
Standard operating procedure
Document a repeatable process with clear controls and exceptions.
An SOP for a fictional recurring operation.
Sample purpose
Document a repeatable process with clear controls and exceptions.
Audience: Operations manager, Team lead- Structure
- 4 sections
- Criteria
- 12
- Sources
- 5
- Watches
- 3
- Default approach
- Review first
Set the purpose first. Then change every section, criterion, and agent setting before anything runs.
Fictional sample
Structure and criteria
Sample content shows the shape of a useful document. Copying it is optional.
01 Review firstTrigger and preparation
For this standard operating procedure, states the trigger, prerequisites, and responsible role.
Criteria
- The trigger is an observable event with a time, such as an order received before 12:00.
- Prerequisites list the access, stock and role cover needed before step one.
- Names who decides to start when more than one role can.
Sources
- Orchard order intake (fictional) api.orchardsupply.exampleArrival time and channel of each order.
- NIST SP 800-53 Rev 5 csrc.nist.govControl documentation vocabulary.
Sample content
Orchard Supply is documenting fictional order intake, approval, and dispatch steps. The weekday process starts when an order arrives before noon. Kai Lopez owns the queue; orders missing a delivery address stop before dispatch.
02 Review firstProcedure steps
For this standard operating procedure, orders actions with observable completion checks.
Criteria
- Each step has one role, one action and a start and end point.
- Each step has a completion check recorded in a system, not a mental check.
- Dependencies are explicit where one step must finish before another.
Sources
- Orchard dispatch SOP (fictional) api.orchardsupply.exampleCurrent step order and slot rules.
Watches
- Follows Trigger and preparation
Sample content
Order Operator action Completion check 1 Log order and timestamp Order ID appears in intake sheet 2 Verify quantity, address, and approval All required fields present 3 Assign dispatch slot Warehouse confirms slot 03 ManualQuality and exceptions
For this standard operating procedure, defines an exception route and stop condition.
Criteria
- Each exception is an if-then rule with an owner and response time.
- No exception reads handle as needed; each has an action and a stop condition.
- Every exception leaves a record with date, reason code and decision so a supervisor can audit it.
Sources
- Orchard exception codes (fictional) api.orchardsupply.exampleCodes, owners and response times.
Watches
- Follows Procedure steps
Sample content
- ☐ If address is missing, place order on hold and notify account owner
- ☐ A second staff member checks orders above $5,000
- ☐ Record dispatch confirmation against the order ID
04 Review firstDocument control
For this standard operating procedure, records owner, version, and review date.
Criteria
- Owner, version and next review date are current; a lapsed date is flagged as stale.
- Each version change records what changed and why.
- Review frequency matches how often staffing or tools change, at least yearly.
Sources
- Orchard document registry (fictional) api.orchardsupply.exampleOwners, versions and review dates.
Watches
- Follows Quality and exceptions
Sample content
- 2026-10-05 · Procedure owner reviewKai checks steps against the current dispatch workflow.
- 2026-11-02 · Exception sampleReview five held or corrected orders with the team.