Common Mistakes in News Summaries: How to Write a Digest People Actually Finish

You can write a completely accurate summary and still lose the reader halfway down paragraph two. Accuracy is not the same thing as clarity. Most digests that get abandoned fail for the same handful of reasons, and every one of them has a fix that takes minutes rather than talent.

Here are the mistakes that cost summaries their readers, what each one looks like on the page, and how to repair it before you publish.

The lead is buried three sentences down

The lead is the single most important thing: what happened, to whom, and what changes as a result. Too many summaries open with the background briefing, or with the announcement of an announcement.

Buried: "Following a lengthy consultation that began last spring, and after a series of meetings with interested parties, the department has now confirmed that changes will be introduced later this year affecting..."

Fixed: "Households will pay more for the service from October. The department confirmed the change on Tuesday after a year of consultation."

The test is simple. Read your first sentence and ask whether a reader who stopped there would know the story. If they wouldn't, the lead is still buried.

How to find the lead quickly

Write one line on what happened, then one line on why it matters. Whichever line would make someone look up from their phone goes first. Chronology is not importance, and the newest development is usually the lead — not the beginning of the story.

The summary assumes the reader has been following along

News reaches different readers at different points. Some have read every update; most have read none. If your summary refers to "the ongoing dispute", "the minister's earlier comments" or "the second phase" without a short reminder, the reader is lost and gone.

The fix is a context clause: a few words, attached to the reference, that say what the thing is.

• Instead of "The regulator's second review concluded...", write "The regulator has been examining the complaints since March. Its second review concluded..."
• Instead of "Following the U-turn...", write "The council had planned to close the site. On Tuesday it reversed that decision..."
• Instead of "The scheme was delayed again...", write "The housing scheme, first approved in 2019, was delayed again..."

Any reference to something that happened before today gets a reminder attached. It costs eight words and keeps the reader in the room.

Where a story touches health, money or legal matters, say plainly what the change means in practice, and add one line reminding readers to check their own position with a qualified adviser. Readers respect the honesty, and it stops a summary from reading like personal advice.

Jargon, acronyms and in-house language

Jargon is efficient inside an organisation and opaque outside it. If a term would send your reader to a search engine, you have handed them a reason to leave. Swap and move on:

• stakeholders — the groups affected, or the people involved
• consultation — a public request for views
• fiscal consolidation — spending cuts or tax rises
• operationalise — put into practice
• utilise — use
• in a bid to — to
• amid — during, after, as

Acronyms get spelled out on first use and shortened afterwards. If a reader would need a glossary to get through 150 words, the problem is not the reader; the story needs cutting back to its essentials.

Hedging that says nothing at all

"Sources say", "it is understood", "concerns have been raised", "questions remain" — these sound careful but leave the reader with nothing to hold. Hedging is sometimes necessary, but it should be deliberate and specific. Name who is saying it where you can. Where you cannot, say why the claim is being reported without a name, in a handful of words.

Watch for the passive voice doing the same job. "Mistakes were made" hides the person who made them. "The company made the errors" does not. Readers trust a summary that tells them who did what, even when the answer is complicated.

Shaped like an article instead of a digest

A digest is not a shortened article. It has a different shape. If you preserve the original structure — the scene-setting, the long quotes, the order in which things happened — you will end up with something long that still misses the point.

A workable shape for a short summary:

1. Lead. What happened, in one sentence.
2. Context. Why it matters, or what came before, in one or two sentences.
3. Details. The two or three facts a reader actually needs, strongest first.
4. Next. What happens now, and when, if that is known.

Quotes work best in small doses. One short quote that captures the disagreement or the mood is usually plenty. A paragraph of quotations belongs in the full story, not in the summary.

Figures without meaning, and wobbly timelines

A number on its own tells the reader very little. A budget cut means something only alongside a comparison, a scale or a consequence — how it compares with last year, who it affects, what it stops. If you cannot supply that, replace the figure with the effect: "the service will close two days a week" lands harder than a percentage nobody can picture.

Timing matters too. "Yesterday" and "this morning" go stale the moment a digest is read later. Use named days and dates instead, and keep your tenses consistent throughout. A reader should never have to work out whether something has already happened or is still being discussed.

A five-minute edit that catches most of this

Before you publish, run the summary through this pass. It takes less time than writing another paragraph.

1. Read only the first sentence. Does it say what happened?
2. Underline any word a neighbour outside your industry wouldn't know. Replace or explain it.
3. Find every reference to something earlier and check that it carries a reminder clause.
4. Delete any opening sentence that sets the scene rather than reports the news.
5. Count the names. Keep the two that matter most and cut the rest.
6. Read the final line. Does it say what happens next, or does it simply stop?
7. Explain the story out loud to someone in one breath. Anything you had to add belongs in the text.

None of this requires a bigger word count or a cleverer turn of phrase. It requires deciding what the story is, saying it early, and removing everything that delays the reader's understanding. Do that consistently and the digests you publish will be the ones people reach the end of.

Photo: freephotocc / Pixabay