The Client Is Asking for What? 3 Proven Ways to Handle Out of Scope Requests

True story. We were hired as a temporary Head of Marketing for a founder-led company. The scope was already ambitious: build the marketing plan, manage the budget, evaluate and hire the team, interview vendors, run media buying, own performance reporting, and contribute at the executive table. A big engagement. And the work went well.

Too well, actually.

Because we’d built a strong relationship with the founder, she started pulling us into things that touched marketing but had no business being in our SOW. Sales meetings. Investor decks. Board presentations. Random strategic projects that were really busywork for someone at our level. It was flattering. It was also eating our margin alive, and none of it was what we were paid to do.

That’s what out of scope requests look like in practice. Not a dramatic confrontation. Not a client trying to take advantage. Just a relationship that got warm enough that the edges of the engagement quietly disappeared.

Here’s what I’ve learned after 20 years and 400+ client engagements: managing client expectations isn’t a soft skill. It’s a system. And if you don’t have a system, you’re going to lose.

What Is an Out of Scope Request?

An out of scope request is any task, deliverable, or time commitment a client asks for that falls outside what was agreed to in the statement of work (SOW). It doesn’t have to be large. In fact, the most damaging out of scope requests are small ones that accumulate unnoticed over time.

The dangerous version isn’t the big ask. A single large request is easy to handle. It’s loud enough that everyone notices. The version that kills you is the slow drift. A small request here. A “quick favor” there. A Slack message that says “just one more thing.” Your team doesn’t even realize they’ve crossed a line. They were just trying to be helpful. By the time someone notices, you’ve quietly absorbed 20 hours a month of unbilled work and the margin on that account is gone.

Scope creep almost never walks through the front door. It sneaks in through the side, and it gets in because your team is trying to be nice.

Why Do Clients Keep Asking for More?

Clients who keep asking for more are usually not being unreasonable. They simply don’t have a clear internal model of what was agreed to versus what’s adjacent to it. There are three common triggers.

The first is the post-signing energy spike. The moment the SOW is signed, the client is energized and starts throwing everything at the engagement. If your onboarding process doesn’t establish clear boundaries immediately, you’ve handed them permission to keep going.

The second is misaligned documentation. If your verbal conversations during the sales process, your written proposal, and the final SOW say different things, you’ve built scope creep into the foundation of the relationship before you’ve done a single day of work. If you let the first few out of scope requests slide because you want to be “easy to work with,” you’ve just taught the client that the SOW is a suggestion. And once that’s the lesson, it’s very hard to unteach.

The third is new stakeholders entering mid-engagement. A VP gets added to the account on the client side, they have their own agenda, and suddenly requests are coming in that have nothing to do with what was negotiated. Nobody is being malicious. The new stakeholder just doesn’t know where the line is. Nobody told them. How you handle their first two requests sets the tone for everything that follows. The right move is to escalate peer-to-peer. The account lead raises it with the person who signed the contract, not by messaging the new VP about change orders. Managing client expectations when a new stakeholder enters means resetting the conversation at the right level, with the right person.

How Do You Tell a Client Something Is Out of Scope?

The most effective way to handle out of scope requests is to use what I call the Acknowledge-Name-Option framework: acknowledge the request, name the scope reality, and offer options. Never lead with no.

It sounds like this: “Happy to take a look at this. Want to flag that it’s outside our current scope, so here’s how I’d think about it. Option one, we slot it in and pause [specific in-scope item] to make room. Option two, we add it to the scope and I’ll send over an updated SOW. Option three, I can point you to someone who can handle this faster and cheaper than we can. What works best for you?”

Three things are doing work in that response. You’re not saying no. You’re offering solutions. You’re making the trade-off visible, which moves it from “the agency is being difficult” to “we have to make a decision together.” And you’re modeling transparency, which builds trust over time.

That’s exactly how I handled the founder situation I mentioned. Because we’d built real rapport, weekly 1:1s and direct access, I could raise it without making it a crisis. What I said was essentially: “We love being this embedded with you, and we’re happy to take on this extra work. But it’s outside our current scope, which means we either need to pause something in-scope to make room, or we expand the SOW. We’re both running businesses here, and I know you’d want us protecting our margins so we can keep doing our best work for you.”

She chose a combination. Some items got added formally to the scope. She stopped asking us to do things her own team members could handle. The relationship got stronger, not weaker.

What Are the Biggest Mistakes Agencies Make With Out of Scope Work?

There are two opposite mistakes, and they’re both expensive.

The first is a lack of transparency, both internally and externally. If your team doesn’t know what’s in scope, they can’t recognize what isn’t. Scope awareness is a system, not an instinct. Everyone working the account needs to know exactly what’s been agreed to, and needs to be empowered to push back politely when a request crosses the line.

