Scope creep rarely arrives as one dramatic request. More often, it appears as a small favor, an extra revision, or a new “quick” task added to a message that already contains approved work. Each request may seem harmless. The problem is the accumulation: your calendar fills up, the original deadline becomes unrealistic, and nobody has a shared record of what changed.
A boundary script helps you respond before the new request becomes invisible labor. It is not a way to punish a client or shut down collaboration. It is a short explanation of the current agreement, the effect of the new request, and the choices available for moving forward.
These scripts are written for freelancers, virtual assistants, designers, writers, and other independent service providers. Adapt them to your contract, statement of work, and relationship. A message cannot replace a clear agreement, and a script should not be used to make a legal claim you have not confirmed.
First, separate a change from a clarification
Not every follow-up question is scope creep. Before you push back, identify which situation you are actually handling:
- Clarification: The request explains or refines an item already included.
- Correction: Your work does not match the agreed requirements and needs fixing.
- Priority change: An included item should happen earlier or replace another item.
- New work: The request adds a deliverable, channel, audience, meeting, or round of revisions.
- Ongoing support: A one-time task is becoming a recurring responsibility.
This distinction keeps the conversation fair. If the client is clarifying an approved deliverable, treat it as part of delivery. If the client is requesting a new deliverable, describe it accurately instead of pretending it is included.
You can also check the original scope before replying. Look at the proposal, contract, project brief, approval notes, and any written change decisions. Do not rely only on memory or on the latest message. A calm boundary is easier to write when you can point to a specific source of truth.
Use a four-part boundary message
A practical boundary script has four parts:
- Acknowledge the request. Show that you read it and understand the desired outcome.
- Name the current scope. State what the existing agreement includes.
- Explain the impact. Mention time, deadline, priority, or price without dramatizing it.
- Offer a next step. Give a choice: add it through the change process, trade it for another item, or schedule it later.
For example:
Thanks for flagging the additional onboarding page. The current project includes the welcome email and the three-page resource guide. Adding a page will require extra drafting and review, so it is not included in the current delivery. I can add it as a change for [fee / hours] and move the final handoff to [date], or we can keep the existing scope and discuss the page in a follow-up phase. Which option works better?
The wording is direct, but it does not accuse the client of doing anything wrong. It makes the tradeoff visible.
Scripts for common requests
“Can you also do this quick thing?”
I can take a look. The current scope covers [included items], and [new task] would be an additional deliverable. If you want to add it, I’ll confirm the time and any deadline change before starting. Otherwise, I can put it on a follow-up list for [date or phase].
This avoids agreeing to work before you understand its size. “Quick” describes the client’s expectation, not necessarily the effort involved.
“Please make a few more changes.”
I’ve completed the [number] revision rounds included in the agreement. I’m happy to review these additional changes, but they would be outside the included rounds. I can quote the extra review as [fee / estimated hours], or we can identify the highest-priority edits to keep within the current scope. Please let me know which route you prefer.
Use the actual revision terms from your agreement. If the new notes correct an error on your side, handle that differently from a new preference or direction.
“We need this by tomorrow.”
I understand the new deadline. The current plan has [deliverable] scheduled for [date], and moving it to tomorrow would require changing [other task / review step]. I can offer [option A] by tomorrow, or complete the full deliverable by [date]. Please confirm which priority you want me to use.
A rushed deadline is often a priority decision disguised as an instruction. Put the displaced work on the table so the client can choose knowingly.
Make “yes” more precise
A boundary does not always mean saying no. It can mean saying yes with conditions:
Yes, I can add that. To keep the quality of the current deliverables, I would need to move [milestone] to [date] and add [fee / hours]. If that works, I’ll update the task list and send the revised summary.
This is collaborative without being vague. The client gets a clear answer, and you avoid donating time by accident.
Record the decision after the conversation
If you discuss a scope change on a call, send a short recap afterward. Include the request, decision, price or estimate, new deadline, and owner of the next action. For example:
Recap: We are adding [deliverable] and removing [other item] from this phase. The revised handoff is [date]. The added work is [fee / hours], subject to [approval or invoice terms]. I’ll update the project list after your confirmation.
Keep the recap in the normal project channel. A private note is useful for your records, but it should not be the only place the agreement exists.
If the client keeps ignoring the boundary
Repeated requests without approval are a process problem, not a writing problem. Restate the boundary once, stop unapproved work, and point to the contract or change procedure. If the pattern continues, consider whether the engagement is still workable. Follow your agreement for pauses, termination, payment, and handoff, and get professional advice for a serious dispute.
You do not need a dramatic speech to protect your capacity. A specific reference to scope, a visible tradeoff, and a clear next step are usually enough. The free Mosaic Maker Templates checklist can help you organize recurring admin and follow-ups around these decisions: https://mosaicmaker5.gumroad.com/l/skgtmh
Top comments (0)