# Sop Writing

> Writes governance-ready standard operating procedures with precise scope, role accountability, step controls, and audit-ready evidence requirements. Use when users ask to draft, improve, or standardize SOPs for operational, finance, or data governance processes.

- Skill: `bkjohn2018/sop-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bkjohn2018/sop-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bkjohn2018/sop-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: bkjohn2018 (https://skillmd.com/u/bkjohn2018)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/bkjohn2018/sop-writing

---


# SOP Writing

## When to Use
- A team needs a repeatable, auditable way to execute a process.
- Existing SOPs are inconsistent, vague, or outdated.
- Governance or audit requires explicit controls and evidence.
- Users request a formal SOP template with role ownership.

## SOP Structure Standard
Use this section order in every SOP:
1. Purpose
2. Scope
3. Definitions
4. Roles and responsibilities
5. Prerequisites and inputs
6. Procedure steps
7. Control points and exceptions
8. Outputs and evidence retention
9. Review cycle and version history

## Workflow
1. Apply `governance-writing-style-guide` before drafting.
2. Confirm process trigger, end-state, and frequency.
3. Identify accountable owner, executors, reviewers, and approvers.
4. Draft prerequisites, systems, data inputs, and access requirements.
5. Write numbered steps with one action per step and clear expected result.
6. Mark control points (approval gates, reconciliations, threshold checks).
7. Add exception handling with escalation path and response time.
8. Define required evidence artifacts and retention requirements.
9. Add version metadata, review cadence, and change-control notes.

## Writing Rules
- Use imperative voice for procedure steps.
- Use consistent role names throughout the document.
- Avoid ambiguous terms such as "as needed" without criteria.
- Every critical step must state output and evidence.
- Every exception path must include owner and escalation trigger.

## Output Template
```markdown
# Standard Operating Procedure: [Process Name]

## 1) Purpose
[Why the SOP exists and what risk/control objective it supports]

## 2) Scope
- In scope:
- Out of scope:
- Frequency:

## 3) Definitions
- Term:
- Definition:

## 4) Roles and responsibilities
| Role | Responsibility | Backup Role |
|---|---|---|

## 5) Prerequisites and inputs
- Systems:
- Required access:
- Inputs:

## 6) Procedure steps
1. [Action]  
   - Expected result:
   - Evidence produced:
2. ...

## 7) Control points and exceptions
- Control:
- Trigger:
- Required action:
- Escalation path:

## 8) Outputs and retention
- Output artifact:
- Storage location:
- Retention period:

## 9) Review and version history
- Owner:
- Next review date:
- Version:
- Change summary:
```

## Acceptance Criteria
- SOP can be executed by a trained backup without verbal clarification.
- Each critical step has explicit evidence output.
- Controls are measurable and tied to risk reduction.
- Scope boundaries prevent duplicate or conflicting procedures.
- Review cadence and owner are defined.

## Quality Checklist
- Purpose and scope are concise and non-overlapping.
- Role accountability is unambiguous.
- Procedure steps are sequential and testable.
- Exceptions include clear escalation criteria.
- Evidence retention is explicit and audit-ready.