The one-pager is the most-requested and least-taught document in business writing. Someone asks for "a one-pager on this" and what they usually get is the full document with the font reduced and the margins squeezed — technically one page, and useless, because the compression removed the whitespace rather than the content. A real one-pager is a different document with a different job, and writing one is a skill worth having.
What the format is actually for
A one-pager exists because a decision-maker has ten minutes and eight things to read. It is not a summary of a longer document in the sense of a shortened copy; it is a self-contained argument that stands alone and points at the detail for anyone who wants it.
Three common jobs:
- Getting a decision. Here is the situation, here are the options, here is the recommendation, here is what I need from you.
- Aligning people. Here is what we are doing and why, so everyone is working from the same understanding.
- Introducing something. Here is what this product/project/proposal is, for someone encountering it for the first time.
The three want different structures, and the first thing to establish before writing is which one you are doing. A decision one-pager that never asks for a decision has failed regardless of how well written it is.
The structure
For the decision case, which is the most common:
Title. Name the thing and the ask. "Warehouse capacity: approval to lease the Redhill unit" beats "Warehouse capacity update", because the reader knows in four seconds what is wanted from them.
The ask, first. One or two lines: what you want, from whom, by when. Not at the bottom. A reader who stops after the first paragraph should still know what you are asking for.
Context, compressed. Three or four sentences establishing why this exists. Assume the reader knows the business but not this problem. Resist the history — nobody needs the eighteen-month narrative.
Options, with the trade-offs. Two to four, each with a sentence on cost, time and risk. The credibility of a one-pager comes almost entirely from this section: showing that alternatives were genuinely considered is what distinguishes a recommendation from an advocacy piece.
Recommendation, with reasoning. Which option and why, stated plainly. Include what you are giving up by choosing it. A recommendation with no acknowledged downside reads as either naive or evasive.
What happens next. The concrete first steps and who does them, if approved.
Where the detail lives. A link to the full analysis, model, or supporting document. This is what lets you cut hard: nothing is being hidden, it is one click away.
For the alignment and introduction cases, replace options-and-recommendation with what-we-are-doing and what-it-means-for-you.
Writing it: cut in the right order
The reason most one-pagers fail is that people write the long version and then shrink the presentation. Cut content, not whitespace.
The order in which to cut:
- Background you included because you know it, not because the reader needs it. This is usually 30–40% of a first draft.
- Process narrative. How the analysis was done rarely belongs; the conclusion does. Nobody reading a one-pager needs to know which three consultants you spoke to.
- Caveats and hedges. One line acknowledging the main uncertainty is honest; a paragraph of qualification is defensive and dilutes the argument.
- Repetition between sections. One-pagers repeat themselves more than their authors realise, because sections were written separately.
- Adjectives and intensifiers. "Significantly improved" is one word longer than "improved" and no more informative.
What not to cut: the numbers, the ask, the downside of your recommendation, and the whitespace.
The general technique is covered in concise writing: cut your word count and self-editing techniques for better writing.
Making one page readable
Layout does real work here, because a page of dense text is not a one-pager in any useful sense.
- Headings for each section, so a reader can jump to the part they care about.
- Short paragraphs — three or four lines maximum.
- A bulleted list for the options, because they are genuinely a list and prose makes comparison harder.
- Bold the ask and the recommendation. Two bold phrases on a page draw the eye correctly; twelve draw it nowhere.
- Keep the font at 10–11pt and the margins normal. If it does not fit, the content is too long — that is information, not a formatting problem.
- A small table for option comparison, if there are three or more dimensions to compare. See making accessible PDF tables if it is going out as a PDF.
The recurring mistakes
Burying the ask. The most common failure by a distance. If the reader has to reach paragraph six to find out what you want, most will not.
One page of six-point type. Everyone recognises this and nobody appreciates it. If the content genuinely requires two pages, write two pages and say so — a well-organised two-pager beats an unreadable one-pager.
Presenting one option. A single recommendation with no alternatives reads as a decision already made, and invites the reader to invent the alternatives themselves, usually badly.
Omitting the cost. Every proposal has one — money, time, opportunity, risk. A one-pager that does not state it will be sent back with exactly that question.
Writing for the wrong reader. A one-pager for a CFO and one for an engineering lead about the same decision are different documents. Establishing who reads it changes what needs explaining.
Making it a summary of the deck. A one-pager derived from a presentation inherits the presentation's structure, which was built for a speaker, not a reader. Write it fresh.
The relationship to longer documents
A one-pager is not a replacement for the analysis; it is the interface to it. That relationship should be explicit:
- The one-pager links to the full document, model, or data.
- The full document exists and is finished — a one-pager pointing at something you have not written yet does not survive its first question.
- The numbers in the one-pager match the numbers in the full document, exactly. Nothing destroys credibility faster than a discrepancy discovered by someone checking.
For the longer forms, see how to write an executive summary — which is a related but distinct genre, living inside a document rather than standing alone — and how to write a project brief and writing a business case for the documents a one-pager frequently fronts.
A test before sending
Two checks that catch most problems:
The ten-second test. Give it to someone uninvolved and take it back after ten seconds. Ask what you want from them. If they cannot say, the ask is not prominent enough.
The objection test. Read it as the person most likely to say no. The first objection they will raise should be addressed somewhere on the page. If it is not, you have written an advocacy document rather than a decision document, and it will come back with that objection attached.
More generally: proofreading checklist before you hit send.
Summary
A one-pager is a self-contained argument, not a compressed report. Lead with the ask, compress the context ruthlessly, show the options you rejected and why, state the downside of what you are recommending, and link to the detail rather than including it. Cut content rather than margins — if it will not fit at a readable size, that is a signal about scope, not a formatting problem to solve with a smaller font.
