Nobody acted on it.

It had been in the report for a month. That is the failure this week is about, and it is the most common one in the trade: not a report that was wrong, a report that was right and changed nothing.

Why it is not a writing problem

The temptation is to conclude that the warning was not clear enough, or not loud enough, and to write it in bold next time.

That rarely works, because the reason nothing happened usually has nothing to do with the sentence. It is that the report said a thing was going to be a problem without saying what anybody was supposed to do about it, who was supposed to do it, or what it would cost if they didn't. A statement of fact doesn't create an obligation.

Somebody reading it can agree with every word and still have nothing to act on.

And there is a second reason, less comfortable. A risk raised every week for a month stops sounding like a warning and starts sounding like background. The repetition that feels like diligence to the person writing it feels like noise to the person reading it.

What a report is competing with

The people who could act on that line are reading it alongside twenty other things, most of which are already on fire. A ten-page document arriving on a Monday doesn't get read in order. It gets skimmed for whatever the reader is currently worried about.

So the middle of page six is not a place where decisions happen, regardless of what is written there. That is not carelessness on the reader's part. It is what happens to any long document sent to somebody with a full day.

Moving the decisions to the front

What I found helped — not solved, helped — was to stop lengthening the report and start rearranging it.

The items that needed a decision went to the first page. Not the summary of progress, not the curve. Three questions, in plain language: what decision is needed this week, who has to take it, and what happens if it is not taken.

The effect was modest and real. Those items came up earlier in meetings and came up more often. It didn't resolve every one of them, and plenty still sat there for weeks. What it changed was the chance of an important item being missed entirely, which is a smaller claim than solving the problem and a more honest one.

The mechanism is not mysterious. A named person with a named consequence is harder to leave alone than a paragraph describing a situation.

The report that proves it later

Here is the part that makes the whole thing worth doing even when nobody acts.

The line in the report didn't change anything at the time. Months later it is the reason the delay can be explained, and it is the difference between a claim that is supported and one that is asserted. Claims Week 6 sets out why the contemporaneous record carries the weight it does. This is where that record is either created or not, on an ordinary Monday when the warning is being ignored.

So the answer to a report nobody reads is not to stop writing it. It is to write it knowing it has two jobs on two timescales — to change a decision this week, and to be the evidence a year from now

— and to accept that it will often fail at the first while doing the second perfectly.

Where this leaves the trade

Twenty-five weeks of this track have been about one thing: a number arrives from somebody, it means something specific, it closes on a particular day, and it can be checked against a record produced for another purpose.

None of that matters if the report built from it changes nothing. The last skill is the one that is hardest to teach and easiest to recognise — writing so that a person who is busy, sceptical and already behind can see what they are being asked to decide.

A planner who assembles accurate numbers that nobody acts on has done most of the job. The remaining part is not more data.

System design

The first page of a report is the only page that reliably gets read. What goes on it decides whether the document changes anything.

Record	Produced by	Required quality	Verified against	Feeds
Decision needed	Project controls	A request, not a description of a situation	The underlying data	The meeting
Owner	Project controls	A person who can take it	Organisation	Follow-up
By when	Project controls	A date the consequence is measured against	The programme	Escalation
If not taken	Project controls	The cost of doing nothing, stated	Schedule and cost impact	Whether anybody acts
The report itself	Project controls	Specific enough to be read as evidence later	The records behind it	Delay analysis, claims

Four columns and rarely more than three rows. It doesn't make people act. It reduces the chance that something important is read as background and left alone.

Practical insight

Open your last four weekly reports side by side and look for a line that appears in all four.

There will usually be one. When you find it, ask three questions of it. Does it say who has to act? Does it say by when? Does it say what happens if nobody does?

If the answer to all three is no, the item was never a request. It was a note, repeated four times, and the person you needed was reading it as background. Rewrite that one line as a decision with a name and a date, put it at the top of next week's report, and see whether anything different happens.

Sometimes nothing does. But you will have found out something useful either way, which is whether the problem was the message or the room.

Key takeaways

• The common failure is not a wrong report. It is a right one that changed nothing.
• A statement of fact creates no obligation. A decision with an owner and a consequence does.
• A warning repeated weekly stops reading as a warning and starts reading as background.
• Long documents are skimmed for whatever the reader is already worried about. Page six is not where decisions happen.
• Moving the decisions to the first page reduces the chance of an item being missed. It doesn't make people act.
• An ignored warning still does the second job: it is the contemporaneous record that explains the delay later.
• Accurate numbers that change no decision are most of the work and not the whole of it.

Records born here. Decision page · action list with owners and dates · the report itself, as the contemporaneous record.

What is coming next

This track assumed one thing throughout: that every record you chased belonged to the same project, under one contract, with one chain of command.

What follows is where that assumption stops holding — when the scope sits with another company, when the critical path runs through somebody else's purchase order, and when the number you are reconciling has two owners in two organisations who both produced it correctly.