Planning an On-Site Crew Workshop That Actually Sticks
A practical guide to setting up a training day for a studio crew: choosing what to cover, preparing the room, running the session and checking afterwards that routines have changed.
6 minutes to read
Start with the faults your crew already knows
The best workshops begin with a short list of problems the crew has already met. Before anyone books a day, ask the gallery team, the floor staff and the engineers to write down the last five times something went wrong during a live show or a rehearsal. Keep the notes plain: what was seen, who noticed, how long it took to fix. You will usually find the same three or four themes repeating, such as a lost return feed, a late graphics cue or a camera that came up with the wrong colour balance.
That list becomes the spine of the session. It stops the day from turning into a general lecture on signal flow and keeps it tied to the building, the kit and the people who will be in the room. When I run on-site sessions for crews, I ask for this list at least a week ahead so that the exercises can be built around real equipment and real habits.
- Collect five recent faults from each department
- Note how long each one took to resolve
- Group them by signal path rather than by person
Decide who needs to be in the room
A workshop works best when the people who depend on each other train together. A vision mixer who has never heard the audio assistant describe a sync problem will not change how they call a cut. Aim to bring one or two people from each role in the live chain: gallery, sound, camera, graphics and the engineer on call. Smaller groups of six to ten let everyone touch the equipment and speak up.
If the crew works in shifts, run the session twice rather than squeezing everyone into one afternoon. Cover for the live schedule is a practical matter that should be settled by the studio manager before the date is fixed. A half-empty room, or one where half the crew keep stepping out to take calls, teaches very little and leaves the rest feeling that the training was an interruption.
Prepare the room and the kit
Choose a space where the real equipment can be used, ideally the gallery itself or a studio on a quiet day. A classroom with slides is a poor substitute for a working desk where a signal can be broken on purpose and traced. Agree in advance which systems may be switched, patched or taken offline, and tell anyone who relies on them. Nothing sours a training day faster than an accidental on-air problem.
Bring printed signal flow drawings for the room, even rough ones. If none exist, drawing the first version together on a whiteboard is a useful exercise in itself, because people disagree about where the embedder sits or which sync source feeds the monitors. Have spare cables, a test signal generator and a loop of known good material ready so the group can compare a faulty chain against a clean one.
- Printed signal flow drawing for each position
- Test patterns and a known good clip
- A named person to protect the live schedule
Run the day in short, practical blocks
Keep explanation short and the hands-on part long. A useful rhythm is twenty minutes of talk on one routine, then forty minutes of exercise at the desk. Start with the path a picture and its sound take from camera to output, since everything else, including fault finding, depends on that map being in everyone's head. Then move to live routines: how the team confirms sources before a show, how cues are called, how problems are reported over talkback.
Fault finding comes in the afternoon, when people are comfortable. Introduce a fault quietly, such as a muted embedder channel or a delayed return, and let the crew work through it with the drawing. Insist on a method: check the last point where the signal was good, move one step at a time, and say aloud what has been ruled out. The aim is calm, repeatable habits rather than clever guesses.
Leave something written behind
A session that leaves nothing on paper fades within a fortnight. Before everyone leaves, agree a one-page pre-show check, a short fault reporting routine and an updated signal flow drawing, and pin them where the team works. Keep the language the crew itself used during the day rather than textbook terms, so the notes feel like theirs.
Ask one person in the studio to own the documents and update them when equipment changes. That ownership matters more than the quality of the first draft. A drawing that is wrong is worse than no drawing, because people trust it. Written notes also help new starters, who can be walked through the routines in an hour instead of picking them up through mistakes during live shows.
- One-page pre-show check
- Fault reporting routine for talkback
- Named owner for the drawings
Check what changed a month later
Return to the original list of faults after a few weeks and see which ones have stopped. Ask the crew, not just the managers, because they will tell you plainly whether the checks are being used or have quietly lapsed. If a routine has been dropped, find out why; it is often too long, or sits at the wrong point in the preparation for a show.
Where the same fault returns, treat it as a sign that the cause lies in the equipment or the layout rather than in the people, and consider a separate review of that path. Training is one part of a steady workflow, and it should sit alongside sound maintenance and clear responsibilities. A short follow-up conversation costs little and shows whether the day made a difference that lasts.
A good crew workshop is built from the studio's own faults, held at the real desk, run in short practical blocks and followed by a few written routines that someone owns. Keep the group small, include every role in the live chain and look again after a month. Done this way, a single day gives the team a shared method for tracing problems, and that is worth more than any amount of slides.
Ask for a quote
- Phone
- 01223 480162
- Write to us
- [email protected]