When a client asks for something that was not in the agreement, answer in writing within a working day, say what the new request is, say what it costs in hours and money, and ask for a yes by a named date. Do not do it first and raise it later. Below are three versions of the email, from a soft heads-up for a small extra to a firm change order with a price and a deadline, plus a way to tell which one a request needs and when to pick up the phone instead.

Scope creep is rarely a client trying to get something for free. Most of the time the client has seen the work take shape and thought of one more thing, and nobody told them it was extra. The email's job is to say so in a way that keeps the relationship and still protects your hours. If you have no written scope yet, fix that first with the scope of work template, because every version here points back to it.

First, decide whether it is really outside the scope

Before you write anything, put the request next to the scope document and ask three questions.

  1. Is it named in the deliverables list? If yes, it is in scope, even if it is more work than you expected. That is your estimate problem, not the client's.
  2. Is it named in the exclusions? If yes, point to the line. This is the easiest email you will ever write.
  3. Is it silent? Most scope creep lives here. The request is reasonable, the scope does not mention it, and you have to decide whether it is a clarification (in) or an addition (out). A useful test: would you have priced it if it had been in the first conversation? If yes, it is an addition.

Write down your honest estimate before you reply. Say a client of a small web studio asks for a second contact form with a file upload. You think it is 3 hours of build and 1 hour of testing. At $95 an hour that is 4 times 95, or $380. You now have a number, and the email can be calm because the math is done.

Which version to send

Situation Version What you do
First small extra, under about 30 minutes of work 1. Soft Do it, say it was extra, log it
A real addition, a few hours, a client who is generally reasonable 2. Firm Written change order, work waits for a yes
Third or fourth extra, or an addition that moves the end date 3. Priced, with a deadline Price, new date, decide-by date, and what happens if there is no answer

Version 1: the soft heads-up

Use this for the first small extra. You do the work, but you name it, so the next request does not arrive as a surprise.

Subject: Added the extra photo row, one note on scope

Hi Lena, I added the second photo row to the services page this morning, so you can see it in the preview link. That was outside the three-page plan in our agreement, but it was about 20 minutes, so there is no charge this time. For anything larger than that, I will send a quick price before I start, so you are never surprised on an invoice. Let me know if the row works for you.

Marcus

Why it works: it opens with the finished work, and the scope note comes second. "No charge this time" is a gift with a limit attached, and "I will send a quick price before I start" sets the new rule without scolding anyone. Keep a simple log of these small extras (date, what, minutes). If you give away 10 of them, the log shows you a pattern you can raise at the next check-in.

Version 2: the firm change order

Use this when the request is a real addition. The email names it, prices it, and does not start the work until the client agrees. The structure is always the same: what you asked for, what it adds, what it costs, what stays the same.

Subject: Change request: second contact form with file upload ($380)

Hi Lena, thanks for the idea. A second contact form with a file upload is not in the original agreement (section 2 lists one form). Here is what it adds:

Work: 3 hours of build and 1 hour of testing, 4 hours total at $95 an hour.
Cost: $380, added to the final invoice.
Timing: the launch date stays Friday, November 20.
Everything else in the agreement stays as written.

If you would like it, reply "approved" and I will start today. If you would rather keep to the original plan, no action is needed.

Marcus

Why it works: the client can say yes with one word, and the no costs them nothing. The "no action is needed" line matters. People push back when they feel cornered, and they approve readily when saying no is easy. Keep the agreement's own section number in the email so the client sees a rule you both signed.

Put a change-order clause in the original agreement so this email is never a surprise; the scope template above includes one. For services priced by the hour, the guide to billing a client for services covers the terms that say what counts as extra and when it gets invoiced.

Version 3: the priced request with a decide-by date

Use this when the extras keep coming, or when the addition pushes the end date. Now there are two costs, money and time, and a deadline for the client to choose. It is still polite. It is also specific enough that nobody can claim to have been confused.

Subject: Decision needed by Wed, Nov 11: the extra pages change our Nov 20 launch

Hi Lena, we have now had four requests beyond the agreed three pages: the photo row, the second form, a pricing page and a blog template. Adding the last two is about 11 hours, which is $1,045 at $95 an hour, and it moves the launch from Friday, November 20 to Friday, December 4, because the blog template needs a content review.

Two ways forward:
A. Approve both for $1,045 and the December 4 launch.
B. Launch on November 20 as agreed, and build the pricing page and blog template as a second phase after launch, at the same $1,045.

Please reply A or B by Wednesday, November 11. If I do not hear by then, I will go ahead with the original three pages and the November 20 date, and we can add the extras afterward. I am glad to talk it through. I am free Tuesday at 10.

Marcus

Check the math. 11 hours times $95 is $1,045. The default (what happens if no answer) is the safe one for both sides: the agreed work ships on the agreed date, and nothing is built unpaid. State the default in the email every time. Written as a plain sentence, it saves you chasing for a reply. The same logic works when the client is slow to answer in general; see the email to a client who is not responding. If the change has already pushed the date and you need to tell the client, the project delay email has a version for scope changes.

Lines that make any version better

  • Quote the request in their words. "On Tuesday you asked for a form where customers can attach a photo" shows you listened and fixes the date it started.
  • Put the price in the subject line when you can. A client who sees "($380)" reads it as an offer.
  • Name what stays the same. Launch date, other deliverables, the total of the original quote.
  • One request per email. If three things arrived, send three short change requests or one table, not a paragraph that mixes them.
  • Keep the tone of a colleague. No "as stated in our contract." Say "section 2 lists one form."

When a call works better than a change order

Pick up the phone, then follow up in writing, in four cases.

  1. The extra is bigger than about 20 percent of the project. That is a renegotiation, not a change order, and it goes better by voice.
  2. The client has already pushed back on a change request. A second written exchange tends to harden positions. Call, listen, then confirm what you agreed.
  3. You have already done the work. If the extra is built and the client does not know it costs money, call before the invoice goes out.
  4. The relationship is tense. Read how to handle a difficult client before you write.

After the call, send a two-line recap: "Thanks for the call. We agreed to add the pricing page for $475 (5 hours) and keep November 20. Reply to confirm and I will start." That email is your record. If the client keeps asking for more than the agreement covers and will not accept the price, the honest next step is in how to say no to a client.

Mistakes that make scope creep worse

Saying yes by default and planning to "sort it out at the invoice" is the biggest one. A surprise charge feels like a bait and switch even when the client asked for the work. Second is vague pricing: "it will be a bit extra" invites an argument about what "a bit" means. Third is raising it only when you are angry. Write the email on the day the request arrives, when you are still neutral, and send it after a short read-through. Last, do not apologize for the price. You can be warm without being sorry that your hours cost money.

Once a change order is agreed, Rocketship can send it as its own quote that the client signs and pays online through Stripe. Rocketship takes a 1% platform fee on each payment, separate from Stripe's own processing fee, and the client stays in your CRM and pipeline with both quotes, so what was added, and when, is on record in one place. Plans and what each includes are on the pricing page.