Scope creep is unpaid work. Here is how to bill for it

Here is how to bill for scope creep: log each out-of-scope request and its hours on the day it happens, then turn that dated record into a change order the client approves, priced hourly, as a fixed add-on, or as a next phase. Without the record, extra work is a favour. With it, it is an invoice line.

What is scope creep, and why does it go unpaid?

Scope creep is work added to a project without anyone adjusting the price, the deadline or the approval that goes with it. The 2008 edition of PMI’s PMBOK Guide described it much the same way: features added without dealing with the effect on time, cost and resources, or without the customer’s approval, as cited in a PMI conference paper on its causes.

The same paper makes the point that matters for billing: “If an expansion of scope is approved, then it is not scope creep.” Change is not the problem. Unpriced change is. So the fix is not refusing extra work, it is converting it into approved scope with a price on it.

How it goes unpaid depends on how you bill. On a fixed fee, every extra hour comes straight out of your effective rate. On hourly work the hours get billed, but they land on an invoice bigger than the estimate the client budgeted against, which is exactly how a client comes to question your invoice. On a retainer, extra requests eat the hours meant for the planned work. Same cause every time: the extra work was never named as extra.

What are the signs of scope creep?

Scope creep rarely announces itself. It arrives in language that makes each request sound too small to raise:

• “While you’re in there”, “quick”, “just”. The size estimate is coming from the person who is not doing the work.
• A new name in the feedback thread. New stakeholders bring requests the brief never covered.
• Rounds that never close. Feedback arrives in drips, so round two never ends and round three never officially starts.
• The deliverable changes shape. “Can we get a version for social?” “Could it work in Spanish?” Each is a new deliverable.
• Your hours rise faster than your list shrinks. The one signal you can check with numbers. If most of the estimated hours are gone and fewer than half the deliverables are done, something was added.

One more, and it is uncomfortable: scope you add yourself. The PMI paper calls it gold plating, building things nobody asked for. It is scope creep too, and the one kind you cannot bill.

How do you prove scope creep happened?

Scope creep is invisible until it is measured. Each request is small, and only the total hurts. The client never sees the total, because the requests went out one at a time over weeks. Neither do you: memory rounds small things down to nothing.

So the conversation, when it comes, is one feeling against another, and the one asking for money tends to concede. A dated record changes that. “Seven requests since 3 March, 8.75 hours, none of them in the signed scope” is not an opinion. The client cannot argue with dates. They can only decide what to do about them, and that decision is a change order.

Keep one log per client:

Date	Request, in their words	Who asked, where	Hours	Status
3 Mar	”Can we get a blog template while you’re in there?”	Marketing lead, Slack	4.0	Flagged, approved hourly
7 Mar	Third round of homepage changes (two agreed)	Founder, email	2.5	Flagged, awaiting reply
12 Mar	Newsletter sign-up form	Marketing lead, call	1.5	Not flagged
14 to 21 Mar	Four small copy swaps on approved pages	Various, Slack	0.75	Courtesy, no charge

No single row is worth a fight. Together they are more than a working day the fee never covered. Copy each request in verbatim: “can you look at” and “can you build” are different requests, and a paraphrase drifts towards the bigger one.

The hours column is where most people fall down, because nobody stops mid-task to switch a timer. Give each client a separate project, such as “Client name: changes”, with its own billable flag. Then either log time to it as you go, or use a billable hours tracker that records in the background, so you only sort the blocks afterwards. Folded into the main project, the extra hours vanish.

What should an out-of-scope work clause say?

The clause does the arguing so you do not have to: you are pointing at something you both signed, not asserting a principle. It needs four things: scope defined as a list, a definition of a revision round, a rule for approving extra work, and a price for it. Put the deliverables in a schedule so the clause can point at them.

Scope and changes. The work covered by this agreement is the deliverables listed in Schedule A, including [two] rounds of revisions on each. A round of revisions is one consolidated set of written feedback on a delivered draft. Anything else is additional work, including new deliverables, further rounds of revisions, and changes to work you have already approved.

Before starting additional work, I will tell you in writing that the request is outside the agreed scope and give you an hourly estimate or a fixed price, with any effect on the timeline. Additional work starts once you approve it in writing, and a reply to my email is enough. It is billed at [rate] per hour unless we agree a fixed price, and invoiced with the next regular invoice.

Requests under [15] minutes each are included at no charge, up to [one hour] a month. I keep a dated log of all additional requests and the time spent on them, and share it with each invoice. Where additional work affects an agreed deadline, the deadline moves accordingly.

The log sentence is the one most templates leave out. It tells the client, long before any dispute, that the record exists.

In New York City, a written scope is often a legal requirement, not just good practice. The Freelance Isn’t Free Act requires a written contract for work worth $800 or more, including agreements with one client that add up to $800 in any 120-day period, and the contract must spell out the work. The city’s model freelance agreement tells freelancers to factor revisions into the price, and offers optional terms limiting both parties to the listed items and requiring changes in writing. On a large contract, have a lawyer read your version.

How do you say no to scope creep without losing the client?

You rarely need to say no. What you must avoid is saying yes and starting in the same breath. Acknowledge the request, say it sits outside the agreed scope, and promise a price by a specific time. On a call: “Happy to do that. It’s outside what we scoped, so I’ll send a quick quote this afternoon.” No lecture, no clause number, no apology.

Then give one of three answers:

