mixlyra
Live Production Workflow: Common Mistakes and How to Avoid Them
JournalLive Workflow

Live Production Workflow: Common Mistakes and How to Avoid Them

Most live programmes that stumble do so for ordinary reasons: a vague run sheet, a rushed rehearsal, an untested fault plan. Here is what goes wrong and what to do instead.

James Whitaker6 min read

Run sheets that only the producer can read

The most common fault I see in a gallery is a run sheet written for one person. The producer knows that item four means the guest is already seated, but the vision mixer operator, the camera crew and the audio operator are reading the same line and guessing. When a segment overruns by thirty seconds, nobody can decide quickly what to drop, because the document does not say what is movable and what is fixed.

A usable run sheet gives every role something to act on. Each line carries the source, the camera or shot, the audio state, the graphics call and the planned duration. It marks hard times, such as a handover to another service, apart from soft ones. It also names who calls each cue.

Keep it to a page or two where you can. A sheet that has to be scrolled during transmission will be ignored at the moment it matters most.

  • Give every line a source, shot, audio state and duration
  • Mark fixed times separately from flexible ones
  • Name the person who calls each cue
  • Print copies so nobody depends on a screen

Treating rehearsal as a formality

Rehearsal is often squeezed to whatever time is left after set-up, and then used to run the show once at walking pace. That tests the happy path and nothing else. The problems that reach air are the awkward ones: the transition between two items with different camera positions, the guest who arrives late, the package that starts a second after the cue.

I would rather see a short rehearsal spent on the hardest three moments than a full run that skips over them. Repeat the difficult handovers until the crew can do them without looking at each other. Include the opening and the close, because those are the moments with the least margin.

Record the rehearsal if you can, and watch a few minutes back with the crew. Operators spot their own framing slips far faster on playback than from any note given afterwards.

No agreed fault procedure

Every studio has a failure it has half-planned for and several it has not considered at all. The usual mistake is to assume that someone will work out what to do when a camera drops out or a microphone crackles. Under pressure, three people start fixing three different things, and the programme suffers more from the confusion than from the fault.

A fault procedure is simply a short, agreed list. If the lead camera fails, which camera covers its shot, and who tells the presenter? If a radio microphone dies, which backup is live and who switches it? If the graphics system freezes, what does the director call? Write the answers down once, in calm conditions.

Agree who has authority to make the call on air. One named voice, usually the director, removes the most expensive second of hesitation.

  • List the likely faults per source: camera, audio, graphics, playback
  • Decide the fallback shot or source in advance
  • Name one person who decides on air

Leaving the crew to learn on transmission

A workflow is only as dependable as the people carrying it out, and a new operator placed on camera two for a live news bulletin is learning in front of an audience. This is not a criticism of the operator. It is a planning gap: the studio had a good process on paper and never walked a newcomer through it.

Brief each role on what the others need from them. A camera operator who understands why the director wants a tight shot held for eight seconds will hold it, rather than drifting to a better composition. An audio operator who knows the order of speakers can open the right microphone before the person speaks.

If crew change often, as they do in universities and smaller broadcasters, keep a one-page role card per position. It costs an afternoon to write and saves a great deal of repeated explanation.

Changing too much at the last minute

Late changes are unavoidable in live television, and the mistake is not making them but making them without a route through the system. A producer adds an item twenty minutes before transmission, the run sheet is updated on one machine, and the crew are told verbally by whoever happens to be nearby. Half the gallery works from the old version.

Decide how changes travel. One person owns the master run sheet, changes are announced to the whole gallery at once, and anything altered inside the final stretch before air is repeated back by the people it affects.

Resist the temptation to add one more thing. A programme with a clean, rehearsed running order will usually serve the audience better than a fuller one the crew have only half understood.

  • One owner for the master run sheet
  • Announce every change to the whole gallery together
  • Repeat back late changes before going to air

Skipping the review afterwards

The programme ends, the crew are tired, and the review is put off until a week that never comes. Without it, the same small faults appear in every edition: the late graphic, the slow handover, the microphone that is always opened a beat after the guest starts speaking.

A ten-minute debrief straight after transmission is enough. Ask three questions: what slipped, why, and what changes before next time. Write the answers into the run sheet or the fault list so the improvement is part of the process, not just a conversation.

Over a season, those small corrections matter more than any single piece of equipment. A studio that reviews every show tends to become steadier week by week, which is what producers actually want from a live workflow.

mixlyra

mixlyra plans and supports live television production from York: studio integration, camera work, acoustics, lighting and dependable daily workflows.

Contact

14 Navigation Road
York YO1 7EP
[email protected]
01904 557316