How to Write a Numbers Heavy Story Clearly for Journalists 2026

To write a numbers heavy story clearly, find the one finding the data actually supports, give every figure a denominator and a baseline, round it to what the data can bear, and attach it to something a reader can picture. Everything else belongs in a graphic or a methods note. Most of that work happens before you write a single sentence of the lede.

The workflow below is what I use when statistics carry the argument rather than decorate it: homicide files, hospital readmissions, budget lines, polling, climate records, quarterly earnings. On a well-built story it takes about two hours on top of the analysis, and roughly half of that is deciding what not to publish.

Six moves, in order:

1. Find the one finding the data supports, and write it as a sentence with no numbers in it.
2. Give every figure a denominator and a baseline — what is being counted, over what period, out of what population, compared with what.
3. Separate headline figures from evidence, then round both to the precision the data can actually bear.
4. Put one number in each sentence and pair it with meaning in the same breath.
5. Move patterns into a chart instead of narrating a series of values in prose.
6. Verify, attribute and disclose the limits, including sample size and margin of error, before the copy leaves the desk.

Here is how each of those moves works in practice.

What You Need

Five things, and you cannot skip the first two without publishing something you will have to correct.

• The dataset and its documentation. Not the file, the codebook or methodology note. You need to know what one record is: one person, one admission, one reported incident, one parcel, one inspection.
• Your own analytical notes. The exact query, every filter, every exclusion, and the date you ran it. If you cannot rebuild the headline figure from those notes in five minutes, the figure is not ready for copy.
• A spreadsheet to recompute from scratch. One clean sheet with raw counts in one column, rates in another, and the rounding applied by formula rather than typed. Hand-typed arithmetic is where stray percentages come from.
• A second reader for the numbers. Practitioners on r/Journalism ask the same question over and over: who fact-checks the numbers when there is no data editor? The honest answer in most shops is a colleague on another beat who re-runs your top three figures without seeing your sheet.
• A charting tool and reader context. For the pattern, not the finding: Flourish, Datawrapper, Tableau or a plain spreadsheet all work. Reader context means knowing who reads this beat and what they already believe about it.

One more piece of preparation has become unavoidable. Threads on r/Journalism keep surfacing the same complaint about AI-generated drafts carrying plausible-looking figures with no source attached. If a number in your draft cannot be traced to a query you ran or a document you hold, it does not go in, no matter how confident it sounds.

Step-by-Step: How to Write a Numbers Heavy Story Clearly

Define the story’s central finding

A dataset supports one finding well. Write that finding as a single sentence containing no numbers at all — “the city’s overdose deaths fell for a second straight year, and almost none of the drop happened in the neighborhoods hit hardest” — before you select a single figure.

If you cannot do that, you do not have a story yet. You have a spreadsheet. Test the finding against impact, proximity, prominence and timeliness, and if it fails two of the four, keep digging before you start writing.

How to tell it worked: every other number you gathered either supports that finding, complicates it, or moves to the graphic. Anything that does none of those three was never in the story.

Separate essential numbers from supporting evidence

Sort the figures into three tiers. The headline tier is one or two numbers for the whole story. The supporting tier is context: the comparison year, the national average, the target set by policy. The evidence tier is everything that only makes sense when arranged — by year, by ward, by district, by age band.

That third tier should leave the prose entirely and go into a chart, a table, a caption or a methods note. The test is brutal: if the reader can lose that number and still follow the argument, lose it.

Then apply the ceiling most borrowed from investigative reporting guidance: no more than about eight digits per paragraph. It comes from the IRE handbook Numbers in the Newsroom, and it is the single most useful editing heuristic I know. Eight digits covers roughly a percentage with a denominator and one comparison.

How to tell it worked: no sentence in the draft contains two separate figures. If one does, split it or cut one.

Add context and explain the denominator

A number without a denominator is a decoration. Four questions have to be answerable for every headline figure: what is counted, over what period, across which population, and compared with what baseline.

Choosing the right base matters as much as choosing the right number. “Per capita” simply means per person, and it hides the population differences you are trying to explain.

Base	Use it for	Plain phrasing
Raw count	Events that are individually comprehensible	About 41,000 trips were recorded
Percent	A share of a population you name in the same sentence	Nearly 12% of residents
Per 1,000	Violence, admissions, police contacts	About 4 in every 1,000 residents
Per 100,000	Rare events: deaths, rare diagnoses, small-area rates	Roughly 9 deaths per 100,000 people
One-in-N	Probabilities and survey results	About one in four adults

Check the baseline too. A change with no comparison point is a direction, not a finding, and “surged” without a prior peak and a long-run trend is usually just a bad year read against a bad one. Watch also for averages of averages: a statewide figure built from county averages weights a county of 4,000 the same as one of 400,000.

How to tell it worked: a reader could describe each figure’s denominator from memory after one pass.

Write the numbers into ordinary sentences

Say the number the way you would say it out loud to a colleague. “About one in four residents” beats “24.7% of residents”. “Somewhere between three and four in every 1,000” beats “3.7 per thousand”. Move the decimal when the number is small enough to trip on it — four-tenths of an inch, rather than 0.38 inches, when the comparison is with other small quantities.

Pair the figure with meaning in the same sentence, or the next one. Which is the right denominator for the reader: a household, a ward, a shift, a school year, a single paycheck. Numbers land when readers can convert them into something they already know.

Watch the phrasing traps. “Times more” is ambiguous in English — three times as many or three times more? Give the percentage change instead. And separate a percentage point from a percent change: a rate moving from 2% to 5% rose three percentage points, which is a 150% increase, and the first number is usually the honest one.

How to tell it worked: read the draft aloud. Where you run out of breath, there is a number pile-up.

