Clariox · Scope disputes
How to tell a client something is out of scope, without the fight.
Point at the record, not at the contract. Say what was actually agreed, in the words that were used, then offer the extra work as a priced option instead of a refusal.
The short answer
Saying "that's out of scope" is a claim about a document. Say it as one. Find where the scope was actually set — a proposal, a kickoff message, an email where a number was confirmed — and quote it back before you say what the new request would add. The client is not being told no; they are being shown a boundary that already existed and asked whether they want to move it.
This works because it separates two things people usually collapse into one: whether the request is reasonable, and whether it was already paid for. Almost every scope fight is actually a fight about the second question wearing the costume of the first.
Why "no" on its own doesn't land
A bare refusal invites a negotiation about fairness — is this really extra, is it really that much work, didn't you already say yes to something similar. None of that is resolvable, because it has no anchor. A quoted boundary has one: here is what the scope says, here is what's being asked, here is the difference. The conversation moves from opinion to arithmetic, which is where you want it.
It also protects the relationship in a way firmness alone does not. Nobody feels dismissed by a fact. They can feel dismissed by a decision.
How to say it
1. Quote the boundary first
"The kickoff scope, confirmed on the 14th, covers implementation and dashboards — not the migration." Not a summary of the scope. The words that were used, so there is nothing to argue about except whether they were said.
2. Name the gap plainly
Say what the new request would add that the original scope didn't cover. Be specific enough that a third party could check it against the record.
3. Offer the path, not the refusal
Close with what it would take to do it: a price, a timeline, and what it does to the current date if anything. The client's next decision is now "do we want this," not "are you refusing us."
On a real thread
Unquoted work, flagged before it becomes a fight.
The same Havenpartners thread. Notice the migration is never assigned an owner and never assumed to be included — both would be guesses.
17 Jul, Priya: our data lead says this needs the warehouse migration finished first. That's not in Phase 2. Who's doing that, and by when? [no reply on this point in the rest of the thread]
- Quote the migration separately if it falls to us — it sits outside Phase 2 and was never priced
Open — the input doesn't answer this
Who is doing the warehouse migration, and by when? Asked 17 July, never answered.
What this replaces
The usual alternative is a memory of the scope, recited under pressure, on a call, while the client is still talking. That version loses almost every time — not because the memory is wrong, but because it's unverifiable in the moment. A record you can point to, assembled before the conversation happens, wins because there is nothing left to dispute except whether the words are real. They are.
Common questions
Saying no without the fallout
How do I tell a client something is out of scope without sounding difficult?
State the boundary as a fact about the record, not an opinion about fairness. Say what was agreed, quote it, and say plainly that the new request sits outside it. Then immediately offer a path forward — a price and a timeline for the extra work — so the message is 'here is what this costs' rather than 'no'.
What if there's no written scope document to point to?
Most agencies are in this position more often than they admit. Rebuild the record from what does exist — the kickoff notes, the proposal email, the thread where the number was agreed — and quote it. A record assembled from real messages is still a record; a memory recited from your side alone is not.
Should I do the extra work anyway to keep the relationship?
Sometimes, but never silently. If you decide to absorb it, say so in writing and say what it would have cost. An unstated favour protects nobody and teaches the client that scope is negotiable by asking twice.
How is this different from just being firm about the contract?
Firmness without a record reads as a power move. A quoted decision reads as a fact both sides can check. The second one ends the argument; the first one usually restarts it.
Find your own boundary before the next call.
Paste the thread. You get what was actually agreed, quoted, and what was never priced — before the client asks.