What Review Versions and Revisions Cost, and What Moves the Price

Why revisions are where budgets drift

When producers ask me what an audio edit will cost, the first quote rarely tells the whole story. The recording, the cleanup and the balance are usually easy to estimate. What stretches a job is the stage after the first listen, when feedback arrives and the edit begins to change. In my sessions on review versions and revisions, I start with this point because learners who understand it quote more honestly and plan their own projects better.

A review version is a working copy, not a finished file. It exists so that a client, a presenter or a commissioning editor can hear the whole piece and respond. Every response is a potential change, and every change has a cost in time. Some changes are tiny, such as lifting one word in level. Others ripple through a whole timeline, such as rewording a paragraph that sits under music and picture.

The factors that actually set the price

Price follows effort, and effort on a revision stage comes down to a short list of things. The first is the running time of the piece, because every listen-through takes as long as the programme itself. The second is the number of voices, since each additional speaker means more levels to match and more cleanup choices to revisit. The third is how much of the material has already been locked to picture, because changes after sync usually mean touching video timelines as well as audio.

The fourth factor is the form the feedback takes. A single consolidated list of notes with timecodes can be handled in one sitting. Comments that trickle in from five people over a week cost far more, even when each note is small. The fifth is how many rounds the job allows, which is why I teach learners to state that number before any work begins.

• Running time of the finished piece
• Number of speakers and sources
• How much is already locked to picture
• Whether feedback arrives as one list or in pieces
• Number of review rounds agreed at the start

Defining scope before the first review version

A revision scope is simply a written sentence or two that says what a round of changes covers. It might state that each round includes corrections to edits, levels and sync within the approved script, and that rewrites of the script itself are treated as a new request. That wording protects the editor from open-ended work and protects the producer from surprise charges.

In the course, learners draft a scope note for a sample explainer and then test it against realistic feedback. Does a request to swap a take count as a correction or a change of direction? Is moving a pause a revision or part of the original edit? Working through these cases on paper is far cheaper than discovering the answers in the middle of a live job. The note should also say who sends feedback and who approves the final version.

Handling feedback without losing the thread

Good revision handling is mostly organisation. I ask learners to number every note, record its timecode, and mark it as done, queried or declined, then return that list with the next review version. This gives the client a clear record of what changed and gives the editor a defence if a later round contradicts an earlier one.

Queries matter more than people expect. A note such as make it warmer can mean three different things, and guessing wrong spends a round that nobody planned for. Asking one short question before touching the timeline usually saves an hour. Equally important is keeping each review version labelled with a version number and the date in its file name, so nobody listens to an old copy and sends comments about a problem that was already fixed.

• Number each note and keep its timecode
• Mark notes as done, queried or declined
• Ask one clarifying question before guessing
• Version every file name

Where producers can lower the cost themselves

Most savings sit on the producer's side of the desk. Approving the script before recording means fewer pickups and fewer rewritten lines later. Gathering feedback from all stakeholders into one document before sending it avoids the repeated reloading and re-listening that fragments a day. Agreeing in advance who has the final word stops circular rounds where two reviewers undo each other's preferences.

Source quality also feeds into this stage more than people think. A clean, well-labelled set of authorised recordings produces a review version that needs fewer corrections, so the first round tends to be about taste rather than faults. I teach learners to treat the review version as a question put to the client, with the aim of getting a clear answer in as few rounds as possible rather than polishing endlessly.

Reading a quote with revisions in mind

When you compare quotes for audio finishing, look past the headline figure and ask how revisions are handled. Does the price include one round or two? What happens when a third is needed? Is the hourly rate for extra changes stated plainly? A quote that is silent on these points is not necessarily cheaper, only less finished.

The same questions apply when you quote for others. A fixed fee with a defined number of rounds is easier for a small production team to approve than an open estimate. It also encourages clients to collect their thoughts, which tends to improve the feedback itself. Our paid editing and review services follow this pattern, and the details are set out on the prices page.