Checklists: a complete guide

A checklist is not a to-do list

They look similar. Both are lists with boxes to tick. But they serve different purposes and work in different ways.

A to-do list is dynamic: items get added and removed constantly, order can change based on priority, and the items often have no relationship to each other. Today's to-do list might contain "email Sarah," "book dentist," and "review proposal draft" in no particular sequence.

A checklist is fixed: it captures the correct sequence of steps for a specific recurring procedure, and the sequence is the point. You don't reorder a pre-flight checklist based on what feels more urgent. You go through it in order, every time, because the order reflects how the procedure should work.

The distinction matters because they solve different problems. A to-do list solves the memory problem: don't forget these things. A checklist solves the consistency problem: make sure these things are always done correctly, in the right order, regardless of who's doing them or how familiar they are with the process.

Why experts use checklists

The most compelling case for checklists comes from surgery.

In 2008, surgeon Atul Gawande worked with the World Health Organization to test a surgical safety checklist in eight hospitals across the world, ranging from a well-resourced facility in New Zealand to a hospital in Tanzania with five surgeons serving thousands of patients. The checklist was simple: confirm the patient's identity, verify the procedure, check that the right equipment is available, ensure all team members know each other's names.

The results were striking. In every site, introduction of the checklist was accompanied by a substantial reduction in complications. In seven out of eight, it was a double-digit percentage drop. Across the study, deaths and major complications fell by around a third to a half.

What makes this striking isn't that the steps on the checklist were obscure. They weren't. Every surgeon in the study knew these steps. The problem wasn't ignorance. As Gawande put it: in fields that have become sufficiently complex, errors of ineptitude dominate over errors of ignorance. The mistakes are not made because we don't know what to do, but because we fail to apply what we already know.

Aviation understood this decades earlier. Pilots don't skip checklists because they've flown ten thousand hours. The experience makes them more committed to the process, not less. The checklist isn't there because the pilot is incompetent. It's there because complex procedures under pressure create conditions where even competent people skip steps they know matter.

The same principle applies far from operating theatres and cockpits. Any procedure where the steps are known, the sequence matters, and the cost of skipping a step is significant is a candidate for a checklist.

What checklists do

Reduce errors. Moving the steps from working memory to an external list removes the cognitive load of remembering them and eliminates the risk of skipping something due to distraction, fatigue, or confidence. You either checked it or you didn't. The checklist doesn't lie.

Improve consistency. When a procedure is done by multiple people, or by the same person across many repetitions, a checklist ensures it's done the same way each time. This is how quality control works: not by relying on people to remember everything correctly every time, but by giving everyone the same external reference.

Create a record. A completed checklist is documentation that the steps were followed. This matters in regulated industries (healthcare, aviation, construction) where compliance needs to be demonstrated, but it's also useful in ordinary work. If something goes wrong, a checklist tells you whether the standard procedure was followed or not.

Enable improvement. Because the steps are written down, they can be reviewed. If you realise there's a better order, or a step that can be eliminated, or a step that's missing, you update the checklist. The process becomes improvable in a way that tacit knowledge never is.

Support delegation. A good checklist lets someone less experienced complete a procedure correctly without needing to hold all the knowledge in their head or constantly seek guidance. This is how complex organisations train new people and maintain standards as they scale.

How to create an effective checklist

Identify the right use cases

Not everything benefits from a checklist. The right candidates are:

Recurring procedures where the same steps need to happen in the same order each time. Morning routines, project kickoffs, content publishing workflows, onboarding processes, deployment procedures.

Procedures where errors are costly. The cost doesn't have to be life-or-death. Sending a client a document with the wrong version number, publishing a blog post with broken links, shipping a product without testing a specific edge case: these are all recoverable errors that a checklist prevents.

Procedures performed under time or cognitive pressure. This is where the aviation model is most relevant. When you're busy or stressed or tired, the chance of skipping a step you know you should take increases significantly.

Write it clearly

Boeing's Daniel Boorman, who helped design the surgical checklist format, described the core principle: a good checklist is not a how-to guide. It confirms that the person doing the procedure knows what they're doing and is following it correctly. This means:

Keep items short. Each item should be readable in a second. "Confirm patient identity" is a checklist item. "Ensure that the full name, date of birth, and allergy status of the patient have been verified against the medical record and confirmed with the patient verbally" is documentation, not a checklist.

Use action verbs. "Check oil level," not "Oil level." The verb makes it clear what you're doing, not just what you're looking at.

Use plain language. If the checklist is used by multiple people, use language they all understand. Jargon is the enemy of consistency.

Get the length right

