Construction Change Order Management: A Step-by-Step Process

Construction change order management is the process of identifying, pricing, approving, and documenting changes to a project's original scope so the work gets done and you actually get paid for it. A change order is a written agreement that modifies the contract, adjusting the scope, the price, the schedule, or all three. Manage them well and changes become a normal, profitable part of the job. Manage them badly and they turn into unpaid work, disputes, and margin you never recover.

The money you lose on change orders is rarely lost at pricing. It's lost in the gap between doing the work and documenting it. Here's a process that closes that gap.

What is a construction change order?

A change order formally amends the contract when something differs from the original scope: an owner-requested addition, a design change, an unforeseen site condition, or a discrepancy in the documents. It records what changed, what it costs, and how it affects the schedule, with sign-off from the parties.

The key word is written. A verbal "yeah, go ahead and do it" is how contractors end up performing extra work they can't bill for. No signed change order, no defensible claim to payment.

Why do change orders cost contractors money?

They cost money when the field performs the work before the paperwork catches up. Here's the trap: an owner asks for a change, the super doesn't want to hold up the crew, so the work gets done on a handshake. Weeks later, when you try to bill it, the owner disputes the price or denies they approved it. Now you're either eating the cost or fighting for it.

The other silent cost is scope creep: a series of small, undocumented changes that never individually seem worth a change order, but collectively erode the budget. Catching and documenting changes while they're small is how you protect the margin.

The construction change order process, step by step

1. Identify the change

Recognize when something falls outside the original contract scope. This requires a clear understanding of what the contract actually included, which is why clean original estimates with documented inclusions and exclusions matter so much. Anyone on the team, super, PM, or foreman, should know to flag a potential change.

2. Document and price it

Capture what changed and price the impact: added labor, material, equipment, subcontractor cost, plus markup and any schedule impact. Price it the same disciplined way you'd price a bid, with backup you can defend.

3. Submit for approval before doing the work

Send the change order request to the owner or GC for written approval before performing the work whenever possible. This is the step contractors skip under field pressure, and it's the one that protects you most. If the situation is a genuine emergency, document it immediately and get written confirmation as fast as you can.

4. Get written sign-off

A change order isn't real until it's signed. Track whose court it's in and follow up, because an unsigned change order aging on someone's desk is unbilled work and a schedule risk. This ball-in-court discipline is the same one behind good RFI management.

5. Log it and update the contract

Record the approved change in your change order log, update the contract value and schedule, and make sure billing reflects it. The log is your running record of every change and where it stands.

6. Execute and bill

Now the work proceeds, and it gets billed on the next progress invoice. The loop is closed: changed, priced, approved, documented, built, paid.

What does a change order log track?

A change order log is the single source of truth for every change on the project. At minimum it should track:

Field	Why it's there
CO number	Unique ID for the change
Description	What changed, in plain language
Date submitted	When the request went out
Amount	Cost impact of the change
Schedule impact	Days added or affected
Status	Pending, approved, rejected, or void
Ball in court	Who owes the next action
Date approved	When sign-off came back

Like an RFI or submittal log, the value isn't the list, it's the status. The log should tell you at a glance how much change-order value is pending approval and how much is aging.

Common change order management mistakes

• Doing the work before approval. The single most expensive habit in the business.
• Verbal agreements. If it isn't signed, it didn't happen as far as payment goes.
• Slow pricing. A change order that takes two weeks to price is two weeks of either stalled work or unbilled risk.
• Letting approvals age. Unsigned COs sitting in someone's court are unbilled work.
• No log. If changes live in scattered emails, you lose track of what's owed.
• Ignoring small changes. Scope creep is death by a thousand cuts.

Who should manage change orders?

The project manager owns the judgment: pricing strategy, negotiation, and which changes to push on. But the administrative side, drafting the change order, maintaining the log, tracking ball-in-court, and chasing signatures, is high-volume, time-sensitive work that's easy to delegate. A project admin virtual assistant can keep the change order log current and the approvals moving so nothing ages into lost revenue, while the PM stays focused on the field and the negotiation.

This pairs with the rest of your project documentation. The same discipline that keeps your submittal log and RFI log honest keeps change orders from leaking margin.

The bottom line

Change orders aren't a problem. Undocumented change orders are. Identify changes early, price them with backup, get written approval before the work when you can, and log every one. The contractors who treat change order management as a disciplined process instead of an afterthought get paid for the work they do and keep the margin they earned.

If change orders are slipping through the cracks on your projects, tell us about your workflow and we'll map the admin support that keeps them documented and paid.