The executive summary is the most read and most misunderstood section of a white paper. It appears first. It should be written last. Most teams do it backwards — draft the executive summary first as an “outline”, then wonder why it doesn't accurately represent the paper they actually wrote.
Why you write it last
An executive summary is a summary of a document that exists. If you write it before the document exists, you are writing a proposal for a document, not a summary of one. The difference becomes apparent when the paper's actual argument, evidence, and conclusions don't match what the executive summary promises — which happens constantly when the summary comes first.
Writing the executive summary last also forces a useful discipline: you must be able to summarize your paper's core argument and evidence in 200–300 words. If you can't, the paper's structure probably needs work.
The structure: five elements, 200–300 words
A white paper executive summary contains exactly five elements. Nothing else.
1. The problem (1 sentence). Name the specific problem the paper addresses, with enough specificity that the reader knows whether it's their problem. “Mid-market financial services firms are systematically underestimating their third-party vendor risk exposure” — not “cybersecurity is increasingly important.”
2. Why it matters now (1 sentence). What changed in the market, regulatory environment, or technology landscape that makes this problem more urgent than it was two years ago? Without a “why now,” buyers can defer indefinitely.
3. The solution or approach (2 sentences). Not a feature list — the conceptual approach that addresses the problem. This should be specific enough to be useful but vendor-neutral enough to be credible. The solution section in the paper body is where vendor specifics appear.
4. Three key findings. The three most compelling pieces of evidence from the paper's research section. These should be specific: percentages, dollar amounts, timeframes, named cases. Generic findings (“evidence suggests that organizations which adopt X see improvements in Y”) don't create conviction.
5. The CTA. One specific next step. Not “learn more” — what, specifically, should the reader do after reading this paper? The CTA in the executive summary should match the CTA in the conclusion.
What to leave out
Leave out: methodology details (they belong in the research section), caveats and limitations (unless legally required), background context the buyer already knows, and anything that doesn't directly serve one of the five elements above. Executive summaries that try to do more than summarize end up doing nothing well.
Length and formatting
200–300 words. One page maximum in formatted PDF. No tables, no callout boxes, no charts — the executive summary is prose. Bold the three key findings so a reader scanning for data points can find them immediately. The formatting should be the simplest section in the paper, because the content is the most dense.
The forwarding test
The executive summary's job is to make a senior executive confident enough in the paper's content to forward it to their team or to a peer. Read your executive summary and ask: if I forwarded this to a colleague with the message “worth reading,” would they understand why? If the summary doesn't make a specific case for why the paper is worth a careful read, it hasn't done its job.
White Paper System's pipeline drafts the executive summary last — in step 7, after all other sections exist — and constrains it to the five-element structure. Try it for $15