The Complete Guide to Change Order Tracking in Construction (2026)

Change order tracking is how a construction team records, prices, approves and accounts for every change to a contract's scope, cost or schedule, from the moment it's raised to the moment it's paid. Good tracking means anyone on the project can answer three questions at any time: what changed, what it costs, and who's holding it up.

Most teams still track change orders in spreadsheets and email threads, with each company keeping its own copy. That's where approvals stall, numbers drift apart and disputes start. This guide covers what to track, the statuses and metrics that matter, a step-by-step process for managing change orders, and how to reduce change order delays in 2026.

What is change order tracking?

Change order tracking is the ongoing record of every proposed and approved change on a construction project, including its cost, schedule impact, status, owner and supporting documents. It turns individual change orders into a live view of how the contract value and budget are moving.

A few related terms come up in every change order conversation:

• Change order (CO): a signed amendment to a construction contract that changes its scope, price or schedule.
• Potential change order (PCO): a change that has been identified but not yet priced or approved. Some teams call it a change event.
• Change order request (COR): the priced proposal a contractor or trade submits for approval.
• Construction change directive (CCD): a written order from the owner to proceed with a change before the price is agreed.
• Change order log: the register that lists every PCO, COR and approved change order on a project, with its status and value.

Why change order tracking matters

Every untracked change is a cost the budget doesn't know about yet. When change orders are tracked well, the owner sees committed exposure before it becomes an overrun, the general contractor gets paid for work it has already done, and trades aren't left carrying unapproved costs for months.

Poor tracking shows up the same way on most projects:

• Budgets fall behind reality. Approved changes sit in an inbox instead of on the budget line, so forecasts are wrong.
• Work starts before approval. A trade proceeds on a verbal OK, then the price is disputed later.
• Numbers don't match between companies. The owner, owner's rep, GC and trade each keep their own log, and the totals drift apart.
• Nobody knows who's holding a change. Without a clear status and owner, a change order can wait weeks for a signature no one knew they owed.

What to track on every change order

A useful change order log holds the same core fields for every change, so the team can sort, filter and report on them. At a minimum, track:

1. Number and title: a unique ID and a short description of the change.
2. Origin: what triggered it, such as an RFI, a design revision, an owner request or a field condition.
3. Linked contract and budget line: which commitment and cost code the change affects.
4. Cost impact: the proposed amount, the negotiated amount and the approved amount.
5. Schedule impact: days added or removed, if any.
6. Status: where the change sits in the approval process (see the table below).
7. Ball in court: the company and person who needs to act next.
8. Dates: when it was raised, submitted, approved and billed.
9. Backup: pricing, quotes, drawings, photos and the RFI or directive behind it.

Change order statuses to use

Keep statuses simple and consistent across the project, so every party reads them the same way.

Status	What it means	Who usually acts next
Identified (PCO)	A possible change has been raised but not priced	Contractor or trade, to price it
Pricing	The trade or GC is preparing cost and schedule impact	Trade, then GC
Submitted (COR)	The priced request is with the reviewer	GC, owner's rep or owner
Under review	Reviewers are checking scope, pricing and backup	Owner's rep or design team
Approved	Signed and added to the contract value	Finance, to update budget and billing
Rejected or revised	Sent back with comments, or withdrawn	Submitting party
Billed	Included in a pay application	Owner, to pay

How to manage construction change orders: 7 steps

Change order management is the process around the log: how a change is raised, priced, approved and paid. These seven steps work on most commercial projects. For a deeper walkthrough of each step, see How to Manage Construction Change Orders in 7 Steps.

1. Set change order terms in the contract. Agree markups, pricing backup, approval limits and response times before work starts.
2. Log the change as soon as it's identified. Create a PCO the day an RFI answer, design revision or field condition creates new scope, even before it's priced.
3. Price the cost and schedule impact. The trade or GC submits a change order request with labor, material, equipment, markup and any schedule days, plus backup.
4. Review and negotiate. The owner's rep or owner checks scope and pricing against the contract and sends questions back on the same record.
5. Approve in writing before work proceeds. Use a signed change order, or a construction change directive when work can't wait for final pricing.
6. Update the contract, budget and forecast. The approved amount should move the revised contract value, the budget line and the forecast at once, not at month end.
7. Bill and close out. Include approved changes in the next pay application and reconcile the log at closeout so nothing is left open.

How to reduce change order delays in construction

Change order delays rarely come from the change itself. They come from the handoffs: a request waiting in an inbox, missing backup, or a reviewer who doesn't know it's their turn. Our post on how to reduce change order delays goes deeper, but these habits cut the most waiting:

• Make "ball in court" visible. Every change should show who needs to act next, so a stalled approval is obvious.
• Submit complete packages the first time. Pricing breakdown, quotes, drawings and the originating RFI should travel with the request. Missing backup is a common reason a change order gets sent back. See why subcontractor change orders get cut for what reviewers look for.
• Set approval thresholds. Let smaller changes be approved at the project level, and route only larger ones to executives or the owner's board.
• Agree response times in the contract. A set review window gives everyone a date to work to.
• Link changes to RFIs early. When an RFI answer creates new scope, log the potential change at that moment, not when the invoice arrives.
• Work from one shared record. Every re-keyed spreadsheet or emailed PDF adds a handoff and a chance for the numbers to drift.

