A checklist that keeps the proof you ran it CHECKLIST

A paper checklist's real failure is that a run leaves no trace

The assumed failure is forgetfulness, and checklists are good at that. The actual failure is afterwards. Somebody ticked the box; nobody can say when, or in what order, or whether the item that was left blank was skipped for a good reason or because the pen ran out halfway down the page.

For most lists that does not matter. For a pre-flight, a handover of a firearm, an equipment check before a shift, a calibration, a release to production, the record of the run is worth more than the list itself, because the question that gets asked later is never “did you have a checklist”. It is “show me the one from Tuesday”.

So this is a runner rather than a list. Ticking an item writes the time it was ticked. The run has a beginning, a sequence and an end, and all three are in the record.

Skipping demands a reason

Skipping an item marks it as skipped and asks why, rather than leaving it looking the same as an item that was done. That one behaviour is most of the value here.

A paper checklist where “not applicable” and “done” look identical is a checklist that hides the single item somebody decided not to do, which is, reliably, the item the investigation is about. Making the skip explicit costs the person running it three seconds and turns an invisible gap into a recorded decision with a stated reason, which is both more honest and much better for the person who made it. “Skipped: spare unit not on site, ordered” is a defensible line. A blank box is not.

The timestamps do a quieter job too. A twelve-item list with every tick inside nine seconds did not happen; a list where the times are spread across forty minutes did. Nobody has to accuse anyone of anything, because the record simply shows what it shows, and knowing that changes how the list gets run.

Writing a list worth running

One action per item. “Check the pressure and log it” is two actions and one tick, and under pressure half of it gets done while the tick says all of it did: the same defect SOP exists to find in procedures.

Write the item as the thing you can observe, not the state you hope for. “Valve closed” is checkable by looking. “System safe” is a conclusion, and the person ticking it is guessing.

Keep it short enough to be run properly. A forty-item list gets a run of ticks near the bottom regardless of who is holding it, and that is a property of people rather than of discipline. If the job genuinely has forty steps, it has more than one checklist.

A finished run is sealed with a digest, so a saved record can be shown later to be the record that was made rather than one edited since. Everything stays in this browser until you export it, which means the export is the record: export each run and keep it with the rest of the paperwork. Nearby: SOP writes the procedure the list sits inside, HANDOVER carries what is outstanding to the next shift, and STATEMENT seals an account of what happened the same way.