Why one-page updates end up three pages, and the four decisions that get them back to one.
Everyone who writes a one-page update writes three pages first. That is not a problem — it is how writing works. The problem is what happens next.
People edit the sentences. They tighten the phrasing, cut adverbs, merge clauses. The page comes down from 1,400 words to 1,150 and stays three pages, because length is not a writing problem. It is a decision problem, and no amount of editing prose will solve a decision you have not made.
Four things are almost always doing it.
You know the reader already knows the context. You include it anyway, because leaving it out feels like assuming.
Assume. If they need it, they will ask, and the asking takes eleven seconds against the ninety seconds it costs every reader who did not need it.
The test is not "would this be useful?" — almost anything is arguably useful. The test is "would the reader make a different decision without this?" Background almost never passes that test, because by definition it is the part they already have.
A dashboard of twelve metrics is a way of not saying which one is in trouble.
It feels rigorous. It is actually the opposite: you have handed the reader the job of working out which number matters, which is the job you were supposed to do. Three numbers and a sentence about why beats twelve numbers and no sentence, every time.
If you cannot get below five, you have not decided what the report is for. A report about whether the project will land on time needs different numbers from a report about whether it will land on budget, and a report that tries to do both does neither.
"We ran eleven workshops" is effort. "The design is agreed and the build starts on the 14th" is a result.
Effort belongs in the appendix. Results belong on the page.
This is the hardest of the four, because the effort was the hard part. Those eleven workshops were genuinely difficult and it feels unfair not to mention them. But the reader is not assessing your week — they are deciding something, and effort does not help them decide.
The exception is when the effort is the result: if the point of the update is that a consultation happened and now everyone is bought in, then the consultation is the news. Say that explicitly rather than listing the sessions.
Here is a real sentence, of a kind that appears in most status reports:
We are broadly on track, though there are some challenges in a couple of areas which we are working through.
Thirty words that commit to nothing. Compare:
On track except the data migration, which is three weeks late and needs a decision on scope by Friday.
Twenty-two words that commit to something, and it is the one the reader can act on.
Hedged sentences are always longer than direct ones, so cutting the hedging cuts the length for free. But the reason people resist it is not concision. It is that a direct sentence can be wrong, and a hedged one cannot. "Broadly on track" is unfalsifiable. That is precisely why it is worthless.
Once the four decisions are made, the shape is nearly automatic:
Everything else is an appendix, and an appendix is fine. The discipline is about the first page, not about destroying information.
Read the finished page and ask: what would I do differently having read this?
If the answer is nothing, the page is not short enough yet — and tightening the prose will not fix it, because the problem is that you have not yet decided what you are asking for.
The [One-Page Report Builder](/products/one-page-report-builder.html) is this structure as an Excel and Word template, with a worked example filled in so you can see what a good one looks like rather than inferring it. £19. The blank version is [free](/free.html).