How to Limit Client Revisions Without Losing the Client

By /

You limit client revisions with four moves: put a round cap in the proposal and contract, define a round as one consolidated list of notes, set a short window to respond, and bill anything past the cap as extra work. Do those four things before the first mix goes out, and “just one more tweak” stops running your schedule.

This guide is written for mixing engineers, mastering engineers, podcast producers, post-production editors and studio owners. The principles work for any creative service, but the examples are audio.

Audome
Keep Revisions in One Place
Audome lets audio professionals set revision limits, collect timestamped feedback, and manage client collaboration in one secure workspace.

Visit Audome

TL;DR

  • Include two to three revision rounds in the base fee. Two is the most common choice among independent engineers, and three is a generous one.
  • Define a round as one consolidated, written list of changes from one approver, not a stream of texts and emails.
  • Put the policy in the proposal, repeat it as a numbered contract clause, and say it out loud on the kickoff call.
  • Send a clear checkpoint message when the last included round is delivered, then bill further rounds as out-of-scope work.
  • Software can enforce the policy for you: revision counters, one place for feedback and payment before final downloads.

Table of Contents

Why revisions get out of hand

Most endless revision cycles are not caused by difficult people. They come from a missing structure.

The usual pattern: you deliver a mix, the artist replies with a text about the vocal, the manager emails about the snare, a bandmate sends a voice memo two days later, and the artist then changes their mind about their own first note. Nobody has done anything wrong. But you are now working from four channels and no definition of “done.”

One agency handbook on client feedback puts the most common cause of long revision cycles as rolling, non-consolidated feedback. Good providers treat feedback as a workflow that is consolidated, time-bound and tied to an approval, not as an ongoing conversation. That is the whole idea behind limiting revisions. You are not restricting the client’s say. You are giving their input a shape.

It also helps to be honest about what you are protecting. Every extra round costs real hours: re-opening the session, recalling plugins, bouncing, uploading, reading notes. On a flat per-song or per-episode fee, unpaid rounds come straight out of your hourly rate.

Why revisions get out of hand — overview diagram

Decide how many rounds to include

Before you can limit anything, you need a number.

For audio, the range is narrow. Independent mixing and podcast engineers typically include two to three revision rounds in the base project fee, with two the most common and three considered generous. Additional rounds are billed as separate line items or at an hourly rate. If you want a number for your exact job type, we break it down in separate guides for mixing engineers, podcast editors, producers and vocal editors.

A quick way to choose:

Situation Suggested included rounds
Single song, experienced artist who knows what they want 2
Album or EP with a first-time client 3
Weekly podcast with a fixed template 2, with a short window
Dialogue or post-production with several stakeholders 2, with one named approver
Mastering 1 to 2, since changes are usually small

These are starting points, not rules. Pick the number you can honestly deliver at your price, then stick to it. Changing the cap mid-project is how you lose credibility with the client who is paying you.

Define what a revision actually is

A cap is meaningless if “revision” is vague. The cleanest definition in standard contract language is that a revision round is one consolidated list of changes provided in writing. Anything outside that structure, such as separate emails or scattered texts, or anything past the agreed cap, is treated as out-of-scope work, billed hourly or at a pre-agreed flat fee.

In audio terms:

  • One round: a single batch of notes on a single version, covering as many points as the client wants.
  • Not a new round: fixing something you got wrong, such as a clipped export, a missed note from the previous list or the wrong file format. Mistakes are on you and should never count against the client.
  • Not a revision at all: a change of brief. Re-recording a part, restructuring the arrangement, swapping the vocalist or changing the episode format is new work and should be quoted as such.

The line between a revision and a scope change is where most arguments start, so write examples into your terms. Our guide on what counts as a revision across writing, design and audio goes through the borderline cases.

Put the policy where the client will see it

Many creative providers fail because they bury the policy. A revision clause in an appendix is a clause nobody read.

The approach that holds up is repetition across three moments:

  1. The proposal or quote. State the number of included rounds next to the price.
  2. The contract. Make it a numbered clause with the definition of a round, the response window and the rate for extra rounds.
  3. The kickoff call. Say it in one sentence: “Your fee includes two rounds of notes. Send each as one list, and we’ll go from there.”

