The reader is deciding, not reading

The first job of an email is not to inform. It is to let someone decide, quickly, whether they need to do anything.

That reframing changes everything. If the reader's first question is "is this mine to handle?", then the answer needs to be available in the first two lines. An email that buries the request in paragraph four has not failed stylistically — it has failed at its actual job, because the reader may have already moved on.

Ambiguity is the expensive part

Vague email is not merely annoying. It is expensive, in a way that is easy to miss because the cost is deferred.

A message that says "let's look at the timeline" generates a reply asking what you mean. That reply generates another round. Someone books a call to clarify something a sentence would have settled. Multiply that across a week and a team, and the largest cost of poor email is not the writing — it is the re-reading, the follow-ups, and the meetings that exist only to decode what was sent.

Clear email is a form of consideration. It takes work at the point of writing, and it repays it in other people's time.

The subject line states the action

Most subject lines describe a topic. The useful ones describe what the reader is expected to do.

"The Q3 report" is a topic. "Q3 report — need your sign-off by Thursday" is a request. The reader knows before opening whether this is theirs, and what it commits them to. It costs the same number of words.

The first line is the ask

Put the request first, then the context that supports it. This feels wrong to most writers, because context comes first in their own thinking — they reasoned their way to the request and want to show the reasoning.

The reader does not need your route to the conclusion. They need the conclusion. Everything you would have put first becomes the justification that follows, where it is genuinely useful.

One email, one decision

An email with a single request gets answered. An email with four requests gets answered partially, or answered for the easiest one, and then quietly abandoned.

If you have four things to ask, that is often four emails — or one email with a numbered list and a clear statement of which matters most. The failure mode to avoid is a wall of prose containing several buried requests, where the reader answers the one they noticed.

Keep the shape visible

A useful default is: state the request, give the minimum context needed to act on it, then say what happens next. Three short blocks.

The value is not the template itself but the discipline it enforces. If you cannot fill in "what happens next," you may not yet know what you are asking for — and that is worth discovering before you send, not after.

Cut the throat-clearing

Phrases that open an email without saying anything — "I hope this finds you well," "just following up on my previous note," "as per our earlier discussion" — are not wrong, but they delay the point, and delay is the thing you are trying to eliminate. One line of courtesy is pleasant. Three lines of warm-up is a cost.

Say who does what, by when

Most ambiguity lives in the gap between a request and an owner. "This needs to be reviewed" raises the question: by whom? "Could you review this by Wednesday?" removes it.

Naming the person and the date takes a few extra words and eliminates an entire round of follow-up. Where a deadline genuinely does not exist, say so — "no rush, but before month end" is clearer than leaving it open.

Keep the emotion out of the first draft

Email carries no tone, and readers supply their own. A neutral sentence written in irritation reads as angry; the same sentence written warmly reads as brisk.

The practical fix is mechanical: write the irritated version, do not send it, then cut it down to the facts. What remains is almost always shorter and almost always lands better. The rule is not "never be direct" — it is "be direct about the facts, not about the person."

The reply-all reflex

Broad distribution feels safe and is usually a mistake. Each additional recipient adds someone who must decide whether this concerns them, and often one who replies to all to say it does not.

Check the list before sending, every time. The cost of removing someone who should have been included is one forwarded email later. The cost of including twelve people who should not have been is ongoing.

Hiding the ask at the bottom

Writers often build to the request out of a sense of politeness — context first, ask last. But many readers stop after the first screen, which means the ask is never seen. If the request only appears in the final paragraph, expect a reply asking what you wanted.

Long emails to cover uncertainty

Length is often a symptom of not having decided. When you are unsure what you need, writing more feels like thoroughness. To the reader it is simply more to process, and the ambiguity has not been resolved — it has been distributed.

A short email is usually a sign that the writer did the thinking.

Before

Hi all, following up on our earlier discussion about the vendor renewal. As you know, we've been reviewing the contract and there were a few points raised in the meeting about the pricing structure and the service levels, which the team felt needed more analysis before we commit. I've attached the deck. There are also some questions about the implementation timeline and whether the current resources are sufficient. Happy to discuss further, let me know your thoughts.

Four paragraphs. Attachments. No clear request. The reader finishes without knowing whether they are being asked to approve, comment, or simply be aware.

After

Hi all — I need a decision on the vendor renewal by Thursday. Two things to confirm: the pricing structure (slide 4) and the implementation timeline (slide 7). Both still have open questions; the rest is settled. If you're happy with slide 4 and 7 as they stand, reply "approved" and I'll proceed. If not, tell me which point and I'll revise.

Same subject, same information, one third of the length — and the reader knows exactly what to do.

AI assistants have become genuinely useful for email, and it is worth being precise about which half of the job they do.

They are good at the surface. Shortening a draft, softening a blunt line, reordering so the request comes first, fixing a subject line that describes a topic instead of an action. These are mechanical tasks and they are quick.

They cannot tell you what you want. An assistant will happily produce a fluent email that asks for nothing in particular, because fluency and clarity are not the same thing. If you have not decided what you need from the reader, no amount of rewriting will supply it.

The practical division of labour: decide the request yourself, then use the tool to strip everything that gets in its way. Ambiguity is the one thing you have to solve on your own.

Email is efficient for some jobs and actively harmful for others, and the distinction is worth making explicit.

It works for: a decision that needs a record, information several people need to see at once, a request that can be answered in a line or two, anything that should be searchable later.

It fails for: anything emotionally charged, anything that will need more than two rounds of back-and-forth, and anything that depends on tone being understood correctly.

The tell is usually in the draft. If you have rewritten a paragraph three times to get the tone right, that is a signal the conversation wants a different channel — a call, or five minutes at someone's desk. If you find yourself explaining context that took you hours to reach, a document will serve better than an email pointing at a document.

The one that causes the most damage is using email to deliver something difficult: a delay, a rejection, a correction of someone's work. Written criticism loses every softening signal the voice provides, and it is permanent in a way speech is not. The reader keeps it, and re-reads it, in the worst possible mood.

None of which means avoid the message. It means choose the medium deliberately. Say the difficult thing in person or on a call, then send a short email confirming the facts and what was agreed. You get the record without the damage — and the record is usually better, because both sides have heard each other first.

Reading about email does not change how you write email. The gap between knowing and doing closes through practice with feedback — writing real messages, seeing how they land, and adjusting.

If this is something you would like to build properly, CBS runs a programme directly on it: Email Excellence with AI – Writing Clear and Effective Workplace Messages, which covers structure, tone and using AI tools without letting them flatten your meaning.

Three related programmes are worth knowing about.

Stronger Business Writing with AI – Proposals, Briefings and Reports Made Better with Generative AI — for longer documents.

Writing good replies to Difficult Stakeholders (with AI prompts) — for the emails that are hardest to keep neutral.

Better Business Writing Skills For Administrative Support Professionals — for the correspondence that runs a department.

Ask CBS about current dates, fees and funding eligibility directly — these change, and they will give you the accurate answer for your circumstances.

Put the request in the subject line and the first line. Give only the context needed to act on it. Name who does what, by when. One decision per email. Cut the warm-up and the irritation. Short is not rude; short is considerate.

Most of all: decide what you want before you write. Everything else is editing.

Disclaimer: This guide is provided for general information only. It is not professional, medical or technical advice, and should not be relied on as a substitute for an on-site assessment or the opinion of a qualified professional. Product availability, features and specifications may change without notice — please refer to the product pages on our store for current details and pricing.