The question we hear most about live event workflow reviews

The question behind the question

The enquiry we receive most often is short: what do you actually do when you review a live event workflow, and what do we get at the end? It usually arrives from a producer or technical director who has just come off a show that ran, but ran on goodwill. Nothing failed outright. Yet the talkback was crowded, two people were solving the same problem in different corners of the gallery, and nobody could say afterwards who had authority over a late change to the running order.

A review exists for exactly that situation. It is not an inspection of equipment and it is not a verdict on the crew. It is a structured look at how a show is meant to move from the stage or studio floor to the viewer: which signals go where, who speaks to whom, and who decides what when plans shift. We write down what we find in terms the whole team can read.

What a review covers

Three areas make up the work. The first is signal flow: where each camera, microphone, graphic and playback source enters the chain, how it is routed, where it is monitored and where a fault would be noticed first. We draw this as a single diagram, because most workflow problems are easier to see on one sheet than in a folder of separate documents.

The second is communications. We look at which talkback channels exist, who is on each, and whether the people who need to hear each other can. The third is crew roles: who is responsible for which decision, and what happens when that person is busy. We do not redesign your kit list in a review. If the findings point to a studio or equipment question, we say so and leave it as a separate piece of advice.

• Signal flow from source to transmission or stream
• Communications channels and who sits on each
• Crew roles, hand-offs and decision points

How a review actually runs

We begin with a conversation, usually by phone, to understand the type of show, the venue or studio, and what prompted the enquiry. After that we ask for whatever documents you already have: a run sheet, a rough signal diagram, a crew list. Rough is fine. Many teams have nothing more than a sketch on a whiteboard, and that tells us how the show is really thought about.

Where possible we then watch a rehearsal or a live show from the gallery or the production area, listening to the communications and noting where questions are asked twice. Priya or a colleague takes notes without interrupting. If attending is not practical, we work from recordings of the talkback and a walk-through with your technical lead. The aim is to see the habits of the crew, not an idealised version of them.

What you receive at the end

The result is a written report, not a presentation to be forgotten by the following week. It contains the signal flow diagram as we understood it, a short list of observations in plain language, and a set of recommended changes ranked by how much trouble they would save and how easily they can be made. Several of them are usually small: a renamed talkback channel, a clearer cue sheet, an agreed fallback for a failed source.

We go through the report with you in a call so that questions are answered while the details are fresh. Because the findings are written for the crew as well as the management, you can hand the document to the people doing the work. We do not promise that a show will run without incident afterwards; we promise that the reasons behind the usual incidents will be visible and that the next step will be clear.

What to prepare beforehand

A little preparation makes the review faster and more useful. Gather the most recent run sheet, any signal or patching diagrams, the crew list with roles, and a note of the problems you remember from the last show. The last item matters most. A producer's memory of where things went wrong is often a better guide to our attention than any document.

It also helps to tell us in advance who should be present and who should not. Some teams speak more freely without a manager in the room, and we are happy to arrange the conversations that way. If you plan changes to the venue, the streaming platform or the crew size in the coming months, mention them early, because a review of a workflow that is about to change should look at the new version, not the old one.

• Latest run sheet and any rough diagrams
• Crew list with roles
• Notes on problems from the previous show
• Known changes planned for the next few months

Timing, cost and what we will not do

The length of a review depends on the size of the production. A single-venue event with one gallery takes less time than a multi-stage broadcast with several control areas, and we give an estimate in writing after the first conversation. Prices for this work are set out on the prices page, together with what is included and what would change the figure, so there is no surprise at invoice stage.

We will not rewrite your show for you, and we will not recommend equipment simply because it is newer. If the honest finding is that your workflow is sound and one hand-off needs attention, that is what the report will say. In mid autumn many teams book a review before the winter schedule of events begins, which gives time to rehearse any agreed changes calmly.