Checklists for routine and emergency operations

Goal

Make procedures that are performed rarely or under pressure reliable by externalising the steps rather than relying on memory.

Prerequisites

A procedure that has been performed at least once and whose steps can be written down.

Steps

1. List the steps in the order they must happen; keep the list on one screen. If it is longer, split it into phases.
2. Phrase each item so that its completion is observable ("pipeline green on commit X", "backup restored into scratch instance and row count matches").
3. Mark the points of no return (schema migration applied, DNS changed) and the rollback path from each.
4. Include verification items after the change, not only the change itself.
5. Use the list every time, even when the procedure feels familiar; tick items as they are done.
6. After an incident or a near miss, add the item that would have prevented it and remove items that never matter.

Expected result

Fewer skipped steps, faster hand-over between people, and a procedure document that improves with use.

Limits and test basis

Checklists do not replace understanding; they support it. Overly long lists get skimmed. The method is general practice from safety-critical fields, stated here without an empirical claim.