Show the pattern instead of repeating the data

Some numbers cannot be written well in prose because the shape is the point. A rise and fall across decades, a gap between two districts, a distribution where the average hides everything. Those go in a chart, and the sentence before it tells the reader what to look at.

Keep the finding in the text and the series in the graphic. Label the axes with real units, start bar charts at zero, skip three-dimensional anything, and annotate the line that matters directly on the chart instead of in a footnote. Where space is tight, the footnote is the first thing lost.

Accessibility is part of clarity, not a separate task. Do not encode meaning in colour alone, keep type large enough to read on a phone, describe the takeaway in alt text in plain words, and publish the underlying table under the chart so screen reader users and skeptical readers can both check you.

How to tell it worked: the chart makes the sentence beside it shorter. If it does not, cut the chart.

Verify, attribute and disclose uncertainty

Recompute the top three figures independently, from the raw file, without your working sheet in view. Two people, two results, same number. Then ask the question GIJN’s reporting guidance keeps recommending: what have I forgotten? Usually the answer is a population that changed mid-period, a category that was recoded, or a query that silently truncated.

That last one matters more than reporters expect. A suspiciously round figure is often a download limit, not a finding — the free tier of a data platform may have capped your export at 500 rows without saying so. Check the raw count against the published total before you build a paragraph on it.

Round to what the uncertainty supports. If a survey has a three-point margin of error, two significant figures is the honest ceiling; printing one decimal place implies precision nobody measured. Estimates, forecasts and projections get labelled as such in the sentence, and the source plus its vintage appears in the same sentence as the number.

Publicly reported corrections make the best classroom here. A widely circulated mix-up between eight million and eight billion in federal spending figures came from a misplaced decimal, a documentary’s runtime was reported as rent owed, and a manufacturer’s fatality figure was compared across vehicles without any mileage or exposure denominator at all. None were hard maths. All were missing context.

How to tell it worked: every headline number in the draft has a named source, a period and a population somewhere within one sentence of where it appears.

How to edit a numbers heavy story for comprehension and fairness

The final pass is mechanical. Read it aloud and mark every sentence carrying two or more figures. Check scale consistency across the piece — millions in one paragraph, billions in the next, with no signal to the reader that the scale changed. Strip causal verbs from correlational findings, and check every “because”, “drove” and “led to” against what your method can actually support.

Then do the outside-reader test. Give the lede and the first three paragraphs to a colleague who does not cover the beat and ask them to say what the story claims. Their wrong answer is your fault, not theirs, and it costs five minutes.

Last check on framing: does the headline verb match the finding, or does it reach? Does the chart’s axis start where a reader would assume? Would the same number, plotted differently, tell the reverse story?

A never-write-this, write-this-instead rulebook

This is the crib sheet I keep beside the draft. It covers the phrasings that cause the most corrections and the most arguments in edit.

Never write this	Write this instead	Why
Costs rose four times	Costs quadrupled, or rose 300%	“Times” is ambiguous in English
The rate went from 2% to 5%	The rate rose 3 percentage points, a 150% increase	Points and percent changes are different things
1.4% of the group	About 14 in every 1,000 people in the group	Small percentages are hard to picture
41,233 trips were taken	About 41,000 trips	The extra digits are false precision
512 victims were identified	About 500 victims	Rounding costs nothing and reads faster
Rainfall was 0.38 inches above normal	About four-tenths of an inch above normal	Move the decimal on small quantities
A 0.03% increase in demand	Demand was essentially flat, at 3 more per 1,000 orders	Name the absolute change or drop the figure
GDP grew 2.9% year over year	The economy grew about 3% last year	Match precision to the uncertainty
Deaths per capita fell	Deaths per 100,000 residents fell	Per capita hides the population
The new rule cut cancellations 46%	Cancellations fell from 84 per 1,000 to 45 per 1,000, a 46% drop	Show the before and after, not the percentage alone

Common Mistakes

These ten failures account for most of what gets flagged on data desks, and most were documented in practitioner panels and newsroom threads rather than invented here.

1. Too many numbers in one sentence. The reader stops parsing and starts guessing. Split the sentence or cut one figure.
2. Totals presented as rates. A count of 900 incidents is meaningless without the population it occurred in. Compute the rate, then decide which form to publish.
3. A missing denominator. Never leave the base implicit. Name the population in the same sentence as the percentage.
4. False precision. Extra decimal places imply an accuracy the method never had, and readers tend to treat them as confidence.
5. “Times more.” Ambiguous between times as many and times more. Use the percentage change or “twice as many”.
6. Averages of averages. Unequal group sizes get equal weight. Compute from the underlying counts.
7. Rounded figures treated as findings. A suspiciously round total is often a truncated download, not a story. Verify against the raw count.
8. Causal verbs on correlational data. “Drove”, “led to” and “because of” claim a mechanism your method cannot see. Say “was followed by” or “moved alongside”.
9. Misleading graphics. Truncated bar axes, 3D effects and colour-only encoding all distort the reading the chart appears to support.
10. Unattributed figures. Any number without a source and a vintage is a rumour with decimal places. Name both in the sentence.

Two more worth naming. Arithmetic slips get screenshotted and shared for years, so recompute anything that looks odd rather than assuming it is fine. And a finding that fits a popular narrative too neatly deserves a second analyst, because the tidiness is usually the tell.

Frequently Asked Questions

Conclusion

Start with the finding, not the file. Write the story’s claim in one sentence with no numbers in it, check that every figure has the denominator and baseline that sentence implies, and then cut until a reader who skips the charts still follows the argument. Clarity in a numbers heavy story is not a style pass at the end. It is the difference between a finding that lands and one that gets screenshotted as an error.

Last updated: October 2026