Scope creep rarely arrives as a big ask. It's a dozen small ones. These replies keep the client happy while making extra work visible and paid. Copy, fill the brackets, send.
The first time a request falls outside the agreed scope
Hi [Name], Happy to help with [request]. Quick flag: it's outside what we agreed for [project] ([what the scope covers]), so I want to make sure we handle it properly rather than squeeze it in. I'll send a short quote for it today. If you'd rather swap it for something already in scope, tell me which item and I'll adjust. Thanks, [Your name]
Same day, once you've sized the extra work
Subject: Change order [#]: [request] for [project] Hi [Name], Here's the change order for [request]: - Work: [1-2 line description] - Cost: $[amount] ([hours] hrs at $[rate], or fixed) - Timeline impact: [none / delivery moves from [date] to [date]] Reply "approved" and I'll start on [date]. The original scope and deadline stay as they are until then. Thanks, [Your name]
When small asks keep stacking up
Hi [Name], Over the last [period] we've added [N] requests beyond the original scope ([short list]). I've been glad to help, but to keep [project] on schedule I'm going to start batching new requests into one change order each [week / milestone]. That way you see the cost before anything is added, and the core work stays on track. Anything urgent, just mark it and I'll quote it right away. Thanks, [Your name]
The best fix is a tight scope and a change-order process agreed up front. The full kit has both, ready to paste into your next proposal.
Use Claude, Cursor or Codex? The Scope Guard AI agent skill ($12) spots out-of-scope requests and drafts the change order for you.
Grab the 3 free emails that get unpaid invoices paid and the free Invoice Chase Lite AI agent skill.