How to Write a Summary You Will Still Use in a Month

How to write a summary in five minutes: read the piece once without a pen, then close it and write the main claim in one sentence from memory. Add the two or three points that hold that claim up, and one line on why it matters to you. Aim for roughly a third of the original length at most, and often far less. Check it against the source last, never first. The rest of this guide covers where that process breaks down.

What a summary is actually for

Most advice on how to write a summary comes from classrooms, and it is sound. A summary states the main ideas in your own words, leaves out your opinion, and stays much shorter than the source. One university library guide puts the target at about one third the length of the original article. That rule works for a graded assignment.

It works less well for the person with 200 saved tabs. A summary written for a teacher has to prove you read the text. A summary written for yourself has to answer a different question: will I be glad of this in a month? Those are two different documents, and mixing them is why so many people write summaries once, feel nothing, and stop.

QUEUE: 1 article, 4,800 words, silent read at about 240 words per minute, roughly 20 minutes. The summary you want out of it is under 80 words. That ratio is the whole job.

The one-pass method that survives a busy week

Here is the sequence we use and recommend. It takes about five minutes on top of the reading time.

1. Read the whole thing before you touch anything. No highlighting on the first pass. Highlighting while you read is the most common reason summaries come out as a collage of the author's sentences. You are marking what feels important before you know what the article is about.

2. Close the tab. This is the step people skip, and it is the one that matters. If you cannot write the main claim without looking, you have not understood it yet, and a summary will not fix that. Go back, find the claim, and try again.

3. Write the claim in one sentence. Subject, verb, result. "The author argues that read-it-later apps fail because saving feels like finishing." If you need a semicolon, you have two claims. Pick the bigger one.

4. Add two or three supports. These are the reasons or evidence the author uses, not every example. One short line each. If the piece has a surprising number, keep it.

5. Add the "so what" line. This is the part a classroom summary forbids and a working summary needs. One sentence: what you would do differently, or which decision this feeds. Keep it visibly separate from the summary, so you never confuse your view with the author's.

6. Check against the source. Reopen the article. Fix anything you got wrong, then stop. Do not polish.

There is a reason step 2 works. Research on summarizing has found that writing summaries can improve how accurately readers judge their own comprehension. You find out what you missed while the article is still fresh, not three weeks later when you need it.

How long should the summary be?

Shorter than you think. Here are the lengths we actually use, by purpose:

• Triage note on a saved article: 1 sentence, about 20 words, in the reading app's note field.

• Working summary for later reference: 3 to 5 sentences, 60 to 80 words, one entry in your notes app.

• Summary inside a report or paper: up to one third of the source, usually less, as a prose paragraph.

• Meeting or lecture summary: 5 bullets plus 1 action line, in a shared doc.

A 5,000-word piece needs a 70-word summary, not a 500-word one. If your summary is longer than the abstract the author would write for it, you are retelling, not summarizing.

Three habits that quietly ruin a summary

Copying the first sentence of every paragraph. It looks like a method. It is a shortcut that preserves the author's structure and hides the argument. Articles often bury their claim in paragraph six, and a paragraph-opener summary will walk right past it.

Paraphrasing with a thesaurus. Swapping "important" for "significant" is not summarizing. If you can only restate the sentences, the idea has not moved into your head. Skip the rewording and write what the passage means in plain words, even if it comes out blunt.

Pasting an AI summary and calling it done. This is the temptation of 2026. A generated summary is a fine map, and a poor memory. You did not choose what mattered, so nothing was retained. Use it as a check after step 6, not instead of it. If the machine's version disagrees with yours, that gap is worth ten minutes of rereading.

What changes when you listen instead of read

A lot of our readers take articles in by ear, on a commute, on a run, or because screens are hard to read for long. The method still works, with one adjustment: you cannot skim back.

When you listen, you cannot glance up the page to find the claim. So the close-the-tab step happens by default, since there is no tab to look at. This is an advantage. The moment the narration ends, you are already in retrieval mode.

The cost is that you have no highlights to rely on. Two fixes help.

First, speak the claim out loud, or dictate it, in the first 30 seconds after the audio ends. A 4,800-word article is around 30 minutes at a typical narration pace of 150 words per minute, and the claim fades fast after that. Hands-free dictation into a notes app is enough. You do not need to be at a desk.

Second, keep the summary to the three-line shape: claim, two supports, so-what. On a phone, in a queue, with one eye on the platform, three lines are what you will actually write. For readers with low vision, this is also where a voice note beats typing, so allow it. A spoken summary that you transcribe later is still a summary.

A note on tools. Speechify, NaturalReader and the listen modes in reading apps all give you the audio. None of them writes the summary for you, and you would not want them to. They get the article into your ears. The thinking stays yours.

Where to keep summaries so you find them again

A perfect summary in a dead folder is worth nothing. The storage decision matters as much as the writing.

Attach it to the source. A summary that lives next to the original link survives. Readwise Reader and Instapaper both let you add a note to a saved article, so the summary sits where you will find the article. We prefer this for anything you might reread.

Or pull it into your notes system. If you work in Obsidian or Notion, make one entry per source with three fields: link, summary, so-what. Resist the urge to design a template with eleven properties. Three fields get filled in. Eleven get abandoned by week two.

Review in batches. Once a week, read your summaries, not your sources. Ten summaries at 70 words each is 700 words, about three minutes. If a summary no longer interests you, delete the article too. That is the fastest way we know to shrink a backlog without guilt.

How to summarize things that are not articles

The shape holds, with small changes.

A research paper. Skip straight to the question, the method in one clause, the result with its number, and the limit the authors admit. Four lines. Read the abstract last, and treat it as your check.

A meeting. Decisions first, owners second, open questions third. A meeting summary that begins with "we discussed" has already failed.

A long email thread. One sentence on where it ended up, one on what is still open, one on what is asked of you. If you cannot write the first one, the thread has not concluded and the right reply is a question, not a summary.

A book chapter. Write the claim after each chapter, not at the end. By chapter nine, chapter two is gone.

When a summary is the wrong tool

Not everything deserves one. A summary costs about five minutes, and five minutes times 40 saved articles is more than three hours. Be honest about what you will use.

Skip the summary if the article is news you will forget by Friday. Skip it if you are saving it only because someone shared it. Skip it if you already knew most of it. A one-line triage note, "knew this, nothing new", is a perfectly good outcome, and it frees a slot in your queue.

Write the full version when the piece will change a decision, feed something you are writing, or contradict what you believed. That last category is the rarest and the most valuable, and it is the one people most often fail to capture, because disagreement feels like it will stick on its own. It does not.

Before your next commute

Pick one article from the pile. Read or listen to it once, with no markup. Close it. Write one sentence of claim, two supports and a so-what line, in under 80 words. Then open it and fix what you got wrong.

That is the entire practice. The first summary will feel slow, and the fifth will take three minutes. By the tenth, you will notice that you remember articles you used to lose, and the signal to noise ratio of your reading list improves, because you start refusing to save things you could never summarize.

READY TO TRANSMIT.