What is a Change Order?

The most expensive document in professional services is often the one that never gets raised. The work happens anyway: the extra integration, the second round of revisions, the report that was never in scope. What is missing is the piece of paper that would have attached a price to it. A change order is that piece of paper, and the reluctance to produce one is among the most reliable ways a healthy contract becomes an unprofitable one.

A change order (in some houses a change request, a variation or a contract amendment) is a formal record that the agreed scope of work has changed, and of what the change means for price, timeline and responsibilities. It amends the statement of work rather than replacing it: this deliverable is added, this assumption no longer holds, this date moves, and this is what it costs.

What a change order protects

It is easy to read the change order as a supplier weapon, the mechanism by which firms bill for every breath. A good one protects both sides in equal measure.

For the provider, it keeps price connected to scope. It converts what would otherwise be scope creep into revenue or into a recorded, deliberate gift, and it builds the audit trail that answers, months later, why the engagement cost what it cost.

For the client, the protection is just as real. A change order makes the cost of a request visible before it is incurred, instead of surfacing it later as a shock invoice, a quiet degradation in quality, or a renewal price that seems to come from nowhere. A firm that absorbs unpriced work always recovers the cost somewhere; the change order replaces those hidden recoveries with an open price the client can accept, negotiate or decline.

A change order is not the moment a relationship turns adversarial; it is the mechanism that keeps scope, price and expectations honest on both sides while the work is still moving.

Why firms avoid raising them

If the document is so protective, why do experienced firms leave it in the drawer? Almost never ignorance. Almost always relationship fear. Raising a change order feels like breaking a spell: the partnership talk of the sales cycle gives way to paper, and the delivery lead worries it reads as petty, transactional, a firm that counts every conversation. The fear is strongest exactly where the stakes are highest. The bigger and more strategic the account, the higher the perceived cost of friction, which is why the largest accounts so often carry the most unpriced work.

There is a structural reason too. The person who would raise the change order is the person who must have the awkward conversation, today, face to face. The cost of not raising it lands months later, spread thin, in a margin line owned by someone else. When the pain of speaking is immediate and personal, and the pain of silence is deferred and shared, silence wins by default.

The moment a favour should become a change order

Nobody serious raises a change order for every clarification or minor courtesy. Small favours are the normal texture of a working relationship, and a firm that papers all of them has misunderstood the point. The discipline lies in noticing when a favour has crossed the line, and four signals mark the crossing. The favour recurs: a repeated favour is not a favour, it is the new baseline. It consumes named effort: work that has to be planned and staffed is scope, whatever it is called. It moves an assumption the price was built on. Or the client begins to treat it as owed rather than granted.

Any one of these means the favour has become scope, and scope is a decision: price it, trade it against something, or gift it knowingly. The moment to raise the change order is before the work starts, while both sides can still choose. A change order raised after the work is done is not a decision. It is a plea.

One concrete example

Clearly illustrative, with no customer implied. Midway through a delivery, a client asks the team to support a second data source, since you are in there anyway. The delivery lead judges it at roughly two weeks of effort. Absorbing it silently costs two unpriced weeks, squeezes the deadline and sets a precedent. Raising a change order instead does something nobody expected: when the client sees the price and the date impact side by side, they decide the second source is not worth it this quarter. The unraised change order would not have saved the client money; it would have spent two unpaid weeks building something the client did not value at its real price. That is what the document is for. It let the client make an informed choice, and it saved the provider from donating the work.

A leading indicator, and the decision-intelligence angle

Change-order discipline is one of the best leading indicators of margin health, because it moves before margin does. Delivery margin is a lagging measure: by the time it degrades, months of silent absorption have already happened. A book of accounts where scope visibly moves but change orders are rare is announcing future margin erosion in advance, and the accounts to watch are precisely the ones with high change activity and no commercial paper trail, since that combination is where revenue leakage concentrates.

Seen through a decision lens, every unraised change order is a decision that was made (to absorb the work) without ever being recorded as one. The discipline of decision intelligenceis to make that choice visible: the request captured, the cost estimated, the options priced, an owner named, the choice recorded. Do that, and the absorption pattern across a whole portfolio becomes something leadership can see and act on while there is still time, rather than a forensic finding in next year's margin review.