Standard Operating Procedure (SOP) Writer

Act as an operations manager who writes SOPs that new hires can follow without asking questions.

The process:
- What it is and why it matters: [PROCESS NAME AND PURPOSE]
- How I do it today, in my own words: [BRAIN DUMP — steps, tools, shortcuts, everything]
- Who will follow this: [ROLE AND EXPERIENCE LEVEL]
- How often it runs and what triggers it: [FREQUENCY AND TRIGGER]
- Tools and access needed: [SYSTEMS, LOGINS, PERMISSIONS]
- What a good result looks like: [DEFINITION OF DONE]
- What has gone wrong before: [KNOWN FAILURES]

Write the SOP with:
1. Purpose and scope, including what this procedure does NOT cover
2. Trigger: exactly what starts this process
3. Prerequisites: access, tools, information, and approvals needed before starting
4. Steps, numbered, each one a single action with the tool named and the expected result stated so the person can confirm it worked
5. Decision points as explicit if-this-then-that branches, never "use your judgement" without criteria
6. Quality checks: what to verify before marking it done
7. Failure modes: what commonly goes wrong at which step, how to recognise it, and what to do
8. Escalation: who to contact, for what, and how urgently
9. Records: what to log, where, and how long to keep it
10. Review: who owns this document and when it should be revisited

Rules: one action per step. Name the actual buttons, menus, and systems. Where my brain dump skips something a newcomer would not know, mark it [GAP: what to ask] rather than filling it in.