The Change Order Nobody Wanted to Name

Filed by: D.B. Trench

Field line: If it changes cost, sequence, risk, or responsibility, it is not a favour. It is a change looking for paperwork.

The change arrived with clean boots.

That should have made me suspicious.

Messy changes announce themselves. They drag drawings, cost impacts, contract language, and people who suddenly remember the word entitlement.

The dangerous ones arrive as coordination.

Can we just shift the cable tray route above the service corridor? It keeps the ceiling access cleaner and avoids a clash with the mechanical run.

Just.

There it was, standing beside the site table with a hard hat and no purchase order.

The contractor was not wrong. The proposed route made field sense. The mechanical drawing had changed after the electrical layout was coordinated. The superintendent wanted the conflict solved before crews lost a day arguing under fluorescent lights.

Everyone wanted to be practical.

Practical is good.

Practical without a record is how a change order learns to deny its own childhood.

The site instruction draft was already being softened when I saw it.

Contractor to coordinate revised cable tray routing with mechanical trade to support corridor access.

That sentence sounded helpful. It also forgot to mention sequence, labour, material, inspection, and the fact that the contractor was being asked to perform work differently than the approved drawing package.

The project manager on the contractor side did not call it a change.

The owner's rep did not call it a change.

The consultant called it coordination, which is a useful word until it starts doing unpaid legal work.

I asked the unpopular question.

Does this change cost, sequence, access, responsibility, inspection, or risk?

The table got quiet in that construction way, where nobody is silent but everyone suddenly becomes very interested in paper.

The answer was yes.

Not catastrophic yes. Not claim-the-project yes. But yes enough.

The first cable tray shift had already happened two weeks earlier under a field note. Nobody priced it. Nobody named it. Nobody wanted the delay that would come with stopping work to argue over the formal mechanism.

That one was gone.

It would reappear later as a dispute with bad handwriting and selective memory.

This one could still be named.

I rewrote the instruction before it left the meeting.

Revised cable tray routing is required due to mechanical coordination conflict above the service corridor. Contractor to provide cost, schedule, access, inspection, and trade-sequence impacts before proceeding beyond temporary protection work. Direction to proceed requires written authorization through the change process or explicit acceptance that no cost/schedule impact is being claimed.

That sentence annoyed almost everyone equally.

Good.

Equal annoyance is sometimes how you know the sentence has stopped doing favours.

The superintendent wanted the route cleared.

The owner's rep wanted the schedule protected.

The contractor wanted not to donate labour.

The consultant wanted the design conflict solved without becoming the headline in the next progress meeting.

All reasonable.

All incomplete.

The RFI went in that afternoon. The response confirmed the revised route. The contractor submitted a priced change. The owner challenged two line items. The schedule impact was smaller than the contractor first claimed and larger than the owner's rep wanted to admit.

Nobody got a clean victory.

That is not what the change process is for.

The change process is not a confession booth. It is not a weapon by default. It is the place where cost, sequence, risk, and responsibility stop pretending to be personality issues.

The earlier unpriced shift still came back later.

Of course it did.

The contractor remembered acceleration. The owner remembered cooperation. The field note remembered almost nothing useful.

That was the price of not naming the first change when it still had a clean face.

The second one held.

Not because the sentence was brave. Because it forced the work to travel through the mechanism built to carry it.

For the next time “coordination” starts wearing a change order's coat:

---

Change-name test: Use this when a field request, RFI response, site instruction, or “quick coordination item” may affect the commercial baseline.

Ask: “Does this alter cost, sequence, access, inspection, responsibility, warranty, safety, or risk?”

If yes: name the mechanism before the work becomes memory: RFI, site instruction, change order, contract notice, or explicit no-impact confirmation.

Record line: “Requested adjustment affects [cost/sequence/risk/responsibility]. Proceeding requires [change mechanism/authorization/no-impact confirmation] before work advances beyond [limited holding action].”

Related kit: The Scope Defense Bundle is built for requests that arrive sounding helpful and leave carrying cost.