The second mistake is pushing back on everything. I’ve seen agencies get so rigid about how they manage client expectations that they become genuinely difficult to work with. The client asks for a small tweak and gets a 300-word email about change orders. That’s how you kill goodwill. If something genuinely takes ten minutes and builds trust, do it. You’re banking relationship capital you’ll need later.

But the failure mode that actually destroys accounts is the middle ground: doing all the out of scope work without ever raising it. Your team starts to quietly resent the client. Calls get shorter. Replies get cooler. The proactive suggestions stop. The vibe turns, and the client feels it even if they can’t articulate what changed.

How Do You Prevent Out of Scope Requests Before They Start?

Managing client expectations effectively starts in discovery, before the engagement kicks off. If you’ve done discovery well, you already know what this client is going to ask for in month three. Those items need to be anticipated and explicitly named in the proposal, either as included or as expressly out of scope.

Then three things have to line up: the verbal conversations during the sales process, the written proposal, and the final SOW. They all need to say the same thing. That alignment is the foundation of managing client expectations before the work even begins.

During onboarding, get the full working team from both sides in a kickoff and walk through exactly what’s in scope. Not a deck on the wall that nobody reads, an actual working conversation where people can ask “does this include X?” and you answer it live. That’s where you actually manage client expectations in a way that sticks. A one-page scope summary from that session also protects you when new stakeholders enter the picture six weeks in.

Once the engagement is underway, two operational tools protect you. First, an internal Slack channel or whatever your team uses, where anyone can surface “I think this request is out of scope, thoughts?” before any work gets done. Most scope creep happens below the account lead, between the client’s project manager and the agency’s account coordinator. Your team needs a place to flag it before it becomes invisible.

Second, track individual team member time on every task for every client and review it monthly. Most agencies only use time tracking for margin math at month-end, and they’re leaving the real value on the table. The bigger use is diagnostic. If a team member’s hours on a client jump from 8 to 14 in a month, something is happening that nobody surfaced verbally. The time sheet is the only artifact telling you about it. The U.S. Chamber of Commerce notes that consistent documentation and communication cadence are among the most effective ways to manage B2B client expectations over time. In my experience, time tracking used diagnostically is the single highest-leverage tool for catching out of scope work early, and most agencies don’t run it this way.

Bottom Line

Managing client expectations well isn’t about being rigid. It’s about being honest. Be honest early, often, and in a way that makes clients feel like partners rather than adversaries.

The agencies and consultants who handle this well don’t have fewer scope conversations. They have more of them, earlier, with less at stake each time. The conversation becomes a normal part of the engagement instead of a crisis moment.

Get your system right before the engagement starts. Run the kickoff with intention. Use the Acknowledge-Name-Option framework when out of scope requests come in. Track the hours diagnostically. Most clients who keep asking for more aren’t trying to take advantage of you. They just don’t know where the lines are because nobody drew them clearly enough. That’s fixable. And it’s entirely within your control. If you’re still building out the systems side of your business, this small business planning guide covers the operational foundations that make client work run cleaner.

Frequently Asked Questions

What is the difference between scope creep and an out of scope request?

An out of scope request is a single ask that falls outside the agreed SOW. Scope creep is the cumulative effect of multiple out of scope requests that go unaddressed over time. One is an event; the other is a pattern that builds until it damages the engagement.

How do you handle a client who keeps adding to the project without paying?

Use the Acknowledge-Name-Option framework: acknowledge the request, name the scope reality, and offer three options — absorb it by pausing something in-scope, add it to the SOW with revised pricing, or refer it to someone else. Never do the work silently. Each time you absorb an out of scope request without raising it, you’re teaching the client that the SOW has no teeth.

Should you ever do out of scope work for free?

Yes, but only occasionally and intentionally. If something takes ten minutes and builds genuine trust, do it. The key word is intentional. You should choose to do it, not feel obligated to do it. The moment it feels like you have no choice, the dynamic has already shifted in the wrong direction.

How do you manage client expectations at the start of an engagement?

Three things have to align: the verbal conversations during the sales process, the written proposal, and the final SOW. They all need to say the same thing. Then hold a kickoff with the full working team from both sides. Managing client expectations at this stage means walking through scope explicitly, not as a presentation but as a live conversation where people can ask questions and get real answers.

What is the best way to document scope in a client engagement?

Beyond the SOW, create a one-page scope summary from the kickoff that can be handed to any new stakeholder who joins the account later. Track time by task and by team member from day one. And maintain an internal channel where your team can flag potential out of scope requests before they do the work. Documentation isn’t bureaucracy. It’s the system that keeps the relationship clean.