A Mastering Job Turns Into Mixing: Stop Scope Creep Early

How a mastering job drifts into mixing

Mastering client scope creep rarely starts with a big request. A client books mastering, then sends a folder of stems "just in case," asks if you can lift the vocal a little, or wants a snare tamed that only a mix can really fix. Each request seems small. Together they turn a fixed-price finishing job into open-ended mixing at a mastering rate.

One Reddit anecdote, a single community post and not evidence of how common this is, shows the pattern. A mastering engineer described a client who kept sending multitrack material and asking for mix changes [R1]. The engineer also described several conversations about boundaries that did not stop it [R1]. Talking about the problem was not enough. The fix has to be built into intake, files and written records.

• Stems sent for a stereo mastering booking
• Requests to rebalance individual instruments
• Repeated new versions sent after the work starts

State the service, inputs, outputs and exclusions plainly

Your quote or service description should let a busy artist answer one question: what do I send, and what do I get back? Write the mixing vs mastering deliverables in everyday language. Mastering takes a finished stereo mix and prepares it for release. Mixing balances and processes the separate tracks to create that stereo mix. If you offer stem mastering as a paid option, name it as its own service with its own price. That way it never becomes an unspoken extra.

Exclusions matter as much as inclusions. Say clearly that instrument rebalancing, vocal tuning, editing and rebuilding a mix from multitracks are not part of stereo mastering. Also say how many revisions are included and what counts as a revision. Changing overall loudness or tone fits mastering. Asking for a louder guitar does not. Have whoever drafts your terms check that wording against how you actually work.

• Inputs: one stereo mix file per song, at the format you name
• Outputs: the masters and formats you list, by the date you set
• Exclusions: mixing, editing, tuning and multitrack work
• Revisions: how many, what scope, and how quickly they are turned around

Use a submission check before scheduling

Don't put a project on your calendar until the files pass a quick intake check. Open the delivery and count the files. Confirm each song is a single stereo file. Listen to the start, the end and one dense section, then compare the song titles with the order. This takes minutes, and it catches problems before they eat into a booked day.

If the check fails, the session does not start, and you tell the client why in one short message. That keeps the mismatch in front of them at the point where fixing it costs the least. It also protects your other clients. A day spent sorting someone else's stems is a day the next booked project doesn't get.

Hypothetical worked example: stereo master vs multitrack edit

This is a made-up scenario, not a real case. An artist pays for mastering on four songs. The quote names stereo mix files as the input. The upload holds three stereo files and, for the fourth song, thirty-one separate tracks with a note asking you to "fix the chorus balance and bring up the vocal."

The intake check flags song four. Mastering it means taking one balanced stereo file and finishing it. Doing what the note asks means loading thirty-one tracks, building a mix, getting the client to approve the balance, and only then mastering. That is a different service with its own time cost. The engineer confirms songs one to three for the booked date. For song four, they send the options in the next section and do not touch the stems until the client picks one.

Offer correction, a separate mixing quote or a revised schedule

When a client sends stems for mastering, give them choices instead of a flat no. First, the client can have the mix finished elsewhere and send back a stereo file, with the original price and slot kept if it arrives by a stated date. Second, you can quote mixing as a separate job with its own price, revisions and timeline. Third, if they need more time to decide, the song moves to a later open slot.

Each option has tradeoffs. Returning files for correction keeps your scope clean, but a client without a mixer may stall. Quoting mixing brings in more revenue. Only offer it if you actually want to mix this material, because mixing a project that began as mastering can blur who approves what. Rescheduling protects your calendar but delays their release, so state any rebooking conditions from your actual terms and don't improvise new ones.

Keep written decisions and avoid silently doing unpriced work

After a call, send a short written recap: what was agreed, which option was chosen, the price, and the date. That turns a friendly chat into a record you can point to later. The anecdote above notes that several boundary talks did not change the client's behavior [R1]. A written recap gives everyone something concrete to come back to.

The quietest form of audio job out of scope is the fix you make without mentioning it. Nudging a vocal or rebuilding a stem bounce teaches the client that mixing comes with mastering. It also leaves you without a record that you ever did extra work. If you choose to do a small courtesy fix, say so in writing, label it as a one-time exception, and restate the scope for the next delivery.

Red flags and how to verify what you received

Some mismatches are honest confusion. Others are attempts to get mixing at a mastering price. Watch for files labeled final master that turn out to be stems, "basically finished" mixes with obvious balance problems the client wants solved, and new versions that keep arriving after approval. Check the files yourself. Count the tracks, confirm each file is stereo, and listen, rather than trusting labels or descriptions.

If a client says another engineer always included mixing in mastering, don't argue about how other people work. Point back to your written quote and the services listed there. Keep copies of what was uploaded and when, so any later dispute rests on the real files and messages rather than memory.

• Folder or file names that don't match the contents
• Track counts far above one file per song
• Repeated reopening of songs already approved
• Pressure to start immediately and "sort it out later"

Orderly termination and handoff when mismatches persist

Sometimes the options are offered, recaps are sent, and the stems keep coming. Ending the project can be the professional choice. In the Reddit anecdote, the engineer ended the relationship and refunded the song that had not been finished [R1]. That was one person's decision. It doesn't show that refunds are required, or how much is owed, in your situation.

An orderly ending means a calm written notice that lists the completed work, the unfinished work, and how any money will be handled under your actual terms. It also means returning the client's files and handing over finished masters for completed songs, so they can move on with someone else. Before you promise any refund amount or claim a right to end the work, read your own agreement. If it is unclear, check with a qualified advisor familiar with your jurisdiction.

When escalation makes sense

Most scope problems end with a corrected file or a new quote. Escalate only when money, rights or threats are involved. Examples include a disputed payment you cannot resolve directly, a demand for files you believe you aren't obliged to release, or a client threatening public attacks or a claim. At that point, a business advisor, an attorney, or your payment processor's dispute process may be appropriate. Rules vary by location and platform.

Until then, keep replies short, factual and written. Don't add new conditions in the heat of a dispute, and don't threaten consequences your terms don't support. A clean record of the quote, the intake result, the options you offered and the client's choices is your strongest position in almost any escalation.