Change order template for contractors and agencies
Short answer: A change order needs five fields: a reference to the original contract or statement of work it's modifying, a description of exactly what's changing, the price adjustment (increase or decrease), any timeline impact, and signatures from both parties before the new work starts. The whole point of a change order is converting an informal "sure, we can add that" into something written and agreed before the work happens, not after.
A client or project is asking for something beyond what was originally scoped, and you need a fast, simple way to get the extra work agreed and priced in writing before you start it.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
This page may contain affiliate links from which Blur Studio earns commissions.
If you're searching for a change order template, you're probably mid-project and someone just asked for something that wasn't in the original scope, an extra room added to a renovation, a new feature added to a software build, an additional round of revisions on a design project. The instinct is to just say yes and figure out the paperwork later. Don't, that's exactly how unpaid scope creep happens.
Fields a change order needs
- Reference to the original contract. Name and date of the contract, statement of work, or purchase order this change order is modifying, so there's no ambiguity about which agreement it's attached to.
- Description of the change. Specific enough to actually define the new work, "add a half-bath to the first floor per attached revised plan" not "additional work as discussed."
- Price adjustment. The dollar amount being added or subtracted from the original contract price, stated as both a change amount and a new total, so both sides can see the running total at a glance.
- Timeline impact. Whether the change pushes back the completion date, and by how much, stated explicitly rather than left as an assumption. A change that adds work almost always affects timeline, say so in writing rather than leaving it to come up as a surprise later.
- Signatures and date. Both parties sign before the new work starts, with the date the change order itself takes effect.
Approval and signature flow
The flow that actually prevents scope creep is simple: the change is requested, you write it up as a short change order with price and timeline impact, and no new work starts until it's signed. The failure mode almost every contractor and agency has lived through is doing the work first on a verbal yes and writing up the change order afterward, at which point you've lost your leverage, the client has already received the benefit and has less incentive to agree to a price that now feels retroactive rather than negotiated upfront. Get in the habit of pausing the actual work, even for an hour, to get the signature first, especially once a project has already had one or two changes go through informally, since that's usually when a third one starts to feel like it doesn't need the same process. How to get change orders signed before the extra work starts goes through the signing step in detail.
When the change request itself is verbal
Most change requests start as a casual conversation, a phone call, a comment on a job site, a Slack message, not a formal written request. That's fine, the informality of the request isn't the problem, doing the work based on that informal request without converting it into a signed change order first is. Get in the habit of responding to any verbal "can you also do X" with a short, friendly version of "sure, let me send you a quick change order to confirm the price and we'll get started," which takes thirty seconds to say and sets the expectation without making the client feel like you're creating friction over a reasonable request. For agency projects, handling scope changes without fights gives wording for these requests.
Tracking changes
Keep a running log, even a simple spreadsheet, listing every change order against a project: date, description, price change, new running total, and link to the signed document. For any project with more than one or two changes, this running total matters more than any individual change order, because it's what tells you and the client where the project actually stands against the original budget, and it's the first thing either side will want to see if there's ever a dispute about the final invoice. A project that's had five small, individually reasonable change orders can end up 40% over the original price without anyone noticing in the moment, the log is what catches that before the final invoice becomes an unpleasant surprise.
A note for construction and trades specifically
Change orders carry extra weight in construction, since many state contractor licensing laws and lien rights depend on work being properly documented and authorized in writing, not just on getting paid eventually. If a dispute ever escalates to a mechanic's lien or a licensing board complaint, a clean paper trail of signed change orders is often what determines whether disputed extra work gets paid at all. If you're doing regular change order work on licensed construction projects, it's worth a quick conversation with your state contractor's board or a construction attorney about whether your state has specific written-notice requirements for change orders beyond what general contract law would require, since a few states do.
Getting it signed fast
Because change orders need to happen quickly, mid-project, without slowing work down more than necessary, QuickSigner, an electronic signature tool for sending a document out to be signed online from any device, fits well here specifically, a client can approve a change order from their phone in the time it takes to read it rather than waiting for someone to be back at a desk with a printer. If change orders are a regular part of how you run projects, the Business plan at $5 a month per user ($48 annually) supports a reusable change order template with the fixed fields already in place, so only the description, price and timeline need filling in each time, confirm current pricing directly before committing. An electronically signed change order carries the same legal weight as a signed paper one under the US ESIGN Act and state UETA laws. If you work on site, the on-site change order form is built for that.
A filled-in change order
For a kitchen remodel: "Change Order #2, referencing Contract dated September 3, 2026. Description: Client requests upgrade from laminate to quartz countertops (per attached revised material selection), and addition of under-cabinet lighting not included in original scope. Original contract price: $18,400. Price adjustment: +$2,850 (quartz material and installation upgrade: +$2,100; under-cabinet lighting, materials and labor: +$750). New contract total: $21,250. Timeline impact: completion date moves from November 15 to November 22 due to quartz fabrication lead time. Approved by: [Client signature], [Contractor signature], dated October 12, 2026." Notice the running total is restated, not just the change amount, so anyone reading this change order later, including the client's own spouse or business partner who wasn't in the original conversation, can see exactly where the project stands against the original price without needing to find and add up every prior change order first.
How I'd approach this
I treat "can we just add this quickly" as the single highest-risk sentence in any project, because it's almost always said with good intentions and almost always costs someone money if it's not written down in the moment. My rule: no new work starts until the change order is signed, full stop, even if it's a fifteen-minute addition that feels too small to formalize. The discipline isn't really about any one small change, it's about keeping the habit intact so that when a genuinely large, expensive change request comes in later, asking for a signed change order still feels normal rather than like a sudden escalation that catches the client off guard. Clients, in my experience, respect this more than they resist it once they see it applied consistently from the first small change onward, what actually damages a relationship isn't asking for a signature, it's a final invoice that doesn't match what anyone remembers agreeing to.
Questions people ask
Is a change order legally necessary, or just good practice?
It's not always legally required depending on your original contract's terms, but it's the document that actually protects you if there's a dispute about extra work or its price. Without one, you're relying on proving a verbal agreement happened, which is much harder.
What if the client refuses to sign a change order but wants the work done anyway?
That's the moment to hold firm, doing the work without a signed change order means you're relying entirely on good faith for payment of anything beyond the original scope. A client who won't put a reasonable change in writing is giving you real information about how the rest of the project is likely to go.
Can a change order reduce the price, not just increase it?
Yes, if the client removes scope rather than adding it, the same document structure applies with a negative price adjustment. Document it the same way, in writing, before the reduced scope takes effect.
How many change orders is too many on one project?
There's no fixed number, but a pattern of frequent changes is worth a direct conversation about whether the original scope was actually well-defined to begin with. A SOW with a strong assumptions and exclusions section tends to generate fewer change orders than a vague one.
Do change orders need to go through the same approval chain as the original contract?
Generally yes, whoever had authority to sign the original contract should sign the change order, since it's legally modifying that same agreement. Letting a junior staff member on either side approve changes informally is a common source of later disputes about whether the change was actually authorized.
Should the change order restate the whole original contract?
No, it should reference the original contract by name and date and describe only what's changing. Restating the whole contract each time is unnecessary and makes it harder to see at a glance what actually changed.
Should a change order show the new total price, not just the adjustment amount?
Yes, stating both the change amount and the new running total makes the document useful on its own later, without needing to pull the original contract and every prior change order just to see where the project currently stands.