You are in the middle of a project, making great progress, when the client sends an unexpected request. "Can you just add one more thing?" or "We also need you to take care of this." The request is reasonable, but it was never part of the original agreement. Now you face an awkward situation: how do you say no without damaging the relationship?
Declining a client request that falls outside the agreed scope is one of the most delicate conversations in business. A poorly handled refusal can make you seem rigid, unhelpful, or even hostile. A well-crafted response, on the other hand, can demonstrate your professionalism, protect your boundaries, and even strengthen the relationship by reinforcing the value of your work. The key is to be clear, respectful, and solution-oriented.
This guide compares two distinct approaches to declining an out-of-scope request: the Soft & Collaborative Approach and the Direct & Professional Approach. You will learn the pros and cons of each, when to use which, and get ready-to-copy templates for both styles.
The Soft & Collaborative Approach Explained
This approach prioritises preserving the client relationship. It acknowledges the request, expresses empathy for the client's needs, and gently explains why the work is outside the scope. The tone is warm, collaborative, and focused on finding alternative solutions. This is the best choice when you have a close, trusting relationship with the client, when the request is small, or when you want to maintain a highly collaborative tone.
The soft approach works well because it shows the client that you have heard their request and that you care about their needs. It opens the door for a conversation about how to accommodate them without committing to free work. This might involve discussing a scope change, adjusting the timeline, or offering a separate quote for the additional work.
When to use this approach:
- You have a long-standing, trusting relationship with the client
- The request is minor or non-urgent
- You are willing to offer alternative solutions
- You want to preserve the relationship for future business
Soft & Collaborative Template
Subject Line Options: "Regarding Your Request for [Project]" / "A Quick Note on Your Recent Request" / "Working Together on [Project Name]"
Subject: Regarding Your Request for [Project]
Dear [Client's Name],
I hope this email finds you well. I am writing in response to your recent request regarding [briefly describe the out-of-scope work].
I understand why this would be valuable, and I appreciate you thinking of us for this additional work. However, this request falls outside the scope of our current agreement, which was defined as [briefly describe the original scope]. Our existing timeline and resources were allocated specifically to deliver the agreed-upon deliverables.
I would be happy to explore how we can accommodate your request. We could either adjust the scope of the project (which may affect the timeline and cost) or handle this as a separate project. If you are open to either option, I would be happy to prepare a revised proposal or a separate quote.
Please let me know your preference, and we can discuss the best way forward. I value our partnership and am committed to finding a solution that works for both of us.
Best regards,
[Your Full Name]
[Your Job Title]
[Your Company Name]
[Your Phone Number]
The Direct & Professional Approach Explained
This approach is more structured and straightforward. It clearly states that the request is out of scope and explains the consequences of proceeding without a scope change. The tone is professional and firm, without being defensive or aggressive. This is the best choice when the request is significant, when the client frequently asks for out-of-scope work, or when the relationship is more formal and transactional.
The direct approach works well because it sets clear boundaries and protects your business. It reinforces your value proposition and establishes that you take your commitments seriously. It also prevents misunderstandings about what is included in the project, which can reduce future scope creep.
When to use this approach:
- The relationship is formal or transactional
- The client frequently requests out-of-scope work
- The request is significant and would require substantial effort
- You need to set clear boundaries for future collaboration
Direct & Professional Template
Subject Line Options: "Re: Additional Request – [Project Name]" / "Clarification on Project Scope" / "Scope of Work – [Project Name]"
Subject: Re: Additional Request – [Project Name]
Dear [Client's Name],
Thank you for your request regarding [briefly describe the request]. I would like to clarify that this work falls outside the scope of our current agreement, which covers [briefly describe the original scope].
To complete this additional work, we would need to adjust the scope of the project, which would affect both the timeline and the cost. Specifically, we would require [mention the additional time, resources, or cost required].
If you would like to proceed with this additional work, I am happy to prepare a revised proposal or a separate quote. Please let me know your preference, and we can discuss the details.
If you prefer to keep the project within the current scope, we will continue with the original deliverables and timeline. Let me know if you have any questions about this.
Sincerely,
[Your Full Name]
[Your Job Title]
[Your Company Name]
[Your Phone Number]
Pro Tip: Be Clear About the Original Scope
Before declining a request, go back to your contract or proposal and confirm that it is genuinely out of scope. This gives you a clear reference point and avoids any confusion or negotiation about what was originally agreed.
Common Mistakes That Undermine Your Decline
Even with a good template, certain wording choices can turn a polite decline into a negative experience for the client. Here are the most common mistakes to avoid when declining an out-of-scope request.
- Using an abrupt or dismissive tone. Saying "We can't do that" or "That's not included" can sound cold and unhelpful. Instead, acknowledge the request and explain why it is out of scope.
- Making it personal. Avoid saying "I can't do this" or "I don't have time." Frame it as a matter of business policy: "Our agreement covers X, and this request falls outside that scope."
- Not offering alternatives. A refusal without any alternatives can feel like a dead end. If you can offer a solution—such as a separate quote or a scope adjustment—do so.
- Apologising excessively. A brief apology for the inconvenience is appropriate, but over-apologising can undermine your authority and make the refusal seem unfair.
- Blaming the client. Saying "You didn't include this in the original scope" sounds accusatory. Instead, say "This request falls outside the scope we originally agreed upon."
- Not explaining the impact. If the request requires significant extra work, explain the impact on the timeline and cost. This helps the client understand why the request is out of scope.
How to Handle Pushback from the Client
Sometimes, despite a clear and professional refusal, the client may push back. They may say "But it's only a small change" or "I thought this was included." How you respond is critical to maintaining a positive relationship.
If the client says "But it's only a small change": Acknowledge their perspective, but explain why it requires more effort than they might think. For example: "I understand it may seem small from your side, but it involves [briefly explain the work involved]. To do it properly, we would need to allocate additional time and resources."
If the client says "I thought this was included": Gently clarify the original scope. You can say: "I can understand why that might be confusing. The original proposal covered [specific items]. This request is different because [explain the difference]. I am happy to discuss this further if needed."
If the client becomes frustrated: Stay calm and professional. Acknowledge their frustration without becoming defensive. Reiterate your commitment to finding a solution. For example: "I understand this is frustrating. I want to find a way to accommodate your needs. We could either adjust the scope or handle this as a separate project."
When to Say Yes Without Extra Charge
While it is important to protect your boundaries, there are times when it may be appropriate to say yes to an out-of-scope request without additional charge. This is a strategic decision, not an automatic rule.
You might consider saying yes when: - The request is very small and can be completed in a few minutes - The client is a long-standing, valuable relationship - The request is a genuine error or oversight in the original scope - You want to build goodwill for future business
However, even when you say yes, it is important to communicate clearly. You might say: "I am happy to include this as a one-time goodwill gesture, but please note that future requests outside the scope may incur additional charges." This sets clear expectations for the future.
If you decide to say yes without charge, do so explicitly and document it. You can update the scope of work or send a brief email confirming the addition. This protects you from future misunderstandings and sets a precedent for any additional requests.
Warning: Never Set a Precedent You Can't Maintain
If you give away out-of-scope work for free once, the client may expect it in the future. Be clear when you are making a one-time exception. This prevents scope creep and maintains the integrity of your work.
Checklist: Before You Decline an Out-of-Scope Request
Before you send your response, review it against this checklist to ensure it is professional, clear, and solution-oriented.
- Clear subject line: Does it mention "request," "scope," or "project"?
- Personalised greeting: Have you addressed the client by name?
- Acknowledgment of the request: Have you acknowledged the client's request?
- Clear explanation: Have you explained why it is out of scope?
- Offer alternatives: Have you offered solutions such as a scope change or a separate quote?
- Professional closing: Have you expressed appreciation for the client's business?
- Proofread: Check for typos, incorrect details, or confusing language.
Frequently Asked Questions
Q. Should I decline an out-of-scope request if the client is a long-standing, valuable relationship?
A. You can still decline, but do it with extra care. Acknowledge the relationship, express appreciation, and offer alternatives. For a valuable client, you might consider accommodating the request as a one-time gesture of goodwill, but clearly communicate that future requests may incur additional charges.
Q. How do I define out-of-scope work?
A. Out-of-scope work is any task that was not explicitly included in the original contract, proposal, or scope of work. It may include additional features, changes in specifications, extra meetings, or work that goes beyond the agreed deliverables.
Q. What if the client says they "assumed" the work was included?
A. Gently clarify the original scope and explain why the request is not included. You can say: "I can understand why that might be confusing. The original proposal covered [specific items]. This request is different because [explain the difference]. I am happy to discuss this further if needed."
Q. Should I offer a discount for out-of-scope work?
A. You can offer a discount as a goodwill gesture, especially for a valuable client. However, be clear about the cost and the timeline. A discount does not mean free work—it acknowledges the relationship while still protecting your business.
Q. How do I prevent out-of-scope requests in the future?
A. Be clear about your scope from the start. Include a detailed scope in your contract or proposal. When a client requests additional work, respond with a scope change request as soon as possible. Regular check-ins can also help you identify and address scope creep early.
Q. What if the client refuses to pay for the out-of-scope work?
A. If the client refuses to pay, you may need to make a decision about the relationship. If the client is valuable, you might absorb the cost as goodwill. If the client is not valuable, you may need to hold your ground. In either case, be professional and avoid burning bridges.