Prefer to listen?
This article is also available as a podcast episode
Most construction projects run informally. The client gets updates in meetings, progress is discussed on site visits, problems surface through phone calls and email chains, and the overall picture of where the project stands at any given moment is assembled from multiple sources, none of which is comprehensive or reliable on its own. This informal approach works reasonably well when things are going smoothly. When they are not — when programme slippage is accumulating, costs are drifting or risks are materialising — the absence of structured reporting means that problems are identified late, decisions are made without complete information and interventions that could have been timely are reactive and expensive.
Without a formal monthly report, projects typically run on a series of informal updates — calls, emails, site visits — where the information shared is selectively positive and the picture the client receives is incomplete. Problems accumulate out of sight until they become serious, at which point they are much harder and more expensive to address. A formal monthly report changes this dynamic by creating a structured, regular checkpoint that forces transparency.
Why a Monthly Report Is Not a Nice-to-Have
A monthly progress report does several things at once. It creates a regular rhythm of review that keeps the project team focused on performance. It gives the client an accurate picture of the project — good or bad — rather than the filtered version they get from informal updates. It creates a written record of the project’s status at each point in time, which is invaluable if disputes arise later. And it forces the project manager to actually analyse the project’s performance, not just manage day-to-day activity.
The Anatomy of a Good Monthly Progress Report
A good monthly progress report follows a consistent structure that covers all the key project dimensions. The exact format will vary depending on the project type and the client’s preferences, but the following sections are standard.
Executive Summary
The executive summary is a one-page overview of the project status: where the project is in its lifecycle, whether it is on programme and within budget, what the key issues are and what decisions are required. It should be written for a reader who does not have time to read the full report — a board member, an investor, a senior stakeholder. The executive summary is the most read part of any project report; make sure it is accurate, concise and clearly written.
Programme Status
The programme status section should compare the current programme against the baseline — what was planned versus what is being achieved. It should identify any areas of slippage, the cause of that slippage and the actions being taken to recover. It should give a clear assessment of whether the current completion date remains achievable. Where the programme has been revised, the revision should be documented and the reason for it explained.
Cost Position
The cost position section reports the current forecast outturn cost against the approved budget. It should cover the contract sum, approved variations, anticipated further variations, contingency drawn and remaining contingency. The aim is to give the client a clear picture of where the project stands financially — not just whether it is within budget, but by how much and with what risks. This section should be produced in conjunction with the cost consultant or quantity surveyor where one is appointed.
Risk Register Summary
The risk register summary should report on the current top risks to the project — typically the five to ten most significant live risks — with their current likelihood and impact ratings, the mitigation actions in place, and any changes since the last report. This section is not a complete risk register — it is a management summary that keeps risk visible to the client without overwhelming them with detail.
Issues and Change
The issues and change section records the current status of open issues — matters under discussion, claims being assessed, disputes in progress — and summarises any change control activity during the reporting period: variations instructed, compensation events assessed, or budget adjustments made. This section should be factual and specific, avoiding vague language like ‘under discussion’.
Decisions Required
The decisions required section is one of the most important in the report, and one of the most often omitted. It sets out the decisions the client or relevant stakeholders need to make in the next reporting period — approval of a variation, selection of a material, sign-off on a revised programme. Without this section, decision requirements tend to emerge informally and at short notice, creating pressure and sometimes leading to poor decisions.
Lookahead
The final section of the report should set out the key activities planned for the next four to six weeks — the lookahead. This helps the client understand what to expect and prepares them for any decisions or actions that will be required from them in the coming period. It also provides a basis for the next report: the activities in this month’s lookahead become the baseline against which next month’s progress is assessed.
This Is What We Deliver as Standard
Every client of JC Virtual PMs receives a monthly progress report as a standard deliverable. We cover programme status, cost position, risk, issues and decisions required — giving you the clarity you need to make good decisions and protect your project.
This is exactly what we deliver as standard on every project.
JC Virtual PMs provides comprehensive monthly progress reporting as a baseline deliverable — giving you clear, honest visibility of your project at every stage.
Leave a Reply