Top 3 Change Order Mistakes Project Managers Make

Most jobs don’t lose money on the bid. They lose it in the middle — one undocumented change at a time. And the change order mistakes project managers make are rarely dramatic. Nobody forgets a $40,000 scope change. What kills the margin is the $1,800 framing fix that got a nod on site, the extra mobilization nobody wrote down, the “while you’re at it” that felt too small to paper. Then the job closes out, the numbers don’t add up, and the PM is the one standing in the office explaining where the money went.

If you run projects, this post is for you. Below are the three mistakes I see project managers make over and over, what each one really costs, and the process that fixes all three without adding an hour of paperwork to your week.

Why change order mistakes hit project managers hardest

Here’s the uncomfortable part: when a change order goes wrong, it’s the project manager who wears it. The owner didn’t sign anything, so as far as they’re concerned there’s nothing to pay. The sub did the work, so they invoice you regardless. The GC or the principal looks at the cost report and sees a variance with your name on it.

The damage stacks up in ways that go past one bad line item:

• Unpaid work. Work performed without a signed change order is work you may end up donating. On a job running 5–8% margin, a handful of eaten changes can wipe out the profit on the entire project.
• Disputes at the worst possible time. Undocumented changes surface at final billing — exactly when you need the client cooperative to close out and get retainage released.
• Schedule fights. A change that added six days but was never written up becomes “you’re late,” not “the scope grew.” Now you’re defending liquidated-damages exposure on time you legitimately spent.
• Wrecked client trust. A surprise invoice for changes the client doesn’t remember approving reads like padding, even when every dollar is real.

None of this comes from bad luck. It comes from three specific, fixable habits.

Mistake #1: Letting the work start before the signature lands

This is the big one. The client says “go ahead, we’ll sort the paperwork,” the crew is standing right there, and stopping feels like it costs more than continuing. So the work goes in, and the change order becomes something you’ll “get signed this week.”

Here’s what that decision actually costs you: all of your leverage. Before the work is done, you’re pricing a scope — the client weighs the cost against getting what they want. After the work is done, you’re collecting a bill — the client already has what they want, and every incentive points toward negotiating you down. The same $6,000 change that would have been approved in a minute on Tuesday becomes a $4,200 settlement in November, if you’re lucky.

It gets worse when memories drift. Three months later the client remembers “a small tweak,” you remember a re-frame, and there’s no document either way. I wrote about this failure mode in detail in why verbal change orders cost you money — the short version is that a handshake is worth exactly what it’s written on.

The rule that fixes it: no signature, no work. Not as a threat — as a system. When approval takes days, holding that line is genuinely hard. When you can send a change order from your phone and the client signs from theirs in a couple of minutes, the line holds itself. The excuse for starting early disappears when the paperwork is faster than the coffee run.

Mistake #2: Saving the paperwork for Friday

The second mistake looks responsible on the surface. The PM fully intends to document everything — just later. Changes get scribbled in a notebook or parked in the memory bank, to be written up “when things calm down.” Friday afternoon. End of the month. Before the next pay application.

Three things go wrong in that gap:

1. Details evaporate. By Friday, Tuesday’s change is a blur. Quantities get guessed. The extra half-day of labor gets rounded down because you can’t quite remember. Every guess is a small donation to the job.
2. The subs beat you to it. Your sub documents their extra work same-day — because getting paid depends on it — and their number lands in your inbox before you’ve captured your own. Now you’re reconciling their record against your recollection, and their record wins.
3. Scope creep becomes the culture. When the client sees changes happening with no paper following, they learn that changes are free-flowing and casual. By week six, asking for a signature feels like a personality change, and the pushback starts: “you never made us sign before.”

A change order written the same day takes five minutes and is accurate. The same change order written three weeks later takes forty minutes of forensic reconstruction and is still wrong. Batching doesn’t save time — it converts cheap, accurate paperwork into expensive, disputed paperwork.

