You've finished the report. You've polished the proposal. Then you paste it into an email with a subject line like "Please see attached" and hit send. The document disappears into an inbox, half-read at best. A well-written summary email is the thing that prevents that.
A summary email doesn't replace the document. It frames it. It tells the reader what they're looking at, why it matters to them, and what you're asking them to do next. Done right, it takes under two minutes to read and makes the attached document far more likely to be opened, understood, and acted on.
What a summary email is (and isn't)
A summary email is not a covering note that says "please find the attached report." It's not a full re-run of the document's contents either. Think of it as a short executive layer: the three or four facts the reader most needs to know, stated plainly, with a clear call to action at the end.
The audience for this kind of email is usually someone with limited time: a manager, a client, a committee member. They won't read the document before they've decided whether it's worth their time. Your email makes that decision for them.
The structure that works
Keep it to four parts. Each one does a specific job.
- Context sentence. One sentence that names the document and why it was produced. "Attached is the Q3 market analysis requested at the August planning meeting."
- Key findings or recommendations. Two or three specific points. Not bullet-pointed generalities: real conclusions. "The data shows a 14% drop in conversion from mobile traffic since June, concentrated in the 25-34 age bracket."
- What you need from the reader. A single, concrete ask. Approval, a decision, feedback by a specific date, or just confirmation they've received it.
- Where to find what. If the document is long, a one-line signpost helps. "The cost breakdown is on page 8; the risk register is in Appendix B."
That's the whole structure. Four parts, rarely more than 200 words. Anything longer and the email itself becomes the problem you're trying to solve.
Writing the findings section without rewriting the document
This is where most writers go wrong. They either lift three headings from the document (too vague) or paste in three paragraphs (too long). The right approach is to answer one question: if the reader could only take away one thing from this document, what would it be?
Start there. Write that sentence. Then add the two supporting facts that make it credible. You're not summarising every section. You're surfacing the conclusion the document was written to reach.
Concrete beats vague every time. "Sales are down" tells the reader nothing useful. "Sales in the Asia-Pacific region fell 9% in the first half of 2026, driven by contract delays in two accounts" gives them something to think about, question, or act on.
If you're writing for a senior audience, this connects directly to the skills covered in how to write a plain-language executive brief: surface the decision-relevant information first and let the detail follow.
The subject line and opening line
Subject lines for summary emails follow the same logic as any business email: be specific about content, not format. "Report attached" is not a subject line. "Q3 mobile conversion analysis: 3 findings for your review" is.
The opening line should not be "I hope this email finds you well." Start with the context sentence from your structure above. "Attached is the revised vendor proposal for the Auckland fit-out, incorporating the feedback from the September review." That's your first sentence. Full stop.
For a broader look at how opening lines shape what readers do next, the guide on how to write a business email opening line covers the mechanics in detail.
Tone: confident but not dismissive
A summary email works best when it sounds like a person who knows the material and respects the reader's time. That means active voice, short sentences, and no hedging.
Don't write "it may be worth considering the possibility that." Write "we recommend." Don't write "the document contains some thoughts on." Write "the proposal sets out three options." The document did the careful work. The summary email is where you stand behind it.
Watch one specific trap: the apologetic opener. "I know you're busy, so I've tried to keep this brief." This burns words apologising for the brevity that you're about to demonstrate. Skip it and just be brief.
When to attach vs when to paste
Attach documents when the reader will need to print, annotate, share, or file them. Paste content inline when the document is short (under one page) and the reader is unlikely to need the formatted version.
For long reports sent to external clients, attaching a PDF and sending a summary email is the professional default. For internal audiences on shared platforms, a link to the document with a summary email is often cleaner than an attachment that will go out of date.
If you're attaching something, reference it explicitly in the body. Phrases like "please see attached" are overused, but you do need to tell the reader there's a file there. "The full report is attached as a PDF" is plain and sufficient.
A note on length
150 words is a reasonable target. 250 is the outer limit for most contexts. If you find yourself writing more than that, you're summarising the wrong things or trying to do the document's job in the email. Stop, re-read your four-part structure, and cut back to the essentials.
The test is simple: could the reader make the decision you need them to make, based solely on this email? If yes, it's long enough. If the answer requires them to read the full document first, that's fine too, as long as your email tells them exactly where to look.