Monthly Reporting: That Actually Tells You Where the Money Is

The Report Nobody Reads

I have written hundreds of monthly project reports. And I have been honest enough to admit that most of them were not as useful as they should have been. They reported on concrete pours completed, subcontractor progress, and programme status in detail that nobody at governance level needed. The critical information was buried on page 14 under a heading called "Commercial Summary." The project director had to hunt for it.

The standard monthly report is structured around activities. What did the team do this month? How much concrete was placed? How many RFIs were processed? What percentage of the steelwork is complete?

None of that answers the question the person reading the report actually has. The project director is not reading the report to find out how much concrete was placed. They are reading it to find out whether the project is going to finish on time, on budget, and without a dispute. The standard report structure does not help them answer that question quickly.

A monthly report that takes more than 15 minutes to tell a project director where the money is, where the risk sits, and what needs a decision has failed at its primary purpose.

What the Report Should Answer

A useful monthly report answers five questions. Everything else is supporting detail.

1. What is the financial position?

Not just "expenditure to date." The full picture. Original contract sum. Approved variations. Pending variations with a probability-weighted estimate. Forecast to complete. Contingency status. Variance against the approved budget. If the project is trending over budget, the report says so clearly and explains why. If the cost trajectory has changed since last month, the report says by how much and what caused it.

The financial section should fit on one page. If it does not, the data is not being presented well.

2. What is the programme status?

Is the project on track against the current baseline programme? Not the original programme submitted under Clause 9.2.1 of NZS 3910, but the current working programme. What is on the critical path this month? Are there any delay events that have been notified under Clause 13.5? What is the forecast completion date based on current progress, not the date the contract says?

If the programme has slipped, the report needs to say by how much and what the impact is on cost and completion. If an extension of time claim is pending, the report needs to flag the likely time and cost outcome.

3. What is the commercial position?

How many variations are approved, pending, and disputed? What is the total value of each category? What is the status of the current payment claim? Are there any Construction Contracts Act deadlines approaching? Is there a claim or potential claim that the governance board needs to know about?

The commercial section should include a one-line summary of every variation over a set threshold. The detail can sit in the variation register. The report gives the headline and the direction of travel.

4. What are the top risks?

Not the full risk register. The top five risks that are currently active and require attention. Each one with a current status, a mitigation action, and an owner. If a new risk has emerged since the last report, it goes here. If a risk has materialised into an issue, it moves to the commercial or programme section with a clear cost and time impact.

5. What decisions are needed?

This is the section most reports miss entirely. A useful report tells the reader what they need to do. "Approve the variation for the additional piling at $180K." "Decide whether to instruct the accelerated programme option at $320K to recover the three-week delay." "Confirm the approach to the contractor's extension of time claim before the response deadline on 28 March."

The most important section of any monthly report is the decisions section. If the report does not tell the reader what they need to decide, it is a status update, not a management tool.

Why Reports Get Bloated

Reports get long because the team writing them confuses completeness with usefulness. They include everything because they are worried about leaving something out. They describe activities in detail because that is what they spent their month doing. They attach photographs because it fills pages and looks thorough.

The result is a document that protects the report writer but does not serve the report reader. The project director receives a 35-page PDF. They scan the executive summary. They skip to the financial table. They look at the programme bar chart. They miss the paragraph on page 22 that mentions a potential claim the contractor flagged in a site meeting. They close the report and move on to the next project.

The information was in the report. It was just buried. And when it surfaces three months later as a formal claim, the project director says "why didn't I know about this?" The answer is: it was in the report. But the report did not make it visible.

Building a Report That Works

A good monthly report has a clear structure that stays consistent from month to month. The reader knows where to find each piece of information. The format does not change. The language is direct. The data is interpreted, not just presented.

• One-page executive summary. Financial position, programme status, top risks, decisions required. This page alone should give the project director 80% of what they need.
• Financial dashboard. Contract sum progression, cash flow forecast vs actuals, contingency drawdown, variation value by status. Visual. One page.
• Programme summary. Current progress, critical path activities, delay events, forecast completion date. One page.
• Commercial register. Variations, claims, payment claims, CCA compliance status. One to two pages.
• Risk and decisions. Top five active risks. Decisions required with deadlines and recommended actions. One page.
• Supporting detail. Activity reports, photographs, subcontractor updates, H&S statistics. These are appendices for anyone who wants to go deeper. They are not the report.

Total core report: five to six pages. Supporting appendices as needed. A project director reads the core report in 15 minutes and knows exactly where the project stands.

The best monthly reports are the shortest ones. Not because they contain less information, but because every sentence earns its place on the page.

Reports That Feed Forward

The final test of a good report is whether it feeds forward. Does this month's report connect to last month's? Are the risks that were flagged last month resolved or escalated? Are the decisions that were requested last month confirmed? Is the financial trajectory moving in the direction the last report predicted?

When reporting is done properly, each monthly report builds on the previous one. The project director can track the story of the project through the reports. They can see when a risk was first identified, how it was managed, and what the outcome was. That continuity is what turns reporting from an administrative obligation into a genuine management tool.

Most projects produce reports because they have to. The good ones produce reports because they are useful.