· 6 min read
Freelance Business

How to Deal With Scope Creep Mid-Project: Scripts and Approaches

When scope creep is already happening, you have three options: absorb it, charge for it, or renegotiate. Here's how to have that conversation without losing…

How to Deal With Scope Creep Mid-Project: Scripts and Approaches

You’ve already started the project, the client is asking for more than what was agreed, and you’re trying to figure out how to handle it without making things awkward. You have more options than you think — and the conversation is less difficult than most freelancers expect when they finally have it.

Prevention is the right time to address scope creep. But prevention requires foresight, and scope additions don’t always announce themselves clearly. Sometimes you’re three weeks into a project before you realize that the small additions have accumulated into a problem. Here’s how to handle it at that stage.

Assess what’s actually happened

Before doing anything, take stock of what’s been added. Make a list of the work you’ve done that isn’t in the original agreement. Estimate the hours. Calculate what it would have cost if it had been scoped and priced normally.

This gives you two things: a clear sense of the financial impact, and a concrete basis for any conversation you need to have. “I’ve absorbed about eight hours of work outside the original scope” is a much more actionable statement than “this project is running over.”

It also helps you decide which of the three responses is right for this situation.

Option 1: Absorb it (once, explicitly)

For small additions — under an hour of work — absorbing as a goodwill gesture is sometimes the right call. Long-term client relationships often involve occasional small favors, and fighting over every minor addition can cost more in relationship damage than the addition itself.

But if you’re going to absorb something, say so explicitly. “I’ll include that at no extra charge this time” communicates two things: that you noticed it was outside scope, and that this isn’t the standard process. That small acknowledgment prevents the client from assuming all out-of-scope additions are free.

What you don’t want to do is absorb additions silently. Silent absorption signals to the client that out-of-scope requests are always free, and the requests will continue.

Option 2: Issue a change order

For anything substantial — additions that take more than an hour, anything that meaningfully changes the deliverable, or any pattern of smaller additions — a change order is the professional response.

The process:

  1. Acknowledge the request without immediately agreeing to it: “I’ll take a look at what that would involve.”
  2. Estimate the additional time and cost.
  3. Send a written change order: description of the additional work, the price, and the timeline adjustment.
  4. Begin the work only after the client approves it in writing.

The conversation script when raising this: “That’s a bit outside what we scoped originally — let me estimate it and send over a quick change order so we can move forward cleanly. I’ll have something to you by tomorrow.”

Most clients respond to this reasonably. They may not have realized the request was outside scope, or they may have been testing to see if you’d notice. Either way, a calm, matter-of-fact response that routes through a process is less confrontational than either absorbing it resentfully or refusing abruptly.

A change order doesn’t have to be a formal document. An email that says “Here’s what the additional work involves, the estimated cost is $X, and I’ll start once you confirm” is a valid change order.

Option 3: Renegotiate the project

If the scope has changed substantially — the additions amount to a significant portion of the original project, or the direction has shifted enough that the original quote no longer makes sense — renegotiation is the appropriate response.

This is a harder conversation, but it’s also a reasonable one. “I want to flag something before we go further — the project has grown significantly from the original scope. At this point I think we should revisit the agreement to make sure we’re both set up well for the rest of the engagement.”

What this looks like in practice: you document the original scope, document what’s been added, and propose a revised agreement that covers the full current scope. You’re not blaming the client for the growth — you’re acknowledging that the project evolved and that the original agreement no longer reflects reality.

Handling pushback

Some clients will push back on a change order. Common objections and how to respond:

“I thought this was included.” “I understand why you might have thought that — let me show you the original scope we agreed on. [Reference the proposal or contract.] This addition isn’t listed there, which is why I’m routing it as a change order.”

“It’s just a small thing.” “I hear you — it may seem small, but it actually takes [X hours] to do properly. I want to do it right, which is why I want to handle it cleanly.” If it genuinely is small, consider absorbing it once while naming that you’re doing so.

“You should have told me this sooner.” This is a fair point if scope additions have been accumulating and you’ve been absorbing them silently. The honest answer is: “You’re right — I should have flagged this earlier. Going forward I’ll address these as they come up so there are no surprises.”

Preventing the next one

Mid-project is also the right time to clarify the process going forward. You don’t have to do this as a formal statement — it can be brief: “For anything that comes up outside the original scope, I’ll flag it and send over a quick estimate before we proceed. That way there are no surprises on either side.”

This resets the process without requiring a lengthy renegotiation and positions every future addition as something that goes through a clear channel. Many clients are relieved to have an explicit process rather than navigating an informal one.

Using a proposal and invoicing tool that preserves the original itemized scope — like Waco3 — makes mid-project conversations easier because you can reference the agreed deliverables without having to dig through email chains. The original record is always available, which removes a common source of friction.

Scope creep conversations are uncomfortable mainly because freelancers delay them. The earlier you address an out-of-scope request, the easier the conversation is and the less financial damage is done.

Ready to send stronger proposals?

Build, send, and track proposals in one place so follow-up is easier.

Start your free trial →