Change Order Management: Protecting Margins Without Burning Relationships

Change orders are where construction projects quietly lose money. Not through catastrophic events, but through a thousand small decisions made at the edge of a drawing, in a hallway conversation, on a WhatsApp message that nobody logged.

By the time the commercial team consolidates variations for the monthly report, the damage is already done: work was executed, materials were consumed, and the only remaining question is how much of it the client will actually pay for. In most GCC projects we see, that answer is "not enough."

Why change orders bleed margin

A well-run project should make money on variations. Scope changes are the contractor's chance to re-price work under new conditions, capture escalations, and recover indirect costs that the original bid underestimated. In practice, most contractors lose margin on variations for three reasons.

1. The approval gap

Work gets done before it's priced. A consultant asks the site engineer to "just go ahead," the engineer trusts the relationship, and the variation is submitted two weeks later. Now the client has leverage — the work is already in the ground, and any price negotiation is asymmetric. The contractor either accepts a reduced rate or fights a dispute they're unlikely to win.

2. The documentation gap

When the variation claim finally reaches the PMO, half the supporting evidence is missing. Who authorized the change? What were the original conditions? What additional resources were consumed? Without a clean trail, the claim gets rejected or heavily cut. FIDIC and local contracts are unforgiving on notice periods and substantiation — a claim without a paper trail is a claim without legs.

3. The cumulative impact gap

Individually, each variation looks manageable. A SAR 40,000 scope addition here, a two-week extension there. But contractors rarely consolidate the cumulative impact of variations on productivity, sequence, and overheads. The direct cost is claimed; the indirect cost — disruption, idle equipment, acceleration — is absorbed silently into the original budget.

What a disciplined change order process looks like

Protecting margin doesn't mean turning every conversation into a contract negotiation. It means having a repeatable workflow that catches variations early, prices them fairly, and documents them properly — without creating friction that burns the client relationship.

Capture at the point of origination

The moment a site engineer identifies a potential variation — a drawing revision, a site instruction, an RFI response that changes scope — it should enter the system as a potential change. Not a claim, not an invoice, just a logged event with a description, originator, date, and reference to the triggering document.

This single discipline eliminates 80% of disputes. When the variation is logged on day one, the client and contractor are aligned on the fact that something changed. Negotiating the price is then a commercial conversation, not a contractual fight.

Assess before execution

Every logged potential change should trigger an assessment workflow: direct cost estimate, time impact, resource requirements, and a recommendation — proceed, hold for approval, or reject. Nothing gets executed until the assessment is reviewed by a commercial lead and the client signs off in writing, even if it's just an email acknowledging the estimate range.

For emergencies where work must proceed before formal approval, the system should create a "proceed under protest" record — a contractual device well-recognized under FIDIC — so the claim survives scrutiny later.

Price fairly, not opportunistically

The fastest way to burn a client relationship is to treat every variation as a chance to inflate rates. Clients are not stupid; they benchmark rates across projects, and a contractor who over-prices variations earns a reputation that costs them future work.

The right approach is transparent pricing: original BOQ rates where applicable, documented market rates for new items, and a clearly-stated overhead and profit percentage that matches the contract terms. A variation priced this way is almost impossible to reject because there's nothing to argue about.

Track the cumulative impact

Individually small variations can collectively break a project. A disciplined commercial team maintains a running log of all variations with three metrics: total value, cumulative percentage of original contract sum, and cumulative schedule impact. When the cumulative value crosses a threshold — typically 10-15% on GCC projects — it triggers a formal notice of disruption or acceleration, with a claim for indirect costs.

This is where contractors leave the most money on the table. Direct variation costs get claimed; the indirect impact almost never does, because nobody is measuring it.

The client relationship side

A common mistake is treating change order discipline as an adversarial stance. It isn't. Clients — especially sophisticated ones like Aramco, NEOM, and Roshn — actually want their contractors to have clean variation processes. Disputes slow their projects down too. A contractor who shows up with a clean variation log, transparent pricing, and proper notice discipline earns trust, not friction.

The contractors who burn relationships are the ones who surprise the client: unlogged variations appearing at project close-out, inflated rates, missing substantiation, emotional escalation. A disciplined process prevents all of that because everything is visible from day one.

Where BuildaPay fits

BuildaPay's change order module is built around this exact workflow: potential variations are logged from the field, routed to the commercial team for assessment, priced against the project BOQ, and tracked against the cumulative impact threshold. Notice deadlines are calculated from contract terms so nothing falls outside the claims window. The full document trail — RFI, site instruction, drawing revision, approval email — is attached to each variation for audit and dispute resolution.

The cumulative impact dashboard is the piece most contractors don't have in their current systems, and it's where we see the fastest margin recovery: typically 2-4 percentage points on projects where variations exceed 8% of the original contract value.

Practical next steps

• Audit your last three completed projects. How many variations were logged before the work was executed? If the answer is less than 80%, you have an approval gap.
• Calculate the cumulative impact as a percentage of original contract sum. Anything over 10% that wasn't accompanied by a disruption claim is margin you gave away.
• Standardize your variation pricing template. Separate direct cost, indirect cost, and overhead. Share it with clients upfront so there's nothing to negotiate later.
• Train site engineers on notice discipline. A variation logged in the first 7 days is worth three logged at project close-out.

Change orders don't have to be the place projects lose money. With the right discipline, they become the place projects recover it — without burning the relationships that deliver the next contract.