================================================================ SCOPE CREEP SCRIPTS — 12 WORD-FOR-WORD RESPONSES Free resource from SoloStack | solostack.madethis.app ================================================================ 12 scripts for the most common scope creep situations. Use them verbatim, adapt as needed, or combine elements to fit your voice. All scripts assume a professional but firm tone — not aggressive, not a pushover. ================================================================ SCRIPT 1: CLIENT ASKS FOR "ONE SMALL THING" ================================================================ Situation: "Hey, while I have you — could you just quickly do X? It's a small thing, shouldn't take long." Response: --- Happy to look into that! Let me check if it falls within our current scope. Looking at our agreement, [X] isn't included in the deliverables we outlined — so I'd need to add it as a Change Order with a small fee for the additional time. If that works for you, I can put together a quick Change Order and get it done alongside the current project. Want me to send that over? --- WHY IT WORKS: You're not saying no — you're saying "yes, and here's how we do it." The framing ("small fee") keeps it low-pressure while still establishing the process. ================================================================ SCRIPT 2: CLIENT REDEFINES THE PROJECT MID-WAY ================================================================ Situation: You're halfway through a project and the client starts describing a significantly different outcome than what was originally agreed. Response: --- I want to make sure we're building the right thing, so I appreciate you sharing this direction. I do want to flag something: what you're describing sounds different from the scope we agreed on in [Document/Email from Date]. Before I proceed, I'd like to get clear on a couple of things: 1. Is this replacing the original direction, or adding to it? 2. Are we working toward [original deliverable] or something different? Depending on the answer, this may require a Change Order to cover the revised scope. I don't want to get to the end of the project and have us misaligned. Can we hop on a 15-minute call to realign on exactly what we're building? --- WHY IT WORKS: You're not accusing the client of scope creep — you're asking clarifying questions. The call request lets you document the pivot in real time. ================================================================ SCRIPT 3: CLIENT SENDS SCOPE CREEP VIA TEXT/DM (NOT EMAIL) ================================================================ Situation: Client sends a scope addition request via WhatsApp, Slack DM, Instagram DM, or text message. Response (via the same channel): --- Got it! Can you send this to me via email so I have it in the project thread? I keep everything organized there so nothing falls through the cracks. Once I have it in writing, I can confirm whether it's within our current scope or needs a Change Order. --- FOLLOW-UP if they just reply "ok" without sending the email: --- Hey [Name] — just following up on the [X] request you mentioned the other day. Did you get a chance to send that over by email? Want to make sure I capture it properly. --- WHY IT WORKS: You're not refusing to help — you're redirecting to the official channel. This keeps all scope discussions in writing without making it confrontational. ================================================================ SCRIPT 4: CLIENT PUSHES BACK ON A CHANGE ORDER ================================================================ Situation: "I don't understand why I need to sign a Change Order for this — it's basically part of what we're doing anyway." Response: --- I completely understand — it can feel like paperwork for something that seems like a small extension. The reason I use Change Orders isn't bureaucracy; it's so both of us are protected. When I document the scope, cost, and timeline in writing before doing the work, you know exactly what you're getting and what it costs. I know exactly what I'm delivering and when. Without that, small additions can turn into misunderstandings about what was included. The good news is it's a simple document and usually takes a few minutes to review. I'll send it over now — if everything looks right, just reply with approval and we'll get moving. --- WHY IT WORKS: You're reframing the Change Order as protection for them, not just for you. The "reply with approval" language reduces friction — they don't need to sign a formal document in every case, email approval works. ================================================================ SCRIPT 5: REPEAT OFFENDER WHO ALWAYS "FORGETS" SCOPE ================================================================ Situation: A client who consistently adds things, always framing it as "I thought we covered that" or "just a quick add." Response (for the latest incident): --- This is the third time we've had to revisit what's included in the current project, so I want to proactively address it. I've attached our original agreement for reference. Going forward, I'd like to formalize any additions as Change Orders before starting — it keeps us both clear on what's agreed and prevents any surprises at invoicing. For [the current request]: I'll have a Change Order over to you by end of day. Once approved, I can have it done by [date]. --- HARDER VERSION (if the pattern continues): --- I want to have a direct conversation with you because I value our working relationship. Over the course of this project, the scope has expanded significantly beyond what we originally agreed. I've absorbed a lot of that without charging, but I'm not able to continue doing so. Going forward, every addition outside our original scope will go through the Change Order process — without exception. If that's a problem, I'd like to discuss whether this project is still the right fit for both of us. --- ================================================================ SCRIPT 6: CLIENT SAYS "I THOUGHT THIS WAS INCLUDED" ================================================================ Situation: "Wait, that's not included? I assumed it was part of the package." Response: --- I can see why you might have expected that — it's a reasonable assumption. Let me pull up our agreement so we can look at what was specifically outlined. [Reference the contract or SOW] As you can see, our agreement covers [X, Y, Z]. [The requested item] isn't listed there. I know that's frustrating, especially if it seemed like a natural part of the project. Here's what I'd suggest: I can put together a Change Order so we can add it cleanly. Alternatively, we can table it for a future project if the budget isn't there right now. What would work best for you? --- WHY IT WORKS: You're acknowledging their perspective without validating their claim. Offering two paths (Change Order now or future project) keeps the conversation forward-moving. ================================================================ SCRIPT 7: AFTER PROJECT DELIVERY — SCOPE EXPANSION ================================================================ Situation: You've delivered the project and the client comes back with "one more thing" they want before they'll sign off. Response: --- Glad to hear the project is getting close to done! I do want to flag that [the additional request] is outside the scope of what we agreed on [date]. The deliverables we contracted for have been completed. If you'd like to add [X], I'm happy to do that — I'd just need to set it up as a new project or a Change Order so we're both clear on the scope and cost. In the meantime, I'll send the final invoice for the completed work. Once that's settled, we can discuss the additions. --- IMPORTANT: Don't wait on sending the final invoice. Deliver the completed work, send the invoice, and offer the additions as a separate engagement. ================================================================ SCRIPT 8: VERBAL AGREEMENT BEING USED TO OVERRIDE CONTRACT ================================================================ Situation: "But we talked about this on the call — you said you'd include it." Response: --- I remember our conversation, and I appreciate you bringing this up. However, looking at the written agreement we signed on [date], [the request] isn't listed in the scope of work. My process is to document everything we agree on in writing before starting work — that's what protects both of us. If there was something we discussed that I didn't capture in the contract, that's something we should have caught and addressed before starting. At this point, if you'd like to add [X], I can do that with a Change Order. But I can't take on additional work based on a conversation we had before the contract was finalized. I hope you understand — it's not about being difficult. It's about working in a way that's clear and fair to both of us. --- ================================================================ SCRIPT 9: SCOPE CREEP DISGUISED AS A "BUG FIX" ================================================================ Situation: "This isn't working the way I expected — can you fix it?" (But what they're describing is not a bug — it's a feature they didn't specify.) Response: --- Thanks for flagging this. Let me look at it. [After review:] I took a look, and what you're describing isn't a bug in the technical sense — the [feature/deliverable] works as specified in our agreement. What you're describing is a different behavior than what was scoped. To be specific: our agreement specified [what was agreed]. You're describing [what they want instead]. These are different things. I'm happy to implement the change you're describing, but it would need to be a Change Order since it goes beyond what we built to spec. I can send that over with an estimate if you'd like to move forward. --- WHY IT WORKS: The distinction between a bug (something broken) and a change request (something different from spec) is legally and contractually significant. Make this distinction clearly and in writing. ================================================================ SCRIPT 10: CLIENT ESCALATES TO A COMPLAINT ================================================================ Situation: Client becomes frustrated and says things like "this isn't what I paid for" or "you're not delivering what we agreed." Response: --- I'm sorry to hear you feel that way — I genuinely want this project to be a success for you. Let me make sure we're working from the same information. Here's what our agreement specifies: [Paste or summarize the relevant scope from the contract] Here's what I've delivered so far: [List completed deliverables with dates] If there's a gap between what was agreed and what was delivered, I want to know about it and fix it. If the issue is that the agreed scope doesn't fully meet your needs, I'd like to talk about how we can address that through a Change Order. Can you be specific about what you feel is missing? I want to make sure I understand your concern before we figure out how to resolve it. --- NOTE: Keep this response factual. Don't apologize for work you did correctly. Acknowledge their frustration while redirecting to the contract as the objective reference point. ================================================================ SCRIPT 11: GRACEFUL EXIT WHEN SCOPE HAS EXPLODED ================================================================ Situation: The scope has doubled or tripled, the client won't use the Change Order process, and the relationship isn't salvageable. Response: --- [Client Name], I need to be direct with you. Since we started this project, the scope has expanded significantly beyond what we originally agreed. I've tried to address this through Change Orders, but we haven't been able to reach agreement on a fair process for the additional work. I don't think we're able to continue this project in a way that works for both of us. I'd like to bring our engagement to a close. Here's what I propose: - I'll deliver [completed deliverables] in their current state within [X] business days. - You'll owe [amount for work completed to date based on contract terms / hourly rate]. - All intellectual property created to date transfers to you upon receipt of final payment. I'm sorry it didn't work out. I'm happy to answer questions about the deliverables I hand off to make the transition as smooth as possible. [Your name] --- WHY IT WORKS: You're exiting professionally, specifying what you'll deliver and what they owe, and keeping the door open for a clean handoff. This is better than ghosting or escalating. ================================================================ SCRIPT 12: PROACTIVE MIDPOINT SCOPE CHECK-IN ================================================================ Situation: You're halfway through a project and want to get ahead of scope issues before they become conflicts. Send this at the project midpoint: --- Subject: [Project Name] — Midpoint Check-In Hi [Client Name], We're at the halfway point of [Project Name] and things are on track. I wanted to do a quick scope check-in before we head into the second half. Here's where we stand: COMPLETED: - [List completed deliverables] IN PROGRESS: - [List in-progress deliverables + expected delivery] REMAINING: - [List remaining deliverables + expected delivery] A couple of things I want to confirm before we proceed: 1. Based on our conversations, I want to make sure we're still aligned on the final deliverables. Are there any additions or changes you're thinking about? 2. [Any specific questions about feedback or direction] If there's anything you'd like to add or adjust, now is a great time to discuss it — I can assess whether it fits our current scope or needs a Change Order, and we have time to plan accordingly. Looking forward to the second half — we're in good shape. [Your name] --- WHY THIS IS VALUABLE: Clients often sit on scope additions for weeks, then drop them at the end. This script surfaces them early, when you can still address them without a crisis. It also creates a written record of scope alignment at the midpoint. ================================================================ QUICK REFERENCE — WHEN TO USE EACH SCRIPT Script 1 → Casual "small thing" request Script 2 → Project direction shifting Script 3 → Scope via text/DM Script 4 → Client resists Change Order Script 5 → Pattern: repeat scope offender Script 6 → "I thought it was included" Script 7 → Post-delivery scope additions Script 8 → Verbal override of contract Script 9 → "Bug fix" that's actually new scope Script 10 → Complaint / escalation Script 11 → Exit when scope has exploded Script 12 → Proactive midpoint check-in ================================================================ Get the full contract clause templates, change order document, and the complete scope creep prevention guide at: solostack.madethis.app/resources/freelance-scope-creep ================================================================