Five Workflow Planning Mistakes We See Before a Programme Reaches Air

The commonest mistake I meet is treating the delivery specification as something to read once the cut is finished. By then the frame rate, audio layout, loudness target and file wrapper have already shaped decisions that are expensive to reverse. A programme shot and graphics-built at one rate, then asked to arrive at another, picks up conversion artefacts that nobody planned for and nobody wants to own.

The fix is dull and effective: obtain the broadcaster's or client's technical requirements at the first planning conversation, and write the relevant lines into the workflow document before cameras are specified. If the requirements are not yet available, record the assumption you are working to and who confirmed it, so a later change is a visible decision rather than a surprise on delivery day.

• Ask for the written delivery spec during planning, not after the shoot
• Record frame rate, audio layout and loudness target in one place
• Note any assumption and the name of whoever agreed it

Ingest looks trivial on a diagram. In practice a multi-camera studio day produces many cards or recordings that must be copied, verified and labelled while the crew is still tired and the next set-up is waiting. When one person is asked to do this between other jobs, naming slips, a card is overwritten, or a clip is copied once and never checked.

We plan ingest as a named job with a named person and a defined place to work. Every copy is verified against its source before a card is cleared, and clips follow a naming pattern agreed before the first take. It is not glamorous, but a clean ingest log is what lets an editor trust the material on Monday morning.

• Give ingest an owner rather than sharing it around
• Verify every copy before any card is cleared
• Agree the naming pattern before the first take

Titles, lower thirds and bugs are often arranged last, because they feel like decoration. They are not. Graphics have templates, fonts, safe areas and sometimes data feeds, and each of those can fail at the worst moment. A name spelled wrongly in a lower third is seen by everyone watching and corrected by no one until the next transmission.

Our habit is to collect names, titles and captions from the producer early and have one person check them against a written list. Templates are tested on the actual playout chain, not only on the designer's screen, so that colour, legibility and safe area are judged where the viewer will see them. Late changes are accepted, but they pass through the same check as everything else.

• Collect and verify names and captions before the shoot
• Test templates on the real playout chain
• Route late changes through the same proofing step

Every component of a playout chain can work alone and still fail as a system. A file plays on the edit machine and stutters on the playout server, or an audio channel arrives in the wrong order because two systems follow different conventions. These faults are found cheaply in a rehearsal and expensively on air.

Wherever the schedule allows, we run a short end-to-end test with representative material: a few minutes of picture, sound and graphics taken from the editing area through to the output, checked on the monitoring the operator will actually use. Even a brief test exposes mismatched formats, missing codecs and wrongly mapped channels. If time is truly short, test the riskiest element first and say plainly what remains unchecked.

• Run representative material through the whole chain
• Check on the monitoring the operator will use
• If time is short, test the riskiest element first

A workflow understood by a single engineer is a risk, however capable that engineer is. Illness, a second location or a handover to another crew can leave everyone guessing which folder holds the approved version or which output carries the clean feed. I have inherited enough undocumented set-ups to be firm about this.

We keep a short, current document for each production: signal and file paths, naming rules, contacts, who approves what, and where final files go. It is written in plain language and read aloud at the start of the day so errors surface early. Keeping it current matters more than making it elaborate, and it is revised whenever the plan changes, not once afterwards.

• One short document covering paths, names, contacts and approvals
• Read it aloud at the start of the day
• Update it whenever the plan changes

None of these mistakes is exotic, and that is the point. They share a cause: the work between shoot and air is treated as a gap to be filled at the end rather than part of the programme from the start. Giving it the same attention as cameras, lighting and sound is usually enough to prevent most of the trouble.

If you are planning a programme and are unsure which of these deserves attention first, begin with the delivery specification and work backwards. Each earlier stage then has a clear target, and the people responsible for ingest, graphics and playout know what they are building towards. Conversations in these weeks of mid autumn, before winter schedules fill, tend to go more calmly.