Gawande's research found that the most effective checklists were short. Long checklists get ignored or rushed through. The key is to include only the steps that actually matter: the ones where skipping them causes problems, not the obvious ones that nobody forgets. If you're tempted to include something just because it theoretically could go wrong, leave it off. A checklist with fifty items is a checklist nobody will use carefully.

Test and revise

The first version of a checklist is rarely the best one. Run it through the actual procedure a few times. Are there steps missing that you only realised once you were doing it? Is the sequence actually right? Are any of the items ambiguous? Revise based on what you discover, and keep revising when you notice things that aren't working.

Keep checklists where you'll use them

A checklist only works if it's used. That means it needs to be available when and where the procedure happens. If it's a digital procedure, have it open in a tab. If it's a physical procedure, have it printed or displayed in the relevant space. Checklists stored in folders you never open are indistinguishable from no checklist at all.

Keeping all your checklists in one searchable place, whether that's a notes workspace or a dedicated folder, makes them easy to find and update. Tagging or naming them consistently means you can search for them by context rather than browsing.

Where checklists are useful

The source material's list is worth expanding:

Morning and evening routines. The procedural elements of your day: take medication, check calendar, clear inbox, review task list. Once captured as a checklist, these stop requiring active memory.

Meeting preparation. Agenda sent? Right people invited? Materials prepared? Decisions from last meeting reviewed?

Project kickoffs. Stakeholders identified? Goals defined? Timeline agreed? Roles clear? Risks considered?

Content publishing. Proofread? Images optimised? Links tested? SEO metadata filled in? Social copy written?

Employee onboarding. Accounts set up? Equipment provided? Key people introduced? Access permissions granted? First tasks assigned?

Software deployment. Tests passing? Documentation updated? Rollback plan in place? Stakeholders notified?

Client deliverables. Final version confirmed? Branding consistent? Contact details correct? File formats match request?

Recurring reports. Data sources up to date? Previous period comparison included? Numbers sense-checked? Charts consistent?

The common thread: a procedure you do repeatedly where getting all the steps right matters and where the steps are known in advance.

Checklists and other systems

To-do list: A to-do list captures what you need to do. A checklist ensures you do specific recurring procedures correctly. Use both: your to-do list might include "publish the blog post," and your checklist tells you everything you need to verify before you hit publish.

GTD: Checklists fit naturally into GTD's reference system. They're procedures, not tasks. In a GTD setup, a checklist lives in reference material and gets triggered when the relevant task appears on your next actions list.

Bullet journal: Checklists work naturally as collections in a bullet journal. Create a collection for each recurring procedure, and use it as a reference when you need it.

PARA: Checklists that relate to specific projects live in those project folders. General-purpose checklists (morning routine, meeting prep) live in resources.

Task management basics: Where task management focuses on deciding what to do and in what order, checklists handle the execution of known procedures. They reduce the cognitive load of the doing itself.

Frequently asked questions

What's the difference between a checklist and a procedure document?

A checklist confirms that a procedure was followed correctly. A procedure document explains how to do something. The difference is scope: a checklist is short and fast to use, designed for someone who already knows the procedure. A procedure document is comprehensive, designed for someone learning it. Complex processes often have both: a procedure document for training and a checklist for regular use.

How long should a checklist be?

As short as it can be while still covering the steps that actually matter. Gawande's research found that shorter checklists are used more carefully and produce better results. If you're finding yourself adding many items, consider whether all of them are actually necessary or whether you're documenting a procedure rather than creating a back-check tool.

Should I use checklists digitally or on paper?

Either works. Digital checklists are easier to update and can be templated so you start fresh each time without resetting items. Paper can be faster in physical environments and doesn't require a device. Many people use both: a digital checklist for computer-based work and a printed or displayed checklist for physical procedures.

Can checklists be too rigid?

Yes. A checklist that covers every conceivable step in a procedure becomes a source of friction rather than help. The checklist should cover the steps where the cost of forgetting is highest, not every step in the process. Leave room for judgment. The checklist confirms that the essentials are handled; it shouldn't replace thinking.

What about creative work where procedures change?

Checklists aren't for the creative parts of creative work. They're for the procedural elements that surround it: the publishing workflow after you finish the piece, the project setup before you start, the review process before you ship. The creative work itself stays flexible. The checklist handles everything else.

How often should I update my checklists?

When you notice something is wrong, missing, or could be better. There's no need to review checklists on a schedule if they're working. But when you make an error that a checklist should have caught, or when a procedure changes, update it immediately while the context is fresh.

The Checklist Manifesto by Atul Gawande (2009) is the defining work on why checklists work. Related guides: To-do list, Task management basics, GTD.