How to Write a Change Order That Actually Protects You

The customer catches you on the way to the truck and asks whether you could move the outlet while you're at it. It's ten minutes of work. You say sure. Six weeks later there's a disagreement about the final invoice, and it turns out you did eleven of those.

Change orders are not paperwork for large commercial jobs. They're the mechanism that keeps small favors from eating a residential contractor's margin, and the reason they get skipped is that at the moment they're needed, they feel disproportionate.

What a change order is

A written amendment to the original contract, agreed by both sides, that alters the scope, the price, the schedule, or some combination. It doesn't replace the contract, it modifies it, which is why it references the original rather than restating it.

The word "agreed" is doing the work. A change order you wrote and never got signed is a note to yourself. It documents your intention and proves nothing about theirs.

What has to be in it

The version that holds up is not long, but it can't skip any of these.

• A sequential number and a date, so the record has an order
• Reference to the original contract or quote it modifies
• A specific description of the change, in scope terms rather than intent terms
• Why it's happening, briefly: owner request, unforeseen condition, design change
• The cost impact, broken into material, labor, and markup rather than a lump sum
• The schedule impact in days, including zero if there is none
• The revised contract total after this change
• Signature and date lines for both parties

Two of those get skipped most often, and both matter more than they look.

The revised contract total prevents the slow drift where nobody is tracking the cumulative effect of nine separate changes. A customer who signs the ninth change order showing a new total has been told, in writing, where the job now stands. A customer who signed nine isolated amounts has a genuine claim to being surprised at the end.

The schedule impact matters because time gets forgotten while money gets remembered. A change that adds four days but no cost still needs to say so, otherwise you're late against the original completion date for a delay the customer caused.

The four-step process

Request, price, approve, execute, in that order, and the order is the whole point.

Request is anything that changes the agreed scope. It can come from the owner, from you, from an inspector, or from something you found when the wall came down. Capture it when it happens rather than reconstructing it later.

Price it properly. Change order work is genuinely more expensive per unit than the same work in the base contract, because it's out of sequence, it may mean remobilizing, and it disrupts a plan that was already made. Pricing changes at base contract rates is a common instinct and it's a quiet loss on every one.

Approve means signed, before work starts. This is the step that gets skipped, and skipping it is where nearly all change order disputes originate.

Execute, then keep the signed copy with the job file.

When the work genuinely can't wait

Sometimes stopping is not an option. You've opened a wall and found active water damage, and waiting two days for a signature means two more days of damage.

The answer is not to proceed silently and sort it out later. Document immediately: photograph the condition, write down what you found and what you propose, send it to the customer in writing, and get any acknowledgment you can, even a text saying "go ahead." An email sent at the time, describing the condition and the expected cost, is far stronger evidence than a recollection offered afterward.

Then paper it properly as soon as you're able. The verbal or text approval is a bridge, not a destination.

The small ones are the expensive ones

Nobody forgets to write up a fifteen thousand dollar addition. What goes undocumented is the two hundred dollar favor, repeated. Each one feels too minor to justify a form, and collectively they can absorb an entire job's profit while everyone involved feels they've been reasonable.

There's also a relationship cost to skipping them, which runs opposite to what people expect. Contractors avoid change orders because they think raising money mid-job damages goodwill. What actually damages goodwill is a final invoice containing charges the customer never agreed to. A signed change order at the time is a normal transaction. The same amount discovered at the end feels like being taken advantage of.

Setting the expectation at contract signing helps enormously. One sentence explaining that any change to the agreed scope gets written up and priced before work proceeds turns the first change order from an unpleasant surprise into the process working as described.

Make it fast enough that you'll actually do it

Every contractor who has lost money on undocumented changes already knows they should document changes. The gap is not knowledge, it's friction. If writing one up means opening a laptop, finding a template, and retyping the contract reference, it will not happen on a Tuesday afternoon.

What makes the habit stick is being able to raise one in a couple of minutes, from the job, with the original contract details already populated and the running total calculated for you. The paperwork that gets done is the paperwork that takes less time than the conversation it prevents.