Keeping Revision Rounds Within Scope: What We Teach in Review Versions

Why the review stage gets its own module

Review Versions and Revisions is the last module in the curriculum, and for many learners it is the one that changes how they work day to day. Editing a voiceover cleanly is a craft skill. Getting a finished piece signed off without the work drifting into endless small changes is a different skill, and it deserves its own teaching time.

In these autumn weeks, with several groups reaching this point in the course, it seemed right to explain what the module covers and why it sits where it does. By this stage learners have prepared source files, edited takes, cleaned dialogue, balanced levels and locked audio to picture. The review version is where all of that is shown to someone else for the first time.

The module is practical. Learners work with an approved script and authorised recordings, and they practise the conversation around the audio as much as the audio itself.

What a review version actually is

A review version is a working copy made for judgement, not a final deliverable. It carries everything the reviewer needs to comment accurately: the edited voiceover laid against picture, clear markers where cuts or repairs were made, and a short note stating what was done and what remains open.

We teach learners to export it in a format that plays reliably on whatever the reviewer has to hand, with a clear file name that shows the version number. A reviewer who cannot open the file, or cannot tell which version they are hearing, will send feedback that is vague or about the wrong take.

Learners also practise keeping a review version honest. If a noise reduction setting is still provisional, or one sentence has no clean alternative take, the note says so plainly. Raising a known weakness yourself keeps the review focused on decisions rather than discoveries.

• Edited audio laid against picture
• Version number in the file name
• A short note of what was done and what is open

Receiving feedback without losing the thread

Feedback rarely arrives in a tidy form. A producer might write that a line sounds flat, that a pause feels long, or that the whole second half needs more warmth. In the module, Daniel Okafor and I have learners sort comments like these into things that can be acted on and things that need a question first.

A comment that names a timecode and a wish, such as shortening a gap before a sentence, can be handled directly. A comment about feel needs a short reply asking what the reviewer is hearing and what they would prefer. Learners practise writing those replies in a calm, brief way that keeps the reviewer involved without turning every remark into a debate.

They also practise logging each comment against the version it came from. That record becomes useful the moment two reviewers disagree, because the disagreement is visible on the page and can be settled by the person who has the final say.

Agreeing scope before the first round

The most useful habit in this module is deciding scope at the start, not in the middle of a dispute. Learners draft a short statement for each project: how many review rounds are included, what counts as a revision, and what counts as new work, such as a rewritten script or a changed running order.

A revision, in the sense we teach, corrects or adjusts audio that was edited from the approved script and the recordings supplied. A changed script, a replacement recording or a new picture cut is a different job and is agreed separately. Putting that line in writing early makes later conversations short and friendly.

Learners practise explaining this to a client in plain words, without sounding defensive. The aim is not to limit helpfulness. It is to make sure everyone knows what the next round will cover and roughly how long it will take, so that nobody is surprised.

• Number of review rounds agreed up front
• Revision defined as changes to the approved script and recordings
• Script or picture changes treated as separate work

Running a revision round in practice

When feedback comes in, learners work through it in a fixed order. They read all the comments once before touching the timeline, group them by section, and resolve any contradictions by asking before editing. Only then do they make changes, saving a new numbered version rather than overwriting the last one.

Each round ends with a short reply that lists what was changed and points to anything left unchanged, with a reason. If a request would fall outside the agreed scope, the reply says so kindly and offers to handle it as a separate piece of work.

This routine keeps the audio steady. A mix that has been nudged in ten directions by ten loosely recorded comments tends to lose the natural rhythm that the earlier modules worked to protect. Careful rounds protect it.

Where this leaves the course

By the end of the module, learners hold a complete workflow from authorised recordings to a signed-off result, and they can describe each handover in terms a producer will understand. The final delivery work then follows naturally, because the file being exported has already been agreed by the people who matter.

The skills here are modest and practical, and they depend on practice rather than talent. Learners who rehearse the notes, the replies and the scope statements find that review rounds become shorter and calmer, and that the audio comes out better for it.