How to Handle Out-of-Scope Client Requests: Examples, Response Templates, and Change Order Best Practices
Published 28 October 2026
Client requests are a normal part of running a service business. Problems start when a client asks for work that wasn't in the original agreement. These out-of-scope client requests can add to workloads, push deadlines, and strain the relationship.
For marketing agencies, studios, consultants, and development teams, the challenge is knowing how to respond without damaging the client relationship.
The answer is a clear process: check each request against what was agreed, explain any change, and get approval before starting additional work. This guide shows how to tell whether a request was agreed, respond professionally, and use a change order process to keep projects on track.
What Counts as a Request Beyond the Agreement?
These are tasks, features, or deliverables that go beyond the work agreed in a contract, proposal, or statement of work (SOW).
For example, a client may hire a digital marketing agency for SEO services and later ask for a complete website redesign. Or a web development client might ask for new features after the project requirements were approved.
Other common examples:
- Asking for additional website pages beyond the agreed deliverables.
- Asking for more design revisions than the agreed revision rounds.
- Adding new SEO tasks beyond a monthly retainer.
- Requesting extra functionality after development has started.
Not every new request is additional work. Some tasks are already covered by the original agreement. That's why checking the agreed requirements before you respond matters.
How to Tell Whether a Request Was Agreed
Before accepting or declining a request, follow these three steps.
1. Review the Original Agreement
Check the contract, proposal, or statement of work for the agreed deliverables, revision rounds, exclusions, pricing, and deadlines.
2. Compare the Request With the Agreed Scope
Decide whether the task is already included, needs clarification, or is additional work. If the agreement is unclear, ask questions before you decide.
3. Confirm Before Committing
Don't promise delivery or quote additional fees until you understand the request and its impact. A quick check against the agreement prevents misunderstandings later.
How to Handle a Request Beyond What Was Agreed, Step by Step
Once you've identified a request that may go beyond the agreement, use a consistent process.
Step 1: Acknowledge the Request
Thank the client and confirm you understand what they need. This keeps the conversation constructive rather than making the client feel turned down.
Step 2: Verify the Agreed Scope
Review the original requirements and decide whether the request falls within the agreed deliverables. If needed, discuss the details with your team.
Step 3: Explain the Impact
If the request means additional work, explain how it affects cost, resources, or the delivery timeline. Be specific and transparent so the client can make an informed decision.
Step 4: Get Written Approval
Before starting additional work, document the revised requirements, pricing, and deadlines. Get written approval through the agreed process, such as an approved change order or a written contract amendment.
This keeps the conversation about the agreement, not about you, and gives the client a clear view of their options.
Response Templates for Additional Work
Knowing what to say can be hard, especially when you want to keep the relationship positive. These templates help you respond clearly and professionally.
Template 1: Politely Explaining Additional Work
Use this when a request goes beyond the agreed deliverables.
Template 2: Requesting Clarification
Use this when you're unsure whether the request is included.
Template 3: Requesting Approval for Additional Work
Use this when the client agrees to proceed with extra work.
These templates set clear expectations without creating unnecessary conflict.
Change Order Process: How to Approve Additional Work
A change order documents an agreed change to the original project requirements. It is particularly useful when additional work affects the deliverables, budget, or schedule.
A practical change order process includes five steps:
- Describe the change: Clearly explain what the client wants to add, remove, or modify.
- Define the deliverables: Specify what the additional work includes and any relevant exclusions.
- Estimate cost and time: Document the additional fees and expected impact on the delivery schedule.
- Obtain written approval: Get the client's confirmation before beginning the additional work.
- Update project records: Keep the revised scope, approvals, and timeline accessible to everyone involved.
For smaller changes, a written amendment or approval through an established project workflow may be sufficient, depending on the contract. For substantial changes, a formal change order can provide greater clarity.
The key is to make sure both parties understand and approve the change before work begins.
How to Prevent Scope Creep in Future Projects
Handling individual requests is important, but preventing recurring scope problems is even better.
Start by defining deliverables, revision rounds, exclusions, and responsibilities clearly at the beginning of every project. Document important client decisions and set a standard approval process for additional work.
You can also use tools that connect client requests with the original agreement.
ScopeLinq turns kickoff notes and email threads into a scope record your client confirms, then checks each new request against it: Included, Additional work, or Needs clarification, citing the line it relied on.
Instead of relying on memory or searching through long email threads, both sides can refer to the same record of what was agreed.
Conclusion: Keep Your Time and the Relationship
Requests that go beyond the agreement don't have to become a source of conflict. By reviewing the original agreement, explaining the impact of additional work, and getting written approval, you keep the work priced and the relationship intact.
The goal isn't to decline every new request. It's to make sure expectations, responsibilities, costs, and timelines stay clear.
Check the next request against what was agreed
If your team handles client requests across several projects, ScopeLinq keeps one record both sides confirmed and answers each new ask from it.
Try it on a sample →Frequently Asked Questions
What should you do when a client requests work beyond what was agreed?
Review the original agreement, explain why the request may require additional work, and discuss the cost and timeline before proceeding.
How do you politely tell a client that additional work costs extra?
Thank the client, explain that the request goes beyond the agreed deliverables, and offer a clear estimate for the additional work.
When should you use a change order?
Use a change order when an agreed project change affects deliverables, pricing, responsibilities, or deadlines and needs formal documentation.
How can businesses prevent recurring extra requests?
Define project boundaries clearly, document client approvals, maintain accessible scope records, and establish a consistent process for reviewing additional requests.