The body of a business email is the part between your opening line and your sign-off, and it's the part most writers treat as an afterthought. Subject lines get workshopped. Closings get agonised over. The body just gets written, usually fast, usually without a plan. That's why so many emails require two or three follow-ups to get a single answer.
A well-structured email body does three things: it delivers the context a reader needs, it makes the request or point unmistakably clear, and it tells the reader exactly what comes next. Those three jobs need to happen in roughly that order, and each one has its own pitfalls.
How much context is enough?
The single most common mistake in business email bodies is front-loading context that the reader doesn't need. Writers treat their email like a story, warming up to the point across three paragraphs before the reader knows why any of it matters.
Flip the structure. State the purpose in the first sentence of the body, then provide the context that supports it. One sentence of background is usually enough. If you're writing to someone outside your organisation who doesn't know the project, two sentences might be justified. Beyond that, you're padding.
A useful test: cover the first sentence of your body with your thumb. Does the rest of the email still make sense? If yes, delete the first sentence. It was throat-clearing.
The right paragraph length for email
A paragraph in a business email is not a paragraph in an essay. Keep each one to 3 sentences at most. One is fine. Two is often ideal. Long blocks of text in an email body read as walls, and most readers scan rather than read linearly, so a buried sentence in paragraph four gets missed.
Each paragraph should carry one idea. When you catch yourself using the word "also," that's a signal you're smuggling a second idea into a paragraph that was supposed to carry one. Give the second idea its own paragraph instead.
White space is your friend. A short, clean paragraph reads as confident. A dense one reads as disorganised, even when the content is solid.
Being direct without being blunt
Direct writing and blunt writing are not the same thing. Direct means your reader knows what you want within 10 seconds of reading. Blunt means you've cut the parts that make the request reasonable and human.
Compare these two versions of the same request:
- Blunt: "I need the report by Thursday."
- Direct: "Could you send the report by Thursday? We're presenting to the board on Friday and need a day to review."
The second version is not softer. It's clearer. The reader understands the deadline and the reason behind it, which makes them far more likely to meet it. One sentence of rationale converts a demand into a request without changing the urgency.
The same principle applies to questions. Don't bury them in the middle of a paragraph. Put a question on its own line. Readers who scan will find it; readers who read carefully will still find it.
When to use bullet points and when not to
Bullets work when you have 3 or more discrete items that don't flow naturally as prose. A list of documents you need, a set of dates to confirm, or a series of decisions someone needs to make are all good candidates for bullets.
Bullets don't work when the items are actually steps that happen in sequence, when there are only 2 items (just write them as a sentence), or when you're using them to avoid writing a coherent argument. A bullet-pointed email body that's mostly bullets reads as a draft, not a finished piece of writing.
One list per email is a good rule. Two lists signal that the email is probably covering too many topics and should be split into two messages.
How to end the body before the sign-off
The last paragraph of your email body is not the place to introduce a new idea. It's the place to confirm the action, the timeline, or the next step. One of these frames almost always works:
If you're asking for something: restate what you need and when. "Please send the revised figures by end of day Wednesday." If you're providing something: tell the reader what to do with it. "Let me know if you have any questions on the attached." If you're requesting a decision: make the choice explicit. "Are you happy to proceed on those terms?"
Ending the body with a vague "let me know what you think" after a complex email is the most common way to trigger a follow-up. The reader doesn't know what thinking is expected of them, so they defer.
Tone calibration in the body
Most writers default to one tone for all email, usually either too formal or too casual for the context. Formal tone in an email to a colleague you've worked with for 3 years reads as cold. Casual tone in a first contact with a senior external stakeholder reads as presumptuous.
The body is where tone gets set most firmly, because it's where the most words are. A quick check: read your draft aloud and ask whether it sounds like you in a professional conversation, or like a document. Email is closer to conversation. If it sounds like a form letter, it probably needs loosening. If it sounds like a text message, it probably needs tightening.
Contractions help. "We're reviewing the proposal" is warmer than "We are reviewing the proposal" and no less professional. Use them.
The opening line of your email does a lot of the tone-setting work before the body even starts. If you're not sure how to handle it, writing a strong opening line covers that in full. Similarly, once your body is solid, your closing sentence needs to carry the reader cleanly toward the sign-off without introducing friction.
A simple structure to fall back on
When in doubt, this three-part structure works for most business emails:
1. Purpose. One sentence stating what the email is about or what you need. Put this first, always.
2. Context. One to three sentences giving the reader what they need to act. Not the full history. Just enough.
3. Next step. One sentence stating what you want the reader to do, by when, and why it matters.
That's it. A 5-line email following this structure will outperform a 20-line one that buries the point. Most business emails should be shorter than the writer thinks. Read your draft once, cut the slowest paragraph, and send it.
If you find yourself writing the same email repeatedly, for example a status update or a progress report, it's worth building a template from your best version. The structure above is a good starting point for one.
Email bodies don't need to be clever. They need to be clear. A reader who finishes your email knowing exactly what's expected of them is the outcome to optimise for, every time.