The "that's extra" email: how to answer out-of-scope requests without losing the client

Here is an example message (invented, but you will probably recognise it):

"Love the new homepage! Could you also just put together a quick banner for our Instagram? Shouldn't take long."

It's friendly, it's small, and it isn't in the project. Most freelancers have a few ways to answer it. Saying yes and quietly doing it is one. Writing an awkward paragraph and deleting it three times is another.

This article gives you a better way. First you spend 30 seconds deciding what kind of request it is. Then you send the reply that fits that kind. At the end there's a filled-in one-page change request you can copy.

Why "sure, no problem" costs more than the time

Doing one small extra thing for free feels generous, and sometimes it's the right call. But if you say yes by default, three things happen:

This is a common problem, not a personal failing. Scope creep shows up as a recurring challenge in freelancer surveys such as freelancermap's. Upwork's community forum has thread after thread from freelancers whose clients keep adding work (example, another).

What you want isn't a firmer "no". You want a consistent, calm way to say "here's what that involves, and here are your options."

Triage in 30 seconds: which kind of request is it?

Before you write anything, put the request into one of four boxes. Each box has its own next step.

Request type How to spot it Default next step
Tiny favour Takes less time than your threshold (see below), creates no new deliverable, and is a one-off Fold it in. Say so in writing and log it
New deliverable A thing that isn't on your list of deliverables: a banner, an extra page, a second blog post Quote it, or park it for a later phase
Extra revision round Feedback arrives after the agreed rounds are used up Quote the extra round
Changed goal The project itself has shifted: a new audience, a new feature, "actually, we're thinking of rebranding" Pause and re-scope before doing more work

If you can't tell which box it goes in, open your scope document or proposal and find the line it relates to. If the original wording really was ambiguous, that's useful to know too. Clarify it now, and tighten the wording on your next project.

The "just do it" threshold

A rule of thumb that gets shared in freelance communities: if a request takes under about 15 minutes, just do it. (This summary of Reddit discussions describes it, so treat it as a community habit, not research.)

It's a reasonable starting point, but set your own number and add two conditions:

  1. Log it anyway. Write down every fold-in, even the five-minute ones. Three "tiny" favours in a week are a pattern, and you'll want the list when you price the next project.
  2. Say it out loud. "Happy to include this one" tells the client it was extra without making it awkward.

The reply structure: five parts

Every out-of-scope reply can follow the same five steps. You don't need all of them at full length, but keep them in this order.

  1. Acknowledge. Respond to the idea, not just the cost. "Good idea" or "I can see why you'd want that" costs you nothing.
  2. Name the scope. Say plainly that it's outside what you agreed. Point to the agreement if you can.
  3. State the impact. Time, money, or both. Be specific.
  4. Give options. Usually three: swap it for something already planned, schedule it after the current milestone, or price it as a change.
  5. Ask for a decision. End with a question the client can answer in one line.

Notice what's missing: apologies, long justifications and policy quotes. You're giving information and choices, not defending yourself.

Three example replies

These are written to be adapted. Change the tone to sound like you, and fill in your own numbers. Not legal advice; adapt these to your contract and your client.

1. Tiny favour (fold it in, but say so)

Hi Sam,

Sure, I've added the updated phone number to the footer. That one was quick, so no charge.

Just so we're both tracking it: it's a small addition outside the original list, and I've noted it in the project log. Anything bigger I'll quote separately before starting, so there are no surprises.

Best, [Your name]

2. New deliverable (quote it or park it)

Hi Sam,

An Instagram banner to go with the launch is a good idea.

It isn't part of the current project, which covers the five website pages in our scope summary. I can do it in one of two ways:

  • Add it now: [PRICE], and it would push the site handover back by [DAYS] days.
  • Do it after launch: same price, starting the week of [DATE], so the site date doesn't move.

Which would you prefer? Once you confirm, I'll send a one-page change request to approve.

Best, [Your name]

3. Revision overflow (quote the extra round)

Hi Sam,

Thanks for the notes on the About page. Quick heads-up before I start: we've used the two revision rounds included in the project.

I'm happy to do a third round. It would be [PRICE] and take about [DAYS] working days. If it helps, send all remaining changes in one list and I'll treat them as a single round.

Shall I go ahead?

Best, [Your name]

For a changed goal, don't reply with a price straight away. Suggest a short call: "This changes what we're building, so I'd like to re-check the plan with you before I quote." Then rewrite the scope, not just the invoice.

The change request: one page, filled in

The email gets agreement in principle. The change request puts it in writing: what's changing, what it costs, and that the client said yes. It doesn't need to be long. Here are the fields, with a filled-in example. The project and names are invented.

Field Example
Request ID CR-02
Date 14 March
Requested by Sam Rivera, Marketing Lead, Northside Yoga (fictional)
What's being asked for One Instagram launch banner (1080 x 1350 px), matching the new site style
Related scope line Scope summary, "Deliverables": 5 website pages. Social graphics are listed under "Not included"
Type New deliverable
Option chosen Do it after launch
Cost [PRICE]
Time needed About [HOURS] hours
Effect on timeline None on site handover. Banner delivered the week of [DATE]
What the client provides Final launch date and offer wording, by [DATE]
Client decision Approved / Declined / Parked
Approved by and date "Approved" reply email from Sam, 15 March

A reply email saying "approved" is enough for most small changes. If your contract has its own formal change process, follow that instead. This page sits alongside your contract and doesn't replace it.

If you'd rather not build all this yourself: the Scope Guard & Client Onboarding Kit (coming soon) includes a blank change-request form, a change log for tracking every request (fold-ins included), and ten email scripts covering the situations above and more. Templates come as .docx and .md, with CSV trackers for Google Sheets or Notion.

When the client pushes back

Sometimes the reply is "I assumed that was included." That's normal, and it's usually honest. Some ways to handle it:

What not to do: threaten, quote contract clauses in your first reply, or go quiet and do the work while feeling resentful. All three cost more than one slightly awkward email.

Make it routine, not a confrontation

The easiest "that's extra" conversation is the one the client saw coming. If you explain how changes work at the start of the project, in one or two sentences at kickoff, then your reply later is just you following the process you both agreed. It doesn't come across as a sudden boundary.

Something like: "If anything new comes up, I'll tell you whether it fits the current scope. If it doesn't, I'll send a short note with the cost and timing so you can decide."

The client onboarding checklist shows where that line fits, along with a revision limit and a client-confirmed scope summary. And if you want to catch extra work before you quote, the AI hidden-dependency check walks through a prompt that flags gaps in a vague brief.

Want the full set?

This article covers the triage, three replies and one change request. The Scope Guard & Client Onboarding Kit turns it into a complete workflow from first brief to kickoff:

The templates come as .docx and .md, with CSV checklists for Google Sheets or Notion. The prompts work in any chat AI assistant. It isn't a contract and it isn't legal advice: it's the process around your contract.

The kit isn't on sale yet. See what's in the kit


Sources

← All posts