Put the answer in the first sentence — then earn the reader’s time, don’t spend it.
Bottom line up front. The recommendation and the ask go in the first sentence, so a reader who stops there still knows what you want and why it matters. Everything after is a fixed skeleton: two lines of context, three evidence-backed reasons, the risks, and a next step with an owner and a date.
The hard part isn’t writing — it’s cutting. Compression is a decision skill: you cut by asking what does the decision-maker not need, not by shrinking every sentence equally. A one-pager is a promise that you did that thinking for them.
build the one-pager from a 20-page report
The 20-page report
Tap place to move a block into the brief.
Your one-pager
Reorder or cut. Budget: 8 lines.
Press time a skimming reader to see how fast an executive reaches your bottom line.
The skeleton never changes; only the content does. Fill it top-down, then cut anything the decision-maker doesn’t need to decide.
BOTTOM LINE Recommend X. Requesting your sign-off by [date]. <- first sentence, always
CONTEXT Two lines: what's happening, what's at stake.
REASONS 1) evidence 2) evidence 3) evidence <- three, each backed
RISKS The main downside, and how you'll watch it.
NEXT STEP Action - owner - date. <- someone owns it
compression test for every line:
does the decision-maker NEED this to decide?
yes -> keep (a reason, a risk, the ask)
no -> cut (methodology, history, appendix) move it to a link, not the page
Cut toward the decision, not toward a word count. Two crisp reasons the reader needs beat six they don’t — and a 40-page appendix belongs behind a link, not on the page.
| Reach for a BLUF one-pager when… | The trade-off |
|---|---|
| A busy decision-maker must act and has minutes, not hours. | Forces you to actually decide the recommendation before you write. |
| The reader can skim and still needs the point. | Nuance and caveats get compressed — keep the ones that change the call. |
| You’re asking for a specific decision, sign-off, or resource. | Weak when the goal is exploration, not a decision — use a discussion doc. |
An interviewer says: “You have a 20-page analysis. The VP has two minutes before a decision meeting. Brief them.” A strong answer opens with the bottom line — “I recommend delaying the launch two weeks; I need your sign-off today” — then gives two lines of context, three reasons each tied to evidence (the 4× crash rate, two of six checks passing, the staffing gap), the one real risk (missing the activation goal by about a point), and a next step someone owns by a date. The methodology, the stack traces, and the competitor teardown stay in the appendix, linked, not printed. When the interviewer asks “what did you cut and why,” you answer with the decision test: none of it changed the call, so none of it earned space on the page.
Check yourself
Your one-pager is three lines over budget. Which cut is most in the spirit of BLUF?
A reader skims only the first sentence of your brief and stops. For BLUF to have worked, that sentence must contain…