Read the fine print above the signature line. Most forms say the price and time shown are full and final compensation for all costs and time arising out of or related to the change. Sign with zero days in the time box and, depending on the wording, you may have agreed the change has no schedule impact, direct or cumulative. Do that thirty times and you have signed away the claim that explains why you finished late and over budget. International and some domestic forms call it a variation or variation order. Same trap.
The release language trap
The issuing party drafts the form, and the release language does exactly what it says. Typical wording releases all claims for cost and time "arising out of or related to" the changed work, sometimes including impacts on unchanged work. That last part is the killer, because your real exposure is what the change does to everything around it: sequence, crew flow, access and float.
The direct cost is the easy number, and usually the only one anyone prices. The time box gets a zero because "this little change does not move the end date."
Every change order is a possible time event. Check it
The most defensible answer to "does this change cost time" is a time impact analysis: build the fragnet for the changed work, insert it into the current update, and let the network answer. AACE RP 52R-06 is the recommended practice for this prospective TIA. You get one of two answers:
- The change pushes completion. The fragnet lands on the critical path and the end date moves. The easy case. Record the modeled completion impact and address the requested time and any reservation of rights with counsel before signing.
- The change eats float. The fragnet lands on a near-critical path and consumes total float without moving completion. Most people call this "no impact." It is impact you have not felt yet.
Float consumption is the finding everyone throws away, and it decides jobs. A change that burns 8 CDs of total float on your riser sequence did not move the end date today. It moved your margin for error. The next change, weather event or late drawing lands on a path with no room left.
The cumulative effect: how eaten float becomes a late job
The pattern that buries subs is arithmetic, not bad luck.
- CO 004 eats 6 CDs of total float on your path. End date unchanged. Time box zero, signed.
- CO 011 eats 5 more. End date unchanged. Signed.
- CO 019 resequences an area and eats 7 more. Still unchanged. Signed.
- CO 026 needs 3 CDs on a path that now has none. The project goes late.
Each change was "minor." Together, they consumed the float and then the calendar. When you finally ask for time and extended cost, the answer comes armed with your own signatures: twenty-five executed change orders, each releasing all time impact from that change. The compounding was real, and the record says you waived it one piece at a time.
Volume of change carries a second cumulative cost: disruption. A constant stream of changes costs productivity through resequencing, remobilization, trade stacking and broken crew rhythm, the mechanics in the schedule compression article. That cumulative impact claim is recognized, and blanket releases are how it gets defeated.
What to do on every change order
- Price time with money, every time. A CO is not fully priced until the network answers the time question. Ask for the TIA or run your own before the price is final.
- Do not accept "it is just one activity" as the analysis. One added activity can be nothing or can restructure a path. The fragnet in the current update is the answer, not an opinion in a meeting.
- Put float consumption on the record even when you sign for zero days. If the TIA shows float consumed without moving completion, say so in the CO or a transmittal: this change consumes N CDs of total float on the affected path, and we reserve our rights regarding the cumulative effect of this and other changes.
- Get reservation language into the change order before you sign. Words to the effect of: execution of this change order does not waive rights to time extension or to the cumulative impact of this change together with other changes and events. Have your attorney tune it to your contract, then use it consistently.
- Keep a running float log. A simple contemporaneous record (CO number, path affected, CDs of total float consumed) tied to the monthly updates. When the compounding pushes the job, this log is the spine of the claim.
On multifamily work in the Carolinas we have watched this exact stream of small electrical changes run through a job, each signed as cost-only, none individually critical. The subs who logged float consumption change by change had a cumulative story the schedule could support. The others had a stack of releases.
This is the core of our change order and time impact analysis service, alongside the notice letter that protects delay events and our advocacy and notice support scope. One caution: release enforceability is a legal question that varies by contract and jurisdiction, and we are schedulers, not lawyers. What the network shows is our side. What the signature waives is your attorney's.
Do not sign the time box yet. Send us the CO and current schedule, and we will run the fragnet and tell you whether it moves the end date, eats your float, or both.