Before You Book Crew Training: A Checklist for Studio Managers

A workshop works best when the people who depend on each other learn together. Gallery staff, sound, camera operators and the engineer on call all touch the same signal path, yet they are often trained separately. Mixed groups expose assumptions: the camera team learns what the gallery sees when tally fails, and the gallery learns why a pedestal move takes the time it does.

Group size matters too. Beyond about eight people, hands-on exercises become demonstrations, and quieter crew members stop asking questions. If your team is larger, two shorter sessions usually serve better than one long one.

Also think about freelancers who work with you regularly. Including them costs little and prevents the habit of explaining the same routine on every booking.

Ask the trainer plainly whether the content will use your equipment, your patching and your naming conventions. A talk about signal flow in the abstract is easy to give and easy to forget. Tracing a source from camera head through the router to a gallery monitor on your own system is something people remember the next time a feed disappears.

Send diagrams, patch lists and any existing fault logs beforehand, even if they are untidy. A good trainer would rather see a messy real system than a tidy theoretical one. If documentation is thin, say so; building a simple signal chart together can be part of the day.

Agree in advance which fault-finding exercises are safe to stage on live infrastructure and which should be walked through on paper or on a spare chain.

On-site training competes with real work, so timing deserves care. Pick a block when the studio is dark or when a rehearsal can double as a practical exercise. Running a workshop beside a live show rarely works; attention drifts to the transmission and the trainer is left with half a room.

Allow room for breaks and for questions that run over. Fault finding in particular produces tangents that turn out to be the most useful part of the session, and rushing them defeats the purpose.

Check practical points as well: access to the control room, a space with a screen or whiteboard, and whether any equipment must be taken out of service. Telling the crew early, and explaining why the session matters, makes attendance something people want rather than endure.

Before committing, ask what remains once the trainer leaves. Useful outputs are modest: a one-page fault-finding sequence for the most common failures, an annotated signal diagram, and a short list of routines the crew agreed to adopt. These live on the gallery wall or in the shared drive and get used, unlike slide decks.

Decide who owns follow-up. Someone on your team should be responsible for checking, a few weeks later, whether the routines have stuck and whether the same faults still catch people out. Without an owner, good intentions fade by the next busy week.

Finally, be clear about scope in writing. The enquiry goes through the contact page, a written quotation confirms what the session includes, and an invoice follows, so nothing is left to assumption on either side.