How to Prepare Your Studio for a Workflow Review

Start with what the review is meant to answer

A workflow review works best when it is asked a narrow question. Before anyone visits your studio, write down the one or two problems you want settled. It might be that changeovers between programmes take too long, that a particular feed drops out now and then, or that new crew members struggle to learn the routing. A vague request such as making everything better produces a vague report, whereas a focused question lets the reviewer spend the visit looking at the right racks, cables and habits.

At mediqly we assess the signal path and the way a production actually runs, then report in writing on what to improve. That report is only as useful as the brief behind it. Spend an hour with your studio manager and your most experienced operator and agree on the symptoms, how often they occur and what they cost you in time or retakes. Those few lines become the opening page of the review.

• Name the specific symptom, not a general wish
• Note how often it happens and since when
• Say who is affected: presenters, camera operators or playout

Gather the paperwork you already have

Most studios hold more documentation than they realise, scattered across folders and inboxes. Collect any signal flow diagrams, patch bay labelling sheets, equipment lists and wiring schedules, even if they are out of date. An old diagram is still useful, because the gaps between it and the room as it stands today often point straight to the cause of a fault. Do not tidy it up before sharing; a corrected copy hides the very drift the reviewer needs to see.

If no diagram exists, a sketch on paper is a perfectly good start. Draw the path from each camera and microphone through the mixer, monitoring and routing to the final output, and mark anything you are unsure about with a question mark. Those question marks tell the reviewer where assumptions have crept in. Add the make and model of key units, firmware versions where you know them, and the approximate age of the cabling runs.

• Signal diagrams, even if outdated
• Patch labelling and cable schedules
• Equipment list with models and firmware versions

Record a real production day, not an ideal one

The most revealing material is an honest account of a normal working day. Ask the crew to keep a simple log for a week: what was set up, what was changed mid-session, what had to be reset and how long each step took. A workflow can look sound on a diagram and still lose twenty minutes to a routine that everyone has quietly worked around. Those workarounds are exactly what a written review is meant to bring into the open.

Resist the urge to run a perfect session while a reviewer is watching. If a live show usually goes out with a late rehearsal, let it happen that way. Where possible, photograph the control room and the rack layout from a few angles, and note which equipment is used constantly and which sits idle. A log kept by three different people, in their own words, tells you more than a single polished summary ever will.

• A week of short notes from the people who operate the room
• Photographs of racks, desks and cable runs
• A list of regular workarounds and who taught them

Brief the people who will be asked questions

A review can feel like an inspection, and crews sometimes respond by saying what they think the visitor wants to hear. Tell your team beforehand that the purpose is to find friction in the system, not fault in the individuals using it. Ask each operator to prepare one thing that slows them down and one thing that works well and should be left alone. Both belong in the report, because a good review protects what already functions as much as it points to what should change.

Arrange time with the people who know the room best, usually the senior operator and whoever handles maintenance. Keep these conversations short and practical, standing at the equipment rather than around a meeting table. Memory is sharper when a person can point at the patch bay or the intercom panel. If freelancers regularly work in your studio, include one of them, since they see habits that permanent staff no longer notice.

• Explain that the aim is to improve the system, not to judge people
• Ask each operator for one pain point and one strength
• Include a regular freelancer if you use them

Agree the scope and what the report will contain

Before any work begins, settle in writing what the review covers. A studio may want only the signal path from cameras to the mixer, or the whole chain through monitoring, intercom and playout. Say which rooms are included, which productions will be observed and whether any live broadcasts are off limits for access. Thomas Willoughby handles this stage at mediqly, confirming scope and a quotation so that nobody is surprised by what is, or is not, being examined.

Ask also what shape the findings will take. A useful written report separates faults that need fixing soon from habits worth changing over time and from items that are simply fine. It should say plainly what evidence supports each point. Agree who will receive it and how decisions will be made afterwards, because a report that nobody owns tends to sit in a folder. A short follow-up conversation to go through the findings is worth arranging at the outset.

• Rooms, productions and access limits written down
• Findings sorted by urgency
• A named person who owns the next steps

Keep the review useful after it is delivered

The report is the beginning of the work rather than the end. Once it arrives, read it with the crew, not only with management, and mark each point as agreed, to be discussed or not applicable to how you work. Small changes such as relabelling a patch bay or documenting a routing preset can be made within days, and they build confidence for the larger decisions about replacing equipment or reorganising the control room.

Plan to revisit the same log after changes are made. If you timed the changeover before, time it again and compare the figures honestly. Autumn is a sensible season for this, since many studios are settling into a busier schedule and changes made now have months to prove themselves. Keep the original diagram and the report together, dated, so that the next reviewer, or the next new starter, can see how the room has developed.