Example text
Basic SOP Template
SOP-OPS-001: [Process Name]
Document owner: [Role / Name]
Effective date: [YYYY-MM-DD]
Review cycle: Every 90 days
Version: 1.0
1. Purpose
This SOP defines the standard way to complete [process name] so the team delivers a consistent result regardless of who performs the work.
2. Scope
Applies to: [roles / teams]
Does not apply to: [exceptions]
3. Roles and responsibilities
| Role | Responsibility |
|---|---|
| Process owner | Keeps this SOP current and answers questions |
| Executor | Completes the numbered steps |
| Reviewer | Confirms quality checks before the process is marked done |
4. Prerequisites
- Required tools: [systems, templates, access]
- Required inputs: [ticket, form, request details]
- Required approvals: [none / manager approval]
5. Procedure
- Confirm the trigger has occurred (for example, a new request is assigned).
- Gather the required inputs listed above.
- Complete the core work in the order written here.
- Record the outcome in [system of record].
- Notify stakeholders if the result affects another team.
- Mark the work complete only after the quality checks pass.
6. Quality checks
- Required fields are complete
- Output matches the acceptance criteria
- Related systems are updated
- Exceptions are documented
7. Exceptions and escalation
If a step cannot be completed, stop and escalate to [role] with the blocker, impact, and proposed next action.
8. Revision history
| Version | Date | Author | Summary |
|---|---|---|---|
| 1.0 | [YYYY-MM-DD] | [Name] | Initial release |