After twenty years of writing monthly reports — and sitting on the other side of the table reading them — I can tell you the uncomfortable truth: most project reports are written to be sent, not to be read. They get skimmed for thirty seconds, filed, and forgotten. Then everyone acts surprised in month eight when the delay that was buried on page eleven becomes a crisis.
A good report does one job. It tells a busy person what changed, what it means, and what you need from them. Everything else is decoration.
Start with the verdict, not the story
The first thing your reader should see is the status: on track or not, and by how much. Not the project background. Not the weather summary. The verdict.
“Progress 62% against a plan of 68%. We are 4% behind, driven by late glass delivery. Recovery plan in place, expected back on plan by end of September.”
Three sentences. Your director now knows more than most reports manage in ten pages. If they read nothing else, the report already worked.
Every number needs a partner
A number on its own means nothing. “We installed 2,656 m² of cladding” — is that good? Nobody knows. “We installed 2,656 m² against a planned 2,900 m²” — now it means something.
This is the single most common failure I see in subcontractor reports: actuals without baselines. Progress without plan. Cost without budget. If your report shows a number, show what it was supposed to be next to it.
Bad news goes at the top, with a price tag
There is a strong temptation to soften problems — mention the delay quietly in the narrative, hope it resolves before anyone asks. This always backfires. Always. The problem surfaces eventually, and when it does, the question won’t be “why is there a delay?” It will be “why didn’t you tell us?”
Report problems early, plainly, and with numbers attached: what happened, the impact in days and money, what you’re doing about it, and what you need. That last part matters most. A problem reported without an ask is just complaining. “RFI-009 has been unanswered for 12 days; every further week delays skylight fabrication by a week — we need the consultant’s response by Thursday” gives your reader something to act on. Now the delay is a shared problem, on the record, with a date.
Keep the same skeleton every month
Readers develop muscle memory. When the finance manager knows the payment position is always in section 4, she finds it in five seconds. Change your structure every month and you force everyone to re-learn your report — so they stop trying.
My skeleton has been the same for years: status summary, progress against plan, commercial position, issues and asks, next period, photos. The content changes; the bones never do. It also makes the report faster to write, because you’re filling a form, not composing an essay.
Respect the cut-off
Pick a data date and hold it. Everything in the report reflects the project as of that date — not “roughly this week,” not numbers from three different days stitched together. Mixed cut-offs produce reports that contradict themselves, and a reader who catches one contradiction stops trusting every other number.
Photos are evidence, not decoration
Two or three photos, each with a caption that states location and date, showing the work you claimed. A progress photo with “L14 north elevation, 18 July” under it supports your 87%. Ten random site photos support nothing.
The one-page test
Before sending, ask: if my reader only sees page one, do they know the status, the biggest problem, and what I need from them? If not, rearrange until they do. The appendices can run to any length — the report itself is page one.
None of this requires talent. It requires structure and discipline, which is good news, because structure can be templated. That’s exactly why every report template in the Project Mate library opens with a status summary and pairs every actual with its plan — the format does the discipline for you, and you fill in the month.