The rule that fixes it: the change order gets written the day the change is agreed. Same day, every time, no pile.

Mistake #3: Writing change orders that don’t hold up

The third mistake is subtler: the PM does send a change order, on time, before the work starts — and it still ends up in a dispute, because the document itself is mush. “Additional electrical work per discussion — $3,500” is not a change order. It’s an invitation to argue later about what “additional” meant.

A change order that holds up answers five questions without room for interpretation:

• What exactly is changing? Scope in plain words — locations, quantities, materials. “Add four recessed fixtures in the master bedroom ceiling, including circuit from panel” beats “extra lighting” every time.
• What does it cost? A firm number, or a clearly defined T&M basis with rates. If you’re not sure how to build that number so it covers your real costs, start with how to price a change order so you actually get paid.
• What does it do to the schedule? Days added, in writing. This is the one PMs skip most, and it’s the one that saves you when the completion-date conversation gets tense.
• What’s the new contract total? A running total means the client is never surprised at final billing — they watched the number move with every approval.
• Who approved it, and when? A signature and a date stamp, not a thumbs-up emoji.

Vague documents have a way of resolving against the person who wrote them. The client’s reading of an ambiguous scope will favor the client — and you handed them the ambiguity. For a fuller checklist of habits that keep changes clean, see change order best practices every contractor should use.

The fix: a change order process project managers can run at full speed

Notice that all three mistakes share a root cause: friction. When writing a change order means getting back to the office, opening a Word doc, exporting a PDF, emailing it, and chasing a signature for a week, busy PMs will defer it — and every deferral is one of the three mistakes above waiting to happen.

So the fix isn’t discipline. It’s dropping the friction to near zero. Here’s the whole process:

1. Change comes up on site. You talk it through with the client.
2. Before anyone lifts a tool, you fill in the scope, price, and schedule impact on your phone — two or three minutes.
3. The client gets it instantly, reviews it, and signs from their phone. Date-stamped, documented, done.
4. The contract total updates automatically, so the running number is never in dispute.
5. The crew starts the work — covered.

That’s what ChangeOrdersPro does, and it’s 100% free — every feature, unlimited change orders, no card. (Skeptical? Fair. Here’s why it’s free.) If you’d rather keep reading first, the blog covers pricing, templates, T&M changes, and the rest of the paperwork nobody teaches you.

Three mistakes, one root cause, one fix. The PMs who get burned aren’t careless — they’re busy, and their process punishes them for it. Make the paperwork faster than the mistake, and the mistake stops happening.

Frequently asked questions

What is the most common change order mistake project managers make?

Starting the work before the change order is signed. Once the work is in place, the client has what they wanted and you have no leverage — you're collecting a bill instead of pricing a scope. The fix is a hard rule: no signature, no work, made practical by using a tool fast enough that approval takes minutes instead of days.

Should a project manager ever do change order work on a verbal approval?

It's a gamble with your margin. Memories drift, people leave projects, and months later a "small tweak" and a major re-frame can be the same undocumented conversation. If the client is standing right there, that's the perfect moment to send the change order from your phone and get it signed before the crew starts.

What should every change order include to avoid disputes?

Five things: a specific scope description (locations, quantities, materials), a firm price or defined T&M basis, the schedule impact in days, the new running contract total, and a dated signature from someone with authority to approve. If any of those is missing, the document can still be argued over — which defeats the point.

How fast should a change order be sent after a change is agreed?

Same day, ideally on the spot. Details are accurate and the client's memory of the conversation is fresh, so approval is quick. Every day of delay makes the writeup slower, the numbers fuzzier, and the approval harder — and it teaches the client that changes happen without paperwork.

Daisy Porter

Co-Founder, ChangeOrdersPro

Daisy writes about the unglamorous side of running a build — the paperwork, the change orders, and the conversations that keep a job profitable. ChangeOrdersPro is the free tool her team built so contractors can send a professional change order and get it signed from a phone in about 30 seconds.