Change order cause: the one word that decides who pays

Read the cause field before the dollar figure. The change order cause is the only part of the form that decides whose money pays, and it is usually one word chosen by the person who wrote the change, not by the person who will fund it.

What the change order cause field actually does

Every change order carries an amount, a description and a reason. Owners read the amount. The reason is what moves the money.

There are four common categories, and the boundaries between them are genuinely blurry.

Owner directed change. The owner asked for something different. This is owner money and nobody disputes it.

Design gap or error. The documents did not describe the work correctly. Depending on the contract and the facts, this lands on the owner, on the design team, or in a negotiation that lasts longer than the work itself.

Unforeseen condition. Something physically present that nobody could reasonably have known about. Usually owner money, subject to whatever the contract says about site investigation.

Contractor coordination. Two trades that should have been sequenced together were not. This is normally contractor contingency, inside the ceiling, and it costs the owner nothing directly.

The same physical event can be written up under any of the four. A duct that will not fit above a beam is a design gap if the drawings showed clearance that does not exist, and a coordination failure if the drawings were right and nobody checked. The event is identical. The invoice is not.

Why classification drifts toward the owner

Nobody has to act in bad faith for this to happen. Three ordinary pressures push in the same direction.

The person writing the change order is usually a project engineer working quickly under schedule pressure, using whatever category the last similar change used. Precedent, not analysis.

Contractor contingency is finite and visible internally. A change classified as coordination consumes it. A change classified as a design gap does not. That is not fraud, it is arithmetic that everyone in the room understands.

And the owner reviewing the change order has ten days, no baseline, and a schedule that punishes delay. Approving is cheaper this week than arguing.

Repeat that fifty times across a job and the drift is substantial. The cost and change exposure assessment exists because the drift is invisible in any single change and obvious across the register.

Two events, one form, different payers

The fastest way to see how much rests on the cause field is to take one event and write it up twice.

A mechanical contractor reaches the third floor and finds that the main supply duct will not clear a structural beam. Work stops on that run. The fix costs $86,000 in rework, rerouting and delay to the ceiling grid.

Written as a design gap: the coordination drawings issued for construction showed clearance that the structural shop drawings later contradicted. The documents were inconsistent. The cost belongs to the owner, subject to whatever the agreement with the design team says about recovery.

Written as contractor coordination: the structural shop drawings were issued nine weeks before the mechanical layout was finalized, both were in the contractor model, and nobody ran the comparison. The documents were consistent and the process failed. The cost sits in contractor contingency, inside the ceiling, and the owner pays nothing.

Both versions can be written honestly from the same file. Which one gets written depends on who looks first and what they look at, and the difference is $86,000 on one duct run.

This is the reason the categories belong in the contract rather than in a dropdown menu. Defining them afterwards means defining them while somebody is already holding an invoice.

What a contract can do about it before signature

Classification disputes are cheap to prevent and expensive to resolve. Four provisions do most of the work.

Name the categories in the contract. If the agreement lists the four causes and says which fund each one draws on, the argument happens once, in the negotiation, instead of fifty times during construction.

Require the cause on every change order, in writing, with reasoning. Not a dropdown. Two sentences explaining why this event belongs in this category.

Say who decides a disputed classification, and how fast. A named individual and a stated number of days. Without it, the default is whoever can wait longest, and that is never the owner.

Require the change order log in a format you can read. Cause, date, amount, status, and the document reference. A log that shows only approved amounts hides the pattern entirely.

None of these four is unusual, and none costs the contractor anything if the classification is honest.

A worked example

A job runs $1,900,000 of change orders against a $55,000,000 guaranteed maximum price, which is about three and a half percent. Not alarming on its own.

Sorted by cause, $1,240,000 is written as design gap, $390,000 as unforeseen condition, $210,000 as owner directed, and $60,000 as contractor coordination.

Contractor coordination is three percent of the total. On a job with fourteen trade packages and a compressed enclosure sequence, three percent is low enough to be worth a question.

Reading forty of the design gap changes against the drawings, eleven describe conditions that were shown correctly and simply were not coordinated between two trades. Those eleven total $418,000.

Reclassified, they would have come out of contractor contingency, which sits inside the ceiling. Classified as they were, they came out of owner money.

No single change order was obviously wrong. The pattern only appears when the register is read as a whole, sorted by cause rather than by date.

The same register sorted by date tells you the job is running at three and a half percent, which reads as healthy. Sorted by cause it tells you that almost two thirds of the movement was written against a category the owner funds, on a job where the interfaces were the hardest part. Same file, same numbers, a different question asked of them.

None of this makes the contractor dishonest. Eleven changes out of forty is not a pattern of deceit, it is the ordinary result of a category boundary nobody defined and a review window nobody had time to use. Both of those are fixable before signature and neither is fixable afterwards.

What to do before you sign, and after

1. Write the four causes into the contract and name the fund each one draws on.
2. Require written reasoning on every change order, not a category code.
3. Name the person who decides a disputed cause, and the number of days they have.
4. Require the full log monthly, sorted by cause, including rejected and pending items.
5. Once a quarter, sort the register by cause and look at the coordination share.
6. When that share is implausibly small, ask for the reasoning on the largest design gap items.

The quarterly reading takes an hour and is the only one of the six that finds anything after the fact. The other five stop it happening. More of this subject sits in change orders, exclusions and claims.

What we do

We read the change mechanism before signature and write down what each category will cost you once work starts. After signature the same reading runs monthly against the live register, and that is the job Costwitness was built for. Findings cite the change number and the clause, ranked by dollars, with the question to put to the contractor.

Questions people ask