Construction Reporting: Why Monthly PDF Reports Arrive Too Late

It is the first Tuesday of the month, and the project manager on a $45M aged-care build in Melbourne opens the monthly report PDF. Forty-two pages. Twelve charts. A cover page with the project logo. The cost summary shows forecast final cost sitting $180,000 above the approved budget. She scrolls to the programme section. Two activities are flagged amber. One has already turned red since the data was pulled, but the report does not know that yet. The numbers in front of her are three weeks old.

She picks up the phone.

The monthly report is structurally too slow

This is not a failure of effort. The commercial team spent two days assembling the report. They pulled cost data from the finance spreadsheet, programme updates from the scheduler’s laptop, safety stats from the site management system, and RFI status from an email thread. They formatted it, reviewed it, sent it to the project director for sign-off, and released it on the first of the month.

The problem is the rhythm. A monthly reporting cycle means every decision-maker on the project works from data that is, on average, two to three weeks behind reality. On a fast-moving build with weekly subcontractor claims and daily programme shifts, three weeks is not a minor lag. It is the difference between catching a cost variance at $30,000 and discovering an overrun at $300,000.

Only 31% of construction projects came within 10% of budget over the past three years

KPMG Global Construction Survey

KPMG’s Global Construction Survey found that only 31 percent of projects came within 10 percent of their original budget, and just 25 percent finished within 10 percent of their original deadline.[1] The same survey found that while 73 percent of executives expressed confidence in the accuracy and timeliness of their project reports, independent benchmarks showed those self-assessments were consistently a full tier above reality. The industry believes its reporting is better than it is.

Why the lag persists

The reporting delay is not laziness. It is architecture. On a typical Australian construction project, cost data lives in one system (or a spreadsheet), the programme lives in another, safety records sit in a third, and quality and correspondence run through email and shared drives. Nobody is withholding information. The information simply does not live in the same place.

Research by FMI and Autodesk found that construction professionals spend 35 percent of their working week, over 14 hours, on non-productive activities: searching for project data, resolving conflicts caused by bad information, and fixing avoidable mistakes.[2] Nearly half of all rework traces back to poor communication and poor project information. The monthly report is a symptom. The root cause is disconnected data.

“Construction ranks among the world’s least digitised sectors. In the United States, construction ranks second to last on digitisation indices, while Europe places it in last position.”

McKinsey Global Institute, Reinventing Construction Through a Productivity Revolution[3]

14 hrs/wk

time construction professionals spend on non-productive activities like searching for project data

FMI/Autodesk

What it costs when reporting lags behind reality

Consider a real scenario. A subcontractor on a $25M commercial fit-out submits a variation claim for additional electrical rough-in, triggered by a design change issued three weeks earlier. The variation is legitimate, but the project manager does not see the cost impact until the monthly report lands. By then the work is complete, the labour hours are spent, and the negotiation leverage is gone. A claim that could have been managed at $40,000 in week two is now $120,000 in week six, with back-charges and delay costs layered on top.

This pattern repeats across every trade package. Prolongation costs, including site overheads, supervision, and plant hire, continue to run regardless of whether anyone has noticed the programme has slipped. On a project running $800,000 a month in preliminaries, every week of undetected delay costs $200,000. Multiply that across multiple active variations and an ageing programme, and the margin erosion that most builders experience becomes inevitable.

$200K/wk

approximate cost of undetected delay on a project running $800K/month in preliminaries

What a construction project dashboard should actually show

The answer is not a better PDF. It is a different reporting model entirely. A project dashboard that updates in real time, pulling from every active system on the project, replaces the monthly snapshot with a continuous picture. The question shifts from “what happened last month” to “what is happening now.”

A useful construction dashboard shows five things at a glance:

• Committed cost versus forecast final cost, updated as every subcontract, variation, and purchase order is approved, not when someone re-keys it into a spreadsheet

• Programme variance, with real-time task completion feeding directly from site, so a slipped activity shows up the day it slips, not three weeks later

• Open RFIs and non-conformance reports, with ageing and response times visible, so a stalled RFI does not quietly push the programme

• Safety metrics, including incident rates, open corrective actions, and overdue inspections, updated as site teams record them

• Cash flow position, comparing forecast revenue against actual cost curves month by month

The difference between a monthly report and a live dashboard is not polish. It is decision-making speed. McKinsey’s research estimates that simultaneous digital transformation across project delivery could unlock 50 to 60 percent productivity gains across the industry.[3] Most of that gain is not about new technology. It is about getting existing information to the right person before the window for action closes.

Vanity metrics versus actionable metrics

Not all dashboards are equal. A report that shows total invoices processed, percentage of programme complete, or cumulative safety hours is reporting activity, not performance. These are vanity metrics: they look healthy even when the project is bleeding margin.

Actionable metrics answer a different question. Not “how much have we spent” but “how much are we going to spend.” Not “how far through the programme are we” but “are we going to finish on time, and if not, which activities are driving the delay.” Not “how many safety inspections have we done” but “how many corrective actions are overdue.”

The shift from vanity to actionable reporting is the shift from backward-looking to forward-looking. A cost report that only shows actuals-to-date tells you what has already happened. A forecast that shows committed cost, approved variations, and projected final cost tells you what is about to happen, in time to do something about it.

The Australian context

The scale of the problem is not small. Infrastructure Australia’s 2025 Market Capacity Report puts the major public infrastructure pipeline at $242 billion over five years, a 14 percent increase from the prior year.[4] The Australian Bureau of Statistics tracks over $60 billion in quarterly construction work done nationally.[5] The Australian Constructors Association has called construction productivity “among the worst” of any sector, noting that raising it to the national average would restore productivity growth to levels not seen since the 1990s.[6]

These are not theoretical numbers. Every dollar of that pipeline flows through project reports. When those reports arrive three weeks late, decisions are three weeks late. On a $242 billion pipeline, even a fractional improvement in reporting speed translates to billions in avoided rework and recovered margin.

Where Plexa fits

The reason most construction dashboards require manual assembly is that the data lives in separate systems. Cost is in one tool. Programme is in another. Quality, safety, correspondence, and procurement each have their own platform, their own login, and their own update cycle. Someone has to pull from all of them, reconcile the formats, and paste the result into a PowerPoint.

Plexa is built differently. Because every module, Finance, Program, Quality, Correspondence, Site Management, and Procurement, lives inside one connected platform, the dashboard is not assembled. It is live. When a variation is approved in Finance, the forecast updates. When a task slips in Program, the programme variance updates. When a non-conformance is raised in Quality, the defect count updates. No export. No re-keying. No three-week lag.

That project manager in Melbourne should not be opening a 42-page PDF on the first Tuesday of the month to discover a cost variance that started three weeks ago. She should be looking at a dashboard that showed the variance on the day it was approved, with the forecast already adjusted, the programme impact already flagged, and the related RFI already linked. The information was always there. It just needed to live in the same place.

Related reading

The margin pressure that late reporting creates is explored in depth in why construction profit margins keep getting tighter. The case for consolidating project data into one system is the subject of the single source of truth in construction management. And for a broader view of where construction technology in Australia is headed, including the tools that are replacing the monthly PDF, that post maps the landscape.

If you want to see what a live project dashboard looks like on a real build, book a 30-minute demo with the Plexa team.