The Nut Graph: Setting the Scene Before the Number

Opening Scene

A headline announces: “City Water Rates Rise 8%.” True, specific, and led with correctly. But the very next paragraph — the one most readers actually read — doesn’t repeat the number. It explains why it matters: this is the third increase in two years, it follows a drought that strained the reservoir, and it lands hardest on residents in the district least able to absorb it. That paragraph has a name in a newsroom: the nut graph. It’s the “so what” that turns an isolated fact into something a reader has a reason to care about. Strip it out, and the headline number just sits there, technically true and functionally inert.

A data report that leads with a number and moves straight to the next chart has skipped exactly this step.

In Plain English

The nut graph is the context, immediately following the lede, that explains why the headline finding actually matters — the comparison, the trend, the stakes, or the history that turns a bare number into something meaningful. A metric on its own has no inherent significance; “8%” means nothing until you know what it’s being compared against, whether it’s unusual, and who it affects. Writing the nut graph well is the difference between a reader nodding at a number and a reader understanding why they should act on it.

The Old Way

Without a deliberate nut graph, data communication tends to leave context out entirely or scatter it in the wrong place:

The bare number — presenting a metric with no comparison point at all, leaving the reader to supply their own sense of whether it’s good, bad, unusual, or routine, which they usually can’t do accurately without domain expertise the report should have provided.
Context buried in an appendix — the historical trend, the benchmark, or the driving factor that would explain the number’s significance exists somewhere in the report, just three sections away from the number it’s meant to explain.
Context as an afterthought in the Q&A — the “why does this matter” explanation only ever gets delivered verbally, when someone in a meeting asks, rather than being written into the report where every reader can find it.

Each of these treats context as optional decoration rather than as the thing that actually makes a finding usable.

What’s Changing (and Why AI Is the Reason)

AI can now automatically retrieve and attach comparison context to a raw number — historical trend, peer benchmark, seasonal norm — far faster than an analyst pulling each comparison manually. What used to require separately querying last year’s figure, the industry average, and the seasonal baseline can now happen as a single automated step alongside the headline metric itself.
This makes selecting the right comparison, out of many available ones, the harder and more important task. A model can retrieve five different valid comparisons for the same number — year-over-year, versus target, versus peer group, versus forecast — but only a human who understands what the reader actually needs to decide can choose which comparison genuinely explains why the number matters here.
Automatically generated context raises a new risk: technically accurate comparisons that are contextually misleading. A number can be compared against a chosen baseline that happens to make it look better or worse than the fuller picture warrants, and an AI system optimizing for “provide a comparison” has no inherent sense of which comparison is the honest one, which is a judgment a nut graph, well written, has always had to make deliberately.

The Metaphor, Fully Extended

Newsroom Element	Data Storytelling Concept
The paragraph right after the headline explaining why it matters	The nut graph — the context that turns a bare finding into a meaningful one
A headline number with no sense of whether it’s unusual	A metric presented with no comparison point, benchmark, or trend
Context buried three sections into a long dispatch	Explanatory context placed far from the number it’s meant to support
An editor asking “so what?” of every draft before it runs	The discipline of checking that every headline finding has its stakes explained
A wire service auto-attaching last year’s figure and the sector average to a new number	AI automatically retrieving comparison context alongside a headline metric

For Beginners: What to Actually Do

After stating your headline finding, immediately answer, in the next sentence or two, “compared to what, and why does that comparison matter?”
Choose one comparison deliberately rather than listing every available one — a nut graph with five competing comparisons is as unhelpful as a nut graph with none.
Place context immediately after the finding it explains, not in a separate section the reader may never reach.
When an AI tool auto-attaches a comparison to your metric, check that the comparison it chose is actually the fair one, not just the first one available.

For Practitioners and Leaders: The Deeper Layer

Add “does this finding have its context immediately attached” as a specific, checkable item in your report review process, distinct from checking that the finding itself is accurate.
When adopting AI tools that auto-generate comparisons, review which baseline they default to and confirm it’s the contextually honest one for your reporting, not just the technically available one.
Recognize that omitting a nut graph is a subtler form of misleading than an outright wrong number — the reader draws their own, often incorrect, conclusion about significance when none is provided.
Train your team to distinguish “providing a comparison” from “providing the right comparison,” since the two are easy to conflate once comparison generation is automated.

Quick Recap

The nut graph is the context immediately following a finding that explains why it actually matters — the comparison, trend, or stakes behind the number.
Without it, reports default to bare numbers, buried context, or context that only surfaces verbally when someone asks.
AI can now auto-retrieve comparison context fast, but choosing the right comparison among several valid ones remains a human judgment.
Automated context introduces a real risk of technically accurate but contextually misleading comparisons, which a deliberate, honest nut graph has always had to guard against.

Where This Fits in the Series

Article 4 established ordering a piece by importance; this article covers what belongs immediately after the lede — the context that makes it matter. Article 6 looks at a specific, powerful kind of context: the narrative turn, where what actually happened contrasts with what was expected.