Your project manager gets a call from the client. "Hey, while you're there, can you also handle the additional blocking in the east wing? It wasn't in the original scope, but it would be really helpful."
Your PM, who values the relationship and wants to keep the client happy, says, "Sure, we can take care of that."
The crew does the work. Nobody writes up a change order. Nobody tracks the additional labor and materials. Nobody sends an invoice. The work gets buried in the project's general costs, and when the job closes out, the margin is thinner than estimated — but nobody knows exactly why.
This scene plays out on construction job sites hundreds of thousands of times per day across North America. And it's quietly, systematically destroying profitability.
The Scale of the Leak
Revenue leakage through unbilled change orders is one of the largest and least-discussed profit drains in the construction industry.
According to research by Procore and the Construction Financial Management Association:
- The average construction project experiences 35-50% more change orders than were anticipated during pre-construction
- An estimated 5-10% of total project revenue is lost to unbilled or under-billed change orders
- 75% of contractors report that tracking and billing change orders is one of their biggest administrative challenges
- The average time to process a change order from identification to billing is 21 days — during which the details become harder to document and easier to dispute
For a $15M construction company, 5-10% revenue leakage means $750,000 to $1.5 million per year in work that was performed, materials that were consumed, and labor that was paid — but never billed to the client.
This isn't money you failed to earn. It's money you earned and then forgot to collect. That distinction matters, because it means the solution isn't about winning more work or improving estimating. It's about capturing the value of work you've already done.
Why Change Orders Fall Through the Cracks
The change order leakage problem has roots in every dimension of business operations — People, Process, and Technology.
The People Dimension
Project managers avoid conflict. The PM's primary job, in their mind, is to keep the client happy and the project moving forward. Writing up a change order feels adversarial. It interrupts the flow of the relationship. So they absorb small changes — "It'll take an extra half day, it's not worth the paperwork" — without realizing that 50 small changes add up to a catastrophic margin erosion.
Field supervisors aren't trained to identify scope changes. Your superintendent knows construction. They can build anything. But can they read a contract scope section, compare it to a client request, and determine whether the request constitutes additional work? In most mid-market operations, this skill is assumed, not trained. Supers default to "just do it" because they don't want to slow down the work or look unhelpful.
The owner enables it. When the PM does push back on a change, and the client calls you directly — "Your PM is being difficult about a small addition" — what do you do? If you override your PM and authorize the work without a change order, you've just taught your entire team that billing for extra work is optional. The path of least resistance becomes the standard operating procedure.
The Process Dimension
No real-time change identification process. When a client requests additional work, the request is typically verbal — on the job site, over the phone, or in a casual email. There's no structured intake process that captures the request, evaluates the scope impact, estimates the cost, and documents the authorization before work begins.
Change order documentation is an afterthought. The work gets done first. Then, days or weeks later, someone tries to reconstruct what happened — what was the additional scope, how many hours did it take, what materials were used. By then, memories are fuzzy, time sheets have been submitted and processed, and the material receipts are buried in a pile on someone's desk.
No systematic close-out review. When a project ends, how thoroughly do you review the scope versus what was actually delivered? In most mid-market operations, the close-out process focuses on punch lists and final payment — not on whether every deviation from the original scope was captured and billed.
The Technology Dimension
Disconnected systems. The original scope lives in the contract. Daily labor reporting lives in time-tracking software. Material costs live in the accounting system. Client communications live in email. Change orders live in... where exactly? Often, they live in a Word document template that someone fills out when they get around to it.
When these systems don't talk to each other, there's no way to automatically flag when actual costs exceed estimated costs for a specific scope element — a signal that either scope changed or the estimate was wrong. Both are important to catch. Neither gets caught when data lives in silos.
No field capture tools. Your superintendent is on a job site. The client requests additional work. The super should, at that moment, be able to document the request, take a photo of the existing condition, note the scope addition, and trigger a change order workflow — all from their phone, in under two minutes. If the process requires returning to the office, logging into a desktop application, and filling out a multi-page form, it won't happen. Period.
The Anatomy of Revenue Leakage
Let me walk through a real example to show how change order leakage compounds on a single project.
A $1.2M commercial renovation project. Original contract scope is well-defined. Over the course of the 16-week project, the following happens:
Week 2: Client asks the framing crew to relocate a doorway. PM agrees verbally. Additional labor: $2,400. Additional materials: $600. Change order written: no.
Week 5: Architect issues a revised drawing showing a different ceiling height in the conference room. PM identifies it as a change but decides to "deal with the paperwork later." Additional cost: $4,800.
Week 7: During electrical rough-in, the crew discovers that the existing panel needs to be upgraded — something not identified in the original scope because the as-built drawings were inaccurate. The work is necessary to proceed. Additional cost: $8,200. Change order drafted but not submitted because the PM wants to "bundle it with other changes."
Week 10: Client requests upgraded finishes in the lobby. PM writes a change order and sends it for approval. Client approves. Amount: $12,000. This one gets billed.
Week 12: During HVAC installation, modifications are needed to accommodate existing ductwork that wasn't documented. Additional cost: $6,100. PM considers this "unforeseen conditions" and absorbs the cost rather than pushing for a change order.
Week 14: Client requests after-hours work to accelerate the schedule for three days. Premium labor rate applies. Additional cost: $9,400. PM verbally agrees. Change order: never written.
Project close-out: The $12,000 lobby upgrade gets billed and paid. The remaining $31,500 in additional costs — work that was performed, labor that was paid, materials that were purchased — is absorbed into the project's general costs. Final margin: 8.4% instead of the estimated 16.2%.
The PM reports that the project "ran over on costs." The owner assumes the estimate was bad. Nobody identifies that $31,500 in earned revenue was simply never billed.
Multiply this pattern across 30-50 projects per year, and you understand why mid-market contractors consistently underperform on margin targets.
Fixing the Leak: A Systematic Approach
The solution to change order leakage requires intervention at every level — People, Process, and Technology. And it starts with a cultural shift.
Cultural Shift: Change Orders Are Not Adversarial
The first thing to change is the mindset that billing for additional work is somehow hostile to the client relationship. It's not. Clients expect to pay for additional work. What damages the relationship is surprising them with a large change order after the work is done, or — worse — building resentment because you're absorbing costs that should be billed.
Professional change order management actually strengthens relationships because it creates transparency. The client knows exactly what they're paying for and why. There are no hidden costs, no passive-aggressive margin padding on future projects, and no end-of-project billing disputes.
Train your PMs and superintendents to frame change orders as documentation of agreed scope adjustments — a mutual record that protects both parties. Not a gotcha. Not a confrontation. A professional business practice.
Process Fix: Real-Time Change Identification
Implement a simple but non-negotiable process:
- Any request that changes scope, schedule, or cost — from the client, architect, engineer, or field conditions — gets documented immediately. Not tomorrow. Not next week. Right now.
- The documentation includes: what changed, why, estimated cost impact, and who authorized the work to proceed.
- No work begins on changed scope until the change order is documented and acknowledged by both parties. For emergency changes where work must proceed immediately, documentation happens within 24 hours.
- Weekly change order reviews during project meetings ensure nothing has slipped through. The PM walks through the previous week's activities and explicitly asks: "Did anything happen this week that wasn't in the original scope?"
Process Fix: Close-Out Audit
Before finalizing any project, conduct a scope reconciliation. Compare the original contract scope to the actual deliverables. Identify every deviation. Confirm that every deviation has a corresponding change order and invoice. This exercise typically catches 10-20% of unbilled changes that slipped through the real-time process.
Technology Fix: Mobile Change Order Capture
Give your field teams a mobile tool — it can be as simple as a configured form app — that allows them to document scope changes on the spot. Photo documentation. Voice-to-text notes. GPS and timestamp verification. The technology should make documentation easier than not documenting. If the process requires less effort than the workaround (ignoring it), adoption happens naturally.
This is the Wright Brothers thin-slice in action. Don't implement a comprehensive change management platform. Start with mobile capture on three projects. Prove the process. Refine it based on field feedback. Then scale.
The 90-Day Revenue Recovery
AnchorPoint's Protocol TRIOS for change order management:
Days 1-30: Forensic Review. Audit the last 12 months of completed projects. Compare estimated margins to actual margins. Interview PMs and supers about scope changes that occurred but weren't billed. Quantify the leakage. This number becomes the business case for change.
One AnchorPoint client — an $18M general contractor — discovered during this phase that they had failed to bill $890,000 in change orders over the previous 12 months. The owner, who had been blaming bad estimating for thin margins, realized that the estimates were fine. The billing process was broken.
Days 31-60: Process Implementation. Deploy the real-time change identification process and the close-out audit protocol. Train PMs and supers. Role-play difficult conversations with clients. Establish the "no undocumented changes" standard and back it up with management support when PMs push back.
Days 61-90: Technology and Measurement. Implement mobile capture tools. Track change order identification rates, documentation timeliness, and billing recovery. Establish weekly reporting that shows the dollar value of change orders identified, submitted, approved, and billed.
The Bottom Line
Change order revenue leakage is the most preventable profit drain in the construction industry. The work is performed. The costs are incurred. The revenue is earned. The only thing missing is the bill.
Every dollar of unbilled change order work is a dollar that moves directly from your pocket to your client's. Not because they're stealing from you — but because you're giving it away through process failures, conflict avoidance, and systems that can't keep up with the pace of real-world construction.
Fix the culture. Fix the process. Fix the technology. In 90 days, you can plug a leak that's been draining 5-10% of your revenue for years. The money is already yours. You just need to collect it.
