How to Write a Process Checklist Anyone on Your Team Can Follow

A process checklist is one page of numbered steps that lets someone other than you do a recurring job the same way every time. To write one, pick a job that only you know how to do, do it once while writing down every click and decision, then hand the list to someone else and watch them follow it without help. Fix every spot where they get stuck. That is the whole method. The rest of this guide shows which jobs to start with, what goes on the page, and how to keep it from going stale.

Why write down how your business runs?

In The E-Myth Revisited, Michael E. Gerber asks owners to imagine their business as the prototype for a franchise: a model so clearly written down that someone with ordinary skills could run it the same way in another town. You may never franchise anything. The exercise still works, because it forces one question: if you were away for two weeks, could anyone else do this job?

In most small businesses the honest answer is no. Payroll lives in the owner’s head. The bookkeeper knows which supplier always invoices twice. The person who set up the website is the only one who knows where the domain is registered. That works until someone gets sick, quits or goes on holiday, and then a routine job turns into a crisis.

A written checklist fixes three things at once. The job gets done the same way every time. Someone new can learn it from the page instead of from you. And you can hand it off, to a hire or to an outside team, without losing how it was done.

Which processes should you document first?

Don’t try to write down everything. A pile of half-finished documents helps nobody. Score each recurring job against the questions below and start with the one that gets the most yes answers.

For most owners, the first three checklists are payroll, the HST return and month-end bookkeeping. They score yes on the first three questions, and a slip carries a penalty. If you want the deadlines that go with them, our guides to payroll remittance deadlines and HST filing deadlines in Ontario list the 2026 dates.

What goes in a process checklist?

Keep it to one page. If a job needs more than about fifteen steps, split it into two checklists. Every checklist needs the same seven parts:

1. Name of the job, in the words your team already uses.
2. When it happens: the trigger or the date, such as “the 3rd business day of each month”.
3. Owner: the one person responsible for doing it, and a backup.
4. What you need before you start: the tools, files and logins, by name and location.
5. Numbered steps, one action each, starting with a verb.
6. How you know it’s done: the result someone could check, such as “the difference is $0.00”.
7. Last reviewed: a date, and who reviewed it.

Write in plain words. The reader is the newest person on your team, not you. Where a step involves a decision, write the rule: “If the amount is over $500, ask the owner before paying.” A screenshot helps for software steps. A sentence of why helps for steps people are tempted to skip.

What does a finished checklist look like?

Here is a worked example for one of the most common back-office jobs. Your version will name your own bank and software.

Notice what the example leaves out. It doesn’t explain accounting. It doesn’t contain a password. It does say where each file goes, which matters for the next reason.

Where should passwords and records go?

A checklist should say where a login lives, never what it is. Name the password manager entry and who can grant access. When the person leaves, you change one password and the checklist still works.

Your CRA business account is the one login you should never share at all. The CRA lets you authorize a representative from the Profile page of My Business Account, which gives an employee or outside bookkeeper their own access that you can remove later. Form AUT-01 covers offline access by phone, mail, fax or in person, not online access.

Records matter for the same reason. The CRA says you generally must keep required records and supporting documents for six years from the end of the last tax year they relate to. That applies to the 2026 tax year. A checklist that says “save to Finance / Bank / 2026” means the statement and the reconciliation are in one place when you need them, whoever did the work. If your files are already scattered, our bookkeeping health check is a good place to start.

How do you test a process checklist?

The test is simple and most people skip it. Give the checklist to someone who has never done the job. Sit beside them and say nothing. Every time they hesitate, ask a question or open the wrong screen, write it down. Those are the gaps.

Then fix the page, not the person. If they missed a step, the step was unclear or missing. If they made a judgment call you disagree with, the rule wasn’t written down. Run the test again with the fixed version. A checklist is ready when someone new can finish the job from the page alone and get the result in the “done when” line.

How do you keep process documents current?

A checklist that describes last year’s software is worse than none, because people trust it. Three habits keep them accurate:

• Update when something changes. New software, a new rule, a new person doing the job, or a mistake that the checklist didn’t prevent. Each of these is a reason to open the page that week.
• Review once a year anyway. Pick a quiet month and read every checklist. Tax rules and deadlines change annually, so anything tied to the CRA gets checked against canada.ca, not memory.
• Keep them in one place. A shared folder you own, named the way your team thinks, such as Payroll, HST, Customers. Not in someone’s personal email.

Doing it yourself or handing it off

Writing your first checklists takes a few evenings, and you will learn things about your own business along the way. The table shows the trade-off.

Writing the checklist is also step three of handing a job off. Our guide to outsourcing the back office covers the other steps: choosing the first job, setting up access and agreeing on what you will see each month.

Process documentation as part of your back office

Intersect runs the back office for small businesses in Guelph and across Ontario, and process documentation is part of our admin and back-office support. We write down how each job is done today, run it, and keep the checklist current, so the knowledge stays in your business and not in one person’s head. We’re based on Carden Street in downtown Guelph, we’re Indigenous-owned, and a real person answers the phone. See everything we handle on the services page, or tell us which job you’d write down first.

Frequently asked questions

What is the difference between a process checklist and an SOP?

A standard operating procedure (SOP) is the formal version: purpose, scope, roles, steps and sign-off. A process checklist is the working version, one page of numbered steps someone ticks off while doing the job. Most small businesses need the checklist first. Write the full SOP later, only for the jobs where a mistake is expensive or regulated.

Which business processes should I document first?

Start with the jobs only one person knows how to do, the jobs with a deadline or penalty attached, and the jobs that touch money. Payroll, HST filing, invoicing and month-end reconciliation usually come first. Leave rare, simple jobs until last.

Should I put passwords in a process checklist?

No. Write where the login lives, such as the password manager entry name, and who can grant access. Never write the password itself. For your CRA account, authorize the person as a representative instead of sharing your login.

How often should I update a process checklist?

Every time the tool, the rule or the person changes, and at least once a year even if nothing seems different. Put an owner and a review date at the top of every checklist so somebody is responsible for it.