How to Invoice for Extra Work: A Freelancer's Guide to Change Orders

"Quick question." The two most expensive words in freelancing.

You're three weeks into a $4,500 website project. The client messages at 4:52 PM: *"Quick question — can the contact form also CC our sales inbox?"* You type "Sure, no problem," spend three hours wiring it up, and never mention money. The client never offers. Both of you walk away thinking it was a favor. One of you is wrong.

Now multiply that by the ten "quick questions" that arrive over the life of an average project — the extra revision round, the pricing page, the CMS walkthrough call. None of them in the quote. All of them done. None of them invoiced. That's how a $4,500 project quietly becomes a $4,500 project with 30 hours of unpaid work stapled to it.

This guide covers the three things nobody teaches you about billing for extras: when to invoice, what the invoice should look like, and the exact words to send it with — without sounding like you're nickel-and-diming a good client.

Why extra work always ends up free (until you make a rule)

Extra work doesn't get done for free because clients are cheap. It gets done for free because of three mechanics that have nothing to do with the client:

1. The baseline was never written down. If your original scope is "a website, $4,500," then technically *everything* is included. You can't bill against a document that doesn't exist.
2. The request is framed as a question, not a purchase. "Can you also…?" and "while you're at it…?" are framed as favors. Replying "sure" turns a billable change into a gift before you've had time to think.
3. The invoice comes too late. When you bill for the extra revision at the end of the project — mixed into a final invoice with no explanation — the client's brain reads it as a surprise fee. So you swallow it instead. The moment to bill was when the request was made, not four weeks later.

Sound familiar? I broke down exactly how this compounds in What Is Scope Creep?. The short version: it's never one big change, it's twenty small ones. The fix isn't being braver — it's having a mechanism that turns "quick question" into a documented, priced change before you touch the work.

What a change order is (steal this from construction)

Construction figured this out a century ago. When a building's plans change mid-project, the general contractor doesn't just "do it and see." They issue a change order: a written document that describes the change, the cost, and the impact on the schedule — signed by both parties *before* work begins.

Change orders exist because in construction, "while you're at it" can add $40,000 and three weeks to a build. Nobody moves a crane until the change order is signed.

Freelancers have the exact same problem with smaller numbers. Your "crane" is your skill, and your "three weeks" is three days of your life. Yet most freelancers run an entire project with no change-order mechanism at all — just a hope that the client remembers what was agreed.

A change order for freelance work is simply: a dated record of a scope change, with hours, rate, and amount, confirmed by the client before you start. It doesn't need to be formal. It needs to exist.

The 3 tests: should you invoice for this?

Not every message deserves an invoice. If you bill for a 30-second "hey, can we make the button green?" you'll sound exhausting. Here's the filter I use — bill anything that fails even one of these tests:

Test 1: Was it in the scope document? If your written scope says "revision rounds: 2 included," then revision round 3 is billable by definition. No negotiation needed — the document decided. If there's no document, the scope is whatever the client says it is, and you lose.

Test 2: Will it take more than 15 minutes? Fifteen minutes is the freebie line. A question you can answer while the coffee brews? Include it. Anything that eats a real work session — research, setup, a new deliverable — gets logged and priced.

Test 3: Does it change your estimate by more than 5%? On a 20-hour project, 5% is one hour. If an add-on pushes the project more than an hour over your estimate, it changes the economics of the job — and the client should see that in writing.

The genius of the 15-minute / 5% rule is that it's impersonal. You're not judging the client's request; you're applying a rule you made in advance. "This crosses my 15-minute threshold, so I log it" is a policy, not an accusation. If you want to check where a project stands against these tests in 30 seconds, the free Scope Creep Calculator shows the running total of every add-on against your original quote.

What a clean extra-work invoice looks like

The invoice itself is where most freelancers blow it. A single line that says "extra work — $400" invites the question *what extra work?* Instead, structure the invoice as agreed vs. added, so the client sees exactly what they bought, what they added, and what each addition cost:

Two details make this invoice feel fair instead of greedy:

• Every added line references a change order number (CO-01, CO-02). It tells the client the charge isn't a surprise — it's a recorded change they can look up.
• The included items are listed at $0. Showing "2 revision rounds — $0" makes the generosity visible, which makes the billable third round feel like a rule, not a rip-off.

If you haven't been tracking change orders, you can still reconstruct this — but you'll be doing archaeology. Reconstructing a month of Slack messages to figure out what was asked, when, and for how many hours is miserable, and clients dispute vague line items. That's why the logging happens at the moment of request, not at invoicing time.

The wording: how to send it without sounding greedy

The hardest part of charging for extra work is the sentence you say *before* you send the invoice. Here are three that work.

When the request arrives (before you do the work):

"Happy to do that. Quick heads-up: it's outside the original scope, so I'll log it as a change order — looks like about 3 hours at our agreed rate, so $300. You'll see it on the project page and the next invoice. Want me to go ahead?"

This accepts the work, prices it, and gives the client an off-ramp in one paragraph. Notice it asks almost nothing — "want me to go ahead?" invites approval, but the work is framed as the default. Most clients say yes. Some drop the request. Both outcomes are wins.

When the invoice goes out (mid-project):

"Heads-up: your invoice for this sprint is attached. It includes two change orders we logged together — the pricing page (CO-01) and the extra revision round (CO-02). Everything else matches the original quote. Happy to walk through either line."

The magic phrase is *"we logged together."* It converts a one-sided bill into a shared record. You're not announcing a fee; you're reporting on a process they participated in.

When the client pushes back:

"Totally fair to double-check. Those two lines came from the change orders we logged on [date] — here's the link to the project page, where you can see the original quote side by side with the additions. If anything looks off, tell me and we'll fix it."

Notice what this doesn't do: it doesn't argue, and it doesn't re-litigate whether the work was in scope. It points to a record. When your records are good, you never have to win an argument — you just open the document.

The bottom line

You can't invoice for work you never wrote down, and you can't invoice convincingly for work you logged at the end. The change order is a habit: when the request lands, log it, price it, and confirm it — before the work starts. A tool like ScopeGuard makes the whole loop one click — log the add-on, the client sees it, and the invoice builds itself from the change order numbers. And if you're wondering what the system costs before you commit, the honest math is on the pricing page.

Next time a client opens with "quick question," you'll know what to do. Answer the question — and then open the change order before you open your editor.

*Related: What Is Scope Creep? · The Change Order Template Freelancers Can Copy (Plus a Scope Change Log) · 6 Client Email Scripts That Stop Scope Creep*