What change order overruns look like on property projects
A change order is a written amendment to a construction or service contract that changes its scope, price or schedule, and a change order overrun is the gap between the approved project budget and the contract value once those amendments are added.
Capital projects in real estate have a poor track record on budget. In KPMG's global construction survey, project owners said only 31% of their projects came within 10% of budget.[1] Change orders are not the only cause, but they are the part an owner can see coming, because each one needs someone's approval.
Picture a lobby and amenity refresh in a 200-unit multifamily building. The contractor finds rotted subfloor under the old tile. The architect swaps a light fixture that went out of stock. The asset manager asks for an extra EV charger. Each change is agreed in a site meeting or an email thread and seems small on its own. The finance team sees them only when the pay application arrives, and by then the contingency is spent twice over.
CFO / Finance Leader
Learns about overruns from the monthly pay application, long after the work was agreed and done.
"Who approved all this, and when?"Development or Project Manager
Approves field changes quickly to keep trades moving and tracks them in a personal spreadsheet.
"If I wait a week for sign-off, the crew goes home."Asset Manager
Has to explain to investors or owners why a budget approved at committee grew without a vote.
"I need the forecast at completion, not last month's actuals."AP Manager
Receives pay applications with line items that do not match any approved change or PO.
"Is this extra in the contract or not?"Are change orders pushing your projects over budget?
Tick every statement that is true today. Three or more means the problem is likely costing you real money.
Six root causes behind change order overruns
Change orders are normal on building work. The overrun comes from how they are captured, priced and approved. These are the patterns we see most in development, renovation and capex programs.
Approval happens in the field, not in the system
Site teams agree changes verbally to avoid delay. The paperwork follows weeks later, so finance only learns of the commitment after the money is already spent.
No single running total per project
Pending, approved and rejected changes sit across email, the contractor's log and a project manager's spreadsheet. Nobody sees the cumulative figure against budget.
Approval limits apply per change, not in total
A project manager may approve anything under $10,000. Twelve changes under that limit add up to a six-figure overrun that no senior person ever reviewed.
Changes are priced without a baseline
Once a contractor is on site, competition is gone. Without the original schedule of values and unit rates at hand, change pricing is hard to challenge.
Reporting tracks paid cost, not committed cost
Monthly reports show what has been invoiced. Approved but unbilled changes are invisible, so the forecast at completion always looks better than reality.
Scope was loose when the contract was signed
Allowances, exclusions and unclear drawings guarantee changes later. Many change orders are the cost of decisions deferred at the bid stage.
What uncontrolled change orders cost an owner
Published research shows how often building projects miss budget, and how change orders add to contract value even on well-run jobs.
The direct cost is the added contract value, often priced without competition because the contractor is already on site. The indirect costs follow: contingency spent on avoidable changes and not available for real surprises, lender or investor draws that need to be reopened, delayed completion that pushes back lease-up or rent start, and finance time spent reconstructing who approved what when the final account is disputed. An average change of around 4% sounds small until it lands on a project where the contingency was already committed.[2]
Estimate your change order exposure
Enter your figures. Nothing is stored or sent anywhere.
The expert playbook: six practices that keep change orders inside budget
None of these needs new software to start. A shared log and clear approval limits will catch most of the problem. The order matters: visibility first, pricing discipline second, payment controls last.
"At KPMG I worked on procurement transformation programs where the approval policy looked perfect on paper. The problem was always the route. If the site manager has to email three people and wait, the change gets agreed on a handshake. Make logging and approving a change faster than the handshake, and the running total takes care of itself."Md. Kafil, Co-founder and CEO, Zapro. Former senior product specialist on SAP Ariba Network and procurement transformation manager at KPMG.
Keep one change order log for every project
Set cumulative approval limits, not just per-change limits
Price changes against the original bid
Report committed cost and forecast at completion
Match pay applications to approved changes before payment
Tighten scope before the next contract is signed
"In every system I have built, the expensive errors came from commitments that lived outside the system until the invoice arrived. A change order is a promise to pay. If it only becomes visible when the contractor bills it, finance is reading history. Capture it when it is agreed, and the forecast starts telling the truth."Daniel Sagayaraj, Co-founder and CTO, Zapro. Previously built and ran supplier onboarding and payments for a 15,000-supplier marketplace at Voonik.
How Zapro keeps change orders visible from site to payment
Zapro treats each change as a request with an owner, a value and an approval path, linked to the contract and the budget, so the project total updates when the change is agreed rather than when it is billed.
| Root cause | Zapro capability | What changes |
|---|---|---|
| Approval happens in the field | Procurement: purchase requests and "Prompt to buy" with Z1 | Site teams raise a change from a phone in plain language, and Z1 drafts the request with value and reason. |
| Limits apply per change, not in total | Approval workflows with role-based access control | Changes route by value and role, so larger items reach finance or the asset manager before work begins. |
| No single running total | Spend Analytics with budget tracking | Committed and paid spend per project and category in one dashboard, so the overrun shows while it is still small. |
| Changes priced without a baseline | Contract Management with version tracking | The original contract and every amendment sit in one place, so the agreed rates are at hand when a change is priced. |
| Unapproved extras get paid | AP Automation with PO and receipt matching | Invoices are captured and matched to approved POs and receipts, and anything outside them is flagged as an exception. |
Zapro syncs vendors, accounts and payment status with your ERP or accounting system, so project budgets in Zapro match the ledger your finance team closes on. See Zapro integrations.
A 30, 60, 90 day plan
Days 1 to 30: Count it
- List every active project and its approved budget
- Collect pending and approved changes into one log
- Calculate forecast at completion for each project
- Agree reason codes for changes
Days 31 to 60: Control it
- Set per-change and cumulative approval limits
- Require pricing against contract rates
- Start weekly committed cost reporting
- Pilot on the two largest live projects
Days 61 to 90: Hold it
- Roll out to all projects and capex programs
- Match every pay application to approved changes
- Review change reasons with the design team
- Update scope templates for the next bids
KPIs to track progress
| KPI | How to calculate | Review |
|---|---|---|
| Change order rate | Approved change value divided by original contract value | Monthly, by project |
| Pending change exposure | Total value of changes raised but not yet approved or rejected | Weekly |
| Contingency remaining | Contingency budget minus approved and pending changes | Weekly, by project |
| Forecast at completion variance | Forecast final cost minus approved budget | Weekly |
| Retroactive approvals | Share of changes approved after the work had started | Monthly |
| Unapproved billing caught | Value of billed items held for missing change approval | Each pay cycle |
Go deeper with our guide to procurement KPIs.
What a Zapro customer saw after moving this work into one workflow
"Implementing Zapro improved our vendor coordination significantly, leading to a substantial reduction in costs and faster vendor onboarding."Akhil Sikri, CTO, Zolo
Why Zapro for this challenge
Change order overruns are a timing problem: the commitment is made on site and the number reaches finance weeks later. Zapro closes that gap by putting every change, its approval and its budget impact in the same record from the day it is raised.
The contractor relationship in one record
Contract, amendments, POs and invoices sit against the same vendor, so the history of every change is there when the final account is negotiated.
Z1 does the checking
Zapro's AI layer reads requests, matches invoices and flags risk, so project teams spend less time chasing paperwork.
Budgets by project and property
Spend Analytics tracks budget and spend by project, category and vendor across your portfolio.
Unlimited users on every plan
Site managers, project managers and finance can all use the same workflow without per-seat cost, starting at $699 per month.
When Zapro may not be the right fit
- You run one small renovation a year with a single contractor. A shared spreadsheet and a signed change order form may be all you need.
- You need full construction scheduling, drawing management or BIM coordination. Zapro handles approvals, contracts, budgets and invoices, and works alongside dedicated construction project tools.
- Your general contractor manages all change control under a guaranteed maximum price and you only see a monthly summary by design.
Frequently asked questions
What is a change order in construction and real estate?
A change order is a written amendment to a construction or renovation contract that changes the scope of work, the price, the schedule or all three. Common reasons are unforeseen site conditions, design changes and owner requests made after the contract was signed.
What percentage of change orders is normal on a project?
It depends on project type, contract form and how complete the design was at bid stage. Renovations of older buildings tend to see more change than new builds with complete drawings. The more useful measure is your own trend by project type and the share of changes that were avoidable.
Who should approve change orders?
The project or development manager usually approves small field changes up to a set limit. Larger changes, and any change that pushes cumulative approvals past a share of contingency, should go to finance or the asset manager. Owner-requested changes should be approved by whoever holds the budget.
How do you stop change orders from exceeding the budget?
Log every change the day it is raised, price it against the original contract rates, set cumulative approval limits, and report committed cost weekly instead of paid cost monthly. Then check every pay application against approved changes before payment.
Do we need software to control change orders?
Not to start. A shared log and clear approval limits fix the worst gaps. Software such as Zapro helps once you run several projects at once, have site teams approving in the field, or spend finance time matching pay applications to changes by hand.
About the experts behind this page
Sources
- KPMG via PR Newswire, Construction Project Failures Weigh on Industry Despite Advances in Planning and Controls: KPMG Survey, 2015
- AIA Contract Documents, The Truth About Change Orders, research note
Editorial note: this page is published by Zapro, which sells procurement software. Best practices are written to work with any tool, and figures are cited to their original publishers. Last reviewed 29 September 2026; next review due March 2027. See how the Procurement Challenges Directory is researched and reviewed.