Write a Checklist That Actually Gets Used

Why this matters

A good checklist is how you make sure the same job gets done right by anyone, every time, without you standing over it. It catches the step that gets skipped when someone is rushed, protects against the expensive miss, and lets a newer tech perform like a careful veteran. But most checklists fail. They are too long, too vague, written by someone who does not do the work, and they end up ignored or filled out blind. A checklist that gets used looks very different from one that gets written and forgotten. The skill is in the design.

What a checklist is for, and what it is not

Be clear on the job a checklist does, because that shapes how you write it.

• A checklist is a memory aid for the steps that matter and get missed. It is not a full instruction manual. It assumes a competent person and reminds them of the things that are easy to forget or skip under pressure.
• It is for the critical and the forgettable, not the obvious. Do not put "drive to the job" on it. Put the verification step that, when skipped, causes a callback.
• It exists to catch the failure, so every item should earn its place by preventing a real, known problem. If you cannot say what skipping an item would cost, it probably does not belong.

Keep it short, or it dies

The single biggest reason checklists get ignored is length. A fifty-item list is not used, it is rubber-stamped, which is worse than no list because it gives false confidence. Discipline the length:

• Aim for the vital few. The handful of items that, if missed, cause real harm. A short list that gets used beats a thorough one that gets ignored every time.
• Cut anything obvious or trivial. If a competent person never forgets it, it does not need to be on the list.
• Split a giant process into a few short checklists tied to natural points in the job (before start, before sign-off) rather than one wall of items.

A checklist should be glanceable. If it does not fit on a screen or a card, it is too long.

Write items as clear, checkable actions

Vague items get vague compliance. Each line should be a specific thing a person can clearly mark done or not done.

The strong versions leave no room to interpret "done" loosely. A good item names the action and the standard for done in one line.

Two kinds of checklist, used differently

Borrowed from how aviation does it, there are two patterns, and they are not interchangeable.

• Do-list: read the item, then do it. Used for an unfamiliar or rare procedure where the list is teaching the sequence as you go.
• Confirm-list: do the work from memory and skill, then run the checklist to confirm nothing was missed. Used for routine work the person already knows. This is the more common type in a shop, and it is a backstop, not instructions.

Match the type to the situation. Handing a confirm-list to someone doing a job for the first time leaves out the teaching. Forcing a veteran to read a do-list for routine work is slow and patronizing, and they will stop using it.

Build it with the people who do the work

A checklist written in the office and handed down gets ignored. One the crew helped build gets used, because they trust it and it reflects how the work really goes.

• Draft it from real jobs, especially from the after-action reviews of things that went wrong. Every recurring failure is a candidate checklist item.
• Have the people who do the job review it. They will catch the item that is impossible as written, the step that is out of order, and the missing item that bites every time.
• Pilot it on real work before you make it standard, and fix what does not fit.

Maintain it, or it goes stale

A checklist is a living document. The work changes, tools change, and a list that no longer matches reality gets dropped. Keep it current:

• When a checklist item proves wrong or pointless, fix it. Do not make people keep following a step everyone knows is dead. That teaches them the whole list is optional.
• When a new failure pattern shows up, add the item that would have caught it.
• Periodically prune. Items accumulate. Cut the ones that no longer earn their place so the list stays short.

A stale checklist is worse than none, because it trains people to ignore checklists.

The test of a good checklist

Ask: would skipping this list cause a real, known problem, and is the list short enough that a busy person actually runs it instead of rubber-stamping it? If both are yes, you have a checklist that gets used. If the list is long, vague, or full of obvious items, it will quietly die no matter how thorough it looks on paper.

References

• See related: After-Action Review: Learning From a Bad Job
• See related: Standardize the Truck Setup Across Crews
• Trade-standard practice for quality control and process documentation