Scope creep is rarely a client being sneaky. It is a vague scope and two different memories of what was agreed. You remember the statement of work; the client remembers a conversation on a call three weeks ago and a WhatsApp message that said "sure, we can look at that".
You cannot stop clients asking for more, and you should not want to. Extra asks usually mean they like the work. What you can stop is extra work going in without anyone agreeing what it costs or how it moves the date. This playbook covers the habits that prevent most of it, a change-request process for the rest, and the replies to use. It is part of managing a freelance project; for changes that arrive as feedback on a draft, see handling revisions.
Start with an in and out list
The habit that prevents the most arguments takes ten minutes. With every statement of work, include a short list of what is in and what is out, written in the client's language, not yours.
In this project: - Design and build of 6 pages: Home, About, Services, two case studies, Contact - Contact form sending to your email address - Basic on-page SEO: titles, descriptions, image alt text - Two rounds of revisions per page - One 30-minute handover call and a short guide to editing pages Not in this project (happy to quote separately): - Writing the page copy (you supply it) - Blog setup and blog posts - Product photography or stock image purchase - Hosting, domain and email setup - Ongoing maintenance after the 14-day bug-fix window
The "not in" half matters more. Clients do not expect blog setup until they assume it, and they assume it because nobody said otherwise. Read the list aloud at the kickoff call as well; it takes a minute and moves the hard conversation to the day when nobody minds.
Your master services agreement should say that changes to scope, price or dates only count when agreed in writing. That one clause is what turns "but you said on the call" into a request rather than an obligation.
The change-request process
Every new ask, however it arrives, goes through the same short process.
Step 1: Acknowledge it the same day
5 minutesReply to the WhatsApp, email or comment and say you will come back with what it involves. Do not say yes or no yet, and do not start the work.
Step 2: Size it
15 minutesEstimate the hours, the cost and how it affects the delivery date. Note anything else that changes, such as a new dependency on the client's content.
Step 3: Send a change request
10 minutesUse the template below, in email or the shared project doc. Offer the choice: add it now, or park it for a later phase.
Step 4: Get written approval, then start
A thumbs-up emoji on WhatsApp is not enough for anything beyond a small amount. Ask for an email reply or an approval in the doc.
You'll needa reply saying "approved"Step 5: Update the plan and invoice it
Add the change to your project doc and timeline, mention it in your next weekly update, and bill it as agreed.
Decide how the change is paid before the client approves it. For a small change, adding it to the next milestone invoice is fine. For a large one, ask for an advance on the change itself, the same way you did for the project; the deposits and payment terms playbook has the wording.
Change request #[number]: [Project name] Date: [date] Requested by: [name], on [date] by [email / call / WhatsApp] What is being added: [One or two sentences. e.g. "A Case studies page with up to four case studies, using the existing page design. Client supplies text and images."] What it changes: - Cost: ₹[amount] [+ GST if applicable] - Time: [number] working days - Delivery date: moves from [date] to [date] - Anything else: [e.g. "Client to supply case study content by 10 March"] Payment: [added to the next milestone invoice / 50% before work starts, 50% on delivery] Approved by: ____________ Date: ________ (or reply "approved" to this email)
Keep the change requests numbered in one place. By the end of a long project they also tell you something useful: if you wrote six, your original scope was too loose, and the next quote should be tighter.
What to say when the ask arrives
Most scope creep conversations fall into a handful of situations. These replies are short on purpose; the change request does the detailed work.
A genuinely small tweak
Happy to fold this in as part of the current work. No change to the timeline.
Say it, so the client knows it was a choice. Then note it in your log of small favours.
More than a tweak
This is a bit outside the current scope. My quick estimate is about a day and a half, so around ₹8,000, and it would push delivery by three days. Want me to send it as a change request, or park it for the next phase?
"We thought that was included"
Quick check: looking at the statement of work (linked), [X] wasn't listed, so I hadn't planned for it. It's a real two- to three-day piece. I can price it and add it, or we keep it out of this phase. Which would you prefer?
Point to the document, not to your memory. If the document is genuinely ambiguous, consider splitting the difference: do part of it within the price and quote the rest.
A request on WhatsApp or a call
Sounds good, let me look at what it involves. I'll send the details by email today so we both have it in one place.
This is the reply to use most often. It agrees to nothing and moves the conversation to where it can be recorded.
A new stakeholder with new ideas
Good to hear from you, [name]. Some of these change the brief we agreed with [original contact], so let me go through them with [original contact] and send back what fits in the current scope and what would be a change.
Route it through your approver. New stakeholders arriving mid-project with their own vision are one of the larger causes of creep, and the original contact usually wants to manage it as much as you do.
Small asks add up
The dangerous creep is not the big new feature. It is twenty five-minute favours over a month. Each one is too small to quote, and together they cost you a week.
Keep a running list of small extras in your project doc. When it passes a few hours, mention it in your weekly update: "I've folded in about four hours of small extras this month at no charge. From here, I'll send anything new as a change request." Clients rarely mind; most had not noticed how many there were.
On retainers, put a number on it in advance: a fixed number of hours or tasks a month, with anything beyond quoted separately.
When the client will not accept any boundary
Most clients accept a change request without fuss. A client who refuses to pay for anything extra, keeps insisting everything was included, or treats every price as an insult is telling you something about the rest of the relationship. Finish the agreed work well, decline the extras politely, and think hard before taking their next project. Client red flags and dealing with a difficult client cover what to look for and how to handle it.
If you only do one thing from this page, reply to every new ask on the day with "let me look at what it involves", and follow up in writing.
Common questions
What is scope creep in freelancing?
Scope creep is when a project grows beyond what was agreed without the price or deadline changing to match. It usually happens through small requests, "can you also" messages, new stakeholders with their own ideas, or a brief that was vague to begin with. On a fixed-price project every extra hour comes out of your earnings, so a project can slowly turn from profitable to a loss.
How do I tell a client something is out of scope?
Say it on the day they ask, in a friendly tone, and offer a way forward rather than a refusal. For example: "Happy to do this. It wasn't in the original scope, so here's what it would add: about two days and ₹12,000, with delivery moving to the 20th. Shall I send a change request, or park it for the next phase?" Then let the client decide.
What is a change request in a freelance project?
A short written note that describes a new piece of work, the extra cost, the effect on the timeline and anything else that changes, which the client approves before you start. It can be one page or a few lines in an email. Once approved, it becomes part of the agreement, alongside your statement of work, and you invoice it as agreed.
Should I ever do extra work for free?
Sometimes, if the request is small, the client is good to work with, and you decide to. Say clearly that it is a one-off at no charge, so it does not become the expectation. Keep a log of these favours. Once they add up to more than a few hours, the next request goes through the normal change-request process.
How do I prevent scope creep before the project starts?
Write a specific scope: the deliverables with numbers (six pages, four videos of up to 90 seconds), what is not included, the number of revision rounds and the price for extra work. Read the out-of-scope list aloud at the kickoff call. Agree that any change to scope, cost or dates is confirmed in writing, and keep a change-request section in the shared project doc.
