Inside the Edit Suite: How a News Package Is Actually Cut

When students arrive in the edit suite, most expect to open the software and start dragging clips. The real work begins earlier, with a quiet hour of watching. I ask everyone to play back every clip from the shoot at normal speed, with a notepad beside the keyboard, and to resist the urge to trim as they go. A shot that looks weak on first viewing sometimes turns out to be the only clean cutaway in the whole batch.

Logging is dull and it is where packages are won. Each note records the timecode, what is in the frame, whether the sound is usable and any moment that could cause a problem later, such as a face in the background or a number plate. By the end you know what you actually have, which is rarely what you remember filming on a cold morning.

We keep the log in plain words rather than a clever system. Anyone picking up the project should be able to read it and understand the day.

• Watch everything once at normal speed
• Note timecode, content and sound quality
• Flag faces, plates and anything sensitive
• Mark the strongest single moment

Before touching the timeline, I ask students to say the story aloud in two sentences. If they cannot, the edit will wander. This sentence becomes the spine, and every clip either supports it or is left out, however good it looks. It is the hardest discipline we teach, because students understandably love their own footage.

Next comes the interview selection. We pick the clips of speech that carry information or feeling and discard the rest, remembering that a contributor's words must keep the meaning they intended. Trimming a pause is fine; trimming a qualification so a person sounds more certain than they were is not. We discuss this openly in class, with real examples from student shoots, because the line is easier to see on a screen than in a rulebook.

Only then do we begin placing material, usually the voice track first, since pictures are chosen to fit the words.

The reporter's recorded voice goes down first, read against the script at the pace of an ordinary speaker, not a performer. We listen back for breaths, clipped words and sentences that read well but sound stiff. Often the script changes at this stage, and that is welcome. A line that takes too long to say usually takes too long to understand.

Pictures follow. The aim is simple: when the voice mentions something, the viewer should see it, or at least not see something contradictory. We avoid cutting to a shot merely because it is attractive. Wide establishing frames open sequences, close details give texture, and the cutaways that Daniel's students gather in the field are what make an interview cut feel smooth instead of jumpy.

Sound beds, natural effects and a light mix come last, and we keep levels steady so nothing jolts the listener.

• Voice track first, then pictures
• Match shot to what the words describe
• Use cutaways to hide interview joins
• Keep ambient sound consistent across edits

Before anything is exported, we run a fairness pass. I ask students to watch the package as someone who appears in it, then as someone who disagrees with its conclusion. Does the ordering imply a link the evidence does not support? Has a right of reply been included where one is needed? Is a caption, a name spelling or a place label correct? These are small questions with large consequences.

We also check the technical side: audio peaks within safe limits, no flash frames or black gaps, titles inside the safe area, and the running time matching the slot. A package that is twenty seconds over is not a package, it is a problem handed to somebody else.

Students sometimes find this stage tedious until they catch their own error. After that, they tend to take it very seriously indeed, and so they should.

• Watch as a subject and as a critic
• Verify names, spellings and captions
• Check levels, gaps and running time

The commonest fault is over-editing. Students add transitions, effects and music because the software offers them, and the story gets buried. A plain cut is almost always right for news. The second is length: a first assembly is nearly always too long, and cutting it back by a quarter makes it clearer without losing anything that mattered.

Another recurring issue is losing track of versions. Files named final, final2 and really final cause real trouble when a deadline is close. We teach a simple naming habit with dates and initials, and a habit of saving a fresh version before each major change.

Finally, some students avoid asking for a second pair of eyes. A colleague watching without context spots confusion in thirty seconds that the editor, who knows the story, cannot see at all.

• Resist effects and transitions
• Cut the first assembly back by a quarter
• Name versions clearly and save often

The edit suite is where a reporter's care shows. Good shooting and sound writing can be undone by a careless cut, and modest footage can be shaped into something clear and honest by a patient one. We do not ask for flashy results. We ask for packages that a viewer understands the first time and that the people in them would recognise as fair.

Most of this work is repeatable habit rather than talent: log carefully, state the story plainly, build from the voice, check fairness, then export. Students who practise that sequence on small items soon find they can handle longer ones without panic.

If you are early in your career, start by cutting ninety seconds well rather than three minutes badly.