April 2026
Your project shows $500K in variance. How much of that is a real overrun and how much is approved scope changes? If you can't tell, it's costing you money.
Here's a scenario you've probably lived through. Your PM tells you a project is $500K over budget. You feel that familiar sinking feeling. You schedule a meeting. You pull up the cost reports. You start asking hard questions.
Two hours later, your PM explains that $350K of that $500K is approved change orders. Extra work the owner asked for and agreed to pay for. The real overrun is $150K.
Congratulations. You just spent two hours and a lot of stress on a problem that wasn't the problem you thought it was. And worse, you probably missed the problem that actually matters.
Change orders and cost overruns both show up as variance. That's where the confusion starts. But they're completely different situations that require completely different responses.
The owner asked for something that wasn't in the original scope. You priced it, they agreed, and now you're doing that work. The money going out is matched by money coming in. Your budget went up because the scope went up. That's not a problem. That's business.
You're spending more than you estimated for the same scope of work. Something is wrong. Maybe your labor productivity is off. Maybe a supplier is overcharging. Maybe rework is eating into your margin. The money is going out, but no money is coming in to match it. That's the real problem. That's where margin disappears.
Your cost report treats these exactly the same. Both show up as variance. Both make the project look "over budget." But one of them is fine and one of them is bleeding money. If you can't tell them apart in real time, you're either panicking about nothing or ignoring something serious.
When your team can't separate change orders from real overruns, two things happen. And both of them cost you money.
You waste time on fake problems. A project that looks $500K over gets emergency attention from you, your PM, and possibly the owner. You spend hours figuring out what's happening. You have tense conversations. You question your team. And then it turns out most of it was approved work. You just burned a week of attention on nothing.
You miss real problems. More dangerous. A project shows $200K in variance. Your PM says "most of that is change orders." You move on. But nobody actually separated them. Turns out $180K of that $200K was a real overrun. Hidden inside what looked like approved scope. That problem runs for another two months before someone finally digs into it. By then it's $400K.
Both of these happen constantly. Not because anyone is doing anything wrong. Because the tools don't make the distinction automatically.
Procore doesn't separate them automatically. Sage doesn't separate them automatically. Spreadsheets definitely don't separate them automatically. Every one of these tools shows you budget, actual, and variance. That's it.
To actually split change orders from overruns, someone has to manually track every approved scope change, apply it to the right cost codes, and recalculate the true variance. That's a job that takes hours, and most PMs don't have hours. So it either doesn't get done or it gets done wrong.
And when the VP asks "how much is real?" the honest answer is usually "I'll get back to you." By the time they do, the project has moved on.
You should be able to look at any project, any cost code, any day, and see three numbers:
That third number is the only one that matters for margin. That's the number that tells you whether you're making money or losing it. Every other number is noise.
When the distinction is automatic. Real-time, no manual work, updated every day. The conversations change completely.
You stop asking "is this project over budget?" Because you already know. You start asking "is this project actually losing margin?" Which is the real question.
Your PMs stop spending Friday afternoons reconciling spreadsheets. Your accountants stop chasing change order approvals at month-end. Your bonding company gets cleaner reports. Your owner conversations get easier because you can actually prove what's a change and what's not.
And most importantly. Real overruns stop hiding inside approved variance. They get caught early, when they're still cheap to fix.
Here's the math. If even one real overrun per year gets hidden inside change order noise and runs unchecked for 6 weeks, you're looking at an extra $100K to $300K in waste that could have been caught in week one.
Multiply that by the number of active projects and the number of times it happens. Most GCs we work with find $500K+ per year in overruns that were hiding in plain sight. Not because nobody was looking, but because nothing was separating the signal from the noise.
Our tools separate change orders from true cost overruns automatically. Every project. Every cost code. Every day. The second you look at a dashboard, you already know which number actually matters.
We'll show you exactly where the real variance is. And what's just change order noise. If we don't find at least 2% in cost recovery, you don't pay.