Getting Edit and Delivery Ready for the Dark Months Ahead

The clocks are about to change, daylight at the end of the working day disappears, and regional newsrooms move into the busiest stretch of their year. Weather stories, budget coverage, remembrance events and the run into the festive schedule all arrive within a few weeks of each other. Edit and delivery is where that pressure lands, because every story, however it was shot, has to pass through the same few machines and the same few people before it reaches air.

I spend much of my time reviewing how footage moves through newsrooms, and the same pattern repeats each year. Teams plan their camera cover for winter but leave the finishing end as it was in summer. Then a wet Tuesday brings three packages at once, the export queue backs up, and a caption file goes missing. These notes are about the small decisions that prevent that, made while the diary is still quiet.

Every broadcaster and platform asks for slightly different files: frame rate, codec, loudness level, caption format, slate and colour bars, even the file naming. In a calm week these differences are an irritation. In a breaking-news hour they are the usual cause of a rejected file and a second export that costs ten minutes you do not have.

Write one page per destination and keep it where the editor can see it. Test each specification once with a short, unimportant clip and confirm in writing that the receiving desk accepted it. Do this now, while a failed test costs nothing. If a destination changes its requirements over the winter, update the page the same day and tell everyone who exports, not just the person who heard about it.

• One specification page per destination, kept beside the edit station
• Send a short test clip and keep the acceptance message
• Record loudness, frame rate, codec and caption format on each page
• Date every revision so nobody works from an old copy

A good part of a fast edit is not editing at all. It is creating the project, importing graphics, setting the caption style, placing the lower third and arranging audio tracks. Done by hand each time, it adds minutes and invites small errors that surface only on air, such as a misspelt name or the wrong strap font.

Make a project template for each regular format: a voiced package, a short reader with footage, a live-link wrap and a clip for web. Each should open with tracks labelled, graphics loaded, caption styling set and export presets attached. Tom Pritchard, our senior editor, rebuilds ours at the start of every autumn and checks them against the previous winter's problems. Treat your templates as working equipment that needs a service, not as files you set once and forget.

Winter exteriors come back from the field grainier, flatter and with more colour cast from street lighting. An editor who has only cut summer material will lose time correcting it, and a rushed correction shows. Agree with your shooters how footage should arrive: which picture profile, whether files are labelled by location and time, and what to do about noisy low-light shots that still carry the best moment.

Give the edit desk a set of grading presets for common winter conditions, and a rule for when a shot is too poor to use even if the content is strong. Decide that rule in advance. Arguing over an unusable clip at ten to six is how packages miss the bulletin. Good notes from the camera operator about what was happening, who was speaking and what the audio holds also save a first-pass review of everything.

• Standard picture profile and file naming from the field
• Grading presets for street lighting, rain and overcast daylight
• A written threshold for footage too weak to broadcast

Captioning is the step most often squeezed when time runs short, yet it is the one a viewer notices first if it is wrong. Names, places and numbers are the usual failures, and automatic transcription handles local place names badly. Gloucestershire alone has enough awkward village names to trip any tool.

Keep a living glossary of local names, councillors, organisations and recurring terms, and have the person captioning check against it. Build the caption pass into the schedule as a defined step with its own few minutes, not an afterthought once the picture is locked. If two people are on shift, let one finish captions while the other prepares the export. If only one person is available, decide in advance which stories are captioned in full and which go with a shorter treatment, and say so to the desk.

• Shared glossary of local names and recurring terms
• A fixed caption check before every export
• A clear fallback when only one person is on shift

Storage fills quietly. By the start of December many small newsrooms discover that the drive holding live projects is nearly full, and someone deletes the wrong folder in a hurry. Agree now what is archived, where, and who confirms it. Keep delivered masters, caption files and a short text note of the story together so anything can be found when a complaint or a follow-up arrives.

Handover matters as well. Winter rotas bring leave, illness and cover from people who rarely sit at the desk. A one-page guide covering where projects live, how to export, whom to ring at the receiving end and what to do when a file fails will keep the evening running. Priya Chauhan and the team can help write one, but the best version is the one your own editors recognise as how the desk actually works.