The Tools We Use to Plan a Gallery Layout

Start with paper, not equipment

Before anyone talks about desks or monitor sizes, we ask for three documents: a floor plan of the gallery, a list of every source that will arrive in it, and a list of every destination that has to leave it. Most layout problems we meet in control rooms trace back to a missing line in one of those lists. A camera that was added late, a graphics feed nobody counted, a return that the presenter needs but nobody drew. We draw the room to scale on a plain grid, because a scale drawing settles arguments that opinions cannot. If the producer wants a seat beside the vision mixer and the drawing shows only forty centimetres between the desk and the wall, that conversation takes a minute instead of a week of site visits.

The signal list is the second tool, and it is deliberately dull. Each row has a source name, its format, where it physically originates, and where it must arrive. We keep naming consistent across the whole job, so a camera called Cam 2 on the drawing is Cam 2 on the router label, the multiviewer tile and the intercom sheet. That consistency matters more than any piece of hardware. When a show is running and an operator says a name, everyone in the room should picture the same thing. A list that agrees with itself is the cheapest reliability measure we know.

• Scale floor plan of the gallery and adjoining areas
• Source list with format and origin
• Destination list with format and location
• One naming scheme used everywhere

Sightlines and the monitor wall

Once the lists exist, we test sightlines. We mark each operator position on the drawing and draw lines to the monitors that person must read during a show. The vision mixer needs program, preview and every camera at a glance. The director needs the same, plus the timing and graphics. The audio operator may need very little of the wall but a clear view of the studio floor. We use simple cardboard cut-outs at the correct scale when the room allows it. Placing them on the plan, or even on the real floor with tape, shows quickly which positions are crowded and which are wasted.

Monitor wall layout follows from this exercise, not the other way round. We group sources by function rather than by number: cameras together, then playback and graphics, then outside feeds. Program and preview sit where the director's eyes fall naturally, usually at the centre, and the wall is arranged so that a glance never requires a head turn. We also check viewing distance and height against the screen sizes, because a monitor that looks fine in a catalogue can be unreadable from the back row. Where a room is narrow, a smaller tile with clear labels beats a larger one that forces operators to lean.

Routing diagrams that operators can read

The routing diagram is the tool people expect us to be proudest of, but its real test is whether an operator who did not build the room can follow it at two in the morning. We draw it left to right, sources on the left, destinations on the right, with the router in the middle and every path labelled in plain words. We avoid decorative detail. Cable types, patch points and conversion boxes appear where they matter for fault finding, and nowhere else. A diagram crowded with every connector teaches nobody anything.

Alongside the diagram we keep a short table of default router crosspoints: what each destination shows when the system is first switched on. A predictable start state removes a surprising number of early-show problems, because operators know what a blank or unexpected picture means. We also mark which paths are shared and which are dedicated. If two destinations depend on one feed, the diagram says so, and the team can decide in advance what to do when that feed fails rather than discovering the dependency on air.

• Left-to-right flow, sources to destinations
• Plain labels on every path
• Default crosspoints written down
• Shared dependencies marked clearly

Operator procedures written as short run sheets

Hardware does not run a show; procedures do. For every gallery we write a run sheet that covers the minutes before the show, the routine during it, and what happens when something goes wrong. Each step is one sentence, begins with a verb, and names who does it. We keep these to a single page per phase. Long manuals are written with good intentions and read by nobody. A single page can be pinned beside the desk, marked up with a pen, and revised after every rehearsal.

The most useful section is usually the fault list. We ask the team which failures they fear most, then write the first three actions for each. Loss of a camera, loss of talkback, a frozen graphics machine. The answers are rarely complicated, but having them agreed in advance means nobody improvises while the clock is running. We test these sheets by walking the team through them in a rehearsal, with someone deliberately triggering a fault. The wording changes after that first run, which is exactly why we do it before the real show.

Rehearsal as the final measuring tool

No drawing replaces watching real operators use a room. We schedule at least one full rehearsal with the actual crew, and we spend most of it observing rather than adjusting. Where do people reach? Who turns around to ask a question? Which monitor does the director keep glancing past? We note these small movements on the floor plan. A desk shifted by a few centimetres, a monitor raised, a label enlarged: the changes are modest, but they come from evidence and not from assumption.

This is also when the documents earn their keep. If a rehearsal exposes a missing source, the signal list shows exactly where it should have appeared. If an operator hesitates, the run sheet shows which line was unclear. Each tool checks the others. By mid autumn many teams are preparing for busier seasonal schedules, and the rehearsal slot is the first thing squeezed. We would argue it is the last thing to cut, since a single rehearsal usually catches more than a week of desk-based review.