# Standard Operating Procedure: [PROCEDURE NAME]

## Document Control

| Field | Entry |
|---|---|
| SOP ID | [SOP-DEPT-001] |
| Version | [1.0] |
| Effective Date | [YYYY-MM-DD] |
| Owner | [NAME, JOB TITLE] |
| Approver | [NAME, JOB TITLE] |
| Next Review Date | [YYYY-MM-DD — typically 12 months from effective date] |
| Supersedes | [PREVIOUS SOP ID / VERSION, or "None"] |

## 1. Purpose

State in one or two sentences why this procedure exists and what outcome it guarantees when followed.

> Example: "This SOP defines the standard method for processing incoming customer refund requests so that every request is resolved within 3 business days and recorded consistently in [SYSTEM NAME]."

## 2. Scope

Define exactly where this SOP applies — and where it does not.

- **Applies to:** [TEAMS / ROLES / LOCATIONS / SHIFTS covered, e.g. "all customer-service agents at the Austin office"]
- **Does not apply to:** [EXCLUSIONS, e.g. "wholesale accounts, which follow SOP-SALES-014"]

## 3. Definitions

| Term | Definition |
|---|---|
| [TERM 1] | [Plain-language definition — assume a new hire is reading this] |
| [TERM 2] | [Definition] |
| [ACRONYM] | [Spell it out on first use] |

## 4. Responsibilities

| Role | Responsibility |
|---|---|
| [PROCESS OWNER, e.g. Operations Manager] | Maintains this SOP, approves changes, audits compliance [QUARTERLY/ANNUALLY] |
| [OPERATOR ROLE, e.g. Team Member] | Performs the procedure as written; reports deviations to [ROLE] |
| [TRAINER ROLE] | Trains new staff on this SOP and records completion in [TRAINING LOG / LMS] |
| [QA / REVIEWER ROLE] | Verifies output against the acceptance criteria in Section 7 |

## 5. Required Materials, Equipment, and Access

List everything the operator needs **before** starting. A person should be able to check this list and know they are ready.

- [TOOL / EQUIPMENT 1, e.g. "Label printer, loaded with 4x6 stock"]
- [SOFTWARE + ACCESS LEVEL, e.g. "CRM login with 'Agent' role or higher"]
- [FORM / TEMPLATE, e.g. "Form F-102: Daily Checklist, current version"]
- [PPE OR SAFETY ITEMS, if any]

## 6. Procedure

Write one action per step. Start each step with a verb. Include the *what*, the *how*, and the *acceptance check* (how the operator knows the step worked). The example below shows the expected level of detail.

1. **Prepare the workspace.** [Example: Clear the counter, confirm the previous shift's log (Form F-102) is signed off. If it is not signed, stop and notify the shift lead before proceeding.]
2. **Verify inputs.** [Example: Check that the work order lists a valid job number in the format JO-#####. Reject and return any order missing this number.]
3. **Perform the core task.** [Describe the main action. Break into sub-steps if any single step takes more than ~2 minutes or has a decision point.]
   - 3.1 [SUB-STEP]
   - 3.2 [SUB-STEP]
4. **Check the result.** [Example: Compare output against the acceptance criteria in Section 7. If any criterion fails, follow the deviation path in Section 8.]
5. **Record the work.** [Example: Log completion time, operator initials, and batch/job number in [SYSTEM OR FORM]. Records are retained for [RETENTION PERIOD].]
6. **Reset for the next run.** [Example: Return tools to the shadow board, dispose of waste per Section 9, and update the status board to "Ready".]

**Timing guide:** the full procedure should take approximately [X MINUTES] for a trained operator. If it routinely takes longer, flag it to the process owner — that is a signal the SOP or the process needs revision.

## 7. Acceptance Criteria

Define "done and correct" objectively so two different people would judge the same output the same way.

- [CRITERION 1, e.g. "All fields on Form F-102 completed, no blanks"]
- [CRITERION 2, e.g. "Output measures within ± tolerance of the spec"]
- [CRITERION 3]

## 8. Deviations and Escalation

- If a step cannot be completed as written, **stop** at the last safe point.
- Notify [ROLE] within [TIMEFRAME, e.g. "15 minutes"] via [CHANNEL].
- Record the deviation in [DEVIATION LOG / FORM ID], including what happened, when, and what was affected.
- Do not improvise workarounds; only [ROLE] may authorize a documented exception.

## 9. Safety and Compliance Notes

- [HAZARD 1 and its control, e.g. "Blade guard must be in place before power-on"]
- [REGULATORY OR POLICY REQUIREMENT this SOP satisfies, e.g. company policy P-07, ISO 9001 clause 8.5.1, or an industry regulation]
- [RECORD-RETENTION REQUIREMENT, e.g. "Completed forms retained 3 years"]

## 10. Related Documents

- [SOP-XXX-000 — RELATED PROCEDURE NAME]
- [FORM F-000 — FORM NAME]
- [POLICY / WORK INSTRUCTION REFERENCE]

## 11. Revision History

| Version | Date | Author | Summary of Changes | Approved By |
|---|---|---|---|---|
| [1.0] | [YYYY-MM-DD] | [NAME] | Initial release | [NAME] |
| [1.1] | [YYYY-MM-DD] | [NAME] | [e.g. "Added acceptance criteria to Section 7"] | [NAME] |

---
Template by Pellucida (pellucida.ai) — turn this SOP into a training video at pellucida.ai/solutions/sop-to-training-video