1. Yes, and here is what it costs. For anything that is clearly new work.
2. Yes, instead of something else. Swap it for an unstarted deliverable of similar size. No charge, but it still goes in writing, because the scope list changed.
3. Yes, in the next phase. For anything large, or anything that threatens the deadline. The project closes on time and the request opens the next paid piece of work.

Three yeses instead of one no keeps it a scheduling conversation rather than a standoff. A client who refuses all three is telling you something about the relationship.

How do you write a change order as a freelancer?

A freelance change order needs no form. It is an email that names the request, says why it is outside scope, gives a price and a timeline effect, and asks for a written yes. Send it within a day, before you start.

Subject: Change request: [short name for the request]

Hi [name],

Thanks for sending over [the request] on [date]. It isn’t part of the deliverables we agreed in [the proposal / Schedule A], so I’m treating it as a change rather than folding it in.

In plain terms, it involves [one or two lines on what the work actually is]. Two ways to handle it:

1. Hourly: I estimate [X to Y] hours at [rate], and I won’t go past [Y] without checking with you.
2. Fixed: [amount] for the work as described.

Either way it adds about [n] working days, so [deliverable] moves from [date] to [date]. If it isn’t urgent, we can hold it for a second phase.

Reply with 1, 2 or “later” and I’ll get going. I haven’t started on it yet.

[Your name]

The last line matters: a choice that is free to decline is far easier to accept.

How much should you charge for scope creep?

At least your normal rate, and never less because the request is small. Small requests carry the most overhead per minute: the context switch, the re-read of the brief, the check that nothing else broke. The model should follow how well you can estimate the work.

Model	Use it when	Watch out for
Hourly, with a cap	The work is small, vague or exploratory	No cap, and the change order becomes the next surprise invoice
Fixed add-on	The deliverable is well defined and familiar	Price it like the original: honest hours plus the same margin for risk
Next phase	The request is large, changes direction, or threatens the deadline	Get the current phase signed off first so the two do not blur

Say you bill $85 an hour and the request is a landing page variant you estimate at five to seven hours. Hourly with a cap is $85 an hour, not to exceed seven hours. A fixed add-on priced from the top of that range is 7 × $85 = $595. The client who wants certainty takes the fixed price; the one who expects it to be quick takes hourly. A premium for work that jumps the queue is fine if the clause says so up front. Introduced for the first time in a change order, it reads as opportunism.

How do you charge for extra revisions?

Extra revisions are the easiest scope creep to stop, because the contract can count them. Three rules:

1. A round is one consolidated set of feedback, not every message. If feedback drips in, set a collection date: “I’ll gather everything until Thursday and treat it as round two.”
2. A revision is not a change. A revision refines the approved direction. A new direction, or reopening signed-off work, gets a change order however many rounds are left.
3. Say the count out loud. “Here’s round two of two” gives notice before anything becomes billable. Nobody feels ambushed by a charge for round three when every email has been counting.

Bill round three hourly, with a cap, using the change order email.

Should small favours be free?

Sometimes. A five-minute fix for a good client is a reasonable gift. The mistake is giving it invisibly: an invisible favour is experienced as part of the fee, and it prices the next one at zero.

So give favours on purpose and in the open. Set the allowance in the clause, so the client knows the limit before reaching it. Log every favour in the same record as the billable changes. Then put it on the invoice as a no-charge line: “Four small copy changes, 45 minutes, no charge.” Once it is used up, the next small request is additional work, and nobody is surprised.

Can you bill for scope creep after the work is done?

Sometimes. It turns on two questions: does your contract cover additional work, and did you say so at the time?

The contract covers it and you flagged it. Bill it. That is ordinary billing, not retroactive billing, and the log goes with the invoice.

The contract covers it but you never flagged it. You are probably entitled to it on paper, but a surprise charge costs more goodwill than it recovers. Send the log before the invoice, not with it. Bill the items that were clearly new work, consider waiving the grey ones, and say which you did.

No clause, and you never flagged it. You cannot fairly bill it on your own say-so. What you can do is make it visible and reset:

Since [date] I’ve logged [n] requests outside the original scope, [x] hours in total. The log is attached. I’ve absorbed these, and they appear on this invoice at no charge. From here on I’ll quote changes like these before starting, so you can decide on each one.

That shows the client the real size of the project, turns a silent loss into a visible concession, and sets the rule from here on. If the total is large you can ask about a partial payment, and accept a no gracefully.

Two things not to do. Do not recover the hours by padding later invoices: that turns a scoping mistake into a dishonest one. And do not bill hours you cannot evidence. With no record at all, rebuild one from what your tools kept, as in how to reconstruct a week you forgot to track, and round in the client’s favour.

What to do before the next request arrives

Scope creep is billed or lost long before the invoice. Four things, in order:

1. Put the clause in your next contract, with the deliverables in a schedule and the revision rounds counted. For existing clients, add it at the next renewal.
2. Create an out-of-scope project for every active client today, so extra hours have somewhere to go that is not the main project.
3. Answer the next request in writing within a day, using the change order email, and do not start until you have a yes.
4. Send the log with every invoice, even in months when every line says no charge.

If you want the hours column to fill itself in, Stunda records your working time in the background, lets you assign blocks to a client’s changes project with its own rate and billable flag, and turns selected entries into invoice lines. A spreadsheet with the columns above does the same job by hand. The habit matters more than the tool.