Back to red flag patterns

Client phrase pattern

Client Asking for Extra Work Mid-Project — What to Do

This is scope creep. The question is how you handle it.

Important: this phrase does not prove a client is bad. It is a signal to pause before replying, clarify the missing details, and avoid committing inside an unclear project.

The situation

The project is underway. The client sends a message asking for something that wasn't in the original brief. It might be framed as a small addition, a quick change, or something they "just thought of."

This is scope creep. The question is how you handle it.

Why most freelancers absorb it

  • The request seems small
  • They don't want to seem difficult
  • They're not sure if it's actually outside scope
  • They don't know how to say no without damaging the relationship
  • They'll "just do it this once" and set a boundary next time

Next time comes. The boundary doesn't.

Why absorbing it is a mistake

It teaches the client that additions are free.

Every time you absorb an extra request without comment, you reinforce that asking for more has no cost. The client isn't being malicious — they're responding to the incentive you've created.

It compounds.

One absorbed addition becomes two. Two becomes the norm. By the end of the project you've done 30% more work than you quoted, at the same price, with no record of why.

It creates resentment that damages the relationship anyway.

The thing freelancers are trying to avoid — damaging the relationship — happens anyway. Just slower, and with more of your time spent.

How to respond

You don't need to refuse. You need to name it and price it.

The formula:

  1. Acknowledge the request
  2. Name it as outside the original scope
  3. Offer a path forward — a quote, a timeline, or a call

Example:

"Thanks for flagging this. This one's outside the original scope, so I'll put together a quick estimate for the additional work and get that to you shortly. Should have it within [timeframe]."

No drama. No apology. No "unfortunately." Just the next step.

When you're not sure if it's in scope

Check the original brief, the quote you sent, or the email thread where the project was agreed. If the request isn't described there — even loosely — it's outside scope.

If you're genuinely unsure, say so:

"Let me check against the original brief to confirm whether this is included. I'll come back to you shortly."

That buys you time to check without committing either way.

Get the response written for you

Writing this message in the moment is harder than it sounds. You're trying to be firm without being aggressive, clear without being cold.

The Scope Creep Email Generator produces a complete, ready-to-send response based on your situation — firm, warm, or direct. Describe the original scope and what's being requested, and get the email in seconds.

Generate your scope creep response →

Before the project starts

Clients who ask for extra work mid-project almost always signal it in the first inquiry — vague deliverables, "we'll figure it out as we go," lists that keep growing. Paste the original inquiry into FreelancerGuard and see what was there from the start.

Scan a client message →

Scan the full client message

This phrase matters more when it combines with urgency, vague deliverables, missing budget, or pressure to start. Paste the full message to see the complete risk pattern.

Check a client message free

Related patterns