N · Checklists

The Checklist Set

Seven working checklists. Tickable in the browser, printable on one or two pages, and deliberately shorter than they could be.

Chapter 36 gives the gate entry criteria in their canonical form. These pages are the working versions: expanded where practitioners asked what a criterion means, grouped by the activity rather than by the gate, and usable during the meeting rather than after it.

G1 qualification and provisional risk G2 architecture and data readiness G3 deployment authorization G4 material change G5 retirement
The five gates in order. Each gate consumes evidence produced between gates: the classification, data, assurance, agent and runtime checklists cover that work, and the gate checklist covers the decision itself.

How these work

  • Ticks are local. Each checklist stores its state in your browser, per page. Nothing is transmitted, nothing is shared between people, and clearing site data clears it. Use it to keep your place in a session, not as a record.
  • The record is elsewhere. A completed checklist is not evidence. The evidence is the record the checklist told you to complete.
  • Print for the meeting. The print button gives you the checklist without the navigation, sized for one or two pages.
  • Shorten them. These are deliberately close to the shortest defensible version. If a line does not change a decision in your organization, delete it locally and say why.

[Practice recommendation] Resist the urge to extend a checklist after every incident. Checklists grow monotonically unless someone owns removal, and a checklist nobody finishes is worse than a short one everybody does. Review length annually and cut.