How to Manage Construction Change Orders Without Losing Money

A change order that gets verbally agreed on Tuesday and priced "later" is the one that eats your margin by Friday. Price it, scope it, and get a signature before the trade lifts a tool, because the moment that work is in place you have lost the leverage to negotiate it.

That one move is the whole job of construction change order management. Everything below is how you actually run it on a live project where the framer is already on site and the owner wants an answer by lunch.

I have seen this across thousands of bids: the cost overrun almost never comes from the one big obvious change. It comes from six small ones nobody wrote down, each "just a few hundred bucks," that surface together at closeout as a 9% swing on a $400,000 job.

What is a change order in construction?

A change order is a written, signed amendment to the original contract that modifies the scope, the price, or the schedule of the work. It is a contract document, the same legal weight as the bid it amends. A verbal "go ahead and do it" is not a change order. A text message is not a change order. An email with no price and no signature is a dispute waiting to happen.

The industry-standard form is the AIA G701, which exists precisely so the change is captured the same way every time. You do not have to use that exact form, but whatever you use has to carry the same fields. If you want the official reference, the American Institute of Architects publishes the G701 and its companion documents, and there is a plain-language overview of the concept on Wikipedia.

What should a change order contain?

A complete change order names the exact scope delta, the dollar amount, the schedule impact in days, and the signatures of both parties before the work starts. Miss any one of those four and you have an open question, not a closed change.

Every change order I sign carries these fields:

• Change order number, sequential, tied to the original contract number
• Reference to the original bid line item it modifies, so the change reads against the baseline scope
• Description of the scope change, specific enough that a different PM could price it from the text alone
• Reason code: owner-directed, design change, unforeseen condition, or scope gap in the original bid
• Cost breakdown: labor hours, material, equipment, markup percentage, each on its own line
• Schedule impact in calendar days, including whether it extends substantial completion
• Revised contract total, original plus all prior change orders plus this one
• Signature blocks and dates for both the GC and the sub or owner

The reason code matters more than people think. When you get to closeout and the owner argues a $12,000 change, "unforeseen condition: rock at 4 feet, photographed and logged 5/14" wins that argument. "Extra excavation" loses it.

How do you price and approve a change order before work starts?

You pick the pricing method that matches how well you know the scope, set the markup before the work begins, and get the signature in hand before the trade mobilizes. The sequence is the protection. Once the slab is poured or the wall is closed, the sub knows you cannot easily undo it, and the number climbs.

Three pricing methods cover almost every change. Pick by how clearly you can see the scope:

Method	When to use it	Where it bites you
Lump sum	Scope is fully defined, quantities known	Sub pads the number; demand the line-item breakdown
Time and materials (T&M)	Scope genuinely unknown at start	Open-ended cost; always set a not-to-exceed cap
Unit price	Repeatable quantities (cubic yards, linear feet)	Quantity creep; verify field counts daily

For T&M work, the not-to-exceed cap is non-negotiable. "T&M to repair the failed waterproofing, capped at $8,500, anything beyond requires a new written authorization" keeps an open-ended ticket from running to $20,000 while you were on another site.

Set the markup in the original contract, not at the moment of the change. A clause that fixes change-order markup at 15% on subcontractor work and 10% on materials means you are never negotiating the percentage under pressure with the schedule slipping. You agreed to it on bid day when you had time to think.

How much do unmanaged change orders actually cost?

Change orders routinely run 5% to 15% of total contract value on a typical project, and on renovation or existing-condition work it runs higher. On a $1 million job that is $50,000 to $150,000 of scope moving through paper that most teams handle worse than they handle the original bid.

The money leaks in three predictable places:

1. Work performed before approval. The sub does it, then sends the price. Now you are arguing about completed work, and retention (usually 5% to 10%) is your only remaining leverage.
2. Schedule impact never captured. The cost gets logged, the 6 days of delay do not. Then the next trade shows up to a site that is not ready and files their own delay claim against you.
3. Scope gaps treated as changes. Something the sub should have carried in the base bid gets slipped in as a change order. A clean record tied to the original bid is how you catch that the "new" work was in the plans the sub bid from (see reading bids to catch scope gaps).

That third one is where vetting and change management meet. A sub who underbids on purpose and makes it back on loose change orders is running a known play. The defense is a baseline you can read every change against.

How does a timestamped record tied to the original bid protect you?

It freezes the baseline so every change reads as a measurable delta from what the sub originally agreed to, with a date attached that nobody can rewrite later. The single most common change-order dispute is some version of "that was always included" versus "no, that was extra." The only thing that settles it is a record of what the original scope said and when each change was logged against it.

This is the part SubSource is built to handle. The platform keeps the original bid, the verified license, insurance, and bond status, and every change order in one timestamped chain, so a change order is not a loose PDF in an email thread. It reads against the exact bid line it modifies, dated, with the running revised total visible. When you are sitting across from an owner or a sub at closeout, the question is not whose memory is better. It is what the record shows. You can see how the platform ties bids, vetting, and changes together at https://subsource.org.

The practical payoff: when a sub submits change order number 7 and your record shows changes 3 and 5 already covered part of that scope, you catch the double-dip before you sign, not after you have paid.

Frequently asked questions

Can a contractor start work without a signed change order? They can, and they do it constantly, but it is the contractor taking the risk. Work performed without written approval is hard to collect on and easy to dispute. The protection is to make written approval a condition in the original contract, so unauthorized work is a clear breach rather than a gray area.

What is the difference between a change order and a change directive? A change order is agreed by both parties before work proceeds. A construction change directive is the owner ordering the work to proceed before the price is settled, usually because the schedule cannot wait. The directive still has to be reconciled into a priced, signed change order afterward, so it is a timing tool, not a way to skip the paperwork.

How fast should change orders be approved? Fast enough that the work is not already done when the signature lands. Set a response window in the contract, commonly 5 to 10 business days, and tie the start of the work to the signature rather than to the verbal request.

On your next bid, before anyone signs, add a single clause: change-order markup fixed at a stated percentage, written approval required before work proceeds, and a 7-day response window. Three sentences in the contract is what turns every change after that into a number you control instead of a fight you have at closeout.