A checklist is an ordered set of actionable items whose completion can be explicitly marked. In rocket manufacturing, checklists control complex work because important steps must not depend on memory. section 4.1 section 4.1.1
A reusable checklist has two phases: defining a template for the work, then running instances of that template to perform and record the work. section 4.1.1 section 4.1.3
Model the checklist by separating stable instructions from run-specific state:
- Represent each actionable item as a Step with a name. section 4.1.3
- Represent a Template as a named collection of steps. section 4.1.3
- Represent an Instance as a named, dated run-through of a template. section 4.1.3
- Represent completion as Status associated with an instance and a step. section 4.1.3
International travel checklist
A template can contain steps such as Passport, Toothbrush, and Bring socks. Completion belongs to a particular run rather than to the reusable template, so a new instance starts with its own status. section 4.1.3
Figure 4.1 The checklist!

Use the checklist figure to anchor the distinction between labeled items and their explicitly marked completion state. section 4.1.1




