Scope creep is one of the most reliable ways to damage a client relationship — and it almost never looks like a problem when it starts. A client asks for “one small addition.” Then another. Then a full rethink of the deliverable, three weeks in. At Choco Media, scope creep agency dynamics are something we’ve had to navigate carefully, because the stakes are asymmetric: say yes too easily and you erode your margins and your team’s trust; push back too hard and you signal that you don’t care about the client’s success. Neither outcome serves anyone.
This post is for agency leads, account managers, and anyone who’s ever found themselves doing work they didn’t quote, for a client who doesn’t think it’s a big deal. We’ll walk through the conversation framework we actually use, the contract language that prevents most issues before they start, and the specific moments where a clear, calm response makes all the difference. You’ll leave with something you can use in your next client call.
None of this is about being adversarial. The goal is a working relationship where both sides understand what’s included, what isn’t, and how to handle the grey areas without drama. That’s better for the client, better for your team, and better for the work.
Why scope creep happens (and it’s rarely malicious)
Most clients who push scope aren’t trying to get free work. They’re responding to a gap between what they imagined the engagement would produce and what the brief actually specified. That gap is almost always created during the sales process, when everyone is optimistic and specificity feels like it might kill the deal.
A few patterns we see repeatedly:
- The brief was written at the start, not the middle. The client’s understanding of what they need evolves as the project progresses. By week three, they know more — and they want that knowledge incorporated, even if it changes what was agreed.
- Verbal agreements don’t survive handoffs. What the sales lead promised and what ended up in the contract are often slightly different. When the account manager comes on board, nobody has a clean record of the informal commitments.
- The deliverable was defined by output, not outcome. “A landing page” means different things to an agency and a client. If the contract says “landing page” and the client imagined a seven-section, three-variant, A/B-testable build, you have a problem.
- The relationship has gone well, so the client feels comfortable asking. Counterintuitively, scope creep is often a sign of a good relationship. The client trusts you. They just haven’t internalised the cost of what they’re asking.
Understanding the cause changes how you respond. A client who’s pushing because the brief was vague needs a different conversation than one who’s testing boundaries. Most of the time, it’s the former.
The contract language that prevents most problems
Prevention is cheaper than repair. Before we get to conversations, it’s worth making sure your contracts and project kick-off documents are doing the heavy lifting.
Define deliverables by specification, not by name
Instead of “three social media graphics,” write “three static social media graphics, sized for Instagram feed (1080×1080px), based on the approved brand guidelines document, delivered as PNG files. Revisions: two rounds included.” Every dimension that could be interpreted differently should be specified. This feels over-engineered until the first time it saves you a revision argument.
Include an explicit out-of-scope section
Most contracts list what’s included. Fewer list what isn’t. Adding an out-of-scope section — “This engagement does not include copywriting for the landing page, development work beyond the items listed above, or paid media management” — removes ambiguity before it becomes conflict.
Specify the change request process
Your contract should include a paragraph explaining what happens when the client wants something that’s outside scope: who identifies it, how it gets documented, how it gets quoted, and what happens to the timeline. If clients know the process exists before they need it, using it feels normal rather than adversarial.
- Change request initiated by either party in writing
- Agency provides a quote within 48 hours
- Work begins only after written approval
- Timeline impact noted in the quote
We’ve found that having the process written down means clients rarely feel blindsided. They knew this was coming. They just forgot to think about it during the sales conversation.
Catching scope creep early: the signals to watch for
Scope creep rarely announces itself. It accumulates through small moments — a Slack message here, an email clarification there — until you look up and realise you’re several days into work that wasn’t quoted.
The signals we watch for:
- “While you’re at it…” — The classic. Usually harmless in isolation, but a reliable indicator that the client’s mental scope is expanding.
- A change in the point of contact. When a new stakeholder enters the project, they often have different expectations than the person who signed the brief. This is the moment to re-anchor on what was agreed.
- Approval rounds that introduce new feedback, not just revisions. Revision rounds are for refining what was agreed. If feedback in round two introduces new requirements that weren’t in the brief, that’s a scope conversation, not a revision conversation.
- The brief document stops being referenced. If the client’s feedback emails no longer mention the original brief, it’s usually because their mental model of the project has moved on. Worth a check-in.
The cost of addressing scope creep late is always higher than addressing it early — for both sides. A conversation at week two is easy. The same conversation at week six, after your team has already absorbed the extra work, is much harder.
The conversation framework: how we actually raise it
This is the part most agencies find uncomfortable. You’ve spotted something that’s outside scope, but you don’t want to seem like you’re nickel-and-diming a client you like. Here’s the frame we use, which keeps the conversation productive:
Name it as a process moment, not a complaint
Don’t say “that’s not in scope” as your opening. Say: “I want to make sure we handle this properly — can we take five minutes to figure out whether this fits within what we agreed, or whether it needs a small change order?” This signals that you have a process, not a grudge.
Reference the brief, not the contract
Contracts feel adversarial. Briefs feel collaborative. When you need to draw a line, reference the brief document: “Looking back at the kick-off brief, we specified X. What you’re describing sounds like Y — that’s a bit different. I want to make sure we’re aligned on what it takes to do that well.” This keeps the conversation forward-looking.
Make it easy to say yes to the process
Clients don’t object to being charged for extra work as much as they object to being surprised by it. If your change order process is fast, clear, and fair, most clients will use it without complaint. We aim to have a change order quote in their inbox within 24 hours. The faster and simpler you make it, the less friction there is.
- Short email, not a formal document
- Clear description of the additional work
- Cost and timeline impact in the first paragraph
- One-line approval ask at the end
For our bespoke retainer clients, we handle this slightly differently — we have a monthly flex budget built into the retainer for exactly this kind of thing, so the change order process rarely comes up. Instead, we review at the monthly check-in what was used and what wasn’t.
When the client pushes back on a scope conversation
Sometimes clients don’t accept the frame. They feel the extra work is obviously included, or they’re frustrated that you’re raising it. This is where agency leads tend to either capitulate (damaging the relationship long-term) or escalate (damaging it immediately).
A few things we’ve learned:
Stay factual, not defensive
Don’t argue about what was “obviously” included or intended. Go back to the document. “Here’s what the brief says — I want to make sure I’m reading it the same way you are.” This keeps the conversation grounded and depersonalised.
Acknowledge the gap without taking blame
Sometimes the brief was genuinely unclear. It’s fine to say: “I think there was some ambiguity in how this was written. Here’s how I read it, and here’s what I think you expected. Can we figure out a fair way to handle the difference?” That’s a very different conversation than either “this is your fault” or “fine, we’ll just do it.”
Decide what you’ll absorb and own that decision
Sometimes it’s right to absorb the extra work — because the brief was vague, because you want to protect the relationship, because the ask is genuinely small. The mistake is absorbing it silently, as if it didn’t happen. If you’re going to do extra work for free, say so explicitly: “We’re going to include this in the current scope because I think there was some ambiguity in how we briefed it. Going forward, changes like this would be a change order.” Making the decision visible means you get credit for it, and it sets a cleaner expectation for next time.
The ongoing relationship: keeping scope healthy over time
For clients on longer engagements, scope management is a recurring discipline, not a one-time conversation. A few practices that help:
- Monthly scope check-ins. As part of the regular monthly reporting rhythm, we include a brief note on scope status — what we delivered, what’s in progress, and whether anything has shifted from the original brief. This normalises the conversation and catches drift early.
- Brief updates, not assumptions. When the client’s priorities shift — which they always do over a 6-12 month engagement — we update the brief rather than just absorbing the change. This keeps the document live and useful.
- Quarterly reviews with a scope component. Our quarterly client reviews include a section on what was in scope vs. what was delivered, with a forward-looking view of any adjustments needed. This is where we renegotiate retainer scope for the next quarter if things have meaningfully changed.
The goal is a client who never feels nickel-and-dimed and a team that never feels taken advantage of. Both are achievable if the process is clear and consistent from the start.
The template: our scope creep response email
When we identify something that’s outside scope, here’s roughly what we send — adapted for the situation, but always hitting the same beats:
Subject: Quick scope check on [X]
Hi [Name],
Thanks for the note on [the new request]. I want to make sure we handle this properly before we get into it.
Looking at the brief we agreed on [date], the current scope covers [original deliverable]. What you’re describing — [new request] — goes a bit beyond that, which means it would need a small change order so we can resource it properly and not affect the timeline on [existing deliverable].
I’ll send over a quick quote today. Happy to jump on a call if it’s easier to talk through it. Let me know.
[Name]
Short, factual, no blame, clear next step. The tone does most of the work.
What this does for the relationship long-term
The agencies that handle scope well tend to keep clients longer. Not because they’re cheaper or more accommodating — but because clients trust them. They know what they’re getting. They know how changes work. They don’t have to wonder whether the agency is quietly resentful or burning out their team on work they’re not being paid for.
We’ve found that the clients who’ve been with us longest are the ones where the scope conversation happened early, was handled calmly, and became a normal part of how we work together. That’s the outcome worth aiming for.
If you’re thinking about how to structure your client work more deliberately — whether that’s refining your briefing process, building a retainer model that handles flex naturally, or just figuring out the right tone for a difficult conversation — we’re happy to talk. Reach out and we’ll figure it out together.