The Change Order: How Extra Work Actually Gets Approved and Paid

Every contractor who has worked a public job has had the same conversation. The work was clearly outside the contract. Everyone in the field agreed it was outside the contract. It got built because the schedule would not wait. And months later the money is still not there.

The uncomfortable answer is that extra work does not become a change order because it was necessary, or because it was obvious, or because a supervisor nodded at it. It becomes a change order because somebody followed a process the contract already spelled out — in the right order, in writing, before the work went in the ground.

This is the third piece in a series on the documents that hold a public project together, after the submittal log and the RFI. Change management is where those two documents get cashed.

Know which instrument you are actually holding

Contractors lose money by using one word — “change order” — for four different things that carry very different rights.

A change order is a fully executed bilateral amendment to the contract. Scope, price, and time are all agreed and signed. This is the only instrument that is genuinely settled.

A change directive — sometimes called a construction change directive or unilateral change order — is an owner instruction to proceed with changed work before price and time are agreed. It obligates you to build. It does not resolve what you get paid, and it usually starts a clock for submitting your pricing and time impact.

A field order or minor-change instruction covers small adjustments that the design team can direct without changing contract sum or time. The risk here is drift: a stack of “minor” field orders can add up to real cost, and each one signed without comment is an implied agreement that it cost nothing.

A constructive change is changed work that nobody ever formally directed — differing site conditions, a design clarification that quietly expands scope, an owner-caused acceleration. Nothing was issued. Your entitlement, if you have one, depends almost entirely on whether you gave notice.

Read your contract at the start of the job and learn which of these instruments it authorizes, who is empowered to issue each one, and what each one requires of you. The names, thresholds, and mechanics vary by agency and by contract; the general categories do not.

Notice is the whole game

If there is one operating rule worth pinning above the desk, it is this: notice protects entitlement, and nothing else reliably does.

Almost every construction contract requires the contractor to give written notice of a condition that may result in additional cost or time, within a defined period after the contractor knew or should have known about it. Miss that window and a legitimate claim can be waived on procedure alone, no matter how good the merits are. Owners and their counsel know this. It is the first defense raised in nearly every disputed change.

Practical discipline that survives audit:

Give notice in writing, through the channel the contract names. A conversation in the field is not notice. A text message to a superintendent is usually not notice either. The contract typically names a form, a recipient, and sometimes a copy requirement — use it.

Give notice early and factually. Notice is not a claim and should not read like one. It states the condition, the date it was discovered, the documents involved, and that cost and/or time impact may follow. You are not required to have the number yet; you are required to speak up.

Give notice even when you expect it to be resolved amicably. Most notices never become claims. That is the point. The cost of an unnecessary notice is a piece of paper. The cost of a missing one can be the whole item.

Log it. Notices belong in a register with the same rigor as RFIs and submittals: number, date, condition, documents referenced, response required-by date, current status, and the change instrument it eventually became.

Price the change the way the contract tells you to

Contractors regularly submit change pricing in whatever format their estimating system produces, then spend three rounds of review being told it is unreviewable.

Most public contracts prescribe how changed work is to be priced and what backup is required — typically some combination of itemized labor by trade and classification with hours and rates, material quantities with supporting invoices or quotes, equipment time at defined rates, subcontractor proposals passed through with a defined markup, and stated allowances for overhead and profit. Many also cap markups and require a specific breakdown format.

Two habits make change pricing move:

Build the proposal to the contract’s format on the first pass. Not your internal format. If the contract requires labor broken out by classification with hours and rates shown, showing a lump sum for labor guarantees a rejection and a two-week loop.

Price time separately and support it with the schedule. Cost and time are different entitlements and get reviewed by different people. A time extension request that asserts a number of days without a schedule analysis showing critical-path impact is the single most commonly rejected item in change management. If the changed work does not affect the critical path, say so and ask for cost only — credibility on that point buys you credibility when you do need days.

Wherever the contract is silent or ambiguous on pricing method, ask before you submit. That is exactly what an RFI is for, and it is far cheaper than a rejected proposal.

Never let the field get ahead of the paper

The most expensive habit in the industry is proceeding on a verbal instruction.

When someone in authority directs changed work verbally and the schedule will not wait, the move is not to refuse and it is not to simply build it. The move is to confirm the instruction in writing the same day — a short letter or email stating what was directed, by whom, when, that the contractor considers it a change, that notice is hereby given, and that pricing will follow. Then proceed under a written directive if the contract allows one.

That single same-day confirmation converts a “he said, she said” into a dated record. It is the difference between a change that gets processed and one that becomes a claim.

Two related traps:

Do not perform changed work under a pending, unsigned proposal unless the contract’s directive mechanism covers you. “We’re waiting on the paperwork” is the origin story of most unpaid change work.

Do not sign a change order with a blanket release you have not read. Executed change orders very often include language settling all cost and time impacts related to that change, including delay and cumulative impact. If time is unresolved or impacts are still developing, that needs to be addressed before signature — reserved in the change order itself, per whatever your contract and counsel allow. Signing first and arguing later rarely works.

Track the log, not just the item

A change order log is a financial control document, not a filing cabinet. At any moment it should show, for every item: the number, the originating event and date, the notice date, the instrument type, scope description, the amount proposed, the amount approved, days requested, days granted, current status, and the pay application in which approved work was billed.

Run that log against the contract sum and against your cost report every month. Three numbers matter and they are frequently out of alignment: what has been formally approved, what has been directed but not priced or approved, and what has actually been spent in the field. The gap between the second and third numbers is unfunded work in progress, and it is the quietest way a profitable job turns unprofitable.

Do not carry changes to closeout. Unresolved changes at the end of a job get resolved in the environment least favorable to the contractor — after leverage is gone, after the crews are demobilized, and after the people who remember the conditions have moved to other projects. Close items as they mature.

The bottom line

Change management is not an argument you win at the end. It is a discipline you execute from the first week: know which instrument the contract authorizes, give written notice fast and factually, price to the contract’s required format, support time with a schedule, confirm every verbal instruction in writing the same day, read releases before signing, and reconcile the log monthly against real cost.

Contractors who run that discipline are not the ones who fight harder about changes. They are the ones who rarely have to.

MODRN Inc. is a New York construction management, contract administration, and estimating firm. This article is general guidance on construction change-management practice and is not legal or contractual advice; notice periods, pricing methods, allowable markups, approval authority, and time-extension requirements are set by your contract documents and applicable law, which you should always confirm for your specific project.