The forecast moves when the work does.
Original budget, approved changes, committed cost and forecast to complete on one row — 1,842 of them on a job like Tower 12. The quantity a crew installs on Tuesday is in the forecast Tuesday night, not at month end.
What it does
Every cost code carries five figures on one row: original budget, approved change, committed cost, cost to date and forecast to complete. Nothing is retyped. Commitments come from the ERP, cost to date from approved invoices and timesheets, and installed quantity from the work capture verified that period.
The forecast is remaining quantity priced at the rate the job is actually achieving, not a percentage someone felt was right. When a crew's production drops three weeks running, the line moves with it and turns before the variance becomes a conversation with the owner. Contractors running budgets this way close 11% tighter to them.
How it works
- 01
Load the cost structure
Cost codes, the original budget and open commitments come across from your ERP on the first sync and stay two-way after that. The structure stays yours — nothing is re-coded to suit the platform.
- 02
Tie quantities to codes
Installed quantities from daily logs, production tracking and capture-verified progress land against the cost code that bills them, so a line's percent complete is a measured quantity rather than an estimate of one.
- 03
Re-forecast nightly
At 23:40 the remaining quantity on every line is priced at the rate the job is running. Lines that move more than ±2.0% are flagged for the PM by 06:00 and roll into the portfolio view finance reads.
Spec
- COST LINES
- 1,842 / JOB
- RE-FORECAST
- NIGHTLY 23:40
- FLAG THRESHOLD
- ±2.0 % PER LINE
- ERP SYNC
- 2-WAY · 15 MIN
11%
Average budget variance improvement