There is a particular kind of notebook page that holds four arrows, two half-finished sentences and a phone number with no name beside it. It made perfect sense on Tuesday. By Friday it reads like somebody else's shopping list. The notes were never really the problem. The problem is what happens next, when you need to turn that sprawl into something you can use. Summarising is a writing job before it is an admin job, and a few habits make a real difference.
Start with what the summary has to do
Before you touch the notes, answer one question: who will read this, and what will they do with it? A summary you'll revisit next month is a different document from one you'll send to a colleague who wasn't in the room.
Write the answer at the top of the page as a single line. Something like Decisions and owners from Thursday's planning meeting, or What I need to check before booking the flights. That line becomes a test you can apply to every sentence you keep. If a line doesn't serve the purpose, it doesn't belong — however interesting it was at the time.
Purpose also sets length. A summary for someone who missed the discussion needs a little context and plain definitions of any shorthand. A summary for yourself can be brutal and brief, because you already hold the background.
Put the conclusion first
Most useful summaries open with the outcome and then explain it. Compare this:
Notes. Discussion about the budget. Several options were raised. Concerns were mentioned about the timing of the review.
with this:
The budget rise was approved. Spend will be reviewed in June. Timing of that review is the open question.
The second version tells you what changed in eight words. The first makes you read to the end and still guess. If your summary buries the point under three lines of set-up, swap the order. Readers skim; give them something worth landing on.
Headings that carry information
A heading is the most valuable line on the page, and most people waste it. Notes, Discussion, Other and Update say nothing. They cost a line and return nothing.
Try headings that state the content instead:
- Travel spend is creeping up
- Three options for the winter schedule
- What we still don't know about the supplier
- Actions for next week
Keep them short, keep them parallel in style, and front-load the words that matter. If a heading works, a reader can find the one line they need without reading anything else. That is the whole point of writing it.
A quick way to test a heading
Cover the section underneath. Does the heading make sense on its own? If not, rewrite it until it does. Headings that survive this test are usually the ones that show up in your memory a fortnight later.
Plain English beats tidy phrasing
Summaries fail most often through padding, not through missing information. The instinct to sound careful and complete leads to sentences that circle the point. Cut the scaffolding and the meaning usually survives intact.
Watch for these, and fix them as you draft:
- Buried verbs. Make a decision becomes decide. Provide an explanation becomes explain.
- Filler phrases. In order to becomes to. Due to the fact that becomes because. At this moment in time becomes now.
- Passive sentences. The form was approved by the board hides nothing, but The board approved the form is shorter and names the actor.
- Long clauses. One idea per sentence. Two short sentences beat one tangled one.
None of this means writing stiffly. Plain English is not the same as flat English. Specific detail is what makes a summary worth keeping: the name, the figure, the reason behind the decision. Adjectives rarely earn their place.
Before and after
Following a discussion regarding the timeline, it was agreed by the group that the launch date would be moved to the second week of April.
becomes
The group moved the launch to the week beginning 8 April. Reason: the venue was booked until then.
Pick a structure that matches the material
There is no single right shape for a summary. Match it to the content:
- Decisions and actions: a two-column list of what and who, with a date beside each.
- A talk or lecture: a heading per theme, one or two lines underneath.
- A chapter or report: one short paragraph per argument, in the order the author made them.
- A conversation: questions on the left, answers on the right.
- Research reading: a bullet for each claim, with the evidence noted next to it.
When in doubt, bullets beat paragraphs for reference notes. Start each bullet with the key word rather than a wind-up, and keep them roughly the same length so the page looks scanable rather than accidental.
Prune without losing the thread
Run a delete test over the finished draft. Take each sentence and ask whether removing it would leave anything unclear or undoable. If the answer is no, cut it. Most first drafts of a summary lose a third of their length this way without losing a single fact.
Two things are worth protecting. Numbers and names, because they are the details you will want in six weeks. And the reasoning behind a decision, because a bare decision without its reason gets relitigated. Leave one line at the bottom for loose ends — Still to confirm: the delivery date — which is often the most useful part of the whole page.
The twenty-second test
Read your summary once, then close the document. Can you say what happened, what comes next and who is doing it? If you have to open it again to answer, the structure needs work, not more words.
A short routine keeps summaries consistent:
- Write the purpose line at the top.
- Draft the headings before the content.
- Fill in one idea per line, in plain English.
- Cut anything that changes no decision and no action.
- Date it and note where the original notes live.
Keep a standard template for anything that recurs — weekly meetings, reading notes, project logs — and you will only ever format it once. The point of a summary is not to look tidy. It is to make the next conversation, decision or piece of work easier, and to spare you from re-reading a page of arrows to find out what you already knew.
Photo: borevina / Pixabay
