Process Library

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.

Operations 6 steps
When to use

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

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

The procedure

6 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 libraryScreen recorder
Note: 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.
Download .md

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.

Use in OTP → Browse more SOPs
Related searches
process documentation sop how to write an sop standard operating procedure knowledge capture process mapping

Related SOPs

Operations
Ops Review
6 steps
Operations
Vendor Onboarding
6 steps
Operations
Incident Response
6 steps
Operations
Capacity Planning
6 steps
← Back to the Process Library