Record Why a Publication Check Does Not Apply

Use a not-applicable status only when a check genuinely falls outside the current edition. Record the reason, the relevant specification, and what change would make the check necessary. Keep unresolved work visible instead of using the status to make a checklist appear complete.

Define the scope of the checklist

Identify the book, edition, formats, and files the checklist covers. A print-only release may not need an ebook navigation review, while an ebook-only release will not use a print wrap cover. The scope should explain those differences before individual rows receive a status.

Avoid using one generic checklist for every possible project without adapting its scope. A long list can still be useful as a starting reference, but reviewers need to know which items belong to the actual release. Otherwise, an empty row can mean anything from irrelevant work to a forgotten requirement.

Separate inapplicable from incomplete

Use distinct statuses for a completed check, an unresolved finding, a check not yet performed, and a genuinely inapplicable item. These states answer different questions. A file that has not been exported cannot pass an export review simply because there is nothing available to inspect yet.

Write the distinction in the working instructions. If a reviewer cannot determine whether a requirement applies, keep the question open and identify what information is needed. Uncertainty about scope is not evidence that the check can be omitted.

Record a concrete reason for each exception

Tie the reason to a specific fact about the edition. A note that the current release contains no ebook is stronger than a generic phrase such as unnecessary. It allows a later reviewer to understand the decision without reconstructing the whole conversation that produced it.

Be careful with apparently absent features. A manuscript may contain no photographs but still include diagrams or decorative images that require review. Check the actual file inventory before marking an image-related task inapplicable. A category name in the outline does not prove what the finished files contain.

Identify changes that would reopen the check

Record the condition that would make the item relevant. Adding an ebook would activate its navigation checks. Adding a full-page illustration could affect the print layout review. A revised cover or a new language edition may create other dependencies that were absent from the original scope.

Use these triggers during change review. The purpose is not to predict every possible future revision, but to preserve the obvious relationship between the exception and the decision that justified it. A status should not become permanent merely because it appeared in an older release checklist.

Review exceptions against current requirements

Compare the exception list with the current guidance for the intended format and the actual publication workflow. An internal preference does not make an applicable platform requirement disappear. Resolve mismatches by changing the file, revising the scope, or obtaining the information needed to evaluate the requirement.

Keep technical applicability separate from editorial judgment. A book without an answer key may not need an answer-key cross-check, but the author still needs to consider whether the exercises provide adequate review support. Removing one checklist task does not establish that the underlying reader experience is complete.

Close the checklist with visible limitations

Before final handoff, read every not-applicable entry and confirm that its reason still matches the selected files. Check for late additions that changed the scope. Preserve the list of exceptions with the completed review record so the result describes exactly what was and was not examined.

Use that record when preparing another edition. Reassess inherited exceptions instead of copying their statuses automatically. A useful checklist makes the publication process easier to inspect because it distinguishes completed work from justified exclusions and unresolved tasks, rather than forcing every row into a misleading green state.