How to Read a Change Order in 30 Seconds and Decide If It Pays

A change order just landed in your inbox. Maybe your PM sent it from the field. Maybe the homeowner texted their designer, who emailed your office, and now there's a PDF sitting in your inbox with a number on it.

You need to know in 30 seconds: does this make money, break even, or cost you?

The average Bay Area residential remodel generates 8-15 change orders. At $500K contract value, each CO that slips through without proper review is a direct hit to your margin. A 3% margin bleed on that job is $15,000. That money doesn't vanish in one big line item. It leaks out across a dozen COs that nobody read carefully.

Here are the 5 fields to scan first.

1. Scope Delta

What changed from the original estimate? A good change order names the original line item, describes what changed, and quantifies the difference. A bad change order says "additional electrical work, $3,200" with no reference to what was in the original scope.

Litmus test: If the CO doesn't name the original line item it's changing, send it back.

This is the most basic filter and it catches problems early. When a CO doesn't reference the original scope, nobody can verify whether the work is truly additional or was already included. Your estimator priced something. The CO needs to say what changed from that price. If it doesn't, you're approving blind.

Get in the habit of rejecting vague COs immediately. It takes your PM 10 minutes to rewrite it with the proper reference. It takes you 10 hours at closeout to reconstruct what happened if they don't.

2. Contingency Draw

Is this change order pulling from contingency or adding net new cost to the project?

This distinction matters more than most GCs realize. If the CO draws from contingency, your margin is already paying for it. The contingency was built into your original bid as a buffer. Every dollar that comes out of contingency is a dollar your margin absorbed. It's not free money.

Litmus test: If it draws from contingency, ask whether the underlying risk was foreseeable. If it was, your estimating needs to improve, not your contingency.

Track contingency draws separately from net-new COs. At the end of the job, you want to know: did we burn contingency because of bad estimating, or because genuinely unforeseeable conditions showed up? The answer tells you whether your next bid needs a bigger contingency or a better scope review.

3. Schedule Impact

Does this change order add days to the project?

Every added day has a carrying cost. Site overhead, insurance, equipment rental, portable facilities, your PM's time. On a typical Bay Area residential remodel, the daily carrying cost runs $400 to $1,200 depending on the phase and crew size.

Litmus test: If the CO adds days and doesn't price the schedule impact, it's incomplete.

A CO that says "add 3 days for tile redesign" but only prices the material and labor delta is missing the carrying cost. Three days at $800/day is $2,400 that's about to come out of your margin if you don't price it into the CO. This is one of the most common margin leaks in residential construction. The direct cost gets captured. The time cost doesn't.

4. Paper Trail Status

Was this change order verbally approved or documented before work started?

Verbal approvals are the number one source of disputed change orders at closeout. The homeowner says "go ahead, that's fine" on a Tuesday walkthrough. Your PM starts the work on Wednesday. The CO gets written on Friday. The homeowner signs it two weeks later, then disputes it at final payment because they "didn't realize it would be that much."

Litmus test: If work started before the CO was signed, flag it. You're carrying risk on every hour of that work.

Set a policy: no work on a change until the CO is signed. Period. If the client pushes back, explain that the signature protects both sides. It locks the price, the scope, and the schedule impact so nobody is surprised at closeout.

5. Profit Margin on the Delta

Does the change order carry your standard markup, or did someone eat the margin to keep the client happy?

This happens constantly. The homeowner wants to upgrade the countertop. Your PM prices the material delta at $4,200 and passes it through at cost because "it's a small change and I didn't want to make it a thing." Now you're doing additional work, carrying additional risk, and making zero margin on it.

Litmus test: If your CO margin is below your contract margin, you're subsidizing the change.

If your contract carries a 22% margin and your COs carry a 10% margin, every change order is diluting your overall job profitability. By the end of a job with 12 COs, that dilution can knock 2-4 points off your final margin. On a $500K job, that's $10,000 to $20,000 that evaporated because nobody enforced consistent markup on changes.

The 48-Hour Rule

Set a policy: any change order not signed within 48 hours gets escalated. Not next week. Not "when the client gets around to it." Forty-eight hours.

Every day a CO sits unsigned is a day your team is working at risk. The work is happening. The cost is real. But the approval isn't locked, which means the client can dispute it later.

Escalation doesn't mean confrontation. It means a quick call: "Hey, I want to make sure you saw the change order for the electrical panel relocation. I need your signature before we proceed so we're both protected on the scope and cost." Professional, direct, protective of both sides.

Track how long COs take to get signed. If your average is over 5 days, you have a systemic problem that no software can fix until you fix the process.

When the Leak Is Systemic

If 3 or more of these five fields are problems on your current jobs, the leak isn't about one bad CO. It's systemic. Your process, your templates, or your tools are letting margin slip on every job.

That's worth diagnosing properly. Grab the 12-point margin leak checklist and run through it on your last 3 completed jobs. You'll find the pattern.

For a broader look at tools that handle change order workflow, read our guide to construction management software for residential GCs. And if Buildertrend's CO flow is specifically what's frustrating you, see our Buildertrend alternative breakdown.