---
name: sop-guide-system-planner
description: "Lays out an SOP skeleton with owner, ordered tasks, and verification checkpoints so a manager can implement a reliable process quickly. Use when you want an SOP planned around verification checkpoints and hand-offs so a process is reliable rather than just documented. Do not use for writing a detailed beginner-friendly procedure or an audit document with compliance sections. Related topics: productivity, work, sop."
---

# SOP Guide System Planner

Lays out an SOP skeleton with owner, ordered tasks, and verification checkpoints so a manager can implement a reliable process quickly.

## When to use

Use this skill when you want an SOP planned around verification checkpoints and hand-offs so a process is reliable rather than just documented. Do not use it for writing a detailed beginner-friendly procedure or an audit document with compliance sections.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Convert the goal statement into a measurable success condition.
3. Number the key steps and attach to each a verification checkpoint stating what is checked, by whom, and the fix on failure.
4. Mark every hand-off point between people or teams.
5. Flag steps that cannot be verified and propose a check for each.
6. Close with the owner, review cycle, and the evidence that would justify revising the SOP.

## Inputs

- **SOP title** (free text, e.g. "Customer onboarding SOP")
- **Goal statement** (longer free text)
- **Department scope** (choose one: Sales, Support, Operations, Marketing, IT)
- **Owner** (free text, e.g. "Name or role")
- **Key steps** (longer free text)
- **Review cycle** (choose one: Monthly, Quarterly, Bi-annual, Annual, None)

## Output

A compact markdown SOP with Title, Goal, Scope, Owner, Steps each followed by a checkpoint, and Review Cycle.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### SOP Guide System Planner

Plan an SOP around where the process can fail, not only what happens.

- SOP title: {{SOP title}}
- Goal statement: {{Goal statement}}
- Department scope: {{Department scope}}
- Owner: {{Owner}}
- Key steps: {{Key steps}}
- Review cycle: {{Review cycle}}

Turn the goal statement into a measurable success condition. Number my key steps and, after each one, add a verification checkpoint: what to check, who checks it, and what to do if it fails. Flag any step with no obvious way to verify it and suggest one. Mark the points where work is handed from one person or team to another, since those are where processes break. Keep it compact enough to scan in a few minutes. End with the owner and the review cycle, plus one line saying what evidence would justify changing the SOP.

## Pitfalls

- Writing checkpoints like make sure it is correct that nobody can actually perform.
- Ignoring hand-offs, where most process failures happen.
- Assigning a checkpoint to the same person who did the step, which removes the independent check.
