
Why Anthologies Resist the Standard Review
A novel gives you one arc, one voice, one journey to judge. An anthology hands you fifteen, twenty, sometimes forty. Reviewers who approach a collection with the same template they use for a debut novel tend to produce either a breathless list of every story or a vague shrug about "mixed quality". Neither serves the reader deciding whether to spend their money. The trick is to review the anthology as a whole and to let a few individual stories carry the argument. That balance is learnable, and it starts long before you open a blank document.
Read First, Take Notes, Then Decide
Before you write a word, read the whole collection properly. Skimming the first three stories and the introduction will not give you a reliable sense of the shape of the book. Editors think in sequencing: a strong opener, a change of tempo in the middle, a closer designed to linger. You can only spot that architecture if you have been through the whole thing.
Keep a running note for each story, but keep it short — a line on the premise, a line on what worked or did not, and a rough ranking. Something like "third-person, quiet, grief, brilliant last page" is enough. This gives you a private map of the book, so you can see patterns emerge whilst you read: recurring images, repeated settings, a run of first-person narrators, a cluster of stories about memory or migration or artificial minds.
Also note the apparatus. Does the editor provide a preface explaining the brief? Are there author biographies or story notes? These are not filler; they tell you what the book is trying to do, and you can hold it to that standard rather than to your own preferences.
Identify the Through-Line Before You Judge
Every anthology has a promise. A themed collection promises variation within a constraint; a best-of-year promises the strongest work the field produced; a single-author collection promises range within one imagination. Work out which promise is being made, and review against that.
Ask yourself:
- What is the stated or implied brief, and do the stories honour it?
- Does the running order build momentum or sag in the middle?
- Is the range of voices, styles and perspectives genuinely varied, or is it the same story told fifteen ways?
- Does the editor's presence show in the selection, or does it read like an unfiltered pile?
Editorial cohesion is the hardest thing to describe and the most valuable thing to your readers. A useful formula: name one thing the editor does consistently well, and one thing the collection lacks. That single sentence will tell a reader more than a paragraph of adjectives.
Choose Your Standout Stories Carefully
You do not need to mention every story. You do need to mention enough that the review feels grounded — usually three to five named pieces, with two of those given real space.
- The anchor: your favourite of the bunch, the one you would press on a friend.
- The surprise: an unexpected voice, genre shift or formal experiment.
- The representative: a story that shows what the collection is mostly like, even if it is not the best.
- The problem piece: if something genuinely fails, say so briefly and without cruelty.
Resist the urge to grade the whole table of contents. A review that says two or three stories are excellent, one is fine, and the rest vary is more useful and more honest than a scorecard of twenty entries — and it respects the fact that tastes differ.
A Structure That Works
Most anthology reviews land well in five or six paragraphs. Open with the concept and the editor's brief, then give your overall verdict on how well the book holds together. Follow with a short discussion of two or three standout stories, including what makes them distinctive, without spoiling their endings. Then address the weaker material and who might still enjoy it — an anthology with three weak stories among fifteen is a very different proposition from one where half the book misfires. Close with the practical question: who should read this, and when.
Keep spoilers minimal. Anthology readers often dip in and out over weeks, and a review that reveals the twist in story seven is a genuine disservice. If you must discuss a detail that matters, flag it clearly so readers can skip ahead.
Handling Ratings and Comparisons
Star ratings are awkward for collections, because one outstanding story can sit beside one that never finds its feet. Say so explicitly. Something like "four stars for the strongest third, three overall" is entirely fair, and readers understand it.
Then: don't review an anthology in isolation if you can help it. Comparing it to one or two similar collections — the same theme, the same editor, the same corner of the genre — gives your verdict context and helps readers find the right entry point. It also lets you talk about the form itself, which is where anthologies become genuinely interesting: the conversation between stories, the way an editor's taste becomes visible only in aggregate.
Finally, remember the pleasure of a good collection. Part of the joy is discovering a new voice in three thousand words, then hunting down their novel. Let that enthusiasm onto the page. It is contagious, and it is the whole reason the form endures.
Coding is used in almost all aspects of life and work now, be it directly or indirectly. It’s not just for companies in the tech sector. “An increasing number of businesses rely on computer code,
Coding is used in almost all aspects of life and work now, be it directly or indirectly. It’s not just for companies in the tech sector. “An increasing number of businesses rely on computer code,
Coding is used in almost all aspects of life and work now, be it directly or indirectly. It’s not just for companies in the tech sector. “An increasing number of businesses rely on computer code,