Before You Commission a Control Room Workflow Audit: A Checklist

A review of how the gallery team, vision mixer and graphics systems cooperate touches people as much as equipment. Decide early which roles are in scope: director, vision mixer, graphics operator, audio, replay, producer, engineering support. Leaving a role out because it feels awkward tends to hide the very handover where problems start.

Tell the team in advance what is happening and why. Crews who understand that the aim is a written picture of the workflow, not a judgement of individuals, answer questions openly and show the shortcuts they really use. Those shortcuts are often the most valuable part of what a reviewer sees.

Agree who owns the result. One named person on your side should receive the report, ask follow-up questions and decide what to act on. Without that, a good document can sit unread for months.

Reviewers work faster and charge for less time on site when the documents are ready. Collect what you already have: signal flow drawings, input and output lists for the vision mixer, graphics template lists, show rundowns, and any fault logs from the past few months. Incomplete or out-of-date drawings are fine, provided you say they are out of date.

Equally important is the list of what changed recently. A new graphics engine, a software update on the mixer, a moved monitor wall or a new tally arrangement can all shift how people work. Tell the reviewer the dates if you know them, even approximately.

If some systems are managed by an outside supplier, say so and check whether the reviewer may speak to them. A workflow that depends on a third party's configuration cannot be described fully without that conversation.

A control room workflow audit is a written review. It describes how the room operates, where time or attention is lost, and what could reasonably change. It is not a rebuild, a purchase recommendation list for new kit, or a replacement for a full engineering commissioning. Agree this boundary before work begins so nobody expects more than the document delivers.

Ask whether the reviewer will watch a live transmission, a rehearsal or both. Watching live shows how pressure changes behaviour, while a rehearsal allows questions mid-flow. Many studios want both, and the choice affects the number of days involved and therefore the price.

Also settle the format of the report. A short summary for managers plus a more detailed section for engineers usually serves a mixed audience better than one long document.

The reviewer needs to stand in the gallery, which is rarely spacious. Decide where they will sit, who will explain things during a show, and whether the crew is comfortable with an observer during a sensitive broadcast. Small practical agreements here prevent awkwardness on the day.

Choose a period that is typical rather than ideal. A quiet week with a skeleton schedule tells the reviewer little about a busy one. If your output swings between heavy and light, consider covering one of each, even if the lighter session is short.

Finally, check the building basics: passes, parking in a central Cambridge location, and whether the reviewer can photograph screens or only take notes. These are minor items, but forgetting them wastes the first hour.

The last question on the list is the one most often skipped: what will you do with the findings? Set a date, a few weeks after delivery, for the team to meet and sort recommendations into those you can do immediately, those that need budget and those you will leave alone for now.

Some changes are simply a matter of renaming sources or agreeing who calls the next graphic. Others touch hardware or software and need engineering time. Separating them early keeps the report from feeling overwhelming.

If you want help turning findings into a training session or a follow-up check, say so at the start so the quotation can reflect it.