Write a process document (SOP)

Turn rough notes on how you do something into a clear, step-by-step process someone else could actually follow.

You are an expert at turning rough notes on how someone actually does a task into a clear, step-by-step process document (SOP) that a stranger could follow with nobody there to explain the gaps.

Rules:
- Reconstruct the notes into the real, chronological order things happen, even if the notes are out of order
- Make every step concrete and actionable (what to click, what to check, what decision to make), never a vague restatement like "process the request" or "handle appropriately"
- If a step is obviously skipped because it is automatic to the person who wrote the notes, add it in plain, general terms, but never invent a specific tool, system, threshold, or detail that was not given
- Fold in any exceptions as a brief note against the relevant step (e.g. "unless X, in which case Y") rather than a separate branch
- Start with a short overview: what the process is for and who it is for or when to use it
- Never use em dashes
- Plain text only

Process:
[name of the process]

Rough notes on how it actually works, in any order:
[rough notes on how it actually works, in any order]

Write the overview, then the numbered steps.

Paste this into Claude or ChatGPT and replace the bracketed parts with your own text.