What We Now Teach in the Final Delivery Formats Module

Why the delivery module changed

Final delivery is the last thing a learner does and, too often, the thing they rush. Over the past term we noticed that people who edited a voiceover cleanly still sent files that were rejected or misfiled, because the format, sample rate or name did not match what the recipient expected. That pattern is what prompted a rewrite of the module on final delivery formats.

I am Catrin Hughes, and I lead the mixing and delivery units. The rewrite keeps the module's purpose unchanged: exporting finished audio in the right file formats, at the right sample rates, with names that make sense to the next person who opens the folder. What is new is the order in which we teach it and the amount of practice attached to each step.

Learners now begin by reading a short delivery request, written the way a producer would write it, and decide what is being asked before touching the export dialog.

Broadcast, web and archive are three different jobs

The module is now split by destination rather than by file type. Broadcast delivery usually asks for uncompressed audio at a fixed sample rate and bit depth, with strict expectations about levels and silence at the head and tail of the file. Web delivery is more forgiving about format but cares about file size and consistency between episodes or segments.

Archive delivery is a different mindset again. The aim is to preserve the cleanest version of the work so that someone can return to it years later, so we cover keeping an uncompressed master alongside any compressed copies, and recording in the notes what was done to the audio.

Teaching these side by side lets learners see why one export setting is right for one destination and wrong for another, instead of memorising a single recipe.

• Broadcast: uncompressed files, fixed sample rate and bit depth
• Web: smaller files, consistent settings across a series
• Archive: an uncompressed master plus a short note of what was done

Sample rates without the mystery

Sample rate is the part learners tend to fear, so we spend real time on it. Video work commonly runs at one rate while music and web audio often use another, and mismatches cause quiet problems: drift against picture, unnecessary conversion, or a file that plays slightly off pitch in the wrong player.

We explain the idea in plain words and then let learners hear and measure the consequences on short authorised recordings. The practical rule we teach is simple. Find out what the timeline or the recipient uses, export to match it, and convert only when there is a stated reason.

This links back to the synchronisation module, because a delivery rate that disagrees with the project is one of the easiest ways to introduce an offset that nobody notices until review.

Naming files so nobody has to ask

A good file name answers questions before they are asked. In the revised module we practise a naming pattern that carries the project, the segment, the version and the date or revision number, in an order that sorts sensibly in a folder. Learners write their own pattern and then test it against a messy folder of near-identical exports.

The exercise is deliberately dull and surprisingly effective. People discover that names like final, final2 and really final tell the next person nothing, and that a short, consistent pattern saves more time than any plug-in.

We also cover what to leave out: spaces and unusual characters that some systems handle badly, and details that belong in a delivery note rather than in the file name itself.

• Project and segment first, so files group together
• Version or revision number, never the word final
• Avoid unusual characters and keep names reasonably short

The practice export at the end of each unit

Each unit now closes with a practice export. The learner receives a short delivery request, prepares the finished audio from an authorised recording, exports it, names it and writes a brief delivery note. An instructor then checks the result against the request and returns written comments.

The point is to rehearse the whole handover, not only the button press. Learners tell us this is the part that feels closest to real work, because the request is specific and the check is exact. A file at the wrong rate is simply wrong, and seeing that early is far kinder than hearing about it from a client.

Feedback is practical and patient. We point to what matched the request, what did not, and what to change next time.

What this means for current learners

Learners already part way through the course do not need to start again. The reworked delivery material is available to everyone studying the module, and the practice exports can be attempted at any point once the earlier units are complete.

If you are new, the prerequisite is modest: comfort with a basic audio editor and a willingness to work carefully with authorised recordings. You do not need prior experience of broadcast specifications. We explain each requirement as it arises and keep the examples realistic for UK producers working on reports, interview films and explainers.

Questions about the module are welcome through the contact page, and I read them myself.