What Counts as a Real Mixing Revision vs New Scope?
A real mixing revision adjusts a decision the engineer already made — louder vocal, less reverb on the snare, more low end on the 808. New scope introduces a different creative direction or work that wasn't in the original brief — adding vocal tuning that wasn't booked, changing the vocal arrangement, swapping the beat version, or requesting a different overall style. Real revisions are covered under your service tier; new scope is billable as additional work. Understanding the difference keeps projects moving and prevents revision-round surprises.
Most buyer frustration with mixing services comes from this boundary being unclear. The engineer thinks the request is new scope; the buyer thinks it's a normal revision. Both sides feel taken advantage of. Clear categories up front fix this.
If you want a mixing service with a clear revision policy written into the agreement before you pay, the BCHILL MIX vocal-mixing service publishes its revision terms and what counts as in-scope.
See Mixing Service OptionsThe Core Definition
A mixing revision is an adjustment to a decision the engineer already made based on the original brief and stems you delivered. The brief was the starting point; the revision refines the result inside that same brief.
New scope is anything outside the original brief. New stems, new creative direction, new services (tuning, editing, bus processing) that weren't part of the original quote, or a fundamental change to what the song is supposed to sound like.
The test: "Given what I originally asked for and the stems I sent, could the engineer have reasonably made this choice the first time?" If yes, it's a revision. If no, it's new scope.
What Counts as a Real Revision (In Scope)
These are normal revision requests and should be covered under your service's included rounds:
- Vocal level adjustments: "vocal is too loud/quiet in the chorus"
- EQ balance: "the mix feels muddy in the low mids" or "the high end is too harsh"
- Reverb and delay amount: "less reverb on the lead vocal" or "longer delay throw on the ad-libs"
- Panning: "widen the hi-hats" or "narrow the doubles"
- Compression feel: "vocals feel over-compressed" or "more punch on the snare"
- Automation: "push the vocal up during the bridge" or "dip the beat during the hook's opening"
- Effects swaps within the same family: "try a plate reverb instead of hall on the vocal"
- De-essing or harshness fixes: "the S sounds are too sharp"
- Low end weight: "the 808 needs more sub"
- Bus processing adjustments: "less glue compression on the mix bus"
These are all decisions the engineer made during the mix. Revising them is the whole point of revision rounds.
What Counts as New Scope (Billable)
These requests extend the work beyond the original brief:
- Adding services not originally booked: "now please tune the vocals" when tuning wasn't in the quote
- New stems: "here's an extra harmony track I forgot to send"
- Replacement stems: "I redid the vocal — use this take instead"
- Arrangement changes: "can you remove the bridge entirely" or "shorten the intro by 8 bars"
- Different creative direction: "I now want the mix to sound like a totally different genre"
- Beat version change: "I got a new version of the beat — redo with this"
- Adding a new instrument or element: "please add a pad I recorded"
- Radio edit or clean version: "also give me a clean version with the curse words muted"
- Stem delivery beyond what was quoted: "can you bounce out 20 individual processed stems"
- Format or sample-rate conversions: "convert the whole project from Logic to Pro Tools"
Any of these reset the work. The engineer now has new inputs or new goals and the mix effectively restarts. Most services charge for this because it's genuinely new work. The guide on preparing vocals before hiring a mixing engineer shows how clean prep prevents many of these scope surprises before they happen.
The Gray Zone
Some requests sit between categories. Engineers handle them differently and this is where miscommunication happens:
| Request | Revision or new scope? | Why |
|---|---|---|
| "The vocal effect doesn't match my reference" | Depends | If the reference was sent before the mix, it's a revision. If it's a new reference, it's new scope. |
| "Mute this section entirely" | Revision | Mix-level automation change, normal revision work. |
| "Replace the lead vocal with this new take" | New scope | New source stem resets the work. |
| "Add a different reverb type" | Revision | Effect swap within an existing decision. |
| "Now also process the drums as a parallel bus" | Depends | If parallel drums are standard, revision. If it's a new creative add, new scope. |
| "I want it louder" | Revision | Level adjustment, standard revision. |
| "Master this for me too" | New scope | Mastering is a separate service. |
When a request falls in the gray zone, the engineer should say so explicitly — "that's outside the original scope, would you like to add it as a paid extension?" — rather than silently decline or silently do the work and charge later.
How to Give Feedback That Doesn't Waste Rounds
The biggest cause of wasted revision rounds isn't scope confusion — it's vague feedback that the engineer can't act on. Useful feedback structure:
- Timestamp: "at 1:15, the vocal feels harsh"
- Specific element: "the lead vocal" not "the vocals"
- Desired change: "less harsh on the S sounds, less sibilance around 6 kHz feel"
- Reference anchor: "closer to how the vocal sits in [reference track] at 0:45"
Bad feedback: "it doesn't feel right" or "make the vocals better."
Good feedback: "At 0:52, the lead vocal feels too bright and the S on 'something' is aggressive. Can you de-ess around 6-8 kHz and pull the high shelf back a bit?"
Specific feedback uses one revision round for three fixes. Vague feedback can burn three revision rounds trying to guess what you meant. The guide on preparing vocals before a mix has similar structure advice for prep notes.
What a Typical Revision Policy Looks Like
Most professional mixing services specify:
- Included revisions: usually 2-3 rounds (budget tier often 1, top-tier often "unlimited" with a soft cap)
- Revision turnaround: typically 2-4 business days per round
- Time window: revisions must be requested within 14-30 days of delivery
- What counts as a round: all feedback submitted in one message = one round; drip-feed feedback across 3 messages = 3 rounds
- Scope definition: what's in-scope vs. what triggers an additional fee
Read the policy before booking. The difference between "2 revisions" and "2 revisions with 14-day window and clear scope definition" is the difference between a smooth project and a frustrating one.
Avoiding Revision Fatigue on Both Sides
Tips that keep revisions productive:
- Consolidate feedback into one message per round. Listen to the full mix, take notes, compile one document. Don't send 10 separate emails.
- Listen on multiple systems before requesting changes. Headphones, car, phone speaker, monitors. What sounds off on one system may be fine on another.
- Wait 24 hours before requesting revisions. Ear fatigue after a first listen skews judgment. Sleep on it.
- Don't chase perfection past round 3. After 3 rounds of revisions, the mix is usually 98% there. Further tweaks often make it worse, not better.
- Accept that some changes are creative preference. If the engineer disagrees with a request artistically, listen to their reasoning. They're hearing it with fresh ears.
When to Pay for New Scope Instead of Arguing
If your song's direction genuinely changed — you decided on a different vibe, you got new stems, the creative brief shifted — pay for the new scope instead of trying to force it into revisions. Trying to jam new-scope work into revision rounds creates:
- A mix that's patched rather than redone
- Engineer resentment that shows up in the final product
- Worse final results than if you just paid for the scope change
A $100 scope-change fee on a $200 mix is often cheaper than the alternative: a final mix you don't love because it was a compromise between two briefs.
How to Write a Revision Email That Stays In Scope
A strong revision email should sound boring. It should not be a new creative manifesto. It should list the changes, group them by section, and avoid sending new stems unless the engineer asks for them. Start with a quick thanks, then give the exact notes. Example: "At 0:48, pull the lead vocal down about half a dB. At 1:12, the delay throw on 'gone' is too loud. Across the whole song, can the 808 feel a little tighter without losing sub?" That is a revision email.
A weak revision email sounds like the buyer changed the song after hearing the first mix: "I think I want it more like Travis Scott now, can you make it darker and add more effects, also I re-recorded the second verse and got a different beat bounce." That might be a valid creative decision, but it is not the same mix job anymore. The engineer has to decide whether to quote a new scope or compromise the original mix.
Keep the revision email tied to the file already delivered. If you need to reference another song, explain which quality you mean: vocal level, dry/wet balance, low-end punch, width, or brightness. A reference without a specific reason usually creates more confusion than clarity.
Revision Timing Matters
Good revision notes usually come after three listening passes. First, listen once without writing anything. Second, listen on a different system and write down problems. Third, compare the mix to your original rough mix and one reference. Then send notes. This avoids the common first-listen overreaction where every difference from the rough mix feels wrong because the ear has not adjusted yet.
Do not wait three weeks unless the policy gives you that much time. Revisions work best when the engineer still remembers the song and the session is still active. If the project has been archived, recalled, and reopened, even a small change takes longer. That is why many services put a 14-30 day window on included revisions.
Also avoid listening with ten people before sending notes. Feedback from too many friends turns one mix into ten competing tastes. Choose one or two trusted ears, then decide. The artist has to own the final direction.
Where Buyers Usually Get Confused
Many buyers assume "revision" means "anything I want changed after delivery." That is not how professional services use the word. A revision refines the purchased service. It does not transform the purchased service into another service. Mixing does not become mastering. Vocal level changes do not become vocal production. De-essing does not become line editing. Arrangement suggestions do not become beat editing.
| Buyer request | Better way to classify it | What to expect |
|---|---|---|
| "Can you make the vocal less harsh?" | Mix revision | Included if rounds remain |
| "Can you tune all the vocals now?" | Added service | Likely paid add-on |
| "Can you use this new beat bounce?" | Replacement source | Likely new scope |
| "Can you send a clean version too?" | Extra deliverable | May be paid if not included |
| "Can the hook feel wider?" | Mix revision | Usually included |
Understanding this before ordering makes the buying experience smoother. You can ask the service what is included, what costs extra, and how to send notes. That conversation is much easier before money changes hands than after a deadline is close.
What a Clear Service Page Should Tell You
A service page should make the revision boundary easy to understand. It should say how many rounds are included, what counts as a revision, what counts as new scope, how long you have to request changes, and how revisions should be submitted. If that information is missing, ask before ordering. A good engineer will answer directly because clear expectations protect both sides.
For artists comparing online options, this boundary can matter as much as price. A cheaper service with unclear revision rules can become more expensive if every change becomes a debate. A slightly more expensive service with clear rules may save time and frustration. The goal is not unlimited changes. The goal is a predictable path from first mix to approved final.
How Scope Changes Affect Turnaround
Scope changes do not only affect price. They affect timing. If you send a new lead vocal after the engineer has already balanced the mix, that can reset tuning, compression, de-essing, automation, reverb sends, delay throws, and final bus balance. Even if the new vocal is better, the engineer is not making one small swap. They are rebuilding the decisions that depended on the old vocal.
This is why a "quick replacement" can add days. The engineer may have other projects scheduled after your revision window. A normal revision can often fit into a shorter slot because the session is already shaped. New scope may need a full working block. If the release date is close, this can create pressure that harms the final mix.
The best way to protect turnaround is to freeze the arrangement before ordering. Final beat, final vocals, final comp, final tuning reference, final notes. If something is not final, say so before the quote. The engineer may recommend waiting, booking editing first, or leaving room in the schedule for a paid update.
Examples by Real Artist Situation
Situation one: the artist sends a rap song with dry lead, doubles, ad-libs, and a rough mix. The first mix comes back and the vocal is too bright in the hook. Asking for less brightness is a revision. The engineer already had the correct files and direction; the note refines the mix.
Situation two: the artist sends the same song, then after the first mix decides to re-record the hook with a different melody. That is new scope. The new hook changes the arrangement, vocal balance, tuning, effects, and maybe the emotional direction of the song. It may be the right creative move, but it is not the original job.
Situation three: the artist asks for a clean version after approving the explicit mix. That depends on the original quote. If clean edits were included, it is a deliverable. If not, it is a new version. This is why artists should mention clean, instrumental, TV, acapella, or stem deliverables before ordering.
How to Protect Yourself as the Buyer
Before paying, save a copy of the service terms or order page. Confirm the included revision count. Ask whether tuning, editing, mastering, clean versions, and processed stems are included. Ask how long you have to request revisions. Ask whether new stems after the first mix are billed separately. These questions are normal. A serious service will not be offended by them.
After delivery, keep your notes factual. If a change is in scope, explain it clearly and send it in the next revision round. If you realize the direction changed, be honest and ask what the added cost would be. That conversation is better than trying to frame a new song direction as a small tweak.
Good revision boundaries protect the buyer too. They keep the engineer from rushing unlimited changes, they keep expectations clear, and they help the final mix move toward approval instead of drifting through endless small edits.
Mastering can create a similar scope issue. If the original order was only a mix, asking for a finished master, clean version, or alternate streaming delivery is usually a new deliverable. If you already know the song needs that final release stage, check the mastering service options before booking so the delivery list is clear from the beginning.
The cleanest project is one where both sides can point to the same brief, the same stems, the same reference notes, and the same revision policy. Then revision rounds become normal finishing steps instead of negotiations. That is what a professional mixing process should feel like.
When in doubt, separate creative changes from technical corrections before you send feedback. Technical corrections usually refine the existing mix. Creative changes usually ask the engineer to reinterpret the song. That simple distinction makes the conversation easier and helps you avoid paying for avoidable extra work.
FAQ
What if the engineer calls something new scope but I think it's a revision?
Ask them to walk you through the reasoning. A good engineer will explain specifically why the request crosses the scope line (new stems, new creative direction, service not originally booked). If their reasoning makes sense, accept it and pay the addition. If the reasoning is vague or changes mid-conversation, push back — it may be a communication issue rather than a genuine scope issue.
Can I send revision notes piecemeal over several days?
Technically yes, but most services treat each batch of notes as a separate revision round. If your service includes 2 rounds and you send 2 separate emails, you've used both rounds. Consolidate feedback into one message per listening session to maximize your included rounds.
What happens if I want more revisions than my tier includes?
Most engineers sell additional revision rounds at a flat rate ($30-$75 per round for mid-tier services). Some services cap revisions entirely and won't sell more. Ask before booking if you anticipate a complex revision cycle — some engineers offer "extended" packages with more rounds built in.
Is it new scope if I ask to try a completely different mix approach?
Usually yes. A fundamentally different approach (different style, different creative direction, different reference) resets the work rather than refining it. Most services charge for alternate mix versions at 50-75% of the original mix price. Some top-tier engineers will do one alternate pass as a courtesy if the brief was genuinely unclear, but this is negotiation rather than standard policy.
How do I document scope clearly at the booking stage?
Get the deliverable list in writing before paying: number of stems, services included (mix, tuning, editing, mastering), number of revision rounds, revision window, what counts as a revision, and what triggers an additional fee. A one-page written agreement prevents 90% of scope disputes. If the engineer resists written terms, that's a red flag — book elsewhere.
Is changing the reference track a revision?
It depends how much the reference changes the direction. A clearer reference for the same sound can fit inside a revision. A completely different reference after the first mix usually becomes new scope because the engineer is being asked to rebuild the taste target.





