Anyone can sit through a play. Writing about it so that a stranger trusts you is a different job. A review that earns a reader's time does four things at once: it tells them what the evening was, gives them the terms in which to judge it, shows the evidence behind your judgment, and lands on a verdict they can use. Miss any of those and the piece collapses into either a plot summary or a mood. What follows is a working method — the kind of checklist you keep beside your notebook, not a rulebook to obey.
A reader who did not attend needs the ground floor of the production: the play and the playwright, the space, the shape of the staging, roughly how long you sat there. Not a synopsis — most readers can find the plot elsewhere — but the physical facts of what was put in front of you. Was the stage a bare black box or a wall of fluorescent tubes? Did the design change between acts, and did that change mean anything? Did the production move fast, or did it settle into a slow, deliberate rhythm that asked for patience and mostly earned it?
Write with nouns and verbs. "Stunning" tells nobody anything; "the fourth wall was a sheet of glass the actors kept pressing their foreheads against" tells everybody something. When you catch yourself stacking three adjectives in front of a noun, cut two and describe the thing instead.
Every show has terms, and criticism that ignores them is just opinion in a louder voice. A devised piece in a sixty-seat fringe venue, a subsidised revival of a classic, and a community musical are not competing on the same field. Your job is to work out what this particular production set out to be, then say whether it got there.
Ambition deserves respect. It is not the same thing as achievement, and a review that confuses the two is no use to anyone — least of all to the company, who will learn nothing from applause they did not earn.
The difference between a review and a verdict is evidence. "The pacing was uneven" is a feeling. "The first forty minutes moved briskly; after the interval, two long dialogues between the sisters were played at the same tempo, and attention in the rows around me visibly drifted" is a claim a reader can weigh. Point to moments. Quote a line if the writing is the story. Describe a gesture, a lighting cue, the way a scene change was handled in near-darkness.
Name performers. The programme gives you the names; using them is basic courtesy and it lets readers follow a career. Be precise about what each person did rather than ranking them — "held the stage in the silences" is more useful than "was the best thing in it". And be careful with a single bad night: if a line was dropped, a mic failed, or an entrance landed early, say so, because a technical mishap is not a performance choice.
Weak: "The second act lost energy."
Strong: "The second act lost energy the moment the two leads stopped sharing the stage; the three scenes played apart were half the length and twice the pace of the one they played together."
You can dislike a show and still say it is good. You can enjoy a show and still say it is thin. Knowing which is happening is most of the discipline. Taste is your allergy to musicals, your preference for naturalistic acting, your impatience with direct address. Craft is whether the text was audible, whether the story was clear, whether the design supported or fought the play, whether the style held together past the interval. Judge craft on the page; admit taste in a line and move on.
If you notice yourself building a four-hundred-word case against a genre rather than a production, you have stopped reviewing. Rewrite the paragraph so it is about the work in front of you — what this company did, on this night, in this room.
Reviews usually end with a rating or a recommendation, and both are blunt instruments. The useful version is conditional: worth seeing for one performance, worth seeing if you like the playwright, worth seeing in its second week once the company has settled. That is a real verdict, and a reader can act on it.
Before you commit, run one test: could you read this sentence to the director's face and stand by it? If the answer is no, it is either inaccurate or needlessly cruel. Both are fixable. Also remember that a review outlives the run it describes. Write about the production, not about the rustling crisp packet behind you, unless the sound really was part of the problem — and then describe it as a technical issue, not a grievance.
Open with your sharpest specific observation, not a summary of the plot. Follow with a short stretch of description so the reader can see the stage, then the argument, then the verdict, then the practical note: running time, interval, whether the content warrants a warning, whether to book early. Keep the synopsis to a few sentences and spend the space you save on the production itself.
A structure that holds up well: hook, description, context, two or three evidenced points of praise or criticism, verdict, practical line. Read the whole thing aloud when you finish. Any sentence you stumble over is a sentence your reader will skip.
Before you file, check the piece against this list. It takes five minutes and catches most of what goes wrong.
Fair criticism is generous with attention and exact about detail. It tells a company what happened, tells a reader what to do, and tells the truth. Get those three lined up and the review will still be worth reading after the set has been struck.
Photo: StartupStockPhotos / Pixabay