Preface
CHK.Preface:1 - The problem and the contribution
Skilled work can fail through a small omission, a forgotten conversation or an answer that outlives its grounds. More documentation can make that worse when it hides the question, interrupts useful work or rewards reassuring entries. Checklist practice concerns the design and use of a limited attention aid within that wider work.
This framework offers six Methods. Selection establishes which questions are worth carrying. Construction preserves those questions in a reusable template. Fitting arranges a usable occasion and access to truthful answers. Use obtains answers and informs action. Reconciliation connects local answers with the shared result. Qualification tests whether proposed criteria and checking means distinguish what matters.
Choose the Method whose inputs are available and whose result you need. Selection starts from a working problem and descriptions of the result; construction needs selected questions; fitting needs a template and a work arrangement. To use the checklist, interpret its questions for the subject and occasion. Reconcile local answers when people rely on them together; qualify a criterion or checking means when its grounds are uncertain. An existing adequate result can supply any of these inputs.
CHK.Preface:2 - Subjects, descriptions and useful characteristics
A team can describe a seminar set as twenty readable cards with wording v2, assembled for delivery. The actual cards have characteristics. The description says something about those characteristics. The team also assumes that a set with those characteristics will serve its exercise. Comparing cards with the description, testing that usefulness assumption, and deciding what to change are different activities.
A mismatch can reveal a defect in the cards, a mistaken description or an unsuitable intended use. It supplies information for that decision; it does not impose a duty to change the cards. Actual legislative requirements, when applicable, retain their specific source and applicability. They are not the general meaning of a checklist criterion.
A criterion here is the condition or distinction used to interpret an answer. “All twenty described cards are present” and “The wording matches v2” are examples. Their grounds and useful coverage remain open to examination. Some questions use direct observation; others consume an already competent result or a reasoned judgement. Neither a blank field nor a plausible answer supplies missing evidence.
This follows the distinction between a subject, an episteme about it and a selected use of that episteme in FPF E.10.D2. A template describes questions for reuse; a filled record describes answers from a particular use. People and technical systems can perform work. For descriptions, files and card sets, identify the actual relation: for example, a file describes the cards, the cards enter an exercise, and an observation supplies grounds for an answer.
CHK.Preface:3 - Change, simultaneous work and the whole result
Checklist questions select conditions within structures of transformations and structures of states of their subjects. The questions need not form a ladder. Wording can change while a set remains assembled; handling a replacement can defeat an earlier count; two preparations can proceed at once. A table, diagram or graph may represent useful relations, but its layout does not determine the states or transformations.
During a workshop preparation, testing a projected example can contribute both to checking the display and to preparing the session. The whole matters at that moment: a technically sharp image of an obsolete example does not serve the exercise. The relevant FPF B.1.5 Method relations and A.15.10 changed-premise relations help identify what the combined work consumes. A supplied projector enables this work; its availability alone does not establish a performed part of the session preparation.
A missing intermediate ability can stop the combination. Someone able to count cards may lack the judgement needed to select instructional examples. The next contribution is then help with the examples, not another count. The three people may also need the same room at incompatible times. OPS.4 helps make that conflict recoverable across participants. Selecting a feasible resource arrangement is additional coordination work; filling three lists cannot resolve it.
For a fuller account of change and subject states, return to FPF A.3.3, A.3.4 and A.22. These foundations help describe the structures used here; a constructive composition of transformations needs its own justified account. Context-state descriptions in E.18 concern the bindings and locality they describe, rather than every state of a checklist subject.
CHK.Preface:4 - Choosing and combining the Methods
For a recurring omission, select a useful question set with CHK.1, express it with CHK.2 and arrange first use with CHK.3. CHK.4 then produces answers on real occasions. Compare the contribution and burden with ME.14, and use ME.16 to choose a worthwhile change. The result can be a clearer question, a different occasion, new support, or retirement of the aid.
For shared work with uncertain criteria, use CHK.6 to challenge those criteria and checking means. CHK.1 retains the useful coverage; CHK.2 and CHK.3 give participants workable local views. CHK.4 supplies local answers. CHK.5 tests their combined use, locates gaps and reopens affected reliance when premises change. Several Methods can be active within the same larger performance; an earlier result is needed only where another action actually consumes it.
One centralized checklist can be sufficient when everyone has the relevant access and it adds little burden. Separate local lists can be sufficient when their uses are independent. Where people rely on one another, this framework keeps the useful local arrangements and connects only the shared claims that affect work. The cost is maintaining those connections. Use the simpler arrangement when it gives the same practical result.
CHK.Preface:5 - Judging use and learning from it
At framework scale, ask whether the important work questions are covered, their meanings survive the chosen forms, people can answer at the right occasion, the answers have adequate grounds, shared conclusions follow from the contributions actually supplied, and uncertain criteria have been challenged. Inherit adequate answers from prior use; revisit the part changed by new evidence or conditions. Each pattern’s Conformance Checklist makes its own contribution inspectable.
These are questions about sound application, not a demand for a second checklist on every checklist. Recognition begins with the ordinary situations in the Readme and Problem frames. Assurance comes from examining the actual questions, observations, mappings, counterexamples and consequences in the later sections. More completed fields do not establish either useful work or a sound Method.
The constructed examples in this edition illustrate reasoning and possible use. They do not report measured effectiveness. Human-use studies and AI evaluation studies inform the Methods under the limits in Sources and dependencies. Practical adoption still depends on capabilities, access, working conditions and the result people value.
The arrangement favors visible, discussable omissions. It can underrepresent tacit expertise, unusual events and concerns that people cannot safely voice. Keep open inquiry alongside the selected questions. Watch for time displaced from the work, repeated uninterpretable answers, prefilled records and harmful reliance on a narrow pass. Use those observations to change or remove the aid.
CHK.Preface:6 - What this publication preserves and where to return
Checklist tables compress questions, answer meanings and their relation to the work. To interpret or adapt a table, recover the domain knowledge, subject states and work descriptions on which its questions depend. To explain its adoption or effects, examine the wider working conditions. Return to the criterion’s domain source when a judgement exceeds the question set; to the named FPF patterns for stronger ontology or structure claims; to the supplying DPF for Method engineering, capability development, operations or administration.
The source line combines R7/R10’s checklist and coordination practice, Gawande’s historical account of professional checklist use, later human outcome and documentation studies, and current primary work on AI criteria and checking arrangements. Their useful contributions converge on situated questions with accessible grounds. Their differences survive: a human conversation, an executable test and a model judgement supply different observations and burdens. The shared language connects these contributions without treating one as a universal substitute for the others.