Monthly projectcontrols report
Five spreadsheets are not a status.
A monthly project controls report is the single document that pulls cost, schedule, change, cash, and risk into one dated read of where a job actually stands. Each of those normally lives in its own spreadsheet, on its own cycle. Assembled to one period cut, the weakest of the five has nowhere to hide.
The capstone of project controls
Every other controls discipline produces a number. The budget produces a variance, the schedule a forecast finish, the change log an exposure, the billing a cash position, the risk register a contingency balance. The monthly project controls report is the discipline that takes those five numbers, cuts them to the same date, and turns them into one honest sentence about the job.
Its whole purpose is contrast. A cost report read alone can look calm while the schedule is quietly losing weeks. A schedule update read alone can look recoverable while absorbed changes are eating the margin that recovery would need. Put the five beside one another, scored the same way, and the weakest one becomes the first thing a reader sees rather than the last thing they find.
This is written from the controller's side of the table, after two decades of assembling these reports by hand: the reconciliation is the work, the formatting is not.
Five scattered reports vs one assembled report
The information already exists on most jobs. The problem is that each piece is written for a different reader, on a different cycle, and goes stale at a different rate. Nobody is reading all five on the same day.
| Report | What it shows | Who reads it | How stale it gets |
|---|---|---|---|
| Cost report | Budget, actual, committed, forecast by line | PM, accounting | Closes two to three weeks after period end |
| Schedule update | Activity status, float, forecast finish | Scheduler, superintendent | Whenever the scheduler last statused it |
| Change order log | Approved, pending, and absorbed change | PM, owner rep | Current in the log, rarely reconciled to the budget |
| Billing and cash | Billed, earned, retained, collected | Accounting, finance | Runs on the pay application cycle |
| Risk register | Open risks, contingency balance | PM, sometimes no one | Quarterly at best |
| Project controls report | All five, cut to one date, scored against baseline, weakest first | Owner, executive, PM | One dated cut per period, never restated in silence |
Cadences reflect common practice on commercial and industrial jobs; your cycles may differ, and that is the point. The assembled report is the only row with one date.
A worked example
Period end, five dimensions scored against their baselines. Cost 82: actual and committed are tracking the budget with a modest overrun forecast on one division. Schedule 71: the critical path has given up three weeks against the baseline finish and the recovery plan is not yet resourced. Change 88: the log is clean, pending value is small and mostly priced. Cash 79: billing lags earned by about a period and retainage is building. Risk and Quality 90: contingency is drawing down in step with retired risk and there are no open nonconformances.
Rolled up, that is a composite health of 82, trend stable. An executive reading only the composite sees a normal month. An owner reading only the cost report sees a normal month. The scheduler, who knows about the three weeks, has already sent the update and moved on.
The assembled report leads with Schedule 71 because it is the lowest of the five, and it carries the forecast beside the status: if the three weeks are not recovered, the cost score moves next, then cash. The number did not change. What changed is that it was placed next to four others and could no longer pass for ordinary.
How the report assembles
Five scored streams enter from the left and converge into one sealed panel. Four of them move at the same pace. Schedule 71 runs amber, moves slower, and is flagged as the weakest once the composite resolves. That is the report doing its one job: the eye lands on the dimension that needs a decision.
Assembling it, in four moves
The report is not a template to fill. It is a reconciliation with a fixed order of operations, and skipping any one of the four produces a document that looks finished and is not.
Choose the period end and state cost, schedule, change, cash, and risk as of that day. A cost figure from the 31st beside a schedule from the 14th describes two different jobs.
Cost against budget, schedule against the baseline finish, change against the approved log, cash against earned, risk against the contingency plan. Express each as a score a reader can compare across the five.
The lowest score opens the report, with the cause and the action. This month that is Schedule at 71. The reader meets the problem before the summary, not after a search.
Every status figure travels with where it is heading: estimate at completion, forecast finish, pending change exposure, projected contingency at the finish. Status is history; the forecast is the decision.
The same month, scored: Cost 82, Schedule 71, Change 88, Cash 79, Risk and Quality 90, composite 82 and stable. The gauge is the executive's view of the report. The dimension bars underneath it are the reason the executive should keep reading.
Monthly controls health
- Start at the lowest bar, not the big number. Schedule 71 is the month. Everything else is context for it.
- Ask what the weakest dimension does to the others. Three unrecovered weeks pull cost down next period and cash the period after.
- Treat a stable trend as a question. Stable across five dimensions can mean one improved while another slid. Look at the bars, not the arrow.
- Check the strongest for false comfort. Risk and Quality at 90 is welcome. It does not offset a schedule problem; the two are not fungible.
Four ways the report lies
A cost report, a schedule PDF, a change log, and a billing summary bound into one file is a binder, not a controls report. Nothing has been reconciled, and each still carries its own date.
Cost closed on the 31st, schedule statused on the 14th, change log pulled this morning. The reader sees one document and assumes one moment. The figures disagree, and no one can say why.
Health 82 reads as a good month. Inside it sits Schedule 71. A roll-up that averages a weak dimension away has removed the one thing the report was built to surface.
When a prior period is quietly revised to make this month look level, the trend is gone. Corrections belong in the report, dated and explained, never absorbed into history.
Chasing five inputs vs having them ready
Most of the time spent on a controls report is not spent writing it. It is spent finding the cost close, waiting for the schedule status, pulling the change log, reconciling billed to earned, and locating whoever last touched the risk register. The report is late because its inputs are.
- ·Five sources, five owners, five cut dates to chase down
- ·Cost is reconciled to the change log in a spreadsheet nobody else can open
- ·The schedule score arrives whenever the scheduler statuses the file
- ·The weakest dimension is whichever one the author noticed last
- ·Budget, committed, actual, and change orders held on one per-project controls hub
- ·Contingency and the earned value measures update as data is confirmed
- ·Schedule status and slip against the planned finish sit beside the cost figures, not in another file
- ·When the period closes, the five inputs are already on the same page
POD's project controls hub keeps cost, schedule, committed, change-order, contingency, and EVM figures current per project as data is confirmed, and POD sends monthly reports built from those figures. Assembling the sealed monthly project controls report is the discipline this guide describes; the hub is what keeps every input ready to assemble when the period closes. It draws on earned value management for the cost and schedule scores, the WIP schedule for cash, and the wider project controls discipline for the rest.
The dimensions, one guide each
The pillar guide: the full discipline this report sits at the end of, from budget to earned value.
Where the cost and schedule scores come from: CPI and SPI, and what they do and do not tell you.
The cash dimension in full: billed against earned, and the over- or under-billed position.
The change dimension: recovered, pending, and absorbed value, and what each does to the forecast.
The risk dimension: whether the contingency balance is tracking the risk that is actually left.
Why the schedule score should be stated in days, and how a late job fools classic SPI.
Project controls report questions
What is a project controls report?▾
A project controls report is the periodic document, usually monthly, that brings cost, schedule, change, cash, and risk together into one dated statement of where a construction project stands. Each of those dimensions is normally tracked in its own system on its own cycle. The report cuts all of them to the same date, scores each against its baseline, and states plainly which one needs attention first.
What should a monthly project controls report include?▾
At minimum: budget against actual and committed cost with the estimate at completion; schedule status against the baseline with the forecast finish; the change log split into approved, pending, and absorbed; the cash position including billed, earned, and retained; and the risk register with the contingency balance. Every figure should carry the same period cut date, and the report should open with the single weakest dimension rather than burying it.
Who reads the project controls report?▾
The owner or their representative, the executive sponsor, and the project manager are the primary readers, and each reads it for a different decision. The owner wants to know whether the commitment still holds. The executive wants to know which jobs need intervention. The project manager uses it to see the whole position at once instead of five partial ones. A good report serves all three from the same page.
How is a project controls report different from a cost report?▾
A cost report covers one dimension: budget, actual, committed, and forecast cost. A project controls report holds that alongside schedule, change, cash, and risk, all cut to the same date, so the interactions are visible. A cost report can read fine while the schedule is slipping and the change log is filling with absorbed work. Only the assembled report shows that the cost figure is about to move.
How often should a project controls report be issued?▾
Monthly is the standard cadence because it lines up with the billing cycle, the cost close, and most schedule updates, which means all five dimensions can be cut to the same date. Weekly is common on fast or troubled jobs for the schedule and change dimensions alone. What matters more than the frequency is that every issue carries one dated cut and is never quietly restated afterward.
How does POD help with the monthly project controls report?▾
POD keeps the figures a project controls report is built from current on a per-project controls hub: budget, committed and actual cost, change orders, contingency, schedule status, and the earned value measures, each updated as data is confirmed. POD also sends monthly reports from those figures. Assembling the sealed report is the discipline this guide describes, and the hub is what keeps every input ready when the period closes.
Keep the five dimensions current between reports
Start with the free budget tracker, then let POD hold cost, schedule, change, contingency, and earned value on one per-project hub, so the monthly assembly begins from figures that are already reconciled.