CHK.2:4.1 - Carry the question and its interpretation together

Take the selected questions and coverage from CHK.1 or another adequate source. Identify information shared across the list, such as the physical set and comparison description. Place it where users can see its scope. Keep question-specific conditions with the question.

Phrase the questions in the language practitioners use for their actual work: the card set, print run or catalogue import. Adapt the selected subjects, conditions and questions as well as their names. Replacing “target system” with “cards” is insufficient if “ready” still hides an unfamiliar or unsuitable account of readiness. Compare the wording with a real case and the recipient’s way of working. EXD.1 helps recover the explanation needed for that use. Framework distinctions can guide the author’s reasoning without requiring every recipient to learn their terminology.

Develop ambiguous headings with someone who understands the work. For a printing checklist, distinguish the person who wrote the comparison description, the system assigned to checking, and the system that actually performed this check. One person may occupy all three positions, but a name under “Responsible” does not tell the recipient which relation is asserted. A system’s role kind and assignment, its capability and its performed work remain distinct; OCE.6 helps when the assignment or enabling arrangement itself needs repair. For a file or description, name the actual relation, such as input to printing or basis of comparison. Use the resulting practitioner wording in the form and retain further explanation only where it helps interpretation.

For each answer, make recoverable what is being asked, what counts as an answer and what grounds could support it. A direct instruction may name the observation; a more complex judgement may point to a domain procedure. ME.8 supplies the broader description of how to carry out the Method. A short checklist can refer to that description without trying to replace it.

Distinguish a reusable instruction from a filled claim. “Count the cards against the contents description” is part of the template’s help. “Twenty cards present in S, observed at 10:00” is an instance answer and its basis. FPF A.3.2 supplies the MethodDescription distinction where the template substantively describes a Method; a table label alone does not establish that membership.