Paste your messy process notes and get a fully structured Standard Operating Procedure with 11 defined sections, decision points, common mistakes, and gap analysis.
Paste your messy process notes and get a fully structured Standard Operating Procedure with 11 defined sections, decision points, common mistakes, and gap analysis. Ideal for ops teams documenting workflows for the first time or standardizing across locations.
Turn these rough notes into a professional Standard Operating Procedure document.
PROCESS NAME: [name of the process]
OWNER: [who's responsible for this process]
FREQUENCY: [how often this runs — daily, weekly, per-event, etc.]
MY ROUGH NOTES:
[Paste your brain dump, bullet points, Loom transcript, or however you captured the process. Don't worry about structure — just get the content down.]
Create an SOP with these sections:
1. PURPOSE: One sentence — why does this process exist?
2. WHEN TO USE: Trigger events that kick off this process
3. WHO'S INVOLVED: Roles needed (not specific people — roles)
4. PREREQUISITES: What needs to be true before starting
5. STEP-BY-STEP PROCEDURE: Numbered steps with enough detail that someone with no context could follow them
6. DECISION POINTS: Any places where the process branches based on a condition (if X, do Y; if not, do Z)
7. COMMON MISTAKES: Things people typically get wrong
8. EDGE CASES: Unusual situations and how to handle them
9. TOOLS & ACCESS NEEDED: Software, credentials, permissions required
10. QUALITY CHECK: How to verify the process was done correctly
11. ESCALATION: When and how to escalate if something goes wrong
After generating the SOP, list any gaps — steps I probably do unconsciously that I didn't mention but a new hire would need to know.
Source: https://craighewitt.com/claude-playbook/operations/sop-machine