A white paper is a long, evidence-based report that argues for one way to solve a problem a specific reader has. To write one, name the reader and the decision they face, pick the type (backgrounder, numbered list or problem/solution), research until every claim has a source, outline from the executive summary to a single next step, then write the body first and the summary last. Most commercial white papers run 2,500 to 5,000 words, roughly 6 to 12 designed pages. A complete sample outline is below.
What a white paper is, and isn't
The name comes from the British government. A government white paper sets out a policy it intends to pursue, often before the legislation, while a green paper is a consultation document that asks for views. The Churchill White Paper of 1922 is an often-cited early example. Since the 1990s, businesses have borrowed the name for long-form reports that make the case for a product, service or way of working.
Gordon Graham, author of White Papers For Dummies (2013), describes the business version as “a persuasive essay that uses facts and logic” to promote a product, service or viewpoint. Both halves matter. It persuades, so it takes a position. It uses facts, so the position has to be earned on the page. That is what separates it from its neighbors:
- A brochure lists features. A white paper explains a problem first and earns the right to recommend something.
- A case study tells one customer's story. A white paper argues about a whole category of problem and may include a short case study as evidence.
- A research paper reports findings and leaves the decision to the reader. A white paper makes the decision for them and shows its working.
The form also has a technical branch. Satoshi Nakamoto's Bitcoin paper, posted to a cryptography mailing list on October 31, 2008, runs nine pages: a short abstract, the problem with trust-based online payments, then the proposed system built up section by section. No sales pitch and no wasted page, which is a better guide to length than any word count.
Choose the type before you outline
Graham sorts commercial white papers into three types. Most papers you will find are one of them or a blend, and each suits a reader at a different point in a purchase.
| Type | What it does | Best for | Reader stage |
|---|---|---|---|
| TypeBackgrounder | What it doesExplains how a product or service works and what it does for the buyer | Best forLaunches, and buyers comparing a shortlist | Reader stageLate: choosing a vendor |
| TypeNumbered list | What it doesMakes a set of points: questions to ask, mistakes to avoid, trends | Best forGetting attention and keeping a prospect interested | Reader stageMiddle: learning the options |
| TypeProblem/solution | What it doesDefines an industry problem and argues for a new approach to it | Best forReaching people who have not picked any approach yet | Reader stageEarly: defining the problem |
Problem/solution needs the most research and is the hardest to write. It is the type this guide follows. Think tanks, agencies and nonprofits use the same shape for policy white papers: a problem, the evidence, a recommendation. Technical white papers from engineering teams are usually backgrounders for an expert reader.
Start with the reader and the decision
The person who downloads a white paper is rarely the person who decides. A facilities manager reads it, then forwards it to a finance director with one line: "We should look at this." The paper has to work without its first reader in the room. So before any research, write three sentences.
Reader: Facilities directors at K–12 school districts with at least one older building still on its original heating controls.
Decision: Whether to ask the school board for a boiler replacement or a smaller controls upgrade in next year's capital plan.
Position: Districts should fix how they schedule heat, room by room, before they size any boiler work, because heating empty rooms is a cost a new boiler does not remove.
If you cannot write the third sentence, you are not ready to outline. Get whoever sponsors the paper (a product lead, a sales director, a client) to agree to all three before research starts. It is the cheapest way to avoid a rewrite in week five.
The title follows from the reader. It names their problem in their words, not your product in yours:
Titles about the reader
- Heat the rooms, not the building: cutting heating costs in older schools
- 9 questions to ask before you replace a school boiler
- Choosing building controls for a district with buildings of every age
Titles about the vendor
- Introducing [Product] 4: next-generation heating control
- Why [Company] leads in smart buildings
- The future of building intelligence
Research that survives a skeptical reader
Research is most of the work, and the reason a white paper is trusted more than a blog post. It comes from three places:
- Your own. Interviews with engineers, product managers and customers, plus data you hold: support tickets, test results, usage figures. Nobody else has it.
- Public. Government statistics, regulators, standards bodies and peer-reviewed studies. Slow to find, hard to argue with.
- Industry. Analyst reports, trade associations and other companies' published surveys. Useful, but check who paid for the research and how many people it asked.
In interviews, ask what customers tried before, what went wrong with it, and which number would surprise an outsider. Record and transcribe. The best line in a white paper is often something an engineer said in passing.
Keep a source log from the first day: for every fact, the title, publisher, date, link and the page or table you used. Trace each number back to where it was first published rather than the article that repeated it, and date figures in the text ("in its 2024 survey") so readers can judge how current they are. If you use an AI tool to find sources, open every one it suggests. Language models can produce a citation that looks right and does not exist, a form of hallucination that is embarrassing in print.
White paper structure
A problem/solution paper follows a predictable order, and readers expect it. Graham's rough split is about three pages of front matter (cover, contents, summary), six to eight pages of body and three of back matter (conclusion, next step, company and sources).
| Part | What goes in it | Rough length |
|---|---|---|
| PartTitle and subtitle | What goes in itThe problem in the reader's words, and who the paper is for | Rough lengthA line each |
| PartExecutive summary | What goes in itThe problem, the approach, the strongest evidence and the recommendation | Rough lengthHalf a page to a page |
| PartThe problem | What goes in itWhat is going wrong, for whom, and what it costs them | Rough length1–2 pages |
| PartWhy current fixes fall short | What goes in itThe usual answers, treated fairly, and where each breaks down | Rough length1–2 pages |
| PartThe approach | What goes in itThe recommended way to solve it, explained as a method, not a product | Rough length2–3 pages |
| PartEvidence | What goes in itData, a short customer example, a worked calculation | Rough length1–2 pages |
| PartHow to evaluate or adopt it | What goes in itCriteria, questions to ask, a timeline | Rough lengthAbout a page |
| PartConclusion and next step | What goes in itThe argument in a paragraph, then one clear action | Rough lengthHalf a page |
| PartAbout the company | What goes in itWho wrote it and where the product fits | Rough lengthA paragraph |
| PartNotes and sources | What goes in itEvery source, numbered to match the text | Rough lengthAs needed |
Make headings say something. "One schedule for a building that is rarely full" tells a skimmer more than "Background", and a reader who scans only the headings should come away with the argument.
A sample white paper outline
Here is a full outline for a fictional problem/solution paper from a building-controls company, written for the facilities directors in the planning note above. The notes under each section say what evidence it needs. The research fills them in.
Heat the rooms, not the building: cutting heating costs in older schools without replacing the boiler
A guide for facilities directors planning next year's capital budget
Executive summary (written last): Many districts heat older buildings on one schedule, so empty gyms, libraries and wings are warmed as if they were full. Replacing the boiler is the usual answer and the most expensive one, and it does not change the schedule. This paper compares three alternatives and recommends starting with room-level scheduling tied to the bell and events calendar, then sizing any boiler work against the load that is left.
- One schedule for a building that is rarely full. How heating schedules are usually set, and which spaces sit empty and when. Evidence: a week of occupancy from one real building, and heating's share of school energy use from a government energy agency.
- What districts try first, and why it disappoints. Manual setback schedules (they drift and get overridden), a new boiler (cost, a summer of disruption, still heats empty rooms), portable heaters (load and safety). Say plainly when a new boiler is the right call.
- Heat by occupancy instead. Zones, room sensors or calendar feeds, setback temperatures, warm-up time before first period. Explained as a method any vendor could deliver.
- What changed in one building. A customer story told with permission: metered energy use before and after, not a model. Then a worked example the reader can redo with their own figures.
- Questions to ask any vendor. Does it work with the existing boiler? Who owns the data? What happens when the network is down? How is payback calculated? Plus a one-building pilot plan.
- What it takes. A summer-break timeline, which staff are involved, and what to ask the board for.
- Conclusion and next step. The argument in four sentences, then one offer: an occupancy review of one building.
- About the company. One paragraph, the first mention of the product.
- Notes. Numbered sources with title, publisher, date and link.
Two things make this outline work. The product does not appear until section 8, and section 2 admits when the expensive option is right. That fairness is what makes sections 3 and 4 believable. For a reusable version of this structure, start from the white paper template.
How to write a white paper, step by step
- Name the reader, the decision and your position
Write the three sentences from the planning note and get them approved. Everything later is measured against them.
- Choose the type and a working title
Match the type to where the reader is: early readers need a problem/solution paper, late readers a backgrounder. Write a title about their problem. You can sharpen it at the end.
- Research and interview
Book interviews first, because calendars are the slowest part. Collect more evidence than you will use and log every source.
- Outline with headings that make claims
Turn each section into a sentence-length heading, then note under it which facts and sources belong there. If a section has no evidence, it is either opinion or it needs more research.
- Draft the body, then the summary
Start with the problem section. Keep paragraphs short, define every acronym once, and test readability by reading a page aloud. Write the executive summary last, when you know what the paper proved. A separate executive summary template helps if it has to stand alone.
- Add visuals that carry evidence
One chart per number that matters, a table for any comparison, and a caption that says what to notice. Stock photos add pages, not proof.
- Review in rounds
First for accuracy (a subject expert), then for argument (someone who matches the reader), then for claims about competitors or results (legal or compliance), then a copyedit against your style guide. Keep each round as a separate version so you can see who changed what.
- Design, publish and reuse
Lay it out as a portrait PDF with a contents page, page numbers and the date on the cover, and publish a web version too. Then cut it into a blog post, a short email and a talk.
Mistakes that sink white papers
- A brochure in a long coat. The product arrives on page one and every section circles back to it. Readers stop.
- Numbers without traceable sources. A statistic cited to a vendor blog that cites another vendor blog is not a source.
- Writing for everyone. "Organizations of all sizes" addresses no one. A paper for school facilities directors can name their board and their budget cycle.
- A summary that teases. "This paper explores the challenges of…" wastes the most-read paragraph. State the recommendation.
- No date. An undated paper with old figures looks abandoned. Put the publication date on the cover and update or retire the paper when its numbers age.
Writing a white paper in Strokes
A white paper is a small project: interview transcripts, a source log, an outline, drafts and review copies. In Strokes these live as documents in one project folder on your own machine. Open the AI Assistant beside the draft, add the interview notes or source log to the chat as context, and ask it to list every claim in a section that has no source, or whether the recommendation actually follows from the evidence section. Select a paragraph and press ⌘K to tighten it in place.
Version history keeps each review round, so you can preview what the legal pass changed, marked up, and restore the earlier version if it went too far. When the paper is done, export a PDF to publish and a Word file for reviewers who comment in Word, or share a link to the document.
Frequently asked questions
How long should a white paper be?
Most commercial white papers run 2,500 to 5,000 words, roughly 6 to 12 designed pages. Gordon Graham, author of White Papers For Dummies, puts the minimum at five or six pages and the typical length at 10 to 12, counting the cover, summary and sources. Technical papers can run far longer. Write as long as the argument needs and cut anything that does not serve it.
How long does it take to write a white paper?
Plan in weeks, not days. Graham cites a 2007 survey of more than 600 writers in which a typical paper took 24 to 50 hours of work, and says his own papers took six to eight weeks from first interview to approved draft, plus a week or two for design. Most of the calendar time goes to interviews and review rounds.
Should a white paper be gated behind a form?
It depends on its job. A form collects contact details but cuts readership, while an open web version is easier to find and share. One middle path is an open page with the executive summary and the full PDF behind a short form. Measure what each version brings in rather than following a rule.
Which citation style should a white paper use?
No single style is required. Use numbered endnotes or footnotes with the title, publisher, date and link for each source, pick one style such as Chicago notes or APA, and apply it consistently. Full details matter because printed copies cannot follow a link.
