The Change Order Template Freelancers Can Copy (Plus a Scope Change Log)
Here's a test. Open your last completed project and answer three questions:
- How many times did the client ask for something that wasn't in the original quote?
- How many of those requests did you bill for?
- How many can you *prove* were requested, on which date, with which price attached?
If you're like most freelancers, the answer is "about ten," "one or two," and "maybe none." The requests live in a Slack thread you'd have to scroll for twenty minutes to find. The prices live in your head. And the one or two you did bill for were lumped into a final invoice as "additional work — $400," which is exactly the line item clients dispute.
The fix is a change order template and a scope change log — the two documents that turn "I think that was included" into "here's the record." Both are below, formatted so you can copy them into any tool today.
When do you actually need a change order?
Not every message deserves a change order. Billing for a 30-second "make the button green" makes you exhausting to work with. Use this threshold: anything over 15 minutes of work, or anything that moves your total estimate by more than 5%, gets a change order. Everything below that is a freebie that keeps the relationship pleasant.
The other trigger is *any* change to a deliverable you already agreed on — swapping the logo direction, adding a page, a third revision round when two were quoted. Even if it's small, a change to an agreed deliverable needs a paper trail, because that's the exact moment clients' memories get selective.
If you haven't seen the mechanics of when to invoice, the full breakdown is in How to Invoice for Extra Work: A Freelancer's Guide to Change Orders. This article is the part you can copy and paste.
The change order template
Copy this into a doc, a Notion page, or a spreadsheet row. One change order per project change.
| Field | What goes here |
|---|---|
| Change order # | CO-01, CO-02… unique per project |
| Project | Client + project name |
| Date | When the change was requested |
| Requested by | Who asked (the client, or you) |
| Original scope reference | Which line of the quote this change touches |
| Description of change | What's being added or altered — concrete, not vague |
| Reason for change | Why it's needed (client request / new info / direction change) |
| Impact on deliverables | What changes about the final output |
| Impact on timeline | Estimated delay, if any (e.g., +2 days) |
| Estimated hours | Your honest effort estimate |
| Hourly rate | The agreed rate for this project |
| Amount | Hours × rate |
| Client confirmation | Date + "approved" — email reply or signature |
| Status | Draft / sent / approved / rejected |
How to fill each field without overthinking it
Description of change is the field that saves you at invoicing time. Write it like a receipt, not a sentence: *"Add a pricing page (5 sections) to the existing site, using the About page template."* Not *"extra page work."* When the client disputes the invoice in three months, the description is what wins the argument.
Estimated hours is where most freelancers undercut themselves. Take your honest estimate and round up to the next half hour. A "20-minute tweak" that involves context-switching, re-opening files, and testing is rarely 20 minutes. Log 0.5–1 hour and you'll stop eating the switching cost.
Client confirmation is non-negotiable. A change order nobody agreed to is a diary entry, not a document. An email reply saying "approved" is enough — but get it before you start the work. The whole point is that the price is agreed *before* the hours are spent, not reconstructed after.
The scope change log template
A change order is one change, one document. The scope change log is the running record of *every* change across a project — the thing you can open in one click when the client says "I don't remember approving that."
| Date | Change order # | Request | Est. hours | Rate | Amount | Status | Client confirmed? |
|---|---|---|---|---|---|---|---|
| Mar 4 | CO-01 | Pricing page (5 sections) | 3 | $100 | $300 | Approved | Yes (Mar 4, email) |
| Mar 9 | CO-02 | Revision round 3 of 2 | 4 | $100 | $400 | Approved | Yes (Mar 9, email) |
| Mar 12 | CO-03 | CMS training call | 2 | $100 | $200 | Sent | Pending |
| Mar 14 | CO-04 | "Make logo animated" | 2 | $100 | $200 | Rejected | — |
Three rows are enough to see the pattern. This project has $1,100 of add-ons — 27% over the original quote — and two of them are already approved and billable. The log turns "I feel like this project is getting big" into an exact number you can show anyone.
Keep these columns tight. You want to be able to scan the log in five seconds, not read an essay. The Request column should be short enough to skim ("pricing page," "rev round 3"), because the full description lives in the change order document it references.
Why manual templates fail (the honest version)
The templates above work. I used versions of them for years, and they did their job — until they didn't. Three failure modes show up every time:
- The log lives in the wrong place. The change order is a Notion page, the log is a spreadsheet, the client confirmation is buried in email. At invoicing time you're juggling three tools and reconstructing dates from memory — which is exactly the archaeology clients smell.
- The client never sees it. You log diligently, but the client's only view of the project is your invoices. The first time they see CO-03 is when it's on the bill — and surprise fees, however documented, start arguments.
- The template only works if you fill it. Templates are passive. They sit there and wait for you to remember to use them at the exact moment a client message lands and your instinct is to just reply "sure." Discipline is a renewable resource that runs out on a Friday at 6 PM.
The third one is the real killer. A template you forget to fill is the same as no template at all.
The automated version
ScopeGuard takes the same two documents and makes them run themselves. When a client asks for something extra, you log it in the tool: the change order is created, the scope change log updates itself, and the amount is calculated from your rate — no spreadsheet formulas, no manual totals.
The part you can't do with a spreadsheet is what happens next: the client gets their own read-only view of the project, showing the original quote next to every logged change and the running total. They see CO-03 the day it's logged, not the day it's billed. When the add-on invoice goes out, it's the end of a process they've been watching for two weeks — not a surprise fee.
That visibility is why change orders stop being confrontations. You're not delivering news; you're reporting facts they already saw. You can try it free for one active project on the signup page, and the Scope Creep Calculator is free forever if you just want to see how deep a current project has drifted.
The bottom line
The change order template and the scope change log are the two documents that separate freelancers who bill for extras from freelancers who eat them. Copy them, use them, and keep them somewhere the client can see.
The template handles the paperwork. The habit handles the discipline. And the sooner both are in place, the sooner "one small thing" stops being a sentence you dread.
*Related: How to Invoice for Extra Work: A Freelancer's Guide to Change Orders · 6 Client Email Scripts That Stop Scope Creep · What Is Scope Creep?*