I have written school reports, program documents and business summaries, and they all face the same reader: a busy person giving your document about ninety seconds. A good report is not the one with the most data. It is the one whose point survives that ninety seconds. Here is how I build them.
Start with the answer
The first lines state what the report is, the period it covers, and the headline result — before any tables. Readers who stop there still leave with the message. Detail belongs after the conclusion, not before it; this is how I was trained to write for school administrators, and business owners appreciate it even more.
One table, one message
Every table or chart gets a title that says what it shows and a one-line note underneath saying what it means. Numbers without interpretation make the reader do the analyst's job — so they skip, and your work goes unread. When a report needs visuals, a simple Power BI or spreadsheet chart beats five pages of raw figures.
Consistent structure, every time
Recurring reports keep the same sections in the same order, period after period. Familiar structure is a kindness: the reader knows where the sales figures, the issues and the next steps live, and comparing periods takes seconds.
End with decisions and next steps
The last section lists what needs a decision, what is already in motion, and what happens next — with names attached. A report that ends in information invites filing; a report that ends in actions invites a reply.
Preparing reports is one of those tasks owners keep because "only I understand the numbers." Usually the numbers just need organising — which is delegable, and is part of my VA work.