A summary has one job: help someone decide whether the original is worth their time, or give them the gist so they never have to open it. That decision takes seconds. Most summaries lose those seconds to throat-clearing, background, and a first sentence that says nothing. The fix is not shorter writing for its own sake — it is writing that starts where the reader's attention already is.
Lead with what the reader needs
Reports are written in the order the work happened. Summaries should be written in the order the reader needs. Those are rarely the same order.
Before drafting, ask three questions. What changes for the reader? What do they have to do about it? What is the one line they would repeat to a colleague? The strongest answer becomes your opening, and everything else becomes supporting detail underneath it.
Take a council publishing two thousand words on waste services. A summary that opens "The council has reviewed its waste strategy" is accurate and useless. "Recycling collections move to fortnightly from March, while food waste is collected weekly" gives a household something to plan around. The consultation, the budget, the reasoning — all of it can follow. None of it belongs first.
The first line does most of the work
Plenty of readers will get through one sentence and no more. Write that sentence as though it is the only one you are allowed. Avoid openers that describe the act of writing rather than the subject: "This article explores", "The report discusses", "The author argues". Say the thing, not the fact that somebody said it.
Test it by covering everything below the first line. Does the sentence still deliver something worth having? If not, keep rewriting until it does. That line also travels on its own — into newsletters, search results, social posts — where nothing else you wrote goes with it.
Cut the scaffolding
Scaffolding is the language that holds a sentence up without carrying any weight. It appears in the same shapes every time:
- "It is worth noting that..."
- "In order to..."
- "It should be remembered that..."
- "The article goes on to explain..."
- "There are a number of factors that..."
The before-and-after is usually obvious. Before: "It is important to note that, in order to reduce costs, the company has decided that it will be closing two of its regional offices." After: "Two regional offices will close to cut costs." Same information, half the words, no loss.
Keep the hedges that do honest work, though. "The trial suggests", "the figures cover England only", "this may not apply if you are self-employed" — those are accuracy, not padding. Where a topic touches health, money or legal matters, keep the caveats intact and point readers to proper advice rather than flattening the uncertainty into a confident claim.
Make it scannable on purpose
Readers scan before they commit. A summary sitting in one solid block of text gets skipped, even a well-written block. A few habits fix most of it:
- One idea per paragraph, two or three sentences each.
- Bold the three or four phrases that carry the meaning — if half the text is bold, nothing stands out.
- Use a list when the source contains steps, criteria, options or figures to compare.
- Start every bullet with a verb or a noun, and keep them parallel.
- Front-load each bullet: the first three or four words should carry the point.
- Break anything running past five lines into smaller pieces.
Then run the bold test. Read only your bolded phrases from top to bottom. If they don't tell the story on their own, they are decoration rather than signposting.
Specifics, not adjectives
"Significant", "several", "a range of", "major improvements" — these tell a reader nothing and quietly wear down trust. If the source gives a figure, use it. If it gives a range, use the range. If it gives nothing, say what it does give: "the report puts no number on it, but says most households in the county are affected."
Do not round up for drama. A summary that inflates a finding gets corrected publicly, and that costs you the reader's confidence in every summary you write afterwards. Where the source is uncertain, stay uncertain.
Names matter too. "The company" becomes the actual company if the source names it. "A study published this month" becomes the organisation and the month. Named things are easier to remember, easier to search for, and easier to trust.
Edit in four passes
Set the length before you start
Decide a target rather than discovering one. For a curated link, 60 to 120 words is usually plenty. For a summary standing in for a long report, 200 to 300. If the reader's question is simply "should I read this?", one tight paragraph beats five loose ones.
- Write the messy version. Read the source properly, take notes, resist shaping anything yet.
- Cut both ends. Delete the first sentence if it is throat-clearing, and the last if it repeats the first. Most drafts improve noticeably with those two deletions alone.
- Read it aloud. Every stumble is a sentence that needs work. Every point where you run out of breath is a sentence that needs splitting.
- Read only the bold text and the first line of each paragraph. If those don't carry the story, reorder until they do.
Putting it into practice
Before publishing, run five checks. Does the first line stand alone? Have you removed every phrase that describes the writing rather than the subject? Can you scan it in five seconds and still get the point? Is there a specific figure, name or date where one matters? And the real test: would you send it to a colleague without adding a note to explain it?
A summary that needs explaining is not a summary — it is a preamble. Get it right and readers start treating your name as a shortcut. They see it, they read it, they know within seconds whether to go further. That is the whole job, and it is worth the four passes.
Photo: Pexels / Pixabay
