Write the Process Down: SOPs That Keep Your Business Running When You Step Away

A business that runs when you do not

An SOP sounds corporate. It is really just a checklist with enough detail that someone else could follow it: one task, written as numbered steps, with a clear finish line. When the steps only live in your head, every helper - a person, a contractor, an AI assistant - needs you standing next to them. Written down once, the task runs the same way every time, whether you are there or not.

Start with something you do every week: posting content, sending the weekly buyer email, answering the same customer question. Do not try to document everything. One task, written well, shows you how to do the next.

The anatomy of a full SOP

Short procedures get used, but short is not the same as thin. A working SOP has eight parts:

1. Trigger. When the task starts. "Friday 4pm" or "when five orders land" - not "regularly."

2. Owner. Whose job it is, and who covers when they are away.

3. Permissions. Which tools and access levels the task touches. Logins live in a password manager, never in the document.

4. Prerequisites. What must exist before step one: the template, the export, the link.

5. Numbered steps. One action per step, starting with a verb. Where a click lives, name its place.

6. Acceptance evidence. What "done" looks like - something checkable, like "the test email arrived and the link opens."

7. Exceptions. What goes wrong and what to do about it, including which decisions come back to you.

8. Version history. Dated lines. When a tool changes or a step breaks, the procedure changes the same day.

Where the short version breaks

The repaired SOP - take it

Here is the same task as a full, working SOP. Rae and her class planner are fictional, but the shape is real: trigger, owner, scoped permissions, prerequisites, steps, evidence, exceptions, history. Copy it and replace her task with yours.

WEEKLY PLANNER BONUS EMAIL - SOP v1.3 (2026-10-25)
Owner: Rae. Backup: the helper Rae has explicitly added to the email tool - shop admin access alone does not include emailing customers.

TRIGGER
Every Friday, 4pm. The planner itself is delivered automatically at purchase - this email is the promised weekly bonus for buyers who opted in to it.

PERMISSIONS NEEDED
Email tool access, granted person-by-person by Rae. Logins live in the password manager - never in this document.

PREREQUISITES
- The bonus email template "planner-friday-bonus" (saved in the email tool)
- This week's bonus file, exported and checked

STEPS
1. Check first: open the email tool's sent and scheduled lists. If this week's bonus already shows as sent or scheduled, stop - do not send a duplicate. If the status is unclear (a failed or half-finished send), reconcile with Rae before resending.
2. Open the "planner-friday-bonus" template.
3. Link this week's bonus file. Do not edit the library link.
4. Send yourself a test. Check the bonus file opens.
5. Send to the "planner-bonus-subscribers" segment: buyers who chose the weekly bonus emails. Buying the planner is not by itself consent to email - the segment excludes buyers who never opted in and anyone who unsubscribed, and the tool's suppression list stays in force.
6. Note the send date and the reported counts in the shop notebook.

DONE LOOKS LIKE
The test email arrived and the bonus file opens. Review the email tool's failure and bounce report: a delivered count slightly below the segment size is normal (suppressions and bounces), anything else needs a look - a sent count alone is not proof of delivery. The email tool's own record plus the notebook line together prove this week's send happened - next week starts from that check, not from memory.

EXCEPTIONS
- The bonus file is not ready by 4pm: send the preapproved "bonus lands Monday" note (saved template - do not improvise a new promise or date). Never skip silently.
- A buyer replies with an order problem: that is a judgment call - answer it yourself, do not hand it to a helper.
- New buyers mid-week: their planner arrives automatically at purchase; they are asked about the bonus emails separately and join the segment only after saying yes.

VERSION HISTORY
v1.3 (2026-10-25): pre-send sent/scheduled check; segment scoped to opted-in bonus subscribers; failure-report review in the finish line; delay note marked preapproved.
v1.2 (2026-10-25): re-scoped to the weekly bonus email; the planner itself is delivered automatically at purchase.
v1.1 (2026-10-18): added the test-send step after a helper sent a broken link.
v1.0 (2026-10-04): first written version.

Test it on someone new

Hand the procedure to a person who has never done the task - or to an AI assistant - and watch. Every place they stop or guess is a missing step. Fix it, then test again. If you test with an AI assistant, keep private information out of the procedure you paste.

One honest wrinkle: if the helper still needs you, ask which kind of need it is. A missing fact is a documentation gap - write it in. A judgment call - refund or not, how to answer an angry email - may be a decision you keep. That is not a documentation failure. Name it in the exceptions: "ask me if X" is a valid step.

Keep it alive

Put the date on it. When a tool changes or a step breaks, update the procedure that day. A procedure nobody updates turns into a trap - it looks like help and behaves like a rumor.

Which phase are you in?

Your first SOP - six lines

Six lines give you the skeleton of a real procedure. Write them for one task you repeat. If a line is hard to write, that line is the work.

Your next step

A written procedure is exactly what an AI assistant can run. Put your first SOP in front of one: running work through AI agents.

Note. Rae and her class planner are fictional, written for practice; the bonus-email SOP is a fictional example with sensitive fields excluded - it names no real logins, customer data or store. In the example the planner itself is delivered automatically at purchase; the weekly email is a promised bonus for current buyers, not delayed fulfillment.