What Final Audio Delivery Costs and What Moves the Price

Why delivery is never just pressing export

Final delivery is the point where the work becomes a set of files somebody else will rely on. A producer may think of it as a few minutes at the end of a project. In practice it is a stage with its own decisions: which formats, which sample rate, which naming, and how each file will be checked before it leaves the studio. When I teach this module, I start by asking learners what happens if a file is rejected. A broadcaster's technical team, a web platform and an archive each have different expectations, and a rejected file means a second render, a second check and often a second round of messages. That repeat effort is where most of the cost in this stage sits.

The cost therefore follows the amount of care, not the amount of audio. A ten minute explainer delivered in one format is quick. The same ten minutes delivered for broadcast, web and archive, each with its own rules, is three small jobs sharing a source. Understanding that difference is the first step toward a fair estimate, whether you are budgeting for your own time or asking someone else to finish the work.

The number of formats is the biggest driver

Each additional format adds a render, a listening check and a naming pass. Broadcast delivery tends to ask for uncompressed files at a set sample rate. Web delivery usually accepts compressed files and rewards a smaller size. Archive copies are kept for the long term and are usually uncompressed, with careful labelling so that nobody has to guess what a file contains in five years. A producer who knows the destination before the edit finishes saves real money. A producer who says everything might be needed pays for every possibility. I always ask for the destinations in writing, because a vague answer at the start tends to become an extra version later.

In the course, learners build a short delivery list for a sample project and see how the time adds up. Two formats take a fraction longer than one, since the checks overlap. Four formats take noticeably longer, because each one needs its own listening pass from start to finish. The pattern is steady enough to plan around, and it is worth recording for your own projects.

• One destination format is the quickest and cheapest case
• Each extra format needs its own render and listening check
• Archive copies add labelling and storage notes

Sample rates, file types and naming

Sample rate and file type are small choices with large consequences. Picture timelines usually run at a fixed rate, and audio that arrives at a different one must be converted with care or it drifts. Converting is quick, but verifying that nothing shifted takes patience, and that verification time belongs in any honest price. Naming looks trivial until a folder holds forty files called final, final two and final corrected. A clear scheme, with the project, the segment, the version and the format in a consistent order, costs minutes to set up and saves hours later. It also makes it far easier for a second person to find the right file.

I teach learners to settle the scheme before the first export, not after. If a client already has a convention, follow it exactly. If not, agree one in a single short message and keep to it. Projects that skip this step tend to need a tidying pass at the end, and that pass is billed time like any other, whoever does it.

Review versions and revisions affect the final figure

The delivery stage rarely stands alone. It follows a review version, and what happens in review decides how many times the final files are rendered. A clear approval means one clean export. Late changes mean the export is repeated, and each repeat needs its checks again. This is why revision scope matters to price. If a project allows a stated number of revision rounds, the delivery cost can be fixed with confidence. If rounds are open ended, the final stage becomes unpredictable and the estimate has to allow for that uncertainty.

The practical advice is to freeze the edit before delivery begins. Once the approved version is locked, changes that arrive afterwards are treated as a new piece of work rather than a correction. It feels strict, but it protects both sides. Producers know what they are paying for, and the person finishing the audio is not asked to re-render files for a decision that was made weeks earlier.

• Approved edits give one clean export
• Open ended revisions make the final stage unpredictable
• Changes after approval are scoped as new work

Checking, listening and quality control

Every file that leaves should be played back, at least at the start, in the middle and at the end, and ideally in full. Automated meters catch levels and clipping, but they cannot tell you that a breath was exposed by a conversion or that a fade ends a fraction early. Listening takes real time, and it scales with the running length and the number of files. A short segment in one format might need only a few minutes of checking. A long programme in several formats can need a full afternoon. This is the part of delivery that people underestimate most, and it is the part I would least recommend cutting to save money.

Learners keep a simple checklist during the course: levels against the target, format and rate confirmed, names correct, playback complete, files opened on a second device. The list is short, and it takes the guesswork out of the final stage. When we quote for finishing work for producers, the checking time is stated openly so nobody is surprised by it.

Planning your own budget for delivery

To estimate delivery honestly, start with the destinations, count the formats, note the running length and decide how many review rounds you will allow. Those four facts explain most of the price. Everything else is smaller detail, such as naming conventions, archive notes or a request for a written delivery summary.

If you are learning the work yourself, treat delivery as its own block in your schedule rather than the last five minutes of the project. Leave time for a proper listening pass and a second look at the file names. Projects that do this rarely come back with rejected files.

If you would rather hand the finishing over, a quote based on those four facts will be clear and comparable, and you can ask for the figures to be broken down by stage.

• List every destination before editing ends
• Count formats and total running length
• Decide the number of revision rounds up front
• Allow separate time for checking