Method

How to write a checklist people actually follow

A checklist is abandoned for one of two reasons: it asks for a judgement, or it lists things nobody would forget.

5 min read

A wish

Something you can see is done

Check plumbing

Pressure-test plumbing for 24 hours

Sort out the permit

Permit number received in writing

Make sure cabinets are ordered

Cabinet order confirmed, delivery date in notes

Final walkthrough

Every snag-list item ticked or waived by the client

In short

  • Write each step so that someone else can see it is done. “Check plumbing” is a wish; “pressure-test plumbing for 24 hours” is a step.
  • Only list what actually gets forgotten. Obvious steps train people to skim.
  • Change the list after every run — the version that survives three projects is worth more than any template.

Most checklists are written once, by one person, in a hurry, and then quietly ignored. The failure is almost never laziness. It is that the list asks the reader to make a judgement call, or that it is padded with steps nobody could possibly forget, which teaches everyone to skim it.

Five rules

  • Write each step as something you can see is done. “Check plumbing” is a wish; “pressure-test plumbing for 24 hours” is a step.
  • Keep each phase short. If a phase has more than eight or so steps, it is probably two phases.
  • Only list what gets forgotten. Steps people would never skip just add noise.
  • Put steps in the order they happen. A list that makes people jump around gets abandoned.
  • Leave room for notes. The decision made on site is often more valuable later than the tick itself.

The first rule carries most of the weight. A step that can be argued about will be argued about, usually at the worst moment.

A wish

Something you can see is done

Check plumbing

Pressure-test plumbing for 24 hours

Sort out the permit

Permit number received in writing

Make sure cabinets are ordered

Cabinet order confirmed, delivery date in notes

Final walkthrough

Every snag-list item ticked or waived by the client

The same four steps, written as a wish and written so they can be checked.

Give the phase an outcome, not just steps

Steps describe activity. An outcome describes what you are holding when the phase closes — the permit number, the signed-off snag list, the tested circuit. Writing the outcome down is what lets someone who was not there tell whether the phase is really finished.

One phase at a time, with the steps that are left and a single way out of it.

Then improve it after every run

The first version of any checklist is wrong in small ways. After each project, spend five minutes changing the flow: remove the step nobody needed, add the one that caught you out.

After three or four projects you will have something no template could have given you — a record of how your work really goes. That is the part worth keeping, and it is the reason to write the list somewhere you will come back to rather than on the back of a drawing.

Put it into practice

Build your first flow, or start from a ready-made one, in a couple of minutes.

Read next