Predictive forecasting watches every job's cost, schedule and billing as they post and calls the overrun early — with the arithmetic behind each call, and what to do about it.
Drag the week, or press play. Everything below is worked out from the cost posted by that week — nothing is hindsight.
Every open job is forecast to completion two ways: budget ÷ cost performance (what the work is costing you per unit of progress) and actual cost plus the recent burn rate carried to the completion date. When the two disagree, the job is flagged.
Fires when forecast at completion exceeds budget · Gives you the dollar exposure, the month it happens, and the cost category driving it.
Progress is read against the plan's own dates — activities past their finish date that are not complete, and jobs where cost has run ahead of the schedule. A slip is priced, not just highlighted, because extra weeks mean extra supervision, equipment and overhead.
Fires when activity dates pass unfinished or cost outruns time · Gives you the activities most exposed and their dollar weight.
Work done but not billed, receivables past sixty days, overtime premium and unapproved change orders are summed and ranked — the four ways a contractor loses money without anyone deciding to spend it.
Fires when exposure appears in any of the four · Gives you the total, the cause, and the jobs and invoices behind it.
The same job seven weeks after the flag above, in the week a month-end pack would first have shown it: two flags, one about cost, one about time, each with the arithmetic that produced it — the drivers named, and a probability behind the call.
Caught in week 5, that is a conversation — resequence the trades, chase the change order, put the crew somewhere else. The month-end pack shows it in week 12, by which point another $959,000 has gone out of the door.
A single number hides the risk. Every open-job forecast is resampled by our frontier models across the variance in labour productivity, cost and schedule dates — trained on proprietary construction cost data — so the answer is a range and a probability, not a guess.
Every prediction is arithmetic on your own numbers, not a black box: the forecast at completion is your cost performance carried forward, the schedule flag comes from your own activity dates, the range comes from resampling the job’s own history — and every figure arrives with its working attached, so a project manager can check it against the job in seconds.
That is what makes an early call actionable. A flag takes five minutes to review; a missed overrun costs the margin. Customers receive an accuracy report that tracks every flag the platform raised against how the job actually finished — and that same rigour is what ConstructBench, our construction benchmark, will publish against the leading general-purpose models.
Hosted for you or self-hosted, read-only, every user included. Connected and reconciled against your own reports in a single 90-minute session.