Start with a rehearsal log, not a floor plan
Most of our reviews begin the same way: someone from nativelo sits in the gallery during a run-through with a clipboard, a stopwatch and a pair of closed headphones. It is not glamorous, but the log we keep in that seat is the backbone of the written review. We note every cue as it is called, who acts on it, and how long the gap is between the call and the picture or sound changing.
A floor plan or a kit list shows what a gallery owns. A rehearsal log shows what it does under pressure. When a director calls a camera change and the vision mixer needs a second request, that moment goes in the log with a time against it. After an hour we usually have thirty or forty such moments, and patterns become obvious without anyone needing to be blamed.
We keep the log in plain columns: time in the show, the call, the response, and a short remark. Nothing clever, because the crew should be able to read it back with us.
- Time in the show, to the second
- The call as spoken, word for word
- Who responded and how long it took
- A one-line remark, never an opinion of a person
Reading the rundown as a working document
The rundown is the second tool we rely on, and we read it differently from the producers who wrote it. We are not checking that the running order makes editorial sense. We are checking whether each line gives the gallery enough warning to act, and whether the same few people are being asked to do too much in the same thirty seconds.
We mark up a printed copy by hand. Pens still beat screens here, because we can circle three cues that land inside one short link and see at a glance that the graphics operator is carrying all of them. Colour coding by role, one colour per person, makes overloaded stretches show up as clusters of one colour.
The marked rundown goes back to the producer unchanged apart from our notes, so they can see exactly what we saw. Often a producer moves a single item and the cluster disappears.
Listening to talkback, which is my part of the job
As the audio engineer at nativelo, I spend much of a review listening rather than looking. Talkback tells you how a gallery really feels. I want to hear how calls are phrased, whether the same instruction is repeated because the first one was missed, and whether two people speak over each other when a show tightens up.
I use a closed-back pair of headphones and a feed taken from the talkback system, recorded where the studio allows it. Listening again afterwards, away from the pressure, lets me count the overlaps and the repeated calls. A gallery that repeats one instruction three times per bulletin is telling us the channel or the phrasing is unclear.
Sometimes the fix is technical: a crowded talkback group, a level that is too low, or a person on the wrong channel. Sometimes it is a small agreement about wording, such as always naming the camera first.
- Overlapping calls per ten minutes
- Instructions that had to be repeated
- Channels that carry more people than they should
A simple timer and a shared vocabulary
We carry a basic stopwatch rather than software, because a crew relaxes around a stopwatch in a way they do not around a laptop pointed at them. We time three things: the gap between a call and its result, the length of each handover between segments, and the dead air, however brief, at any point in the run.
Alongside the timer we work from a short shared vocabulary. Before the rehearsal we ask the director which words the gallery uses for the same action, because crews often have two or three. If one operator says take and another says cut to, the review records that, and the written recommendations use whichever the gallery already prefers.
This avoids the common failure of a review that sounds clever but uses language nobody in the room speaks. The recommendations should read like something the crew could have written themselves.
How the notes become a written review
Back in Norwich, the log, the marked rundown and the talkback notes are laid side by side. We look for the same moment appearing in more than one of them: a late cue in the log, a crowded stretch in the rundown and a repeated call in the audio. A problem visible in all three is nearly always real, and those go to the top of the document.
The written review is organised by what to change first, not by department. Each recommendation names the moment it came from, what we suggest, and roughly how much crew time it takes to try. Small changes that cost nothing, like moving a cue or renaming a talkback group, come before anything involving equipment.
We deliberately keep the document short enough to be read in one sitting by a studio manager between two shows, with the supporting log attached for anyone who wants the detail.
- Recommendations ordered by what to try first
- Each one tied to a logged moment
- Crew time stated honestly, with no promised outcome
What we leave out on purpose
There are tools we choose not to use. We do not ask the gallery to adopt new software as part of a review, and we do not recommend buying equipment until the free changes have been tried. A review that ends in a shopping list usually means the reviewer stopped looking too early.
We also avoid scoring crews. A number attached to a gallery invites arguments about the number instead of discussion of the moments behind it. The log stays factual, and the conversation afterwards stays on the work.
This restraint is part of why crews let us sit in the gallery at all. They can see that the notebook records the show, not the people, and that anything we write can be traced back to a line they could check themselves.
The tools behind a workflow review are modest: a log, a marked rundown, a stopwatch and a good pair of headphones. Their value lies in how plainly they record what happens, so that a crew can recognise its own gallery in our notes. If you want to see how that looks on your own show, the contact page is the way to start a conversation.