A chart's credibility depends on its source and update time traveling with it, not living in the maker's head

What it is

Every chart is a claim about data, and the claim's credibility depends on "where the data came from, when it was last updated, and how it is defined." If this information lives only in the maker's head and does not travel with the chart, the chart becomes unsupported the moment it leaves its original context—screenshotted, forwarded, or pulled up three months later, readers cannot judge whether it is trustworthy, current, or defined in a way relevant to their question. Presenting source and update time with the chart is not decorative metadata; it is the chart's qualification as evidence.

Why it happens

Provenance information works by supplying the inputs for credibility assessment up front: when judging "can I trust this number," readers need the chain—what institution or system produced it (authority), when it was last updated (freshness), how it is defined (relevance). Missing any link blocks the assessment, leaving only blind trust or blind suspicion, neither a rational treatment of evidence. Traveling with the chart is necessary because charts propagate: in the original system, sources may be reachable by "clicking through," but charts are screenshotted and forwarded far more often than viewed in place, and once out of context, the on-chart annotation is the only provenance that travels. The update timestamp also serves another function—aligning the chart with business events temporally ("was this collected before or after the promotion launched?"); without it, temporal alignment with other information cannot be done. The minimally sufficient set is three lines of small text: data source (system/table/institution), data as-of or update time, and the definition or a reference to the definition document. These are mandatory in formal reports and screenshots; on real-time monitoring walls they can be reduced to the update time alone.

Where it stops holding

Provenance detail should scale with the chart's evidentiary stakes: routine team-meeting charts need brief labeling, while externally published or decision-driving charts need complete provenance (definition document links, pipeline versions). For real-time sources, the update-time label also doubles as a freshness alert—it should change color when the update stalls beyond its normal interval (extending into the same group's timestamp semantics). Multi-source charts need per-source attribution, not a single label (extending into the same group's alignment problem). Finally, provenance should live at the chart level, not the page level: a unified footer at the page bottom is lost when a single chart is extracted, whereas chart-level footnotes or title suffixes travel with the image.

Applying it

• Build three provenance slots into chart templates: source, as-of/update time, and definition reference; chart makers must fill them or explicitly mark "internal data."
• Auto-fill the update time from the system and change its color when data stalls; never rely on manual upkeep.
• Make screenshot and export functions carry the provenance footnote by default so out-of-context charts remain traceable.
• Verification: randomly screenshot three circulating charts and check whether the chart alone answers "where from, as of when, defined how"; any unanswerable question is a provenance gap.

Related

• Same group: U8.07.1 Definition changes create spurious trends · U8.07.3 Merging multiple sources requires stating the alignment method
• Nearby: U7.09.3 Data must carry a visible timestamp · U8.07.1 Definition changes create spurious trends
• Search terms: data provenance · source citation · freshness indicator