How We Now Scope a Studio Integration Project From First Visit

Over the last few months we have reworked the opening stage of our Studio Equipment Integration work. Previously a first visit was mostly a conversation and a walk round. Now it produces a short written record that the studio manager can keep, question and hand to colleagues before anything is ordered.

The reason is simple. Vision mixers, routing, monitoring and intercom each look manageable on their own, but problems appear where they meet: a tally that does not follow a source, an intercom channel that cannot reach the floor, a monitor wall that shows the wrong feed after a re-route. Writing the whole chain down first makes those joins visible while they are still cheap to change.

I lead lighting and cameras here, so I see the effect from the floor. When integration is vague at the start, my crews end up waiting for a signal that should have been there at the first rehearsal.

The visit takes a working day for most studios. We look at the control room and the studio floor together, trace the existing signal paths from camera to output, and note where cable runs, patch bays and power are placed. Helen Marsden, who designs our systems, usually attends, and she asks the crew what annoys them most during a live show, because that answer often points to the real fault.

We also record how the room is used. A news desk that goes live every morning needs different assumptions from an interview set used twice a week. Staffing matters too: a gallery run by two people cannot rely on a layout built for five.

None of this needs the client to prepare much. A floor plan helps if one exists, and a list of the equipment already in the building saves time on the day.

• Existing signal paths traced from camera to output
• Cable routes, patch bays and power noted
• Typical show formats and crew numbers recorded
• Known faults and workarounds listed by the crew

After the visit we write a specification in plain language. It names each piece of equipment by role rather than by catalogue enthusiasm: what the vision mixer must handle, how many sources the router must carry, which intercom channels each position needs, and how monitoring is arranged for the director, the engineer and the presenter.

Alongside the equipment list sits a signal diagram. We keep it to one page where we can, because a diagram nobody can read in a crisis is no use. Fallback paths are drawn on it too, so that the question of what happens when a source drops is answered before it occurs.

The client reads this, marks it up and returns it. We would rather hear disagreement at this stage than discover it on installation day, when changing a decision means moving racks.

Where the studio can allow it, we now install in stages that match the way the room is used. Routing and power usually come first, since everything else depends on them, followed by intercom, then monitoring, and finally the vision mixer and its control surface. Each stage is checked on its own before the next begins.

This is slower on paper but faster in practice. A fault found in the router is easy to isolate when nothing else has been connected to it yet. Found after the whole gallery is wired, the same fault can look like five separate problems.

If a studio must keep broadcasting during the work, we plan around its schedule and say honestly which stages will need a quiet period. That conversation belongs in the specification, not in the week itself.

• Routing and power first
• Intercom and monitoring next
• Vision mixer and control surface last
• Each stage tested before the following one

Our test stage is built around a rehearsal rather than a checklist read by an engineer alone. We run the formats the studio actually produces: a cold open from the desk, a switch to a remote guest, a roll-in, a return. The crew operate the system while we watch where they hesitate.

Hesitation tells us more than a passed test. If the director reaches for a button twice, the layout is wrong even if the function works. We adjust labels, shortcuts and monitor positions on the spot, and record each change in the documentation so the next engineer is not guessing.

We also deliberately break things during the test: pull a source, drop an intercom line, lose a monitor feed. Watching the crew recover with the written fallback in hand is the real proof that the fallback is usable.

At handover the studio receives the final signal diagram, the equipment list with settings recorded, and a short operating guide written for the people on shift rather than for engineers. Labels in the gallery match the names in the documents, which sounds trivial and is not.

We offer a follow-up visit once the crew has used the system for a few weeks. By then they have opinions, and some of them are better than ours. Small revisions at that point tend to be quick and make a noticeable difference to how calm a live show feels.

This is the approach we apply to every integration enquiry now, whether it is a single control room refit or a full studio fit-out.