How to handle scope creep without losing the client

When a client asks for something the proposal didn’t cover, don’t answer yes or no on the spot. Check the request against the signed scope. If it fits inside the rounds of revisions they have already paid for, it’s a revision: do it. If it adds, replaces or expands a deliverable, it’s a change request: price it from your day rate, put the fee and the new date on one page, and start once the client has signed it. Your reply is then one of three: yes, at this price; yes, in a later phase; or yes, and it uses one of your rounds. None of them is a no, which is why good clients rarely mind.

Spot it early: the requests that sound small

Scope creep rarely arrives as one big ask. It’s the work that piles up one reasonable request at a time, until you have done far more than you agreed, often without extra pay, as the Freelancers Union’s guide to fighting scope creep politely puts it. A project-management course at Rutgers describes it the same way, as something that creeps up on you slowly rather than all at once. That is why the first small yes matters more than the last big one.

Listen for these:

• “Can you just…” and “one quick thing”
• “While you’re in there, could you also…”
• A new person joining the feedback at the second or third round, with opinions on the first
• A version the scope didn’t name: social sizes, a print file from a web design, a second language
• “Could we see a couple more options?” after a concept was chosen
• A request for the source files, or a new use for the work, when the contract licenses something narrower

None of these is a bad request. Each one is a decision about whether it’s already in the price.

Check the request against the scope

Before you reply, open the signed proposal, or the scope your contract refers to, and go through it in this order:

1. Is this deliverable listed?
2. Is it within the quantities: the number of concepts, pages, sizes and file formats?
3. Is it within the rounds of revisions, and which round is the client on?
4. Does it move the timeline, or the days you have booked for other clients?
5. Does it widen the usage: where the client uses the work, for how long, or on what? Wider usage is a licensing fee, not a revision.
6. Is it on the “not included” list?

Yes to the first three and no to the last three means it’s in scope, so do it, cheerfully. Anything else is a change.

If nothing was written down, write it down now. Send an email that sets out what you agreed (the deliverables, the rounds, the fee and the dates) and ask the client to reply to confirm it. It feels awkward a week into a project, and it’s much harder a month in. In some places a written scope isn’t optional: in New York, both New York City’s and the state’s Freelance Isn’t Free Acts require a written contract for work worth $800 or more, counting everything from the same client over 120 days, and in the city’s words the contract must spell out the work, the pay and the date you get paid. What to include in a freelance contract covers the other laws, and the clause that handles changes.

Revision or change request?

Most disputes turn on this line. A revision adjusts a deliverable you agreed to make, in response to feedback. A change request adds a deliverable, replaces one, or changes the brief it was built on.

	Revision	Change request
What it does	Adjusts an agreed deliverable	Adds, replaces or expands a deliverable, or changes the brief
Examples	A larger headline, a warmer palette, a different photo	Two more pages, social sizes not in the scope, a new direction after approval
How it’s paid	Inside the project fee, up to the agreed rounds	Priced on its own, before the work starts
The dates	Fits the schedule	Usually moves the delivery date
The paperwork	One consolidated list of feedback per round	A change request signed by both of you

Two cases catch people out:

• A new direction dressed as feedback. “Can we try it in a completely different style?” after the client approved a concept is a new brief. The approval is the line.
• Rounds past the limit. A fourth round when the proposal said two is extra work too. Quote it the same way as any other change.

Price the change before you start it

Price it while the client is waiting for an answer, not after you have done the work and hoped.

1. Estimate the time in half-days. Include the knock-on work: files that depend on the one that’s changing, an extra round of feedback, re-exporting, and the emails.
2. Multiply by your day rate. At the $570 a day worked out in how to calculate your freelance day rate, a change that takes a day is $570 and one that takes a day and a half is $855. If you haven’t set your own rate from your costs and time off yet, do that first. A change priced on a guess is usually a discount.
3. Set the new date. Check what else is booked. A change that takes two days moves delivery by at least two working days, and may push the next client’s project too.
4. Add the licensing fee, if there is one. If the change widens the usage, price the usage as well as the time.
5. Put it on one page. What is changing and why, whether it adds to or replaces part of the agreed scope, the fee, the new date, and a place for both signatures. The change-request form in The Studio Kit is that page, ready to fill in.
6. Start once it’s signed. If your contract has a change-request clause, follow its terms; the form is how you use it. The AIGA Standard Form of Agreement for Design Services works the same way: a request outside the scope gets a change order, “essentially a mini-proposal,” that sets out the extra time and money and goes to the client for an authorized signature. Bill the fee with the next invoice, or take a deposit on a large change, as you did for the project.

Three replies, in words you can send

Each reply starts from what the client is trying to achieve, gives the number and the date, and makes the next step easy. Then stop. No apology, no paragraph of justification: you are telling them how the project works, not asking permission to be paid.

Yes, with a price

“Good idea, the banners will help the launch. They weren’t in the original scope, so I’ve attached a change request: three sizes for $570, and final delivery moves from the 14th to the 18th. Sign it and I’ll start tomorrow.”

Yes, in a later phase

Use this one when the date can’t move. “That’s worth doing, and I don’t want it to hold up the launch. Let’s finish the current scope for the 14th, and I’ll send a separate quote for the landing page as phase two, starting the week after.”

Yes, and it’s one of your rounds

Use this one for a genuine revision near the limit. “Yes, that fits this round. It’s the second of the two rounds in the proposal, so please send any other changes with it, in one list, by Friday. Anything after this round I’ll quote as a change request.”

Send the third reply early and often. Telling a client which round they are on is not a warning. It’s information they need to plan their own feedback.

Tip: answer a new request within a working day, even if it’s only to say you’ll check it against the scope and come back with a price. Silence reads as yes, and work you start “to be helpful” is very hard to bill afterward.

When a favor is fine, and how to say it’s a one-off

Not every extra needs a form. A favor is fine when:

• writing the change request would take longer than the work;
• it doesn’t move a date;
• the client is good to work with and pays on time;
• you are choosing to do it, not being pressed into it.

Name it as a favor, so it doesn’t become the new baseline: “Happy to export the favicon too, no charge this time. Anything else outside the scope I’ll send over as a change request.” Then put it on the invoice as a line at $0, with what it would normally cost beside it. The client sees the value, and you have a record if the same request comes back on the next project.

Keep a short list of the favors you do for each client. One is goodwill. By the third, it’s unpaid scope, and time to talk about it, kindly, before the next project starts.

Write the next proposal so it can’t creep

Most scope creep is written into the proposal before the project begins, as a line too vague to check a request against. Close the gaps next time:

• Name every deliverable with numbers: three logo concepts, one of them developed; a 12-page brochure; final files in SVG, PNG and PDF.
• Define a round: one consolidated list of feedback, from one person, within a set number of working days.
• Say who approves: the person whose sign-off counts, so a late arrival can’t reopen approved work.
• Add a “not included” line: the things clients assume, such as copywriting, stock photo licenses, printing, social sizes and source files.
• Say how changes work: “Work outside this scope is quoted on a change request at $570 a day and starts once we have both signed it.”
• Put the client’s dates in the schedule: when feedback is due for each round, not only when you deliver.

How to write a freelance proposal clients say yes to goes through each section, and the contract that follows it should carry a change-request clause that matches. More on working with clients, from the first inquiry to the final file, is in Clients.