This repetition is what our own writing on when to charge for revisions recommends, because a client who has heard the rule three times is rarely surprised when they hit it.

A sample clause you can adapt

This project includes two (2) revision rounds. A revision round is one consolidated, written list of changes sent by the client’s designated approver within five (5) business days of delivery. Feedback received outside this format, or after the two included rounds, is billed as additional work at the agreed rate. If no feedback is received within the window, the project is considered approved.

The five-business-day window is not arbitrary. Many professional contracts use a revision window of three to five business days after delivery, after which the work is deemed approved if there is no feedback. Have a lawyer review any clause before you rely on it, especially the deemed-approval part, since enforceability depends on your state and your contract as a whole.

Name one approver

Design by committee is expensive. When a band, a label rep and a manager each send notes, you end up resolving their disagreements with your time.

At kickoff, ask the client to name a single approver. Agency guidance recommends that each client designate one approver per deliverable before the project starts, which pushes the job of reconciling internal opinions back to the people who can actually settle them. It saves hours of rework and keeps conflicting notes from eroding your margin.

A simple line in your onboarding email does it: “Who has the final say on this mix? All notes should come from them, as one list.”

Triage feedback before you touch the session

Not every note has to be done. Treat each round as a short triage exercise, sorting notes into four buckets, a method common in creative feedback workflows:

  • Implement: clear, in scope, and it improves the work.
  • Push back: it conflicts with the brief or with technical quality. Explain why in a sentence and offer an alternative.
  • Defer: a good idea for later, such as an alternate mix or the next episode.
  • Escalate: it is a scope change and needs a quote.

This keeps scope creep from arriving disguised as taste. “Can the whole thing feel more open?” might be a mix note, or it might mean re-tracking. Triage is where you find out.

Make feedback specific, and make it arrive once

Two habits shorten revision cycles more than any contract language.

First, ask for notes tied to a position in the audio. “The vocal is too quiet” is a long conversation. “At 1:42 the vocal gets buried under the guitars” is a five-minute fix. We cover why this matters in why detailed revisions matter for audio projects.

Second, ask for all notes at once. A single batch lets you see conflicts, order your edits and work through them in one pass. If you are tired of juggling separate comments, one edit pass to resolve client comments shows how to sort a pile of notes into a single session.

Timestamped client notes consolidated into one edit pass

The broader point about feedback loops is that they work when they are consolidated and time-bound. There is a useful overview of how structured feedback loops keep content cycles moving, and the same logic applies when the content is a mix.

Use a billing checkpoint when the cap is reached

The hardest moment is not writing the clause. It is sending the message when a client asks for round three and the contract says two.

A checkpoint message makes this routine instead of confrontational. Once the final included round is delivered, state it plainly: you have now used all included revision rounds. Say it before you do more work. Doing so protects your margin and prompts the client to be decisive with the notes they have left, as we explain in our guide to charging for revisions.

Here is a template:

Hi Sam, round 2 is attached, which completes the two revision rounds included in your project. If you’d like further changes, I can take them on as an additional round at $X. Send everything in one list and I’ll turn it around within Y days. If you’re happy with this version, just approve it and I’ll prepare the final files.

Three things make this work:

  • A price, not a lecture. Give the extra round a fixed fee or hourly rate so the client can decide quickly.
  • A route to approval. Offer the easy way out. Many clients are closer to done than they realize.
  • A tone that keeps the relationship. You are describing a process, not scolding.

Some studios also keep one free “polish” allowance for tiny changes like a fade length or a level nudge. That is your call. If you do it, write it into the policy so it doesn’t become precedent by accident.

Handling the client who ignores the limit

Even with all of this in place, someone will push. A few responses that preserve the relationship:

  • They send notes by text after the round is closed. Reply once: “Thanks. Can you add these to the next consolidated list? That keeps nothing from getting lost.”
  • They say it is a tiny change. Tiny changes still require reopening, recalling and re-exporting. Offer a flat fee for small fixes so there is no haggling.
  • They go quiet and then return weeks later. Point to the response window. A project that was deemed approved can be reopened as a new, quoted job.
  • They are unhappy with the direction, not the details. Pause and escalate. This is a brief problem, and a call usually solves it faster than another round.

