The short answer
Do not start the extra work immediately. Thank the client for the request, show how it changes the agreed scope, state the added fee and delivery impact, then ask for written approval. The request is not the problem; an invisible impact is.
Most awkward scope conversations begin with harmless language: "one more revision," "a quick extra page," or "while you are in there." A professional response does not need to sound defensive. It simply turns an informal idea into a clear decision.
First, check whether the request is actually extra
Compare the request with the proposal, statement of work, or project brief. It is probably outside scope when it adds a deliverable, changes an approved direction, uses more revision rounds, requires a new format or platform, introduces another stakeholder, or moves the deadline without reducing the work.
Deliverable
Was this exact output promised?
Quantity
Has the agreed number of pages, concepts, or revisions increased?
Direction
Is the client replacing an approved decision with a new one?
Timing
Does the request require priority work or a shorter schedule?
If the original wording is ambiguous, own that ambiguity. Clarify the boundary and agree on the next step instead of arguing about who should have understood it.
Use this four-part response
- 1
Acknowledge
Show that you understand the request and its goal.
- 2
Name the boundary
Refer to the agreed deliverables or revision limit without accusing the client.
- 3
Explain the impact
Give the added price, delivery change, and any assumptions.
- 4
Ask for a decision
Offer a clear approve, revise, defer, or keep-the-original-scope choice.
"Thanks for sending this over. I can add it. The original scope covers [agreed work], so [new request] would be an additional deliverable. It will add [fee] and move delivery from [old date] to [new date]. If that works for you, I will send a short change request for approval before I begin."
Copy-and-adapt scripts for common situations
A small additional request
"Yes, I can add that. It sits outside the current deliverables, so I have estimated it separately at [price], with delivery on [date]. Would you like me to add it to the project, or should we continue with the original scope?"
Extra revisions
"We have now completed the [number] revision rounds included in the project. I am happy to make this next set of changes as an additional revision round for [price]. Once approved, I can return it by [date]."
An urgent request
"I can prioritize this for [date]. Doing so will move [existing milestone] to [new date] and add [rush or additional fee]. If the current milestone must stay fixed, I can instead schedule the new request for [alternative date]. Which option works better?"
A one-time courtesy
"This is outside the original scope, but it is small enough that I can include this specific change as a one-time courtesy. Any further additions will be estimated separately before work begins. I will have this one ready by [date]."
How to charge a client for extra work
Use the pricing method that makes the risk easiest for both sides to understand. There is no need to turn every small request into a new contract, but the client should know what they are buying.
Fixed add-on
Best when the deliverable and acceptance criteria are clear. Quote one price for the defined change.
Hourly or daily
Useful when discovery is still needed or the number of iterations cannot be estimated reliably. State the rate and an approval cap.
New phase or milestone
Use this when the request is substantial enough to have its own deliverables, review point, schedule, and payment.
Price the real impact: production time, communication, testing, handoff, and context switching. If the estimate includes uncertainty, explain the assumption or cap instead of hiding it.
What to put in the written change request
A useful record is short enough to read and specific enough to prevent a second misunderstanding. Include:
- The client request in plain language
- The exact added deliverables and exclusions
- Why the request differs from the original scope
- The additional price and payment timing
- The revised milestone or delivery date
- A clear approve, request changes, or decline decision
Need a starting point? Use the free client change request template and keep the client's decision with the request.
Mistakes that make the conversation harder
- Starting before approval. A finished task is much harder to price than a proposed change.
- Calling the client difficult. Discuss the requested work and its impact, not the client's character.
- Saying only "extra charges may apply." Give a price or a defined method for calculating it.
- Leaving approval in scattered messages. Put the scope, price, timing, and decision in one place.
- Making every extra a silent freebie. Even a courtesy should be named so it does not quietly reset expectations.
Prevent the same problem on the next project
Define deliverables, revision rounds, client responsibilities, exclusions, and a change process before kickoff. That does not stop clients from having new ideas. It gives those ideas a fair path into the project.
This guide is general business information, not legal advice. Contract requirements vary by location and engagement.
Frequently asked questions
How do I tell a client that work is out of scope?
Acknowledge the idea, connect it to the agreed scope, explain the price or schedule impact, and offer a clear choice. Keep the message about the work rather than blaming the client. Ask for written approval before starting.
Can I charge for extra work that is not in the contract?
You can propose a separate fee for work outside the agreed scope. Review your contract and local requirements, describe the additional deliverables clearly, and obtain the client's written agreement to the price and timing before doing the work.
What should I do if a client keeps asking for revisions?
Show which revision rounds were included and already used. Group the remaining feedback into a new paid revision round, state its fee and delivery date, and pause additional revisions until the client approves it.
Should I do a small client change for free?
That can be a reasonable relationship decision when the effort is genuinely small. Label it as a one-time courtesy, define exactly what is included, and confirm that future additions will be estimated separately so the exception does not become the new scope.
What if the client refuses the extra fee?
Return to the originally approved deliverables. Offer to remove the new request, reduce another deliverable to keep the budget stable, or move the additional work into a later phase. Do not quietly absorb work you cannot afford to provide.
A professional yes, with clear terms
Turn an extra request into an approved change.
ScopeYes keeps the request, added price, schedule impact, and client decision together before the new work begins.
Create a free change request