How to Summarize a Long Report for a Busy Executive in 3 Bullet Points

A summary written to remind yourself of a report's contents and a summary written for someone who'll spend thirty seconds on it are fundamentally different documents — and most people write the first kind when they need the second.

Lead with the decision, not the analysis

An executive summary that opens with methodology or background before getting to the actual recommendation buries the one thing the reader needs most. State the conclusion or recommended action first; the supporting analysis comes after, for whoever wants it.

Three points, not ten

A long report usually contains far more findings than anyone needs to act on the core decision. Forcing yourself to pick the three that actually matter is harder than listing everything, but it's the difference between a summary that gets read and one that gets skimmed past.

Numbers over adjectives

"Performance improved significantly" forces the reader to ask "by how much" before they can act on it. "Performance improved 23%" answers the question before it gets asked — concrete numbers move faster through a busy reader's attention than qualitative language.

Flag what needs a decision, separate from what's just informational

Mixing "here's what happened" with "here's what we need you to approve" in the same paragraph makes both harder to act on. Separating informational content from anything requiring a response keeps the ask clear.

Offer the detail, don't force it

A summary doesn't need to omit the full report — it needs to make the full report optional. Link to or attach the complete analysis for the reader who wants it, while keeping the summary itself short enough to stand entirely on its own.