Search for "one page report" and you will mostly find evaluation toolkits and PDF forms. Useful if you run a grant programme, less so if you need to tell your team, your board or a client where things stand by Friday. This guide is for the second case.
What a one-page report is
A one-page report states the condition of one thing at one point in time: a project, a quarter, a client account, a product launch. It fits on one screen or one printed page, and it is written, not exported. Someone chose what goes on it and what it means.
That last part is the difference from a dashboard. A dashboard shows forty metrics and leaves the reading to you. A one-page report shows four, says which one matters, and says what to do about it. For the writing itself, step by step, see how to write a one-pager.
When it beats a deck or a long doc
| Format | Best when | Weak when |
|---|---|---|
| One-page report | People read it on their own, before or instead of a meeting | The topic needs a long argument or many charts |
| Slide deck | You present it live and the visuals carry the story | Nobody presents it; slides without a speaker lose meaning |
| Long document | The reader needs every detail: a spec, a contract, a postmortem | The reader needs the gist in three minutes |
| Dashboard | Someone monitors the numbers daily | The reader needs to know what the numbers mean |
A good rule: if the people who read it will not be in the room when you explain it, write a one-page report. Weekly status, monthly client reporting, investor updates and board pre-reads all fit.
What to put on a one-page report
- A headline that is a claim. "Launch on track, support load up 40%" rather than "Launch status, week 6".
- Context in one line. Who it is for, the date, where the numbers come from.
- Three to five key numbers. Each with a comparison: against plan, last period or target.
- One table. The detail that matters, such as workstreams with owner and status, or channels with spend and return.
- What changed. Two or three wins and two or three problems, stated plainly.
- One decision or next step. What you need, from whom, by when.
Four design rules
One headline
The page makes one point. If two points compete (the launch is on track, but hiring is behind), pick the one the reader must act on and put the other in "what changed". Two equal headlines mean two reports.
Numbers first
Put the key numbers directly under the headline, large, before any prose. Readers look for numbers first and read sentences second. Every number gets a label in plain words and a comparison; a number without one is decoration.
One table
Tables are where detail belongs, but one is enough. Keep it to the columns the reader uses to decide, usually four or five. Make status a word with a colour (on track, at risk, blocked) rather than a paragraph, and put the column that matters most where the eye lands.
One decision
End with the one thing you need. "Approve hiring a second support engineer by the 20th" gets a yes or a no. "Thoughts welcome" gets silence.
Examples
Project status report
Headline: "Checkout rebuild on track for 4 November; payments provider is the risk." Numbers: percent complete, open bugs, days to launch, budget used. Table: workstreams with owner, status and next milestone. Decision: approve a one-week buffer for the provider's review. Template: project status report.
Client results report
Headline: "Leads up 31% on 12% less spend." Numbers: leads, cost per lead, revenue attributed, spend. Table: channels with spend, leads and return. Decision: move budget from display to search for next quarter. Template: client report.
Board pre-read
Headline: "ARR up 38%, churn still too high." Numbers against plan, highlights and lowlights, then one decision for the meeting. Guide: the board pre-read. Template: board pre-read.
Monthly investor update
Revenue, growth, burn and runway, highlights and lowlights, and two or three asks. Guide: how to write an investor update. Template: investor update.
Writing it in 30 minutes
A one-page report should be quick to produce, or it will not be produced every period. A routine that works:
- Five minutes: the numbers. Pull the same key numbers as last time from wherever they live, and write each next to its comparison.
- Five minutes: the headline. Look at the numbers and ask what changed most, or what the reader must act on. Write that as one sentence.
- Ten minutes: the table and what changed. Update the status column, then write two or three wins and two or three problems from your notes.
- Five minutes: the decision. One request, with a date.
- Five minutes: cut. Read it as the reader. Remove anything that does not support the headline or the decision.
If it takes much longer, the structure is probably changing each time, or the numbers live in too many places. Fix those once instead of fighting them every week. An AI chat can do the first draft from your raw notes if you give it the structure; see how to write a one-pager with AI.
Keeping it one page over time
Reports grow. Each period someone adds a section and nobody removes one. Two habits help. First, start each period from a template, not from last period's report, so the structure stays fixed. Second, keep one version: if the report is a PDF or a pasted copy, comments arrive by email and the "real" version ends up in someone's inbox.
If you write in Obsidian, myone.page keeps a one-page report as a Markdown note that renders as a page with stat tiles, a table with coloured status labels and a timeline. You share it as a link; readers edit it in the browser, and their edits land back in your note. Start from the one-page report template.