What a checklist is, and why it is different
A checklist is a structured, reusable list of items to be done or confirmed, each with a tick box, in an order that matters. It exists for one reason: human memory is unreliable under pressure, fatigue, and routine, and a checklist moves the burden of “did I do every step?” off your memory and onto paper. You design it once for a recurring process and run it every time that process happens.
That reusability is what separates a checklist from a to-do list. A to-do list is a collection of one-off tasks for today, in any order, discarded when done. A checklist is the same every time — every flight, every shift handover, every new hire, every trip — because the process is the same every time. “What do I need to do today?” is a to-do list. “What are the exact steps to do this correctly, every time?” is a checklist.
This is a list-plan page with a builder: define your items, set who is responsible if it is a shared list, and print or save it as a reusable template.
The evidence: checklists save lives, not just time
The case for checklists is not productivity folklore — it is one of the best-evidenced ideas in operational practice.
The landmark example is the WHO Surgical Safety Checklist: a 19-item list introduced in 2008, run by surgical teams at three points (before anaesthesia, before incision, before the patient leaves the room). It confirms catastrophic-to-miss basics — correct patient, correct site, allergies, equipment, antibiotics. Studies across multiple countries associated its use with significant reductions in surgical deaths and complications. Nineteen items, consistently used, measurably saved lives.
Surgeon and writer Atul Gawande’s The Checklist Manifesto explains the mechanism: in complex, high-stakes work, failures usually come not from ignorance but from skipping a known step — a step the person knew perfectly well, but missed under load. The checklist catches the known steps so human attention is freed for the parts that genuinely require judgement. Aviation learned this decades earlier; medicine, construction, and finance followed. The humble tick box is serious infrastructure.
Read-do versus do-confirm
There are two ways to use a checklist, and choosing the right one matters:
- Read-do — used like a recipe: read each step, do it, in order. Best for unfamiliar tasks or strict-sequence procedures (a startup procedure, a deployment runbook) where the order is part of the safety.
- Do-confirm — used as a safety net: do the work from training or memory, then run the checklist to confirm nothing was missed. Best for experienced people doing a known task (a surgical team confirming patient and site before incision).
Read-do instructs; do-confirm verifies. Using a tedious read-do list with experienced staff who know the job insults their competence and gets ignored; using do-confirm gives them a quick backstop against forgetting. The builder lets you mark which type yours is.
What makes a good checklist item
Every item must be a single, concrete, verifiable action — something you can look at and say “done” or “not done” without argument.
- Bad: “Make sure everything is ready.” (Vague, unverifiable, gets skipped.)
- Good: “Confirm passports are in the bag.” / “Send the agenda to attendees.” / “Back up the database before deploy.”
If you cannot immediately judge an item done-or-not, break it into smaller, clearer items. “Tidy the kitchen” becomes “wipe counters”, “empty bin”, “run dishwasher” — three checkable items instead of one fuzzy one.
Keep it short, or it dies
The most common reason checklists fail is length. A checklist that is too long stops being used — people skim it, skip it, or resent it. Aviation checklists are deliberately brief, listing only critical, easy-to-forget “killer items”, not every conceivable step. The discipline is ruthless: cut anything obvious, anything never forgotten, anything that does not change the outcome if missed.
If a process genuinely needs many steps, split it into several focused checklists — one per phase — rather than one overwhelming list. A short checklist that gets used beats a comprehensive one that gets ignored every time.
Order, responsibility, and sign-off
Order matters only where it matters. Some checklists are sequence-critical (safety steps that must precede others: “isolate power before opening the panel”). There, enforce the order. Others are just collections to confirm (a packing list), where any order is fine — group those logically (by room, by category) for ease rather than forcing a false sequence.
Responsibility and sign-off matter for shared checklists. Adding a “responsible person” field per item removes the gap that lets steps fall between people (“I thought you had it”). For handovers, onboarding, and event setup, naming who owns each step — and a completion tick or sign-off — turns a checklist into an accountability tool. For solo checklists, skip it.
Common mistakes
Mistake 1: Making it too long. Comprehensive checklists get ignored. Cut to the critical, easy-to-forget items.
Mistake 2: Vague, unverifiable items. “Be prepared” cannot be ticked. Every item must be a concrete done/not-done action.
Mistake 3: Confusing it with a to-do list. A checklist is reusable for a recurring process, not a one-off task dump. If it is single-use, it is a to-do list.
Mistake 4: Wrong checklist type. A read-do list for seasoned experts is patronising and gets skipped; a do-confirm safety net respects them. Match type to user.
Mistake 5: Including obvious items. Listing steps nobody ever forgets adds length and dilutes the items that matter. Only list what actually gets missed.
Mistake 6: No owner on a shared list. Without named responsibility, steps fall between people. Assign each item on team checklists.
A note on exporting from this site
You can fill in the builder above and export it as a PDF or print it — which is exactly right for a checklist you want to tick off on paper, laminate for repeated use, or pin up at a workstation. You can also keep it as a reusable template and duplicate it each time the process recurs, which is how a checklist is meant to be used.
The one minor gap: it does not yet output a live spreadsheet with auto-counting or shared tick-state that a team edits simultaneously in real time. For a shared, simultaneously-edited checklist, a Google Sheet or a dedicated checklist app is the better tool. For a personal or printed reusable checklist — which is the vast majority of use — the PDF/print export is exactly what you need.
Worked example
Priya runs a small co-working space and keeps losing time on inconsistent end-of-day closing — sometimes the alarm is not set, sometimes the kitchen is left on. She builds a do-confirm closing checklist, because her staff are experienced and need a safety net, not instructions.
She lists only the steps that have actually been forgotten in the past (building it from failures, not from scratch): lock the back door, switch off the coffee machine, set the dishwasher, turn off the meeting-room screens, check no one remains in the building, set the alarm, lock the front door. Seven items — short enough that staff actually run it.
Because closing is a shared responsibility across a small rota, she adds a “responsible” field and a sign-off: whoever closes ticks each item and initials the sheet. She marks it as a do-confirm checklist, prints a week’s worth, and clips them by the front door. The alarm-not-set incidents stop within the first week — not because the staff did not know to set the alarm, but because the checklist catches the one night someone is distracted and forgets. When a new closing step emerges (a new fire door), she adds it and reprints. The checklist earns its value through repetition, exactly as designed.
Checklist types by purpose
The general template adapts to most needs, but it helps to recognise the common families of checklist, because each has a slightly different design emphasis:
Process checklists. A fixed sequence for a recurring operational task — closing a shop, deploying software, onboarding a new hire, handing over a shift. The emphasis is completeness and consistency: the same steps, every time, so nothing is forgotten between repetitions. These benefit most from a “responsible person” field when more than one person is involved.
Packing and preparation lists. Travel packing, event kit, conference materials. Order rarely matters; grouping does (by bag, by category, by day). The value is catching the one item you always forget. These are the most personal — your packing checklist should be built from the things you specifically tend to leave behind.
Verification / safety checklists. Confirming that conditions are correct before a consequential action — pre-flight checks, equipment safety, the surgical checklist. These are usually do-confirm, short, and ruthlessly limited to the critical items, because their power comes from being run reliably every single time.
Quality / acceptance checklists. Confirming a piece of work meets a standard before it ships — an editorial checklist before publishing, a QA checklist before release, a definition-of-done in software. Each item is a quality criterion, and the checklist is the gate between “I think it’s finished” and “it’s actually finished”.
Compliance checklists. Confirming a regulated process was followed — data-protection steps, health-and-safety requirements, financial controls. These often need a sign-off and a retained record, because the checklist is also evidence that the process was carried out.
Recognising which family yours belongs to tells you whether to prioritise order (process, safety), grouping (packing), criteria (quality), or record-keeping (compliance).
Building a checklist culture, not just a checklist
A single good checklist helps one process. The larger gain comes when a team treats checklists as a normal tool for any recurring, error-prone task — and that takes a small culture shift, because checklists can feel, to skilled people, like an insult to their competence.
The reframe that overcomes this is the one from aviation and surgery: checklists are not for the incompetent; they are for the competent operating under load. A surgeon who uses the WHO checklist is not a worse surgeon — they are one who recognises that anyone, on a bad day, under fatigue, can skip a known step, and that a thirty-second confirmation is cheap insurance against a catastrophic miss. Pilots, among the most rigorously trained professionals alive, run checklists on every flight. The status signal of a checklist is reliability, not inexperience.
Practically, a checklist culture means: the people who do the work design the checklists (not managers imposing them); checklists are kept short and revised when they fail; and running the relevant checklist is simply part of how the work is done, not an extra step bolted on. When checklists are owned by the team and built from real near-misses, they stop feeling like bureaucracy and start feeling like the team’s accumulated memory of “here’s how we avoid the mistakes we’ve made before”.
UK and US notes
Checklists are universal — the structure and the discipline are identical in the UK and US. The only differences are vocabulary on specific items (a “rota” in the UK is a “schedule” in the US; “torch” vs “flashlight” on a safety list) and spelling on labels. The evidence base is international: the WHO Surgical Safety Checklist is used worldwide, and Gawande’s research spans both countries. Whatever the process, the rules that make a checklist work — concrete verifiable items, sensible order, short enough to use, reused every time — hold on both sides of the Atlantic.