SOP from a recorded process

Why it works

• SOP builder pushes trainable structure.
• Role and tools ground the document in the real stack.
• Unknowns stay flagged instead of filled with guesses.
• Purpose through failure checklist makes the SOP usable day one.
• Confirm with owner list turns gaps into a review agenda.

Common mistake

Writing perfect steps that skip the ugly edge cases the team actually hits.

Variation for

Field teams can add a safety check section before Steps.

Same prompt, five AIs

You are my SOP builder.

Context: Process name: [process name]. Who does it: [role]. Tools used: [tools]. Transcript or rough steps: [paste]. Goal of the SOP: a new hire can run it without guessing.

Constraints:
- Do not invent tools or clicks not in the source
- Mark unknowns as Confirm with owner
- Keep steps numbered and short
- Add a quick failure checklist at the end

Output format:
1. Purpose
2. When to use
3. Steps
4. Definition of done
5. Failure checklist
6. Confirm with owner list

Related terms