How to stop scope creep: 5 email scripts for client projects
Three contract lines that prevent most scope creep, and five short emails that turn mid-project asks into paid change orders.
On this page
You stop scope creep by writing the scope down in specific terms, limiting revision rounds, setting a price for changes before the project starts, and answering every extra request with a small, friendly change order. The five email scripts below do the last part for you.
Scope creep is common. PMI's 2018 Pulse of the Profession found that 52% of projects had experienced scope creep or uncontrolled changes, up from 43% five years earlier. That survey covers organisations, not solo businesses, but the pattern is the same at any size. If you do not control scope, it grows.
Why scope creep happens
It rarely starts with a client trying to take advantage. It starts with "while you are in there, could you also..." and a yes that feels easier than a no. Two weeks later the project is 30% bigger and you are working for free.
Wikipedia's entry on scope creep defines it as continuous or uncontrolled growth in a project's scope after the project begins, and says it usually happens when the scope is not properly defined, documented or controlled. Three patterns cause most of it.
Vague scope. "Design the homepage" lets the client's picture of the job grow freely. "Design one homepage in Figma, mobile and desktop, delivered as one file, with two revision rounds" does not.
No change process. If you never said what happens when scope changes, both sides default to "it is fine, I will just do it."
Politeness asymmetry. You feel bad saying no, and the client does not feel bad asking. Repeat that five times and you are doing a third of the project for nothing.
All three are fixable before the project starts. PMI has written about scope creep for years, and its core advice is the same one this post gives: define the work, agree how changes are handled, and keep a record.
Prevent it with three lines in the agreement
Put three lines in every contract or statement of work before the first call about the details.
- The deliverables, specifically. Name the number of pages, the formats, the file types and what is not included.
- The revision rounds. "Includes two rounds of revisions. Additional rounds are billed at $X each." Not "I will revise until you are happy."
- The change rate. "Work outside this scope is quoted separately and agreed in writing before it begins."
With those three lines, "could you also build the FAQ page?" becomes a pricing conversation instead of a boundary fight. Our guides to the statement of work and to writing a revision policy go deeper on the wording. Have a lawyer check the contract language for your country.
Sign-off matters as much as the wording. Wikipedia's guidance for projects says to have the sponsor approve requirements before execution begins. For you, that means the client signs the scope before work starts and approves each milestone as it ends. A client who approved milestone two cannot reopen it as a free revision during milestone three.
The five scripts
Keep each reply short. Long emails sound defensive, and short ones sound professional. Replace the brackets with your own details.
Script 1: the "while you are at it" request
Use it when the ask is outside the original deliverable.
"Happy to take that on. It is outside the original scope, so I would handle it as a small change order: [$X] to add [the thing], delivered with the next milestone. Want me to send the change order for approval, or hold it for a second phase?"
This does not say no, lecture or apologise. It treats the request as a normal pricing question, which it is.
Script 2: the extra round of revisions
Use it when you offered two or three rounds and the client is past that.
"Quick note before I start. We are at round four, and the agreement covers three. I can do this batch for [$Y] as an addendum to the original scope. If that works, confirm and I will have the updates back by [date]."
It points to the agreement, gives a number and sets a date. No drama.
Script 3: "it will only take a minute"
Use it when the client plays down the work to justify it being free.
"Fair enough, most of these are quick once I am in the file. The cost adds up when there are four or five of them. I would rather bundle them as one small change order at the end ([$Z]) so we do not lose track. Does that work?"
You accept their view of the task without giving up the principle, and you turn five awkward conversations into one.
Script 4: the mid-project pivot
Use it when the client wants to redirect the project halfway through.
"I like the new direction. To keep this clean: the original scope was [X], and the new direction is closer to [Y], which is roughly [Z]% more work. I suggest we close the original scope at [milestone] and start a new one for the new direction. I will send the wrap-up and the new scope by [date]."
Two scopes give both sides a clean record, and the extra cost reads as administration instead of a penalty.
Script 5: the repeated small ask
Use it when a client who is otherwise easy keeps sending small extras.
"I have noticed a few extras on this project, which I am glad to do. To keep things fair on both sides, I will track them and send a single change order on Friday. Anything on the list you would rather drop?"
It makes the pattern visible without accusing anyone, and it gives the client a chance to cancel the least important ones.
When the client refuses to pay for changes
Occasionally a client says "this should have been included." Go back to the written scope and quote the relevant line. If the scope was vague, that is on you, and the honest answer is to do the first one as a goodwill gesture and tighten the contract for next time.
If the client keeps pushing, stop work on the extra items, finish what was agreed, deliver it and invoice. Wikipedia's advice on scope control includes the line that you should not accept changes just to please the client, and that occasionally refusing can reduce the risk of the whole project being cancelled. Some requests belong in a follow-up project.
Training and discipline help too. PMI's 2023 Pulse of the Profession reports that organisations that prioritise power skills such as communication saw scope creep on only 28% of their projects. Good communication is cheaper than a fight, and it is also the thing that keeps a client coming back. A clear way to get paid for the extra work is the other half. Bonsai's analysis of more than 100,000 freelancers found that 29% of invoices were paid at least a day late, so make the change order a written, approved item with its own invoice and due date.
How Delivvo turns extras into paid change orders
Delivvo keeps the scope, the changes and the payment in one place, so the conversation is about the document, not about memory.
- Build the original quote from packages and add-ons in Proposals. The client picks, signs and pays the deposit on one page, so the scope they agreed to is the scope on file.
- The signed contract has a signing record with a hash, the IP address, the device and an archived PDF, which settles the "that was not what we agreed" argument.
- When an extra request arrives, send it as a new add-on or a small quote. The client approves and pays for it before you start.
- Inside the client portal, approvals and messages live next to the files. When the client signs off on a milestone, that approval is attached to the project, so it is easy to point back to.
- For stage billing, a payment schedule of up to 12 payments ties each milestone to a payment.
A change order in practice looks like this. A client on a branding package asks for a social media kit on the last day. You send a small quote for the kit with its own price, and the client approves it. You then invoice it with the next sequential number, and the work starts once the deposit is in. If the client lets it sit, nothing is lost: the original project carries on, and the extra item waits on the page until they decide. There is no argument to have, because the offer and the answer are both on record.
One thing worth knowing: the portal keeps file versions. If a client says "I asked for the blue one", you can show which version they approved and when. You can also see a more detailed look at how the approvals work on the client approvals page.
Delivvo is a CRM and client portal for service businesses. See Delivvo for teams.
FAQ
What is scope creep?
It is growth in a project's scope after the project has started, without a matching change in price or time. It usually happens when the scope was vague or there was no process for changes.
How do I say no to extra work without upsetting the client?
Do not say no. Say yes at a price. A short email that offers the extra work as a small change order treats the request as a normal pricing question.
How many revision rounds should I include?
Two or three is common. Whatever you choose, write the number in the agreement and state the price of additional rounds.
Should I do small extras for free?
Occasionally, as a deliberate gift, and say so: "no charge this time". If you do it silently, the client will expect it every time.
Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, so the scope you agreed stays on file and extra requests become paid add-ons. Clients pay you directly through your own gateway, and Delivvo takes 0%. Start free