Run before publication, the honesty checklist prevents distortion; run after a challenge, it only excuses it

What it is

The honesty checklist's value depends on when it runs: run before publication, it is quality control that intercepts distortion before circulation; run after a challenge, the same checklist is merely defense material—the problems it finds have already been absorbed by readers, and the retrospective audit cannot recall the misleading impression already formed. This item is the timing constraint on the whole checklist group: without the "before publication" requirement, the five checks before it can all degenerate into post-hoc window dressing.

Why it happens

Timing matters because misleading is asymmetrically reversible: once a distorted chart is seen, the reader's first impression is formed, and even a subsequent correction reaches and persuades far fewer people than the original (corrections typically reach only a fraction of the original audience, while the seen distortion keeps anchoring memory). The communication-research consensus is that corrections are significantly less effective than the original message's spread—"primacy" is not rhetoric but memory mechanics. Moving the check earlier exploits the same asymmetry from the good side: interception at zero readers costs least and pays most. The timing requirement also has an organizational function: it turns checking from personal virtue into a process node—a mandatory checklist bound to the publish action (unchecked means unpublished) does not depend on the maker's memory or conscientiousness, whereas "post-challenge" checking triggers only on discovered failures, covering the caught subset of risk rather than all of it. Pre-publication check records (who, when, which items passed) additionally constitute the organization's evidence of "reasonable effort to prevent misleading"—an important boundary of responsibility when disputes arise.

Where it stops holding

Pre-publication checking is not a perfect gate: it can be executed formally while skipped substantively (ticking boxes without verifying), which requires a companion spot-audit mechanism (periodically comparing published charts against their check records). The tension between checking and publishing speed is also real—time-critical content (monitoring alerts, live push) cannot carry the full checklist; the solution is a tiered checklist (high-risk charts checked fully, low-risk charts on sampled items), not abandoning the timing requirement. The checklist items themselves need updating as failure modes evolve (new chart types create new distortions), and updating the checklist should itself be on a schedule—the meta-rule of pre-publication checking. Finally, pre-publication checks do not replace post-publication supervision: reader challenges remain an important signal for finding the checklist's blind spots, and the response-to-challenge process complements the pre-publication gate.

Applying it

• Bind the honesty checklist to the publishing workflow: the publish action requires all items checked with checker and timestamp recorded; incomplete means unpublished.
• Tier the checklist by chart risk: outward/decision-facing charts check every item; internal exploratory charts check the critical subset.
• Establish a post-hoc audit: monthly spot-check the consistency of published charts against their check records; inconsistency means the process has become formalized.
• Verification: sample 5 published charts' check records and compare them with the charts' actual state; missing records or mismatched records mean the checklist was not genuinely run before publication.

Related

• Same group: U10.04.1 Check whether axes start at zero or are truncated or broken · U10.04.2 Check whether data range, filter conditions, and exclusions are stated · U10.04.3 Check whether title and annotation claims are supported by the graphic itself · U10.04.4 Check whether uncertainty, missing proportion, and sample size are labeled · U10.04.5 Check whether the conclusion changes under another reasonable rendering
• Nearby: U10.04.5 Check whether the conclusion changes under another reasonable rendering · U8.07.2 Data source and update time must accompany the chart
• Search terms: pre-publication review · publishing workflow · quality gate