Most short story reviews fall into one of two ditches. Either they announce that the piece was "beautifully written" and leave it there, or they retell the plot until the reader has no reason to visit the story at all. Both are comfortable. Neither helps anyone. A useful review answers three questions: what the story set out to do, how well it did it, and who will be glad they read it. What follows is a checklist meant to be used, not admired — run a draft through it before you post. It works just as well on someone else's story as on your own.

First, Name the Story's Ambition

You cannot judge execution without knowing the target. Before you note a single flaw, decide what kind of story this is trying to be: a quiet character study, a tight plot-driven piece, a mood fragment, a comic sketch, a fable with a sting in it. Then ask whether the story is aiming where you think it is.

A 1,200-word piece that closes on an unresolved image is not failing at closure if it never promised closure. It fails only if the buildup insisted on answers it then withholds. Get this wrong and the rest of the review collapses. A review that misidentifies a story's ambition is worthless even when every sentence is complimentary.

The Craft Checklist

Work through these and keep the two or three observations that carry the most weight. You are not grading an exam; you are telling a reader where to look.

• Opening. Does the first paragraph give you a voice, a situation, and a reason to continue — or just weather and furniture? "Rain fell on the empty street" is furniture. A narrator who is hiding something from the person they are talking to is a reason.
• Want. Can you say in one sentence what the protagonist wants, without quoting the text? If not, ask whether the story intended that vagueness. A drifting want is a choice; a missing one is usually an accident.
• Structure. Where is the turn? Most short stories need one clear shift — a decision, a discovery, a reversal, a lie exposed. If you cannot find it, say so plainly instead of murmuring that "the pacing felt uneven."
• Dialogue. Read a page aloud. Do the speakers sound different from each other, and from the narrator? Dialogue that exists only to deliver information is worth flagging by example.
• Point of view. Is it consistent, and does it seem chosen? A wobble mid-scene is easy to name precisely — paragraph three shifts from what she knows to what he is thinking.
• Language. Not "beautiful prose." Quote one line that worked and say what it did. Then name one place where the prose got in the way: three adjectives where one would hold, a metaphor that pulls attention to the writer rather than the scene.
• Ending. Does it change how you read something earlier? Test it: go back and reread the first two hundred words after finishing. A good ending makes the opening feel inevitable in hindsight.

What to Say Instead of "I Liked It"

Praise without evidence is a compliment, not a review. "The prose is gorgeous" tells the writer nothing they can use and the reader nothing they can trust. Replace it with something a stranger could verify:

The description of the flooded cellar does real work — the narrator's fear of the house is planted there, and the last line cashes it in.

"I liked it" can become: "I read the final three paragraphs twice, not because they confused me but because the last line changed what I thought the argument in the kitchen had been about." That is specific, and it is useful.

Criticism needs the same discipline. "The middle sags" is empty. "The pages between the letter and the phone call repeat the same realization in different words, and nothing moves until the call" gives the writer a place to stand.

Audience Fit: Who Will Be Glad They Read This

Reviews of short fiction usually skip this, and it is the most practical thing a browsing reader can get. Be concrete about the reader, not the genre label. "Readers who like domestic stories that end without resolution" tells someone far more than "fans of literary fiction."

Say what the story asks of you: patience through a slow first page, tolerance for an unreliable narrator, an appetite for discomfort. Note the length and the shape of the time it needs — a nine-hundred-word piece suits a commute; another needs a quiet twenty minutes and no interruptions.

The Reading Experience: Pace, Friction, and the Line Level

Record your own responses honestly, then translate them into causes. Where did you slow down? Where did you skim, and why? Skimming is data, not a confession. "I skimmed the second page because the paragraphing was even and nothing was at stake in the next minute" is a craft note disguised as a mood.

Ask whether you were looking forward to the next paragraph, or merely willing to reach it. Ask whether a moment that was supposed to land actually landed, or whether you saw the machinery turning. Both answers belong in the review, stated without drama.

Drafting the Review: A Short Process

1. Read once with no notes. Let the story do whatever it does to you first.
2. Wait an hour, or a day. Jot what you remember. What stuck is what the story actually accomplished.
3. Reread the opening after the ending. Note what has changed.
4. Write one sentence that says what the story does and how well. That is your spine; everything else supports it.
5. Choose two craft observations and one audience note. Resist the urge to be exhaustive.
6. Say the hard thing plainly, and say one true good thing plainly. Order does not matter; specificity does.
7. Cut every sentence that could apply to any story ever written.

Decide where your spoiler line sits, and signal it. Describing the setup is fair; giving away the turn is a different act.

Keeping It Useful

For writers, the same list runs backwards. Read your draft and ask where the turn is, what the first paragraph promises, and whether the ending pays for it. If you cannot answer in one sentence, the story is not ready for a reviewer's attention.

The standard is simple: after reading your review, someone should know whether this story is for them, and the writer should know what to look at next. If both are true, you have written something worth the space it takes up.

Photo: Jakub Zerdzicki / Pexels