Book Review vs. Book Summary: How to Write the Right One

You have finished the book. The document is open. Then the question arrives, usually from an editor or a friend in a book club: is this a review or a summary? They sound like the same assignment. They are not. A summary with a verdict smuggled into the last paragraph, and a review that spends three hundred words retelling the plot, are the two most common ways a good reading turns into a muddled piece of writing. The difference is simpler than most style guides admit. One tells the reader what is inside the book. The other tells them what to do with it.

Two Different Jobs, One Reader

A summary exists to transfer information. Its reader has a reason to know the contents without reading the whole thing: a class discussion on Thursday, a book club vote, a colleague who mentioned it in a meeting. Accuracy is the whole job. If you leave out the reveal on page 240 that changes how the first hundred pages read, you have written a bad summary, no matter how elegant the sentences.

A review exists to make a judgment, and to show the working behind it. Its reader is deciding something: whether to spend a weekend on this book, whether to trust the friend who recommended it, whether the hype is deserved. The review can be wrong in its taste and still be good, as long as the reasoning is visible and the evidence is on the page.

Both forms begin the same way, with a close reading. The work splits at the second step. The summariser asks, what can I leave out without breaking the chain? The reviewer asks, what is this book trying to do, and does it succeed? Answer those two questions in the wrong order and the piece wobbles.

What a Book Summary Actually Does

A summary compresses without arguing. That means preserving proportion. If the middle third of a novel is a court case, the summary should give that section real weight, not one line about the trial. If the book is nonfiction, state the central claim in the first few sentences, then trace the order of the argument: what the author sets up, what evidence carries it, where the qualifications arrive.

Name people and places early and clearly. In a novel, attach a short tag to each character the first time they appear — the older sister who inherits the house, the neighbour who keeps the letters — and then trust the reader to remember. Do not summarise dialogue line by line. Do keep the causal chain: this happened, so that happened, which forced the choice at the end.

A summary skeleton to work from

1. One sentence naming the book, its kind, and what it does.
2. The setup: who is involved, where we are, what is at stake.
3. The spine: four to six beats in order, weighted by how much space they take up in the book.
4. The ending, including the turn or reveal. Summaries do not protect readers from spoilers; that is what reviews are for.
5. One closing line on structure or form, if the shape of the book matters to understanding it.

Length is a compression decision, not a style decision. A 400-word summary of a 500-page novel has no room for subplots. Keep the letter that changes the inheritance; cut the cousin's wedding. When you are finished, read it back and ask whether someone who had read the book would recognise it, and whether someone who had not would follow it.

What a Book Review Must Do

A review needs an argument you could disagree with. Vague praise is not an argument. "The prose is beautiful" is a mood; "the sentences stay short even in the emotional climaxes, which makes the grief feel withheld rather than performed" is a claim, and a reader can push back on it. That is the test. If no reasonable reader could argue with your sentence, it is not doing review work yet.

A useful review usually covers four things in some order: what the book sets out to do, how it goes about it, whether the approach holds up, and who will care. That last part is where many reviews stop too early. Telling a reader the book is good is less helpful than telling them it is good for someone who loved the first half of a certain trilogy but found the ending too tidy.

Reviews also do not have to be harsh to be honest. A review that praises everything reads like a blurb, and readers learn to skip it. If a book is competent and unremarkable, say so plainly and describe what kind of reader would still enjoy it. That is more useful than fake enthusiasm.

Handling spoilers on purpose

Decide your policy before you write and keep it consistent. Most reviews can discuss the opening third freely, describe the shape of the ending without naming the twist, and say outright when they are about to go further. One line near the top — "minor spoilers for the first hundred pages" — buys you a lot of goodwill and keeps the argument intact.

Where the Two Get Confused

Most problems come from a handful of familiar habits:

• The plot dump with a rating attached. Three hundred words of summary, then "I loved it." The reader has learned the story and nothing about whether it is any good.
• The verdict with no evidence. "Overrated" or "a masterpiece" as a complete argument. Opinions are cheap; the reasoning is the product.
• The summary that argues. Phrases like "unfortunately, the author lingers" turn a summary into a review in disguise. That is fine if the label says review.
• The review that assumes the plot is known. Half the audience has not read the book. If you never say what happens, they cannot judge whether your praise is earned.
• Biography in place of engagement. Where the author grew up is only relevant if it changes how the book reads.

Choosing the Right Form for the Publication

Start with the brief. If the editor asked for a summary and you deliver a review, you have not been clever, you have been late. After that, run through the questions that decide the shape of the piece:

• What will the reader do next? Buy or skip it means a review. Understand it, remember it, or discuss it means a summary.
• How new is the book? New releases want timely judgment. Backlist titles and reading-group guides usually want a clear account of the contents.
• How much does the audience already know? A study guide and a general-interest feature need different amounts of retelling.
• Do you have an argument worth defending? If you cannot state your view in two sentences, write the summary first and see whether a judgment emerges.
• What is the reader searching for? People looking for "what happens in" want a summary. People looking for "is it worth reading" want a review. Give them the one the page promises.

Labels are a contract. Calling a summary a review because reviews get more clicks is the quickest way to lose a reader's trust, and it is hard to earn back.

The Hybrid That Works

Plenty of publications want both, and there is a clean way to do it. Write a short opening section headed "What it's about" and keep it tight — 120 to 180 words for a standard review, covering the setup and the central tension without the ending. Then spend the rest of the piece on judgment. For a 900-word review, that means roughly a fifth summary and four fifths argument.

The reverse also works: a summary followed by a clearly separated closing section on who the book suits. What fails is the blend with no seams, where the reader cannot tell whether they are being told what happens or what to think about it.

Summary first, judgment second — and only as much summary as the judgment needs.

Before You Publish: A Short Checklist

• Is the piece labelled honestly as a summary or a review?
• Does the first paragraph tell the reader what they are getting?
• If it is a summary: is the causal chain intact, and are the proportions right?
• If it is a review: is there at least one claim a reasonable reader could dispute, backed by evidence from the text?
• Is the spoiler policy clear and consistent?
• Does the last line answer the question the reader arrived with — what happens, or whether to read it?

Answer those six honestly and the piece will hold together. The reading was the hard part. Sorting it into the right container takes an afternoon.

Photo: cottonbro studio / Pexels