The short answer
Write one entry per process, and give every entry the same eight parts: the trigger, what done looks like, the steps in real order, the exact numbers and words, a rule for each decision point, the exception path when something goes wrong, the limits the reader must not cross, and the date and owner of the entry. Capture each process in about 20 minutes by talking through it while you do it once, then clean up the notes the same day. Then prove it works: your named stand-in runs the process from the page alone, and every question they have to ask becomes a fix to the page.
Passwords, codes and bank logins never go into a process entry. An entry is meant to be read by someone else under pressure. Write which account a step uses and where access is recovered, and point to the access map in your continuity document. The credentials themselves stay in your own password manager.
The 8 parts of a usable process entry
Leave one part out and the reader has to guess at exactly the moment guessing is most expensive. These eight, in this order, are the whole structure.
| Part | What to write | Why it matters |
|---|---|---|
| 1. Trigger | What starts this process: a client pays, an order arrives, the day opens, a complaint lands. | Without a trigger, the stand-in does not know when the process applies at all. |
| 2. Done looks like | One or two lines describing the finished state, so the reader can check their own work. | A done-check turns “I think I did it” into a yes or a no. |
| 3. Steps in real order | One action per step, in the order you actually do them, including the small steps you no longer notice. | Experts skip steps automatically; a stand-in cannot. The skipped step is usually the one that breaks. |
| 4. Exact numbers and words | The real prices, thresholds, deadlines, file names and the exact wording you use with clients. | “Charge the usual amount” is not usable. The number is the process. |
| 5. Decision rules | For each branch: if this, then that. Cover the two or three branches that actually happen. | Decisions are where a stand-in either improvises or stops. Give them the rule you use. |
| 6. Exception path | What to do when the normal path fails: who to call, what to tell the client, what to write down. | Most first-week damage comes from exceptions handled silently, not from routine work. |
| 7. Limits | What this process never authorises: discounts, refunds, promises or payments beyond the written limits. | Limits protect a helpful stand-in from committing the business while trying to help. |
| 8. Date and owner | The date the entry was last verified, and who owns keeping it true. | An undated entry cannot be trusted, because nobody knows whether it still describes the business. |
Vague vs. usable: one example
The example below is fictional and marked as such. It shows the same task written both ways, so you can feel the difference before you write your own entries.
| Vague entry (fails cold) | Usable entry (runs cold) |
|---|---|
| “Send the client an invoice after the job. Chase it if they do not pay.” | “Trigger: job marked complete. Done: invoice sent and logged. Steps: 1) Open the invoice template named INV-Current. 2) Fill in client, job and the agreed price from the quote — never retype a price from memory. 3) Send from the business email and log date and amount in the open-jobs list. Decision rule: if the amount differs from the quote, stop and check the quote first. Exception: if the client disputes the amount, send the written reply from Client Answers and log the dispute; do not offer a discount. Limit: never change payment terms. Verified: [date].” |
The usable version is longer, but every extra line removes a phone call the stand-in would otherwise have to make to someone who may not be reachable.
The 20-minute capture method
Owners stall on documenting because they picture writing a manual. You do not need a manual-writing session. You need one real run of the process, captured.
1. Do it once, talking out loud
Next time you run the process, say each step as you do it and record the audio on your phone, or type rough notes as you go. Include the clicks, the checks and the “I always look at” moments — those are the steps memory hides.
2. Clean it up the same day
Turn the rough capture into the eight parts above while it is still fresh. One action per step. Replace every vague verb — handle, sort out, deal with — with the concrete action you actually took.
3. Fill in the exact figures
Add the real prices, thresholds, deadlines, template names and client wording. If a figure lives somewhere else, name that place instead of copying a value that will go stale.
4. Add the exception you remember
Ask yourself: what went wrong the last time this process ran? Write that case into the exception path, with who to call and what to tell the client.
5. Date it and file it with the twin
Put the date and your name on the entry and file it in the Processes and Prices layer of your continuity document, next to the Handover Planner starter and the checklist, so the stand-in finds everything in one place.
Which five processes to write first
Do not start alphabetically and do not start with the rarest process. Start where a stand-in will be tested in the first week.
| Priority | Process | Why first |
|---|---|---|
| 1 | Taking payment and sending invoices | Money in is the process clients notice first, and the one with the least room for improvisation. |
| 2 | Paying bills and suppliers | A missed payment can stop supply or premises within days; the due dates must be findable without you. |
| 3 | Opening and closing the day | The daily rhythm holds everything else together: inbox, bookings, orders, cash and locks. |
| 4 | Delivering the main service or product | This is the promise the business exists to keep, step by step, at the quality clients expect. |
| 5 | Handling a complaint or a problem | The highest-pressure process, and the one where your exact words matter most. Use the wording from your client answers. |
Test it: the stand-in dry run
A process entry is a claim until someone else has run it. Three small tests, done on a quiet day, find almost every gap:
- The cold read. Give the entry to your named stand-in and ask them to explain the process back to you without doing it. Every place their version differs from yours is a place the page was unclear.
- The supervised run. Watch them run the real process from the page alone. Do not help. Write down every question they ask — each one is a missing line in the document, not a mistake by the reader.
- The exception question. Ask: “What would you do if this step failed?” If the answer is not already in the exception path, add it the same day, then re-date the entry and log the test in your owner absence plan.
Repeat the dry run at the normal 90-day continuity review, or sooner when a price, supplier or tool changes. The free Continuity Freshness Checker flags any layer that has not been reviewed in 90 days.
Five mistakes that make process notes useless
- Writing for yourself. Notes that make sense to the person who wrote them are reminders, not instructions. Write for a competent stranger who has never watched you work.
- Vague verbs, no numbers. “Handle the order” and “charge the usual” force the reader to invent the process. Concrete actions and exact figures are the document.
- One giant document. A single 40-page file cannot be searched under pressure. One entry per process, titled by its trigger, beats one manual every time.
- No exception path. Routine steps are the easy half. Without the failure path, the first real problem becomes an improvisation.
- Written once, never tested or dated. An untested entry hides its gaps until the worst week. A dry run and a date turn a draft into something a stand-in can trust.
One-page summary checklist
- One entry per process, titled by what triggers it.
- Done-check written first: what the finished state looks like.
- Steps in real order, one action per step, no skipped expert steps.
- Exact prices, thresholds, deadlines, template names and client wording filled in.
- A rule for each decision branch that actually happens.
- Exception path: who to call, what to tell the client, what to log.
- Limits in writing: what the reader must never promise, discount or pay.
- No passwords, codes or bank logins anywhere in the entry.
- Date and owner on every entry; filed in the Processes and Prices layer.
- Dry run done by the named stand-in; every question turned into a fix.
Common questions
How do you document a business process so someone else can follow it?
Write one entry per process with eight parts: what triggers it, what done looks like, the steps in the order they actually happen, the exact numbers and words to use, the decision points with a rule for each branch, what to do when something goes wrong, what the reader must never do, and the date and owner of the entry. Then test it: have the stand-in run the process from the page alone, without asking you, and fix every place they get stuck.
What should every process entry include?
A trigger, a done-check, ordered steps, exact figures and wording, decision rules, an exception path, limits, and a date. If any one of these is missing, the reader has to guess at exactly the moment guessing is most expensive: when the owner is not there to ask.
Which business processes should you document first?
Start with the five that keep money and promises moving: taking payment and sending invoices, paying bills and suppliers, opening and closing the day, delivering the main service or product to a client, and handling a complaint or a problem. Document rare and complex processes later; the daily and weekly ones are what a stand-in will face in the first week.
How long should a process entry be?
As short as it can be while still being followable without the owner. For most small business processes that is one to two pages: short steps, one action per step, and the exact numbers filled in. If an entry needs background explanation, put it in a separate note so the steps stay scannable under pressure.
Should passwords or account details go into process documents?
No. Passwords, codes and bank logins never go into a process entry. Write which account the step uses and where access is recovered, and point to the access map in your continuity document. The credentials themselves stay in your own password manager.
How do you know a documented process actually works?
Only a dry run proves it. Ask the named stand-in to complete the process using only the written entry, on a quiet day, and note every question they have to ask and every step they interpret differently than you meant. Each question is a gap in the document, not a failure of the reader. Fix the gaps, date the entry again, and repeat the test at the next 90-day review.
This guide is general information, not legal, insurance or tax advice. ContinuityTwin is an independent service, not affiliated with or endorsed by FEMA, Ready.gov or the U.S. Chamber of Commerce Foundation, whose public small-business continuity guidance its structure follows.
Want your processes documented for you?
ContinuityTwin turns one written questionnaire — about 1–2 hours, by email, at your own pace — into the complete five-layer twin: processes and prices written so a stand-in can follow them, an access map without passwords, suppliers and contacts, client answers in your own words and a handover package, verified and dated. No passwords are ever asked for, received or stored, and the twin is seen only by you and people you explicitly name.
ContinuityTwin Setup — $69 one-time. Full refund before work begins. Continuity Care — $25/month if you want it kept alive: monthly updates, a quarterly handover refresh, and a flag when a section has not been reviewed for 90 days. Cancel anytime.
Free first: the continuity checklist, the owner absence plan and the Handover Planner cover the inventory and timeline this method fills in.