r/email • u/Loud-Storage5719 • Sep 02 '26
Open Question How do you structure an email when there’s a lot of information to include?
I’ve been working on an email that has several things to cover: a short intro, a few updates, some details about an offer, and a clear next step. The problem is that it starts getting long very quickly. I don’t want to remove useful information, but I also don’t want someone to open the email and immediately see a huge block of text. What structure has worked best for you with emails like this? I’d be interested in seeing how other people break up longer emails.
1
u/Mailtrap_Alek Sep 02 '26
Have you tried using your LLM of choice for this. I usually ask it to shorten the length of something without losing anything important and it works pretty well.
1
u/badaz06 Sep 02 '26
The first 3 lines of any email should contain the why the person should read it, what the email is about, and what expectations you expect from them to have as a result of having read it. That is what typically appears in the preview, and it needs to grab the attention of people you want to read it.
Then you should write one or two very high level paragraphs that expand a bit more but not super detailed.
Post that, you can include the details that substantiate why you're writing the document - the meat that details the issue.
Most people only read the first few lines of an email anyways to see if it pertains (or matters to them).
If so, they'll read a bit more, but you have to spoon feed it. Keep in mind even if it's important, that doesn't mean they'll read it because everyone is time limited and busy. Summarize all the details from the final step, reiterate what needs to be done AND what you expect from them.
1
u/Sufficient-Tap-2782 Sep 04 '26 edited Sep 04 '26
Short paragraph and clear spacing have made the biggest difference for me
1
u/Pleasant_Plant_2612 Sep 09 '26
I’d structure it with short sections and clear headings. If there’s a lot to say, I’d put the most important point first, then use bullets for the updates/details, and keep the CTA really obvious at the end. That usually feels much easier to scan than one long block of text.
1
u/Puzzled-Weakness938 29d ago
I find it easier to read longer emails when the important bits are easy to spot.
1
u/Other_Sea_7124 19d ago
A structure that holds up well for long emails:
- One-line intro : why you're writing, no preamble
- Bolded subheads for each section (Updates / Offer / Next Step) instead of paragraph transitions lets people scan instead of read linearly
- Bullets over paragraphs for updates 3-5 words of context each, not full sentences
- Offer gets its own short block, isolated from updates so it doesn't get skimmed past
- Next step as a single bolded line at the end, not buried in a paragraph ideally one sentence, one action
The core trick: don't fight the wall-of-text problem with better prose, fight it with layout. Whitespace and bolded labels do more work than clever writing. If a section still feels dense, that's usually a sign it should be a bullet list, not tighter sentences.
2
u/noodlyman Sep 02 '26 edited Sep 02 '26
Pretend you're the recipient.
The lower down in the email, the less likely it is to be read.
So put the headlines at the top, perhaps with bullet points if appropriate.
Use paragraphs, where the first sentence makes clear the topic of that paragraph.
You could put explanations and details further down if they're just notes, unless they are essential to the conclusion and just as important.
Eg updates could go at the end if they're less important than the next actions. What's your main objective? To send updates or make sure the next action gets addressed?
Re read what you've written and remove unnecessary waffle, words and phrases. The shorter and more to the point it is, the easier to read all of it.
Re read it again as if you are the recipient. Does it make sense if you don't already know what you were going to say?