How to Write a Fair and Useful Book Review: A Checklist for Bloggers and Book Clubs

A review is not a verdict. It is a hand held out to another reader: here is what this book sets out to do, here is how well it does it, and here is whether you might want to give it your evenings. That sounds straightforward until you sit down to write one and find yourself caught between “I loved it” and a plot summary nobody asked for.

Whether you post on your own blog, chair a book club, or write a few paragraphs for a reading group newsletter, a fair review does three things. It describes the book accurately, it supports its judgements with evidence, and it ends with a recommendation a reader can act on. Here is a checklist worth keeping nearby.

Start with the book’s own ambitions

Before deciding whether a book works, work out what it is trying to be. A cosy crime novel, a sprawling family saga, a slim essay collection and a debut memoir are playing by different rules, and there is little sense in marking one down for failing at a game it never entered. A thriller is allowed to withhold information. A memoir is not.

Ask three questions as you read. Who is this book for? What is it trying to make me feel, know or see? And how does it signal that intention — through voice, structure, humour, argument? Keep those in mind and your criticism sharpens, because you can say with confidence that the ambition outstripped the execution rather than simply that you were bored.

The pre-writing checklist

Nobody reviews well from memory alone. Keep notes as you go — a pencil in the margin is enough — and before you draft, make sure you can answer these:

• A one-sentence summary of the plot or argument, in your own words
• The book’s aim, as you understand it
• Three things that worked, with page references so you can check yourself later
• Two things that did not, with concrete examples
• Who would enjoy it, and who would be better off spending their money elsewhere
• Two or three comparable titles, to help readers place it on the shelf
• Two short quotations you might use, copied exactly, with page numbers
• Practical details a buyer wants: length, format, series or standalone, translation, and anything some readers may find distressing

Fifteen minutes of notes saves an hour of waffle. It also guards against the most common fault in amateur reviews: the vague adjective doing work it cannot possibly do.

Make every judgement earn its place

“Beautifully written” tells a reader almost nothing. It might mean spare and exact, or lush and digressive, and those are different pleasures. Show your working instead of labelling the result.

The middle hundred pages lose their nerve. Two confrontations the first act has been building towards happen off the page, and the tension never quite returns.

That is a criticism an author could use and a reader could weigh. The same principle applies to praise: name the chapter, the scene, the turn of phrase, the structural risk that paid off.

Pair criticism with praise where it is honest to do so, but do not force a compliment in front of every complaint. Readers can smell padding. And if you quote, quote accurately and in context — a sentence lifted from an argument it belongs to is not evidence, it is decoration.

Plot, spoilers and the summary trap

Describe the set-up, not the resolution. Two to four sentences is usually plenty. If a detail appears on the back cover, it is fair game; anything past the halfway mark is not, unless you flag it clearly first. Never reveal an ending to prove you read to the last page.

The summary trap catches even experienced reviewers, especially with complicated plots. You spend four hundred words explaining who did what to whom, then a hundred on whether any of it was any good. Flip that ratio. Your reader can find a synopsis elsewhere; what they cannot find anywhere else is your judgement.

When you did not like the book

Separate taste from craft. “This is not a book for me” is a legitimate sentence, and a useful one. “The plot contradicts itself in chapters nine and eleven” is a different kind of claim, and it needs evidence. Being clear about which one you are making keeps you honest and helps your reader calibrate.

Avoid snark. The urge to be clever at an author’s expense is strong, particularly when you have spent three weeks on a novel that disappointed you, but it makes a review less useful rather than more. If you abandoned the book at page sixty, say so, and say why — a review of a partial read is fine as long as it is labelled as one.

Declare your circumstances. If you received a free copy, if you know the author, if the publisher is a friend of a friend, mention it in a line and move on. Readers forgive all sorts of things except the suspicion that they are being sold something.

In a book club, disagreement is an asset rather than a problem. Note where your view diverges from the group’s and why. A review that admits “three of us found the ending earned, two found it evasive” is more interesting than a false consensus.

Write it so it can be read in three minutes

Open with something specific: a scene, a question the book raises, a line you cannot shake. Not “I was kindly sent a copy of…”. Put your verdict early enough that a reader skimming on their phone gets the gist, then earn it in the paragraphs that follow.

Explain what your rating means. A three-star book can be exactly the right read for the right person, and your job is to name that person: “worth it if you want a slow, wintry mystery”, “skip if you prefer plots that resolve cleanly”.

Keep paragraphs short. Use subheadings once a review runs past six hundred words, and bold the sentence that carries your verdict if your blog theme allows it. Set aside the star rating and write one plain closing sentence that tells the reader what to do. That is the sentence most of them came for.

The five-minute final pass

1. Have I said what the book is, what it is trying to do, and whether it does it?
2. Does every criticism come with an example?
3. Would the author recognise their book in my description?
4. Have I spoiled anything beyond the blurb without warning?
5. Is my recommendation specific about who should read it, and why?
6. Have I declared a free copy, a proof, or any connection to the author or publisher?
7. Would I be content to read this aloud to the author’s face, and still stand by it?

If you can answer yes to those, publish. A fair review is not a lukewarm one — it can be delighted, exasperated or furious — as long as the reader can see the working. That is what makes it worth reading, and worth trusting the next time you recommend something.

Photo: Jacek Jan Skorupski / Pexels