How to Write Process Notes People Use
A step-by-step guide to writing short process notes that new helpers can follow without asking questions.
A step-by-step guide to writing short process notes that new helpers can follow without asking questions.
Why do process notes fail when someone new tries to follow them?
They fail because the writer assumes the reader knows things the writer knows but never wrote down. A process note that works is not a polished manual. It is a short map that shows a new person where to start, what to do next, and how to tell when the step is finished. When a helper has to ask a question, the note is missing a decision point, a location, or a definition. The fix is to write for the person who knows nothing about your business, not for yourself.
What should a short process note contain before anything else?
Start with four things at the top of the page: the name of the process, the result it produces, the person who owns it, and the date it was last checked. The result matters most. A note that says "invoicing" is weak. A note that says "send monthly invoices so clients can pay on time" tells the reader why the steps exist. The owner and date stop the note from becoming anonymous folklore. Keep this header to four lines or fewer.
How many steps should a process note have?
Aim for seven to twelve numbered steps. If you need more than twelve, you are probably describing two processes in one note. Split them. If you need fewer than five, the note may be too vague to be useful, or the task may be simple enough that a checklist is better than a note. The goal is not completeness. The goal is that a new helper can finish the task without interrupting you. BDC's operational efficiency guidance points to process improvement as a way to remove waste and increase value, and writing a clear note is a small, practical version of that idea (https://www.bdc.ca/en/articles-tools/operations/operational-efficiency).
Should you write the note in first person or second person?
Write in second person. Use "you" and the imperative. "Open the shared folder" is better than "the folder should be opened." First person notes sound like a diary. Passive notes sound like a policy document. A helper reading "you" knows the instruction is for them. Keep sentences under fifteen words. One action per sentence. If a step needs two actions, write two steps.
How do you handle decisions inside a process?
Decisions are where helpers get stuck. Instead of hiding a choice inside a long paragraph, give it its own step with a question and two outcomes. For example:
- Check whether the client has sent a purchase order.
- If yes, save it in the client folder and continue to step 3.
- If no, send the standard reminder email and stop. Do not start the work.
This pattern turns a silent judgment into a visible fork. It also protects the helper from guessing. A process note with clear decision points needs fewer follow-up questions because the reader can see where they are on the path.
What makes a step easy to follow without asking?
A step is easy to follow when it names the tool, the location, and the finish line. Compare these two versions:
| Weak step | Strong step |
|---|---|
| "Prepare the report." | "Open the monthly report template in the shared drive. Fill in the client name and the date range. Save a copy in the client folder." |
| "Check the numbers." | "Compare the invoice total with the bank deposit. If they match, write OK in the tracking sheet. If they do not match, move the file to the Review folder." |
| "Contact the client." | "Send the update email from the templates folder. Use the subject line shown there. Do not change the wording without asking." |
The strong version answers three questions in advance: where do I go, what do I do, and how do I know I am done?
How do you test whether a process note works?
Give the note to someone who has never done the task. Ask them to follow it while you watch but do not speak. Every time they pause, point to the place where the note failed them. Every time they ask a question, write the answer into the note. One test run usually reveals three to five gaps. Fix only those gaps. Do not rewrite the whole note. A process approach and improvement based on evidence is exactly what a test run gives you: evidence of where the note breaks.
Where should you store process notes so people find them?
Store them in one obvious place, named by process, not by author. "Invoicing note" beats "Maria's notes." Use plain text or a simple document format that anyone can open. Add a short index at the top of the folder so a helper can scan ten process names in one view. If you use a shared drive, give the folder a short link and put that link in the note header. The point is that the note is findable in under thirty seconds, without asking you where it is.
How often should you update process notes?
Update a note when the process changes, not on a calendar. Write the last-checked date in the header. If nothing has changed, leave the date alone. If you change a tool, a client name, or a decision rule, edit the note the same day. A note that is three months out of date is worse than no note because it teaches the wrong steps. A short review routine, like the one in A Weekly Review Routine for Small Firms, can include a quick scan of any notes touched that week.
When should you link a process note to other business documents?
Link a process note to any document it depends on: templates, scopes, status updates, or pricing rules. For example, if the invoicing note requires a signed scope of work before billing, link to Writing a Clear Scope of Work. If the client update note uses a standard status format, link to Status Updates Clients Actually Read. Links keep the note short because you are not repeating information that already exists elsewhere. Check links once a quarter. Broken links are silent failures.
What should you do with questions that keep coming back?
Every repeated question is a missing line in a note. Keep a running list of questions helpers ask you during a task. At the end of the week, add the answer to the note. This is a simple improvement loop, and it costs ten minutes. Over a month, the notes get quieter because the answers are already there. BDC's operational efficiency resources describe process improvement as a way to make a business leaner and more profitable, and this habit is one of the cheapest versions of that work (https://www.bdc.ca/en/articles-tools/operations/operational-efficiency).
Decision checklist: is this note ready to share?
Use this checklist before you hand a note to a new helper.
- The result is written in one sentence at the top.
- The owner and last-checked date are visible.
- Steps are numbered and start with a verb.
- Each step names the tool or folder.
- Each decision has two clear outcomes.
- The note is seven to twelve steps long.
- A new person has tested it once without help.
- Links to templates or related notes work.
- The note is stored in the shared process folder.
- Repeated questions have been added to the note.
If you can tick eight of these ten boxes, share the note. If you can tick fewer, fix the gaps first. The goal is not a perfect document. The goal is that a new helper can follow the note without asking, and that you can spend your time on work only you can do.
