5 out-of-scope reply scripts you can send today

1. New feature mid-project

The client loves the work so far and wants a feature that was never in the brief. Treat it as a change order, not a free add.

Hi [Client],

[Feature] is a strong idea and I can see why you want it in this release. It wasn't part of the agreed scope, so here's what adding it would look like:

- What's included: [short description of the new feature]
- Fee: [price]
- Timeline: adds [X days / weeks] (new delivery date: [date])

I'll keep the current scope on track while you decide. Reply "approved" and I'll send a short change order to lock it in.

[Your name]

2. Extra revision round

You've already used the included rounds and another batch of notes just landed. Price the next round before you open the file.

Hi [Client],

Thanks for the latest notes. We've used the [N] revision rounds included in the project, so another round sits outside the original scope.

- Extra revision round: [price]
- Turnaround: by [date]

If that works, reply "approved" and I'll start on these notes right away. Happy to also park lower-priority items for a later phase if you'd rather protect the current budget.

[Your name]

3. Scope swap (same budget)

They want something new but the budget is fixed. Offer a clean swap of equal effort, or keep both with a quote.

Hi [Client],

We can fit [new request] into the current budget if we swap it for something already scoped. The closest match on effort is dropping [existing deliverable].

Options:
1. Swap [existing deliverable] for [new request] — same fee, delivery stays [date]
2. Keep both — add [price], new delivery date [date]

Which would you prefer? Once you pick, I'll confirm it in writing before I start.

[Your name]

4. Rush add-on

They need something extra and they need it sooner than the calendar allows. Price both the work and the rush.

Hi [Client],

I can take on [request]. It's outside the current scope, and hitting [rush date] means rearranging other work, so here's the rush quote:

- Scope: [what's included]
- Standard fee: [price]
- Rush fee: [rush amount] (to deliver by [rush date])
- Total: [total]

If the original delivery date of [normal date] is fine instead, we can skip the rush fee. Reply with which option you want and I'll lock it in before starting.

[Your name]

5. The 'just this once' favour

A small ask framed as a one-off favour. Name it as goodwill once, or quote it — silent free work trains the next request.

Hi [Client],

Happy to help with [request]. It's outside what we agreed for this project.

Because it's a small one-off, I'm happy to include it as a goodwill add this time at no charge — on the understanding that anything similar going forward is quoted as a change order ([typical fee range] and [X days]).

If you'd rather keep the books clean now, I can do it for [price] with delivery by [date]. Either way works; just tell me which you prefer and I'll proceed.

[Your name]

How to use these scripts

• Send the reply the same day. Silence often reads as a yes.
• Lead with the value of the idea, then name the fee and the date together.
• Offer a clear choice (quote, swap, park, or rush) so the client can decide without a call.
• Get a written "approved" before you start the extra work.
• Point at the original scope, not at the client: "outside what we agreed" beats "you keep adding things".

After they approve, lock it in with a change order. For more reply tones, see the six scope-creep email templates. Not sure if the ask is in scope? Try the free scope check.

Let ScopeLine draft the next reply for you

ScopeLine stores your original deal, logs every extra request against it, totals unpaid scope creep and drafts the reply for you. Free for 3 active projects, no card.