The client picked option B. They loved it. They just had "a couple of small notes" — could the ending be a bit less abrupt, and could it feel warmer, and would it be possible to hear a version that's slightly more like the one their CMO mentioned in passing?
Six weeks later there have been four rounds. The sound is now a compromise between three people's memories of three different meetings. Nobody is unhappy enough to stop, and nobody is happy enough to sign off. The producer is working for free and the brand has a sound logo that no longer does what the brief asked for.
Revision is where sonic branding engagements lose their margin and their point. Not because clients are difficult, but because a revision round is a distinct piece of work with its own method, and most producers treat it as an extension of making. It isn't. Making is generative. Revising is diagnostic.
What a Revision Round Actually Is
A revision round is a bounded exchange with three parts: the client gives feedback on one approved direction, the producer makes changes to that direction, and the client either signs off or names precisely what still blocks sign-off.
Three things fall outside that definition, and naming them early saves weeks.
Trying a different option is not a revision. If the client wants to revisit option A after choosing B, that is a new direction, and it costs what a new direction costs. Producers who absorb this quietly train clients to treat every decision as provisional.
Adding a deliverable is not a revision. "Could we also hear a short version for the app?" is a length variant, part of the delivery kit, not a fix to the approved motif. It may already be in scope. Either way it belongs on the deliverables list, not in the revision queue.
Aggregating new opinions is not a revision. When someone who was not in the presentation adds notes afterward, the round has effectively restarted with a different brief. That is a scoping conversation before it is a production one.
The number of rounds should already be written down. If it was priced and agreed when the engagement was defined, as we cover in scoping your first sonic branding client, then the boundary is a shared fact rather than an awkward negotiation mid-project.
Read the Feedback Before You Open the Session
The strongest instinct after receiving notes is to open the project file and start moving things. Resist it for thirty minutes.
Client feedback on sound arrives in feelings, not parameters. "Too cold," "a bit cheap," "not confident enough," "too much." None of those are instructions. All of them are symptoms, and each one has several plausible causes. Acting on the first cause that comes to mind is how a producer ends up making four changes to fix one problem.
The translation step is simple and worth doing in writing. Take each note and turn it into a hypothesis about a specific parameter:
"Too cold" points at timbre. Add harmonic content, reduce high-frequency emphasis.
"Feels cheap" points at timbre and mix. Source quality, reverb tail, transient clarity.
"Too abrupt" points at motion and duration. Release shape, final note length.
"Not confident" points at pitch and motion. Rising versus falling contour, interval width.
"Too much" points at duration and density. Fewer elements, shorter total length.
Then send the translation back before making anything. One short message: "Reading your notes, I think 'too cold' is about the tone colour rather than the melody, so I'll keep the motif and change the instrument character. Does that match what you heard?"
This costs five minutes and prevents the most expensive failure in revision work, which is fixing something the client never had a problem with.
Change One Parameter at a Time
A sound logo has a small number of variables that actually carry identity: pitch, timbre, motion, and duration. We break those down in the anatomy of a sound logo. Everything else is production detail.
Because the set is small, changes compound fast. Warming the timbre and shortening the tail and softening the attack in one pass produces a version that is different in a way nobody can describe, including the person who made it. If the client dislikes it, there is no way to know which change caused the problem.
Work in single moves. Warm the timbre. Render. Compare against the approved version. Only then decide whether the duration still needs attention. Two sequential single-variable passes are faster than one multi-variable pass followed by an archaeology session.
There is a second reason for the discipline. A revision that changes one thing is explainable in one sentence, and explainable changes get approved. A revision that changes five things arrives as a new sound, and new sounds restart the evaluation from zero.
Protect the Motif
The motif is the two or three intervals a listener would hum back. It is the part that becomes recognizable after the fortieth exposure, and it is the part most likely to get sanded off during revision, because it is also the part that feels most repetitive to the people hearing it twenty times in a week.
Client fatigue is real and it is not a signal. A team that has lived with a motif for three weeks will find it boring long before a single customer has heard it once. When feedback starts pointing at the melody itself after it was already approved, the question to ask is whether the brand's audience has a problem or whether the room does.
That is worth saying out loud, gently: "This is the part designed to stay the same across every touchpoint. It should start to feel familiar to you well before it feels familiar to anyone else — that's the mechanism working."
If the motif genuinely does not fit, that is not a revision. That is a return to the brief, which is a different conversation and a different invoice.
Present the Revision as a Comparison
The mistake that costs the most rounds is sending the revised file on its own.
Heard in isolation, a revised sound logo is just a sound logo. The client has no reference point, their memory of the previous version is approximate, and they will evaluate it fresh, which invites fresh notes on things that were settled two weeks ago.
Send the comparison instead. Three items, in this order:
The approved version, labelled as such
The revision, labelled with the single change made
One line naming what changed and why
The same framing discipline that closes a first presentation applies here, and for the same reason. As we argue in presenting sound logo options so the client actually decides, unframed audio gets judged as taste, framed audio gets judged as fit. A revision without an A/B is unframed audio with extra steps.
Then ask a closed question. Not "what do you think?" but "does this solve the warmth note?" A closed question produces a yes, a no, or a specific residual, all three of which move the project. An open question produces a new round.
When the Feedback Contradicts the Brief
Sometimes the notes ask for something the agreed brief rules out. A brand that documented itself as restrained and precise asks for something more playful. A sound scoped for a two-second app chime is asked to carry a five-second emotional arc.
The brief is the instrument for this, which is the whole reason it exists as a written artefact rather than a conversation. A sonic branding brief that both parties signed converts an argument about taste into a comparison of documents.
The move is to name the tension without resisting the change:
"This note points somewhere warmer than the brief we agreed, which described the brand as precise and restrained. Happy to go warmer — I just want to check whether the brief has shifted, because if it has, the rest of the system should shift with it."
Two outcomes, both good. Either the client realises the note was a personal preference and withdraws it, or the brief has genuinely changed and the whole engagement gets re-pointed at the right target before more work is built on the wrong one.
Silently absorbing brief-contradicting feedback is the most common route to a delivered asset nobody defends internally six months later.
Closing the Round
A round that ends without an explicit close has not ended. It has paused.
Close with three sentences, in writing:
What changed: "Warmer timbre on the second and third notes, tail extended by 200 ms."
What this concludes: "This uses the second of the two revision rounds in the scope."
What happens next: "If this is approved, I'll build the length variants and the documentation, and the full kit lands Thursday."
That last line matters more than it looks. It replaces an open review loop with a delivery date, and it sets up the starter kit documentation as a scheduled deliverable rather than something that appears unannounced in an inbox.
Ask for the word "approved." Not "looks good," not a thumbs-up on a message. A one-line written approval of a named file is what lets the producer archive the session and move to delivery without wondering whether it will reopen.
Mistakes That Turn One Round Into Four
Starting work before confirming the diagnosis. Fixing the wrong parameter costs a whole round and teaches the client that rounds are cheap.
Sending revisions without the original. Guarantees fresh notes on settled decisions.
Bundling changes. Makes success and failure equally unattributable.
Treating fatigue as feedback. The team is not the audience. Their boredom arrives months early.
Accepting notes from people who were not in the presentation without treating it as a scope event. New listeners bring the old brief back into question.
Leaving the round open. No named close means no named end, and no named end means the file stays live indefinitely.
FAQ
How many revision rounds should a sonic branding project include?
Two is standard for a single sound logo, one for a small fixed-scope engagement. What matters more than the number is that it is written in the agreement with a definition of what counts as a round, so the boundary is a shared reference rather than a judgement call made under pressure.
What if the client sends feedback in a voice note or a meeting instead of writing?
Take it, then write it back to them. "Here's what I captured, and here's how I plan to act on it." Spoken feedback is often better feedback, but it is unreliable as a record, and revision disputes are almost always disputes about what was said.
Should the previous version be deleted once a revision is approved?
No. Keep every rendered version with a version number and a one-line description of what changed. Clients reverse direction more often than they expect to, and the ability to say "that's version 2, I still have it" turns a potential round into a five-minute email.
The client approved, then came back a week later with more notes. What now?
Treat it as a new round and say so before starting. A written approval is what makes that sentence easy to deliver without friction. If the approval was never collected, the position is much weaker, which is precisely why it is worth collecting.
What if the revision genuinely made it worse?
Say so and recommend reverting. Producers worry that this admits a mistake, but it reads as judgement rather than error. A studio willing to argue against its own last change is a studio the client trusts on the next one.
