Scope change notice email
Says no to a request without saying no — anchored to what was agreed, then three priced ways forward: descope, extend, or add budget.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your email
SubjectRe: the additional payment-gateway integration — a quick scope note
How to use it well
- →Name the original agreement you're scoping against — "out of scope" only lands as fact, not opinion, when it's anchored to what was actually agreed.
- →Always give three real options (descope, extend, add budget), each with a number or date attached — an open-ended "it'll cost more" invites a negotiation you didn't plan for.
- →Say it as soon as the request lands, not after you've already done the work — asking for budget retroactively reads as a bill, not a proposal.
Part by part
- Thanks for sending over {{request_summary}}
- Acknowledges the request before declining its scope. Opening with the boundary reads as resistance rather than as a professional note.
- this falls outside what we scoped in {{original_agreement}}
- References the agreement by name. It converts a judgement into a factual comparison against something both parties signed.
- here are three ways forward
- Options rather than a refusal. It keeps the conversation about how rather than whether, which is what preserves the relationship.
- and I'll get it moving right away
- Signals willingness. The message says no to doing it for free and yes to doing it, which is the distinction clients care about.
Common mistakes
That's outside the scope of our agreement.Correct and unhelpful. A boundary with no path forward reads as a refusal, and clients respond either by pushing or by quietly looking elsewhere.
Absorbing it quietly to keep the relationship smooth.The most expensive option available. Unbilled additions establish that the scope is negotiable, and the next request is larger — this is how projects lose their margin.
Sending an invoice for the extra work without discussing it.A surprise charge damages trust more than the conversation would have. Scope changes need agreement before the work, not notification after it.
Questions
What should the three options be?
Typically: do it as a change order with cost and timeline, swap it for something already in scope, or defer it to a later phase. Three real choices stop the conversation being a yes-or-no about money.
Is it worth raising for something small?
Yes, and it can be gracious. Noting that something is out of scope and that you will do it anyway costs nothing and establishes the boundary, which makes the next conversation much easier.
How quickly should I send it?
Before starting the work, always. Once it is underway the conversation is about whether to pay for something already delivered, which is a far worse position for both sides.
What if the client insists it was always in scope?
Go back to the written agreement together rather than arguing from memory. If it genuinely is ambiguous, that is a scoping lesson worth taking — and splitting the difference usually costs less than the dispute.