BW-301c · Module 3

The Summary for a Document No One Will Read

5 min read

Some documents are written knowing the body will not be read. The research report that feeds a one-page board briefing. The 80-page audit that produces a two-page findings summary. The 300-page technical assessment that the executive committee sees only as a three-paragraph synopsis. In these cases, the "summary" is not a summary of a document — it is the deliverable. The body exists to justify the summary, not to be read alongside it.

This is not a lesser category of writing. It is harder writing. When the summary is the only thing the audience will read, every weakness in the underlying argument becomes a weakness in the deliverable. There is nowhere else to put the substance.

  1. Write the Body as a Private Document When the body will not be read, write it anyway — but write it as a private working document. The body is where you work out the argument, test the evidence, and find the conclusion. The summary is where you present the conclusion. A summary written without a body is a conclusion without evidence — which may be acceptable for a rushed briefing, but never for a decision that will be attributed to your analysis. The body exists for your integrity, even when no one reads it.
  2. Make Every Sentence in the Summary Carry Weight In a standard document, a weak sentence in the summary can be clarified by the body. In a standalone summary, it cannot. Every sentence must be able to stand alone under scrutiny. If the CFO asks a follow-up question about a sentence in your board summary, you must be able to answer it from the sentence alone — because the sentence is all they have. Write accordingly: each claim fully stated, each figure attributed, each recommendation specific enough to act on.
  3. Anticipate the Questions A standalone summary will generate questions the reader cannot answer by reading further. Anticipate the three most likely questions and embed the answers in the summary. Not as parenthetical asides, but as intentional sentences. "This recommendation would require an estimated $340K investment and an 8-week implementation window — both of which are within the parameters established by the board's Q4 planning session." That sentence answers the budget question and the timeline question before they are asked.

Do This

  • Write the full body first, even if no one will read it — it is how you find the argument
  • Write each sentence to withstand follow-up questions without referring to supporting documents
  • Embed the three most likely follow-up question answers in the summary text itself
  • State figures and timelines with enough specificity that they can be evaluated without context

Avoid This

  • Write the standalone summary without a body — you are presenting a conclusion without knowing if the evidence supports it
  • "Additional details available upon request" — if the decision maker needs to request details, the summary did not provide enough
  • Use hedged language as a substitute for specific claims: "approximately" and "in the range of" signal that you have not done the analysis
  • Compress the argument so aggressively that the summary raises more questions than it answers