Before You Commission a Gallery Workflow Review: A Checklist

A workflow review is most useful when it starts from a question rather than a general wish for things to run better. Before anyone visits your gallery, write down the one or two moments that worry you. It might be the handover between a pre-recorded package and a live link, or the minute after a presenter loses their earpiece. A review aimed at those moments produces fixes you can apply the following week.

I ask clients to bring three things to the first conversation: a recent on-air problem, however small, a description of who sits where in the gallery, and the programme formats that matter most. With those, the written review can follow real behaviour instead of an idealised diagram. Without them, the document tends to read as a list of sensible habits that nobody argues with and nobody acts on.

It also helps to say plainly who will read the report. A studio manager needs a ranked list of changes. A director needs to know what alters in their routine. A technical lead wants signal paths and labelling. One report can serve all three if you know the audience in advance.

• Name the specific on-air moments that cause concern
• List the formats the review must cover
• Say who will read the finished report

Reviewers can only assess what they can see, so collect what already exists before the work begins. That usually means a signal flow drawing, even a rough or out-of-date one, a list of sources feeding the vision mixer, the routing labels as they appear on screen, and any written running order templates your crew uses. Gaps in these papers are findings in themselves, and it is better to discover them during the review than during a live show.

If no drawing exists, that is not a barrier. Part of the review can be walking the racks with your engineer and sketching the paths together. What matters is that someone on your side can confirm what each cable and route is for. Unlabelled patches and routes known only to one person are among the commonest weak points I see in galleries of every size.

Check also that the drawing matches reality. Equipment gets swapped, a spare feed is borrowed for a guest, and a temporary fix quietly becomes permanent. Ask your team to mark anything they know has changed since the drawing was made.

• Signal flow drawing, even if rough
• Source and routing label lists
• Running order templates in current use
• Notes on any temporary or borrowed connections

Most galleries have a fallback plan. Far fewer have one that every crew member can recite. When preparing for a review, test your own plan with a simple question: if the main vision feed to transmission failed right now, who does what in the first thirty seconds? If you get different answers from the director, the vision mixer operator and the engineer, the plan exists on paper only.

List the failures you have already planned for, such as a camera dropping out, a lost audio source, a failed graphics machine or a dead intercom channel. Then list the ones nobody has discussed. The review will cover both, but it works faster when you have already admitted where the thinking stops. Reviewers are not there to judge a crew, only to make the next failure less disruptive.

Note too whether your fallbacks have ever been rehearsed. A plan that has been run once in a quiet hour is worth far more than a better plan nobody has tried, because rehearsal exposes the missing cable or the unclear cue.

A gallery is a small team working under time pressure, and many reliability problems are about communication rather than hardware. Before commissioning a review, consider how your crew talks during a show. Is there a standard set of cue words? Does the director speak to the floor and the gallery in the same way? Is there a clear rule for who may interrupt, and when?

Reviewers will want to observe a live or rehearsal session if possible, and your crew should know why someone is sitting at the back with a notebook. Explain that the aim is to improve the system, not to assess individuals. Crews who feel judged hide the very habits the review needs to see, and the resulting report is weaker for it.

If staff change often, say so. Freelance and rotating crews need procedures that are short, written down and easy to follow on a first shift. A review can then focus on what a newcomer needs in their first ten minutes in the gallery.

Before committing, be clear about what you will receive. In our case the outcome is a written review of gallery procedures, signal paths and fallback plans, with practical fixes. It is a document, not an installation. If the findings suggest equipment changes, those are separate decisions that you make afterwards, with no obligation attached.

Agree which programmes or formats are in scope, how many sessions the reviewer may observe, and who on your side will answer questions. Settle a realistic date for the report that does not collide with a busy broadcast period. Autumn schedules often fill up with election, budget and seasonal programming, so leave room for the crew to take part without strain.

Finally, decide how the report will be used. A review that is read once and filed achieves little. Pick someone to own the list of fixes, set a time to revisit it, and decide which items can be handled by your own staff and which need outside help.

• Confirm formats and sessions in scope
• Name one contact on your side
• Choose an owner for the list of fixes

When you speak to anyone offering this kind of work, ask how they handle live environments they cannot interrupt. Good reviewers observe quietly, ask afterwards and avoid changing settings during a show. Ask what the report looks like, whether fixes are ranked by effect on reliability, and whether the language is plain enough for the whole crew to read.

Ask also what they need from you and how long your team will be occupied. A review that demands days of your engineers is a cost you should weigh against the benefit. Ask whether they will revisit the findings with you after delivery, and what happens if something in the report is unclear or you disagree with it.

Lastly, ask for an example of a typical fix. Strong answers are small and concrete, such as relabelling a routing page, adding a standby source, or rewriting a cue sheet. If every answer involves buying new equipment, the review may be serving someone other than you.