<b>Framework: Write an SOP someone can actually follow</b>

<b>Framework: Write an SOP someone can actually follow</b>
Run this whenever you document a recurring task so it survives you leaving.

<b>Every SOP must contain</b>
— ☐ A trigger: the exact event that starts it (Owner: author)
— ☐ Numbered steps, each one verb-first and checkable (Owner: author)
— ☐ An owner named on every step — never "someone" (Owner: author)
— ☐ A definition-of-done: how you know it's truly finished (Owner: author)
— ☐ The one failure mode this SOP exists to prevent (Owner: author)

<b>Then test it</b>
— ☐ Hand it to someone who's never done the task (Owner: author)
— ☐ They run it with zero questions — if they ask, the step was ambiguous (Owner: reviewer)
— ☐ Fix every gap they hit, then version and date it (Owner: author)

<b>Owner:</b> The person who knows the task
<b>Trigger:</b> A task done more than twice by hand
<b>Done-when:</b> A newcomer completes it with no questions.

If it isn't written, it doesn't exist. Save this. Run it every time.