The overrun you hear about a month too late

Here’s the timeline nobody writes down. In week two, a subcontractor’s labor burn crosses its budget line. The number is sitting right there in the cost codes. In week four, the PM notices while assembling the monthly cost report, and starts confirming it, because you don’t escalate a number you’re not sure of. In week five it goes into the report draft. In week six the report goes out. In week seven the owner reads it and asks what happened.

Five weeks of lag, and every person in the chain did their job correctly.

The lag is structural

Nobody sat on the number. The number just had to wait for its ride: the monthly reporting cycle, the manual export, the reconciliation against the other system that disagrees with it, the meeting where it finally gets said out loud. When data moves by hand, it moves on the calendar of the people carrying it, and everyone is carrying something else too.

The expensive part isn’t the overrun. It’s the five weeks of options that expired while the number was in transit: re-sequencing the work, a conversation with the sub while the leverage still existed, a change order while the cause was still fresh. By week seven the choices left are worse and fewer.

What “in time” actually requires

Catching it in week two doesn’t take AI predicting the future. It takes the boring thing done well: cost codes flowing from the ERP into one view automatically, compared against budget continuously instead of monthly, with a flag that fires when a line crosses its threshold, and a human deciding what to do about it.

The variance flag on our dashboards is a two-inch orange arrow. It is the single most valuable pixel we’ve ever shipped. Not because it’s clever, but because of when it shows up.