How you respond matters as much as the policy. Advice for avoiding friction comes down to the same things: do not tell clients they are wrong, ask what they are hearing, and do not be afraid to give a little where it costs you little. Flexibility on your terms keeps the limit credible.

What the client sees on a marketplace

If you also sell on a freelance marketplace, expect the vocabulary to differ. On Fiverr, a revision lets the buyer reject a delivery and ask for specific changes. The same help page says orders complete automatically three days after delivery if the buyer takes no action, and that revisions must be requested inside that window.

“Unlimited revisions” on such platforms means the seller commits to revising until the buyer is satisfied. That is very different from a fixed-round professional contract, and it is rarely a good deal for the person doing the work. If you sell direct to artists and podcasters, a fixed cap is both more sustainable and easier to explain.

Our perspective: make the limit part of the tool, not a talking point

We built Audome because we kept seeing the same failure: engineers had a policy on paper, but their workflow made it impossible to enforce. Notes arrived by text, by email and in voice memos. Files lived in three places. A client could always claim they never saw the cap, because it lived in a PDF none of them opened.

Our view is that a revision limit only works when the process itself carries it. That means feedback collected in one place, pinned to a moment on the waveform, with every version tracked so everyone can see which round they are on. It means the client does not need an account or a password to leave notes, because friction on their side produces more email, not less. And it means the money conversation happens automatically, not as an awkward message at 11 p.m.

We also think most engineers undercharge for revisions because they dislike the conversation. When the system says “you’ve used your included rounds” and offers a payment link, it stops being personal. The studio sets the rule once. The client sees a neutral boundary, and they tend to send clearer notes because every round now has weight.

The goal is not to squeeze clients. It is to have a project end because everyone agreed it was finished, not because you gave up.

— Kreg

Enforce the limit with Audome

If you want the policy handled for you, Audome lets studios cap the number of free revisions on a project, automatically charge for extra revisions and keep final downloads locked until payment goes through, using Stripe Connect. Clients leave timestamped feedback directly on the waveform without creating an account, and version history shows exactly which round you are on. Files go up to 96kHz/24-bit with unlimited uploads, projects and collaborators.

Plans are published on the Audome pricing page: Studio is $12.50 per month or $150 per year, and Pro is $48 per month or $576 per year. You can see the full product overview on our homepage too. If you also want the approval side for podcasts, our podcast approval workflow guide pairs well with it.

A short checklist to start your next project

  1. Choose your included rounds (two or three) and your rate for extra rounds.
  2. Write a definition of a round and a response window into the contract.
  3. Mention the policy in the quote and again on the kickoff call.
  4. Ask the client to name one approver.
  5. Collect notes in one place, tied to timestamps.
  6. Send a checkpoint message when the final included round is delivered.
  7. Quote anything outside the brief as new work.

If you want a fuller process view, client revision management for producers and how audio engineers handle revisions like pros pick up where this guide ends.

FAQ

How many revisions should I include in my price?

For audio, two or three rounds is the norm, and two is the most common choice among independent engineers. Choose the number your fee can support, and bill extra rounds separately. Whatever you pick, put it in writing before work starts.

What does “unlimited revisions” mean?

It means the seller agrees to keep revising until the buyer is satisfied. On Fiverr, for example, this is separate from a fixed number of revisions that a freelancer offers per service. For most audio professionals, it is a risky promise because there is no natural end point.

What does “last revision” mean?

It is the final round of changes before the work is approved or the order completes. On Fiverr it is the final iteration before an order is completed or auto-completed. In your own contracts, define it by naming the round: “Round 2 is the last included revision.”

Can I charge for revisions if my contract does not mention them?

It is much harder. Without a written cap and rate, a client can reasonably argue that changes are part of the original job. For anything involving a dispute or a large amount of money, talk to a lawyer in your state, and add a revision clause to every contract going forward.

How do I say no to extra revisions without losing the client?

Point to the process, not the person. Remind them that all included rounds are used, offer a clear price for another one, and give them an easy path to approve the current version. Most clients accept a fair boundary when it is presented calmly and early.

Sources

Scroll to Top