Reviewing the Summer Festival Circuit: A Guide for First-Time Critics

The ticket says seven o'clock. The gate opens at ten past, the stage is a black box in a park, and the light won't fall until nine. Somewhere behind you a child is asking whether there will be ice cream. This is the summer festival circuit, and it asks for a different kind of reviewing from the one you learned in a darkened auditorium with a numbered seat and a printed programme. The work on stage can be just as good. The conditions rarely are. Learning to tell the difference between the two — and to file five hundred clean words before midnight — is what a first season teaches you.

The circuit runs on different rules

Indoor reviewing is a settled routine. You arrive, the show starts roughly on time, you take notes in the dark, you go home, you file the next morning with a coffee. Festival reviewing bends every part of that.

There is daylight on the stage, so half of the lighting design is doing nothing at all. There is a beer tent forty metres away, so the quietest scene competes with a queue. The audience has not come to a theatre; it has come out for the evening, and the show is one part of that. Nobody has paid West End prices, nobody has booked six weeks in advance, and a good number of them will decide what they think of the production while standing up to leave.

Deadlines shrink too. A short run means a review published on Tuesday can still sell tickets for Thursday, and an editor will want it in the morning. Plan for four hundred to seven hundred words filed within a few hours of the curtain, not twelve hundred words three days later.

Read the room before you read the show

Get there early — twenty-five minutes, not five — and spend the first ten watching the audience rather than the set. Who has turned up? Families with folding chairs and a cool bag? Groups of friends starting their night out? A knot of regulars who clearly know the company's name? Each of those rooms will laugh, sigh and shuffle differently, and the show will be a slightly different object in each of them.

A comic bit that gets a polite ripple in a six o'clock family slot can bring the house down at ten with a crowd three drinks in. Neither reaction is the truth of the production. Both are information.

Ask an usher two quick questions: how many performances are in this run, and is this the company's first time here? The first tells you how much weight your review is carrying. The second tells you whether a rough edge comes from inexperience with the space or inexperience with the work.

One discipline above all others: review the performance you actually saw. If it rained, if the sound desk died for four minutes, if the lead was replaced that afternoon, say so plainly and then judge what remained. Readers can hold two facts at once.

The venue is part of the production

Open-air and found spaces impose limits, and some of those limits are nobody's fault in the company. Others absolutely are. The useful skill is knowing which is which.

• Sound: a site with traffic behind the seating will swallow unamplified speech. That's the venue. A mic plot that leaves two actors inaudible for the whole first act is a decision someone made, and it's fair to say so.
• Sightlines: a pillar, a shallow rake, a row of tall people. If you moved twice to see the action, mention it once.
• Weather: heat, drizzle, insects, a sunset that turns the upstage wall orange at precisely the wrong moment. Describe it in a clause, not a paragraph.
• Endurance: a hundred minutes without an interval on hard plastic seating is a different experience from the same show in a padded auditorium, and it shapes how an audience listens.

Write about these conditions once, early, and then get to the work on stage. A review that spends six hundred words on the wind is a review that never got started.

Judge the production the company made, not the festival the company arrived in.

Short runs, first nights and the deadline problem

A three-night run gives you almost no room to choose. If you can, see the first performance, because that is the one still running when your review lands. But the first performance of a festival show is often the least settled: the tech was finished at four, the company arrived at noon, and the front of house is still working out where to put the bins.

The honest solution is disclosure, not hedging. One line — “reviewed at the second performance, in light rain” — tells the reader what they need to know and stops you over-claiming. If you go back and the show has visibly tightened, don't rewrite history in a second piece; a short follow-up note is fine when something substantial changes, such as a recast or a cut number, but check with the editor first.

And resist building the whole review around a technical fault. Unless the failure was the story of the night, it belongs in a sentence, not a thesis.

Filing fast without filing carelessly

A rushed review is not the same as a sloppy one. The difference is usually a fixed process that survives a late finish and a long walk to the car park.

1. Photograph the programme page with the credits before the show starts. Spelling a director's name wrong is the error readers forgive least.
2. Fix the facts in your notes by the interval: full title, company, venue, running time, whether there is an interval, who wrote, directed and designed it.
3. Write the verdict sentence first — one sentence you can defend with two examples from the production.
4. Choose three moments: one that worked, one that didn't, one strange enough to be worth describing. Describe before you evaluate; the judgment lands harder when the reader can see what you saw.
5. Draft in one pass, on a timer, without rereading.
6. Edit once for facts — names, numbers, times — and once for rhythm, reading the final paragraph aloud.
7. File with the performance date, the conditions and a contact number, and ask for the word count in advance so you are not cutting at midnight.

Keep one notebook with a hard division: left-hand page for what happened, right-hand page for what you thought about it. It stops the two blurring together when you are tired and writing under a lamp in a tent.

Fairness across a wildly uneven programme

In the same week you may see a company with a touring budget and a company that has built its set out of pallets in the back of a van. The question is never how much money was on stage. It is whether the show did what it set out to do, and whether that was worth doing in the first place.

Two distinctions are worth carrying into every review. Unpaid is not the same as unprepared. Ambitious is not the same as achieved. Holding both pairs apart lets you be generous about resources and exact about execution, which is the whole job.

Watch your tone when you write about a holiday audience, too. A crowd that laughs easily at a broad comedy is not a crowd that doesn't know any better. Condescension reads badly in print and ages worse.

A checklist for the summer season

Print this or copy it into the front of the notebook. It saves an embarrassing email at least once a summer.

• Gate and curtain time confirmed, plus the press contact's number in case of cancellation.
• Arrive twenty-five minutes early; watch the audience for ten of them.
• Programme photographed, names checked twice.
• Two pens, a waterproof cover, a layer for after sunset.
• Notes on the left page, opinions on the right.
• Performance date and weather conditions written into the file.
• A standby plan agreed with the editor if the show is cancelled — usually a short piece on the programme rather than a review of nothing.

None of this makes the job smaller. A festival review written on a picnic bench at half past eleven can still be the most useful thing a small company reads all summer, and the first honest account a curious audience gets. Keep the notebook dry, keep the verdict simple, and give the work on stage the attention the weather keeps trying to take away.

Photo: Mojpe / Pixabay