Scope creep is when a project slowly grows beyond what was agreed: extra pages, features or revision rounds that arrive without extra budget or time. Small requests add up to unpaid work.

How do I tell a client something is out of scope without sounding rude?

Agree the idea has value, say it's outside what you agreed, then give a price and a date for it. Offering options (quote it, swap it or park it for later) keeps the tone helpful.

Should I do small extras for free?

Occasionally, as a deliberate goodwill gesture you mention by name. Doing them silently teaches the client that extras are free, which makes the next request harder to price.

How do I stop scope creep before it starts?

Write a one-page statement of work with an out-of-scope list and a fixed number of revision rounds, and agree that anything not on the page is a change request.

ScopeLine

Free templates

Scope creep email templates: 6 polite replies

A client just asked for "one small thing" that wasn't in the deal. Pick the reply that fits, fill in the brackets and send it today. Each one keeps the relationship friendly and puts a price and a date on the extra work.

1. The small 'quick favour' request

Hi [Client],

Happy to help with [request]. It's outside what we agreed for this project, so here's what it would take:

- Extra work: [short description]
- Cost: [price]
- Timing: adds [X days] to the delivery date

Reply "approved" and I'll fit it in right after [current milestone].

Thanks,
[Your name]

2. A bigger new feature mid-project

Hi [Client],

Great idea, and I think it would add real value. It's a new piece of work rather than a change to what we scoped, so I'd suggest we handle it as a separate change order:

- Scope: [what's included]
- Price: [price]
- New delivery date: [date]

I'll keep the current project on track in the meantime. Want me to send the change order over?

[Your name]

3. Swap instead of add (same budget)

Hi [Client],

We can do [new request] within the current budget if we swap it for something already in scope. The closest fit would be dropping [existing deliverable]. Alternatively, we keep both and I add [price] to the project.

Which would you prefer?

[Your name]

4. One more revision round than agreed

Hi [Client],

Thanks for the notes. We've used the [N] revision rounds included in the project. I'm glad to do another round. It's [price] per extra round, and I can turn it around by [date].

Shall I go ahead?

[Your name]

5. Park it for phase two

Hi [Client],

Love this. To protect the launch date, I'd suggest we park it for a phase two right after launch. I've added it to a running list so nothing gets lost, and I'll send a quote for that list once we're live.

[Your name]

6. A polite no

Hi [Client],

Thanks for thinking of me for this. [Request] isn't something I offer, and I'd rather point you to someone who does it well than do a half job. [Name/resource] would be a good fit.

The rest of the project stays on track for [date].

[Your name]

Tips for handling scope creep

Reply the same day. Silence reads as a yes, and a late 'actually that's extra' feels like a trap.
Lead with yes-and: agree the idea has value, then name the cost and date.
Always give a price and a date together, so the client can make a real decision.
Get approval in writing before you start. An email reply saying 'approved' is enough.
Point at the original scope, not at the client. 'It's outside what we agreed' beats 'you keep adding things'.

Once the client says yes, put it in a change order. To price it, see how to charge for extra work. To prevent the next one, start with a one-page statement of work.

Let ScopeLine draft these replies 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.

Start free on ScopeLine

FAQ

What is scope creep?: Scope creep is when a project slowly grows beyond what was agreed: extra pages, features or revision rounds that arrive without extra budget or time. Small requests add up to unpaid work.
How do I tell a client something is out of scope without sounding rude?: Agree the idea has value, say it's outside what you agreed, then give a price and a date for it. Offering options (quote it, swap it or park it for later) keeps the tone helpful.
Should I do small extras for free?: Occasionally, as a deliberate goodwill gesture you mention by name. Doing them silently teaches the client that extras are free, which makes the next request harder to price.
How do I stop scope creep before it starts?: Write a one-page statement of work with an out-of-scope list and a fixed number of revision rounds, and agree that anything not on the page is a change request.