How to create a checklist your team actually uses: structure, template and the step to an AI employee
A checklist is a short list of the points that have to be done or checked in a recurring task before things move on. Knowing how to create a checklist is easy. Checklists that actually get used day to day are rarer. Often they sit in a folder nobody opens, or they're so long that nobody reads them to the end. In this article, we show what a business checklist is good for in a business with a team and what it isn't, how to structure one, a template to copy and how ticking boxes turns into a report once an AI employee takes over the work.
What a checklist is good for, and what it isn't
A checklist doesn't replace knowledge. It catches the spots where people who know their job still miss something. That happens mainly in three situations:
- When someone gets interrupted. Anyone who takes a phone call in the middle of a task often doesn't remember exactly where they were. The checklist shows them.
- Before a step you can't undo. A quote has been sent, an invoice issued, a payment made. Before steps like these, a short stop with a few fixed checks pays off.
- At handoffs. When a task passes from one person to the next, the checklist records what's already done and what's still missing.
A checklist is less useful in two cases. First, when a task needs judgment: whether a difficult customer gets a discount isn't on any list. We call this the difference between thinking and doing. Second, when a workflow has many variants. Then the checklist gets too long, and what you really need is a work instruction or a process profile for the whole process.
Checklist, work instruction, process profile: what goes where
In many businesses, these three get mixed up. But they answer different questions:
- The process profile, our word for a process description, describes an entire process by five points: trigger, start, the work for each variant, end and report, plus the escalation path. It answers what the process is and who's responsible for it. The template is in How to document business processes: the template for handing a process to an AI employee.
- The work instruction describes the steps precisely enough for someone to follow them without asking, including variants and hard limits. How to write one is covered in How to write an SOP or work instruction that a person and an AI employee can follow.
- The checklist is the shortest of the three. It only contains the points that have to be checked at one specific stopping point.
A good rule of thumb: the checklist points to the work instruction when someone doesn't understand an item. It doesn't repeat it.
Two kinds of checklists
Before you write, it's worth deciding how the list will be used. A common distinction is between two kinds:
Read and do. The person reads an item, does it, ticks it off and moves to the next one. This fits workflows that rarely come up or that someone is just learning, such as setting up a new workstation.
Do, then confirm. The person works from memory, the way they're used to, and goes through the list at a fixed stopping point to make sure nothing is missing. This fits routine work someone knows well, such as sending out a quote.
Most checklists in a small business are of the second kind. That's why they can be short. Someone who knows the job doesn't need instructions. They need a moment to double-check.
How to structure a checklist
Seven rules for a checklist that gets used:
- One purpose, one stopping point. Every checklist belongs to exactly one moment in the workflow: before sending, after receiving, at the end of the day. If the title says when it's used, it gets used.
- Only the critical points. What goes on the list is what often gets forgotten or gets expensive when it's missing. What everyone does anyway stays off.
- Worded so it can be checked. Every item can be answered with yes or no. "Customer number in the subject line" can be checked; "pay attention to completeness" can't.
- In the order of the work. The list follows the workflow, not importance. Otherwise your eyes jump back and forth.
- Short enough for one look. Our house rule: if it doesn't fit on one screen, it's really a work instruction.
- Who ticks it off, and where does the record go? A list that nobody signs off leaves no trace. Write down who uses it and where the result is kept.
- Version and upkeep. Every checklist has a date and a person who maintains it. If a mistake happens that the list should have caught, an item gets added. If an item hasn't been needed for months, it comes off.
A checklist template to copy
Copy this template into a text file or a spreadsheet and fill it in once for each stopping point.
Checklist for: the name of the task and the stopping point, for example "Quote, before sending".
- When it's used: At which step exactly? Who starts it?
- Who checks: Which role ticks it off? Which role gets asked when an item is answered with no?
- Check items: one item per line, answerable with yes or no, in the order of the work.
- What happens on a no: The task stops and goes to the named role. Who, how, by when?
- Record: Where is it noted that the list was gone through?
- Reference: Where is the work instruction in case an item is unclear?
- Version: Date, who maintains the list, when it was last changed and why.
Item 4 is the most important one, and most checklists don't have it. A list that only says what gets checked, but not what happens on a no, pushes the decision back to you. We call this route the escalation path: if a case is unclear, it goes to a person on your team, and afterwards the new variant becomes a rule.
An example: a checklist before sending a quote
Here's what a "do, then confirm" checklist can look like for a business that sends quotes by email:
Checklist: quote, before sending. Used by: whoever prepares the quote. On a no: back to the person who approves the pricing.
- Customer and contact match the inquiry.
- The scope matches the inquiry; any differences are named in the text.
- The pricing is approved, and the approval is noted.
- The quote shows how long it's valid.
- Attachments are complete and open properly.
- The quote is saved in the customer's folder.
- A follow-up reminder is set.
Seven items, all answerable with yes or no, and none of them calls for judgment. The judgment, meaning whether to quote and at what price, sits in the pricing approval. It stays with a person.
Checklists in a quality manual
If you work to a standard such as ISO 9001, you know checklists as part of the quality manual, alongside process descriptions, forms and responsibilities. We don't describe here what a standard requires in detail. For a small business without certification, less than a full manual is often enough. When a manual makes sense and what's enough instead is covered in Creating a process manual: does a business with ten people need one, and what is enough instead.
With or without a manual, checklists for business only work if they're kept in one place everyone on the team knows. How to bring your business's knowledge into a place like that is covered in Business systems: how the knowledge in your head becomes something your team can use.
From ticking boxes to a report: what an AI employee does with a checklist
A checklist is one of the simplest ways to get knowledge out of your head and into a system. Once it exists, someone else can work through it. That can be a new colleague or an AI employee.
For an AI employee, little changes about the checklist itself, but a lot changes about its effect:
- The check items become fixed steps. The AI employee goes through them on every run, the hundredth one too, and on a hectic day too.
- Ticking boxes becomes a report. After every run, you get a message: what's done, what's still open, where there's an exception. The record creates itself.
- The no becomes the escalation path. If a check fails, the AI employee doesn't guess. It sends the case to a person on your team, and the new variant gets trained.
One limit stays in place. For decisions about people, about money and with legal consequences, our house rule is that a person stays involved. In the sample checklist above, that's the pricing approval. How to decide who decides what is covered in Delegating tasks without them coming back to you as questions. And how your team checks every run in the early phase is covered in Autonomy Level 1, Assisted: when your team checks every run.
What this looks like for us
One checklist is a fixed part of every process for us: sign-off, meaning the decision of when an AI employee may work on its own. It's the "sign-off points" field in our process profile, and it has four checks: every variant has been trained. The escalation path has been triggered once. There are four clean runs. There has been a period of side-by-side monitoring. Only when all four are answered with yes does the AI employee run on its own with a report.
At a tax advisory firm, sign-off for filing digital tax assessment notices looked like this: the AI employee was trained one type of assessment at a time, with someone sitting next to it, and signed off after four clean runs. After that, the team monitored side by side for a while. Since then, filing runs on its own and reports back with a completion email. At that firm, it was 2 weeks from the first observation to sign-off; how long it takes in your business depends on the process. The process is at Autonomy Level 2, Autopilot, as of September 2026.
The completion email after every run replaces ticking boxes: whoever reads it doesn't have to check for themselves whether the run went through.
Runs without me
Every two weeks, one process that runs without the owner: what came in, what the AI did, where a person decided. Two minutes to read.
Worksheet
Process Potential Check
With five questions and a first process list to fill in, you find the process that could run on its own first. Comes as a PDF by email once you confirm your sign-up.
Strategy session
In a 20-minute strategy session, you tell us where things get stuck. We'll tell you honestly whether an AI employee is a good fit for you.
Book a strategy sessionFrequently asked questions
How long should a checklist be?
Short enough to fit on one screen. That's our house rule, not a standard. If it gets longer, there's usually a work instruction hiding in it, and that belongs in its own document.
Checklist or work instruction: which do I need?
The work instruction describes how something is done. The checklist checks, at one stopping point, whether it was done. For a process someone is taking over for the first time, you usually need both.
Paper or digital?
That depends on where the work happens. If the work is done at a computer, the list needs to be there. More important than the medium is that the record ends up in a fixed place.
Can an AI employee work through a checklist?
Yes, if the items are worded so they can be checked and it's clear what happens on a no. Then ticking boxes turns into a report after every run. Items that call for judgment stay with a person.
Where can I find a checklist template?
Above, in the section "A checklist template to copy". A template for the whole process is in the article on process documentation.
Read more
A checklist is often the first step toward an automated workflow. Kevin collects examples of workflows that can be automated with AI in Automating Processes With AI: 8 Examples. How new colleagues get up to speed with checklists is covered in Employee onboarding checklist: bringing new people up to speed when you've been explaining everything yourself.
Your next step
Which checklist in your business only gets worked through today because you're standing next to it? On the call, we look at whether Owner Autonomy is a fit for your business and which process is worth starting with. That's also where we go over how it works and what it costs.