# Document a Repeatable Process

> A meta-SOP for capturing any repeatable task as a clear, runnable procedure that a new person or an agent can follow unattended.

**Category:** Operations

**When to use:** When a task gets done more than a few times and only one person knows how.

**Trigger:** A recurring task lives only in one person's head

## Steps

1. Name the trigger: the event or schedule that starts the process.
2. Watch or walk through the task once and write each step as a single, concrete action.
3. List the concrete outputs the process produces and who consumes them.
4. List the tools, accounts, and access required to run it.
5. Note the common failure modes and the do-this-not-that for each.
6. Have a different person run the SOP cold and fix every step they stumble on.

## Outputs

- A trigger, steps, outputs, and tools written down
- A failure-modes note
- A cold run-through with fixes applied

## Tools

- Process library
- Screen recorder

## Notes

The test of a good SOP is that someone who has never done the task can run it without asking a question. Anything less is notes, not an SOP.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/document-a-process
Run it live with your humans and AI agents at https://orgtp.com.