Writing it is the easy part
Ask what takes the time in a monthly report and most people will say the report. The curve, the tables, the narrative, the slides.
Those take an afternoon. What takes the last days of the month is reaching a figure that more than one department will stand behind.
That is the real work, and it is invisible from outside, which is why the monthly report is chronically underestimated by everybody who doesn't produce one.
Where the time actually goes
Collection is slow but predictable. The unpredictable part is what happens when the collected records don't agree, which is most months.
The site quantity doesn't match the surveyed one. The cost report closed on a different date. A late delivery note changes the material position. Each of these needs a conversation with the department that owns the record, and the conversations can't be parallelised because the answer to one changes the next.
This is the routine from Week 8 and the reconciliation from Week 25, compressed into three or four days. Which is the argument for spreading it: the more of it that happens weekly, the less of it lands at month end.
Everybody gets it, nobody reads all of it
The monthly goes to a wide distribution and each reader opens it at a different page.
Senior management reads the summary and stops. The project manager reads the indicators. Department heads read their own section and glance at the rest. The client reads progress, milestones, risks and anything about delay, in that order.
Which means the document is really five documents bound together
, and the parts most people never reach still have to be right — because the one month somebody does turn to page eleven is the month something has gone wrong.
It also means the summary is not a summary. It is the report, for most of its readers, and it deserves the time that implies. Week 20 deals with how to do that without producing five different stories.
The narrative is the part that ages
Charts are read in the month they are issued. The narrative is what somebody reads two years later
, trying to establish what was known and when.
That gives it a second job, and it changes how it should be written. A sentence saying progress was below plan due to various factors is useless in both roles. A sentence naming the cause, the affected activities and what was done about it is useful now and evidence later.
It costs nothing extra. It is the same length. The difference is specificity, and the reason it is usually missing is that specific sentences are harder to agree in the last two days of the month, which brings us back to where the time goes.
Adding rather than replacing
If you are setting the process up, fix the cut-off and agree the reconciliation before the report rather than during it, and keep the summary to one page that can be read alone.
Inherited: the report is probably too long and nobody will let you shorten it. The realistic move is to change the front rather than the whole. Make the first page carry the decisions, the exceptions and the changed dates, and let the rest stay as it is. Length is a habit and it is hard to break. Order is a choice and it can be changed next month.
System design
The report is the last step. What decides whether it can be produced is when the reconciliation happens.
| Record | Produced by | Required quality | Verified against | Feeds |
|---|---|---|---|---|
| Collected data | All departments | Complete by the cut-off, in agreed units | Reporting calendar | Reconciliation |
| Agreed figure | Project controls with owners | Signed off by the record holders, not adjusted alone | Corroborating records | Every document that month |
| Narrative | Project controls | Cause, activities affected, and response — not “various factors” | The variance causes | Now, and delay analysis later |
| Summary page | Project controls | Readable alone, because for most readers it is the report | The detail | Management decisions |
Move as much of row two into the weekly cycle as will go. Whatever is left is what the last days of the month are for, and it can't be compressed by working faster.
Practical insight
Time yourself for one cycle. Record hours spent on collection, on reconciliation, and on producing the document.
Most planners are surprised by the proportion, and the number is useful for two arguments: it justifies the resource, and it shows exactly which of the three would benefit from being moved earlier in the month.
Almost always it is the middle one, and almost always it can be spread into the weekly cycle at no extra cost.
Key takeaways
- Producing the document is an afternoon. Agreeing the number takes the last days of the month.
- Reconciliation can't be parallelised, because each answer changes the next question.
- The more reconciliation happens weekly, the less of it lands at month end.
- Everybody receives the same report and each reader opens it at a different page.
- For most readers the summary is the report, not a summary of it.
- The narrative is what gets read years later. Specific sentences are useful now and evidence afterwards.
- On an inherited report, change the order rather than the length. Length is a habit; order is a choice.
Records born here. Monthly report · the agreed figure and who agreed it · the narrative, which is read twice and years apart.
What is coming next
One document, several readers, several levels of detail — and the risk of telling each of them something slightly different.
Next week: four audiences, four altitudes, and one set of numbers.
Enjoyed this lesson?
Join with Google to get each new lesson the moment it's published — and help me see which topics matter most to you. No spam, one email a week, unsubscribe anytime.
Already following on LinkedIn works too — this is just for the weekly email.