
Client Boundary Setting Scripts: How to Handle Scope Changes Professionally
When a client asks for extra work, compare the request with the approved scope before promising a price or delivery date. Record what would change, review the effect on your team's workload, and send the client a clear option to approve.
A request can be reasonable and still require a new decision. Your team needs a way to respond without quietly adding work to the schedule.
For women business owners who want strong client relationships and workable boundaries, this is a useful process to put in writing. You can be helpful while giving the client an accurate picture of what their request involves.
Check whether the request changes the agreed work
Start with the current scope, including any changes already approved. Look at the deliverables, included revisions, responsibilities, and timing. A correction to work that doesn't meet the agreed requirements is different from a request for a new deliverable.
If the documents are unclear, clarify the agreement with the client. Don't label every question “out of scope” or ask AI to decide what your business owes someone.
I would ask the team to record the client's request in their own words before interpreting it. “Can we add a second audience?” might mean changing one paragraph, creating a separate campaign, or revisiting the strategy. Find out which.
Use a short change-request brief
You don't need a complicated form for every conversation. You do need enough information to decide what the request means. Use these fields:
Request: What does the client want to change or add?
Current agreement: Which approved deliverable or requirement does it relate to?
Reason: What business need is behind the request?
Work affected: What needs to be created, revised, reviewed, or tested?
Impact: What could change in timing, cost, capacity, or other commitments?
Decision: Who can approve the proposed change on each side?
Status: Is it a request, an option under review, or an approved change?
Microsoft's guidance on evaluating project changes recommends defining review criteria and approval authority, including considering effects on funding and delivery dates. For a small service business, the same questions can fit into a brief your team already uses.
Keep unresolved details visible. “Estimate pending review” is more useful than a confident number nobody has checked.
A worked example: an extra email sequence
Consider this fictional example. Ava's agency is creating one welcome email sequence for a client's main audience. The client asks for a second sequence for a different audience and wants both ready on the original date.
The account lead checks the approved scope. It includes one sequence. The delivery team still needs to assess the second audience, writing, and review work. No additional fee or date has been approved.
Ava's team could reply:
Thanks for explaining the second audience. Our current scope covers one welcome sequence. I'll review the additional writing and review work with our team, then send you an option with the fee and delivery timing. We haven't confirmed that both sequences can be ready on the original date. Would you prefer us to assess adding the second sequence now or planning it as a later phase?
This message acknowledges the request and names the next decision. It doesn't invent a quote or imply that asking about an option means the client has approved it.
The account lead should also record an internal owner and due date for preparing the option. That internal planning date is separate from a delivery date promised to the client.
Give the client a choice your team can deliver
Once you've assessed the request, explain the proposed change and its effect. Depending on the work, you might offer to add it for an agreed fee, move it to a later phase, or replace an existing deliverable if that serves the client's goal.
Check each option before presenting it. Swapping one deliverable for another doesn't automatically mean the effort or price is the same. Include review time and any work already completed that would need changing.
If you decide to include extra work at no additional charge, record the decision and what it covers. Your team still needs to understand the revised workload and any effect on other promises.
Ask for approval through the process agreed for the project. Update the scope and task plan after the decision is confirmed. Keep the earlier version recoverable so the team can see what changed.
Use AI to organize the comparison
AI can help compare a request with supplied scope notes and draft questions for review. Use a business-approved account, remove unnecessary private details, and check the result against the original documents.
Paste this prompt above the current approved scope and the client's request:
Help me prepare a change-request review using only the records below. Summarize the client's request, identify the related approved scope, and list work that may be affected. Separate documented facts from questions needing review. Do not decide contractual obligations or invent fees, effort estimates, deadlines, approval, or delivery promises. Draft a concise client acknowledgment that explains the next review step without committing to the change. Return the acknowledgment separately from an internal checklist of details to confirm and people who need to decide.
Watch for unsupported words such as “minor,” “quick,” or “included.” They can make an unreviewed request sound settled. For another way to check commitments before sending a message, see the AI sales follow-up workflow.
Notice the requests that keep coming back
Review change requests with your team after delivery. If clients repeatedly ask for the same addition, your offer description may need more detail, or the addition may deserve its own service option.
Track what was requested, what was approved, and what the extra work involved. Use those records to improve the next scope. Don't assume a few requests establish demand for a new offer.
A clear process helps the team respond consistently. This guide to repeatable service-business systems explains how to document the inputs and decisions a task needs.
If extra requests keep landing on your plate without a clear decision, contact Dani about your sales and delivery process. Bring one recent request and the point where your team was unsure how to respond.
