Reports and documents people actually read

A report that begins with background and arrives at the recommendation on page nine has been organised for the writer's convenience rather than the reader's.

The inversion

The single most valuable structural change.

Conclusion first, then the reasons, then the evidence.

Which is how journalism works and how most professional writing does not.

The reasoning: readers have different depths of interest, and this structure lets each stop where they choose while getting the essential content.

A reader who stops after the first paragraph should still know what you are recommending and why.

The executive summary

Which is usually written badly.

It should state the recommendation, the reasons, and what happens if it is not adopted.

It should be readable alone, without reference to the body.

It should be one page.

It should not be an introduction, a description of the process, or a table of contents in prose.

And it should be written last, since it is a summary rather than a preview.

Structure that can be scanned

Since most documents are scanned rather than read.

Headings that state the content rather than label it: "Costs exceed the budget by 12%" rather than "Costs".

Which means the headings alone convey the argument.

Short paragraphs, one idea each.

The point of each section in its first sentence.

Bullets for anything genuinely enumerable, and not for prose broken into fragments.

And white space, which is not wasted space.

Recommendations

Which are frequently too vague to act on.

State who does what by when.

State the cost.

State what is being given up, since every recommendation has a trade-off and concealing it damages credibility.

State the decision required, specifically: approve, allocate, defer.

And separate recommendations from options, since a list of options with no recommendation pushes the work back to the reader.

Evidence

How to present it.

The point first, the data supporting it second.

Charts with the finding in the title: "spending rose 12% in Q3" rather than "quarterly spending".

One point per chart.

Tables only where the individual numbers matter, since a table where only the trend matters should be a chart.

Full data in an appendix rather than the body.

And sources stated, since unsourced figures are discounted.

Length

Which is a decision rather than an outcome.

Decide the length before writing, based on who reads it and how much time they have.

Most reports could lose a third without losing content.

Length is frequently a proxy for effort, which is a bad reason and a real dynamic.

And a shorter document with a substantial appendix serves both the reader who wants the answer and the one who wants the working.

Writing for multiple audiences

The common complication.

A document read by a board and by specialists has conflicting requirements.

The resolution: layer it. Summary for the board, body for the managers, appendices for the specialists.

Each layer complete at its level.

Rather than a single document pitched at an average that serves nobody.

Tone

Which affects credibility.

Plain words rather than institutional language, which reads as evasion.

Active voice where the actor matters, which is most of the time.

Direct statements of uncertainty rather than hedging every sentence equally.

No throat-clearing: "it is important to note that" can always be deleted.

And avoiding the passive constructions that conceal who decided what, which readers notice.

Revision

The stage that is skipped.

Write, leave it, then cut.

Read only the first sentence of each paragraph — the argument should be visible.

Read only the headings — the same test.

Delete anything that does not support the recommendation, including good material.

And have someone unfamiliar with the work read the summary and tell you what you are recommending, which reveals whether it is there.

The review cycle

Which consumes more time than the writing and is rarely planned.

Decide who genuinely needs to comment, and tell them what you want from them: factual accuracy, or the argument, or the wording — not all three.

Give a deadline and a version number.

Circulate a near-final draft rather than an early one, since early drafts attract comments on things you were going to change anyway.

And resolve conflicting comments yourself rather than convening a meeting, which is what makes documents take months.

Templates and house style

Worth a note.

Most organisational templates are structured for filing rather than for reading, which is why documents written into them are unreadable.

Where the template is mandatory, put a genuine summary at the top regardless.

Where it is not, abandon it.

And a consistent house style — for headings, numbering, dates and terminology — removes a class of small friction that readers experience without identifying.