The PM Dashboard: Real-Time Budget vs. Actual

Why a monthly job cost report is too slow

A traditional job cost report is built from posted invoices and payroll — both of which lag the actual work by weeks. A crew that started falling behind on cost code 16-120 on a Monday will not show up as a problem on the job cost report until the payroll and material invoices for that period are posted, coded, and rolled up, which is often three to five weeks later. By then the PM has lost three to five weeks of runway to fix it — change the crew mix, adjust the method, or flag a change order — and instead is explaining an overrun that already happened.

The fix is not a faster accounting close. It is separating the two questions a job cost report tries to answer at once: what did we commit to spend (accounting's job, and it should stay accurate and auditable) and what does the field say we're actually doing (a field-ops question that can be answered same-day). The PM dashboard is built around the second question.

What feeds the dashboard

• •Cost-coded daily reports: every foreman's hours and quantities land against a specific cost code the day they're logged, not at month-end.
• •Committed costs: approved purchase orders and subcontracts post as committed cost against the budget the moment they're issued, not when the invoice arrives.
• •Vendor invoices and expenses: actual costs post as they're entered, coded to the same cost codes as the budget.
• •Change orders: approved COs post their cost-code breakdown into the budget immediately, so the budget total updates in step with the scope.
• •Payroll: labor hours and burdened cost roll up by cost code from the same field data used for daily reporting.

Budget vs. actual, cost code by cost code

The dashboard's core view is a line-by-line comparison of budgeted cost, committed cost, actual cost to date, and the variance, for every cost code on the job — not just a single job-level total. A job can look fine in aggregate while one cost code is bleeding and another is running under, and those two errors can hide each other in a lump-sum view. Breaking it out by code is what lets a PM catch the one trade or scope that is actually the problem, instead of discovering it only once it has dragged the whole job negative.

Alongside dollars, the dashboard tracks the productivity factor (PF) — actual hours per unit of work against the budgeted hours per unit — and turns it into a productivity index the PM can watch trend week over week. A PF above 1.0 for more than a week or two on a given cost code is the earliest possible warning that a crew, a method, or a scope is running hot, well before the dollar variance would show it.

S-curve and cost-to-complete

The <a href="/features/pm-dashboard">S-curve</a> plots planned vs. actual cost (or earned value) over the life of the job, giving a visual read on whether the project is ahead, on pace, or falling behind its planned burn rate — a shape that is much faster to interpret at a glance than a table of numbers, especially in a project review with an owner or GC.

Cost-to-complete (CTC) takes the current productivity trend and projects it forward against the remaining scope, producing an estimate-at-completion (EAC) that is more honest than simply assuming the rest of the job will suddenly hit budgeted rates. If a cost code is running 15% over on productivity with 60% of the scope still ahead, the CTC forecast reflects that continuing trend rather than resetting to plan — which is the forecast a PM actually needs to decide whether to intervene now.

Why this replaces the spreadsheet reconciliation

The typical alternative is a PM keeping a personal spreadsheet, pulling numbers from field reports, POs, and whatever accounting has posted, and reconciling it by hand every week or two — a real job in itself, done on top of actually running the project. Because Field PM's dashboard is built from the same cost-coded data as the daily reports, POs, and change orders rather than a separate export, that reconciliation step disappears; the dashboard is the report, updated continuously instead of assembled periodically.