How many revisions should you offer clients?

Every engineer has lived the version of this where a job you quoted as finished keeps coming back. The mix was approved, then the artist played it for a friend in a car, and now the snare is "a bit much" and the vocal wants to come up "just slightly," and none of it is written down anywhere. Revisions are the part of client work most likely to eat your margin, and they do it one small favor at a time.

The useful thing to notice is that revisions are a policy problem before they are a talent problem. You can bound them without being difficult about it, and the tools that keep them bounded are the same ones that make your feedback loop faster.

How many rounds is standard

For a mix, two or three rounds of revisions included in the fee is the common freelance norm. For a master, one or two is more typical, because a master is a smaller set of decisions made on a finished mix. Neither number is a law. The point is that you named it before any work started, so the client agreed to a shape, not an open-ended promise.

Put it in the quote in one plain sentence: "This price includes two rounds of revisions." That single line does most of the work, because it reframes the third round from a favor you are refusing into a service you offer at a price. Nobody is offended by a price.

What actually counts as a revision

This is where most of the money leaks, and it has nothing to do with the number of rounds. A revision is a change to the thing you agreed to make. A new request is a change to the agreement itself. "The vocal is too loud in the second chorus" is a revision. "Actually, can we try it as a half-time feel" is a new song.

Most revision disputes are scope disputes wearing a revision costume. When you write the distinction into your terms, you give yourself a calm, non-personal way to say "happy to do that, that one is a new request" instead of quietly absorbing the work and resenting it. If the wider question of client sign-off is what trips you up, there is a full guide on how to get client approval on a version.

Make each round count

Half of all revisions are re-revisions caused by feedback that was too vague to act on. "The mix feels a bit off in the middle" gets you a change the client did not actually want, and now you have burned a round on a guess. The fix is to collect all of a round's notes in one pass, each one pinned to an exact point in the audio.

When a client leaves a comment on the waveform, "the vocal at 1:12" replaces "somewhere in the second verse," and your revision list becomes a set of timecodes instead of a paragraph to decode. A range comment can mark a whole section, like a chorus where the guitars need to come down. One clear list, acted on once, is worth three rounds of guessing. The mechanics of collecting feedback this way are covered in how to send a mix to a client for feedback.

Compare versions honestly, or you will revise toward volume

There is a specific trap that manufactures extra rounds: when a client compares two versions at different levels, the louder one sounds "better," so they ask you to chase whatever made v2 louder. You end up revising toward volume instead of toward the mix, and the next round undoes it.

Let the client compare versions at matched loudness, so they react to the change you actually made. If they cannot hear a difference once the levels are matched, that is worth knowing before you spend a round on it. The why of this is its own guide: why louder sounds better, and how to A/B fairly.

Carry notes across versions so nothing reopens by accident

A revision round should close cleanly. Upload each new version against the same track, so open comments carry forward onto it and resolved ones stay behind as a record. The client then confirms the fix on the exact note they raised, and a comment nobody reopened does not quietly come back in round three. This is the difference between a job that converges and one that keeps re-litigating settled decisions.

End the loop with a recorded sign-off

A stated round limit sets the boundary. A recorded approval is what actually closes the door. When the client signs off on a specific version, capture it: which version, who approved it, and when. That record turns "can we go back to the earlier one" into a clear answer, and it marks the exact moment the included work ended.

A request that arrives after sign-off is not a fourth revision. It is the first round of a new, billable piece of work, and the approval is what lets you say so plainly.

Charging for the rounds past the line

Name a per-round rate in your agreement from the start, so the extra round has a known price before anyone asks for it. When a job does run long, the cleanest way to stay paid is to tie the money to the delivery: the client approves the extra work, pays for it, and the final files unlock on payment. That keeps you out of the awkward chase and keeps the money conversation attached to the work instead of drifting into unanswered email. The whole subject of getting paid without friction is here: how to get paid for mixing and mastering.

Mixing and mastering are not the same shape

Set the two stages separately. A mix has many independent moving parts, so two or three rounds accounts for the back and forth of balance, tone, and arrangement notes. A master is a tighter decision on a finished mix, so one or two rounds usually covers it. When a mastering revision comes in, check what caused it: if the client changed the mix, the master is being redone against a different source, and that is a new job rather than a free recall. Naming that distinction up front saves the most uncomfortable version of this conversation.

Sample terms you can adapt

You do not need a lawyer to make this stick, just a few plain lines in your quote or booking email:

• Rounds: "This project includes two rounds of revisions on the mix."
• What a round is: "A round covers changes to the agreed mix. New sections, arrangement changes, or a change of reference are quoted separately."
• Extra rounds: "Additional rounds are billed at $X each."
• Completion: "Approval of a version marks the project complete. Final files are delivered on payment."

Four sentences, agreed before you touch a fader, remove almost every argument you would otherwise have at the end.

The short version

Decide the number of rounds and write it down. Define what a revision is so scope changes do not sneak in as free tweaks. Make each round count with precise, timecoded feedback compared at matched loudness. Carry notes across versions so nothing reopens, end with a recorded approval, and bill the rounds past the line. The work goes out cleanly, and you finish with a sign-off you can point to.

Frequently asked questions

How many revisions should I offer clients?

Two or three rounds is the common freelance norm for a mix, included in the base fee, with anything beyond that billed. The exact number matters less than writing it down before you start. A stated limit turns 'one more small change' into a clear conversation about scope instead of an argument, and it protects the rounds you did include from becoming an open tab.

What counts as a revision versus a new request?

A revision is a change to the work you agreed on: a vocal that sits too loud, a harsh 's', low end that needs tightening. A new request is a change to the brief itself: a different arrangement, an added section, a switch from the reference you were given. Write the distinction into your terms, because most revision disputes are really scope disputes in a revision costume.

How do I charge for extra revisions?

Name a per-round rate up front in your agreement, so the client knows the cost before they ask. When a job runs past the included rounds, the cleanest way to stay paid is to gate the final files behind payment: the client approves, pays for the extra round, and the delivery unlocks. That keeps the money conversation tied to the work instead of buried in email.

How do I stop endless revisions?

Three things end the loop: a stated round limit, precise feedback collected in one pass, and a recorded approval. Vague notes cause re-revisions, so pin feedback to exact spots and gather it all before you start a round. When the client signs off on a specific version, that version is the agreed one, and a request after sign-off is plainly a new round rather than a free one.

Should mixing and mastering have different revision limits?

Yes, usually. A mix has many moving parts, so two or three rounds is normal. A master is a smaller set of decisions on a finished mix, so one or two rounds is typical, and a recall often means the mix itself changed. Set each stage's limit separately, and if a mastering revision was caused by a new mix, treat it as a new job rather than a free recall.