What Belongs in a Monthly Project Report (and What Doesn't)
Sponsors do not read long reports. Here is the one-page-plus-appendices structure that respects their time and keeps decisions moving.
Project names, parties and commercially sensitive figures referenced in this article have been anonymised or generalised. Examples reflect real situations encountered across multiple projects; they are not attributed to any specific client, contractor or contract.
A monthly project report exists to support decisions, not to demonstrate effort. If your sponsor has to read past page one to find the headline, the report has failed. The thirty-page reports most PMOs produce are read by no one and trusted by no one — the volume itself is the signal that the team is hiding behind the data.
Page one: status (RAG), the three numbers that matter (CPI, SPI, VAC), the three risks that matter, and the three decisions you need from the sponsor this month. That is it. The discipline of fitting it on one page is the discipline of working out what actually matters. If everything matters, nothing does.
Everything else — narrative, photos, schedule extract, cost detail, risk register, change log — sits in numbered appendices. They are there for anyone who wants to drill down, not as a wall to climb. Most appendices are read by exactly one person — the project services lead — and that is fine. They are an audit trail, not a communication device.
RAG status only works when the criteria are explicit. Green means CPI > 0.95 and SPI > 0.95 with no top-three risks materialising; amber means one of those is breached; red means more than one. Without explicit criteria RAG status becomes a political negotiation and the sponsor stops trusting it.
The three decisions section is the lever. By forcing the team to articulate three specific decisions needed from the sponsor this month, you turn the report from a description into a request. The sponsor's job becomes clearer; the steering meeting becomes faster; decisions get made on a 30-day cadence rather than a 90-day one.
Send the report 48 hours before the steering committee, with a one-paragraph cover note. The cover note is the elevator pitch: project state, key signal, decision sought. The meeting then becomes about the three decisions, which is what the sponsor is paid for. The temptation to walk through the report in the meeting is the temptation to waste 45 minutes on context the sponsor has already absorbed.
Common report failure modes: narrative that reports activity rather than outcome; RAG status driven by team feeling rather than criteria; risks copy-pasted from last month with no updates; decisions buried as 'noting items'. Each of these can be fixed by editing discipline, not by more data.
If you only change one thing about your current report, change the order. Put the three decisions on page one, above the RAG. The act of writing them first will sharpen the rest of the report and make the meeting genuinely useful.
Construction project manager (PMP, MCIOB) with 20+ years on infrastructure, commercial and industrial builds across the GCC and NZ. Writes about the controls, contracts and field practices that actually move projects.
Read full bio →