Data Storytelling Template 1
Data story Decision/question: [x] Main finding: [x] Baseline/comparison: [x] Key evidence: [2–4 numbers] Visual, if useful: [x] What the data shows: [x] What it does not establish: [x] Implication/next step: [x]
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Strong data storytelling starts with the decision or question, selects only the evidence needed to answer it, gives readers scale and comparison, distinguishes observation from explanation, and ends with a consequence, recommendation, or next question that is proportionate to the evidence.
Data story Decision/question: [x] Main finding: [x] Baseline/comparison: [x] Key evidence: [2–4 numbers] Visual, if useful: [x] What the data shows: [x] What it does not establish: [x] Implication/next step: [x]
Observation → context → implication Observation: [measured pattern] Scale: [baseline, denominator, time] Exception/segment: [x] Possible explanation: [clearly labeled] Decision implication: [x]
Executive data story Headline finding: [x] Why it matters: [x] Evidence: [x] Risk/guardrail: [x] Decision requested: [x] What to monitor next: [x]
Chart narration check Audience question visible? [ ] Units and denominator clear? [ ] Comparison fair? [ ] Visual adds information? [ ] Causal wording justified? [ ] Exception hidden? [ ] Action proportional to evidence? [ ]
Source-ledger and revision-history audit for Data Storytelling: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].