Change order cost control for owners

For owners and developers, a change order isn't only a contract amendment. It's money leaving the contingency, and sometimes a funding source that has to be redrawn. Cost control starts before construction, in the contract, and continues every month at the pay app.

Before construction: set the rules in the contract

• Markup limits: cap overhead and profit on changes, separately for the GC and each tier of subcontractor.
• Unit rates: agree labor rates, equipment rates and unit prices for likely changes up front, so pricing isn't negotiated under schedule pressure.
• Notice and pricing deadlines: require written notice of a potential change within a set number of days, and complete pricing within another.
• Approval thresholds: decide who can approve what. For example, the owner's rep approves small changes, and anything above a threshold goes to the owner or the investment committee.
• No work without approval: except for documented emergencies, no changed work starts before a signed change order or a written directive with a not-to-exceed amount.

During construction: review every change the same way

1. Check the origin. Owner request, design error or omission, unforeseen condition, or contractor-caused. The origin decides who pays, and design errors may be recoverable from the design team.
2. Check the backup. Labor hours and rates, material quotes, equipment and markup, each against the contract's terms.
3. Check for duplicates. Make sure the scope isn't already in the base contract, an allowance or an earlier change.
4. Check the schedule impact. Agree on time at the same time as cost, so it doesn't come back later as a delay claim.
5. Approve by threshold, and record who approved what and when.

Every month: watch the exposure, not just the approvals

• Contingency remaining, and how fast it's being used compared with progress (is your contingency drawdown faster than construction?)
• Pending exposure: the value of potential changes not yet approved, so the forecast shows them before they're signed
• Changes by origin, to spot a pattern of design changes or owner requests early
• Funding: which source pays for each approved change, so draws don't stall (funding source tracking)
• Pay app reconciliation: only approved changes should appear on the GC's pay app, at their approved values

Owner's reps often run this review for the owner. See how owner's reps and owners and developers use INGENIOUS.BUILD to keep change orders, contingency and funding on the same record, and how approved changes feed the portfolio forecast in Capital Planning.

Spreadsheets vs connected change order tracking

How you track change orders matters as much as what you track. Here's how the three common setups compare.

	Spreadsheets and email	Software with a separate account per company	Connected workspaces
Where the log lives	One file per company, emailed around	Each company's own account	Each company's own workspace, connected live
How a change moves	Attachments and email chains	Uploads, exports or re-entry between accounts	Submitted from one workspace to the next, live
Budget updates	Manual, often at month end	Manual for anyone outside the account	Approved changes update the contract, budget and forecast
Who's holding it	Unclear	Visible inside one company only	Visible to every party with access
Version control	Several copies, often different totals	One copy per company	One shared record, with each party's own view

How INGENIOUS.BUILD tracks change orders

INGENIOUS.BUILD gives every company on a project its own workspace, and the workspaces connect live, with no uploads, exports or email chains. A change order moves from the trade to the GC to the owner's rep and the owner as one record. When it's approved, the linked contract, budget line and forecast update right away, and everyone with access sees the new numbers.

In Project Financials, teams route, review, approve and track change orders while seeing their cost impact on contracts, budgets and the forecast. Contracts show original values, approved changes and revised totals for every commitment.

In Construction Administration, RFIs link straight to Project Financials, so when an answer carries a cost, the impact flows to the owner's rep with the RFI behind it.

Every party, with the right access. Role-based permissions mean trades see their own change orders, pay apps and contracts without opening up the rest of the project, while owners see the full picture. External collaborators are free for the projects you invite them to, so trades can submit change orders from their own workspace.

AI built in, MCP in Pro. INGENIOUS.BUILD includes built-in AI for every user, including change order OCR, so the numbers on a change order document are read in rather than retyped. Built-in AI also reads invoices, drawings, contracts and budgets, and AI email summaries send a daily or weekly digest of your unread notifications: what you missed and what needs your attention. Through the native MCP server, included in Pro, you can connect your own AI, such as Claude or ChatGPT, to live project data within each user's permissions.

INGENIOUS.BUILD uses transparent, per-user pricing billed annually, with unlimited projects. See your per-user rate in the pricing calculator.

Change order tracking metrics to watch

A change order log becomes useful for decisions when you report on it. Track these across a project or portfolio:

• Total approved changes vs original contract value, by contract and for the whole project.
• Pending exposure: the value of PCOs and CORs not yet approved.
• Approval cycle time: days from submission to approval, by reviewer.
• Changes by origin: design revisions, owner requests, field conditions or RFIs.
• Open changes at closeout: anything not yet approved, billed or reconciled.

For a wider view of cost reporting, see the construction cost tracking guide.

Final thoughts

Change order tracking works when every change is logged early, priced with backup, approved in writing and reflected in the budget the moment it's signed. The biggest gains in 2026 come from removing handoffs: when the trade, GC, owner's rep and owner work from one connected record, approvals stop waiting in inboxes and the budget stays current.