How to Summarise What You Read in Your Own Words
2026-05-20 · 8 min read
A repeatable method for turning a dense chapter into a short, accurate summary that proves you understood it rather than copied it.
Why summarising is a comprehension test, not a shortcut
Most students treat a summary as a space-saving device: a way to carry less text around before an exam. It is far more useful as a diagnostic. If you can restate a chapter in six sentences without looking back at it, you understood the structure of the argument. If you cannot, the failure point is visible immediately, and it is almost always one specific paragraph rather than the whole chapter.
Read once for shape, once for detail
The first pass should be fast and structural. Read the headings, the first sentence of each paragraph, and any summary box, and ask one question: what is this text trying to convince me of? Only on the second pass should you slow down for evidence, definitions, and numbers. Reading for detail first is what produces highlighter-covered pages with no memory attached to them, because you were processing sentences without a frame to hang them on.
Close the book before you write
The single rule that separates a real summary from paraphrased copying is that you write with the source closed. Looking at the text while summarising means your sentences are generated from the author's word order rather than from your understanding, and the result feels correct while teaching you nothing. Write from memory, then reopen the source and correct what you got wrong. The corrections are the learning.
Use the claim, evidence, limit pattern
For expository or argumentative texts, three lines per section usually suffice. State the claim the section makes. State the strongest piece of evidence offered for it. State the limit — what the section does not establish, or the condition under which the claim holds. That third line is what most summaries omit, and it is the one that makes the summary useful later when you need to compare two sources that disagree.
Keep proper nouns, drop illustrations
A good summary preserves names, dates, technical terms, and quantities, because those are the parts you cannot reconstruct from reasoning. It drops anecdotes, extended metaphors, and repeated restatements, because those you can regenerate from the underlying idea. If you find yourself writing down an entertaining example, ask what point it was illustrating and write that instead.
Test the summary against a question
Before filing a summary away, write one question the text should let you answer and check whether your summary answers it. If it does not, you have written a table of contents rather than a summary. This test takes thirty seconds and catches the most common failure, which is a list of topics covered with no content attached.
Build a stack, not a pile
Summaries are only valuable if you can find them. Keep one file or notebook per subject, date each entry, and put the source title and page range at the top. When revision starts, you will be re-reading your own words, which are already tuned to your understanding, rather than restarting from a textbook you have effectively never processed.