Writing email that gets read and acted on

A senior manager I once worked with had a private filter rule in her inbox: any email longer than three paragraphs went straight into a folder she read on Friday afternoons. She had never told anyone. She did not feel guilty about it. Her team was constantly baffled by her delayed replies to “urgent” threads and blamed it on her being overwhelmed.

She was not overwhelmed. The emails were just badly written.

Most professional email fails at the same place: the ask is buried. The writer spends two paragraphs on context, one on caveats, half a paragraph on pleasantries, and then, finally, in a subordinate clause near the end, reveals what they actually want. By then, the reader has either skimmed past it or decided to come back later — which usually means never.

This is not a writing problem in the literary sense. It is a structural problem. The fix is not to write more clearly; it is to write in a different order.

The BLUF principle

The U.S. military has a writing standard called BLUF: Bottom Line Up Front. It exists because officers reading field reports under time pressure cannot afford to find the conclusion at the end. The same constraint applies to every senior person in a busy organisation. They are reading your email on a phone between meetings. They have fourteen others in the queue.

BLUF means: the first sentence of the email body is the thing you want the reader to know or do. Not “I wanted to reach out regarding,” not background, not a greeting beyond one line. The conclusion, first.

Paired with BLUF is the subject line, which should not describe the topic — it should state the ask. “Project Alpha” is a topic. “Approve revised timeline for Project Alpha by Thursday” is an ask. The second version lets the reader know, before opening the email, whether they are the decision-maker and when they need to act.

One email, one decision

The second structural error is bundling. Writers bundle three separate questions into one email because it feels efficient. It is the opposite. The reader now has to decide which question to answer first, whether they can answer all three, and what to do if they can resolve two but not the third. The cognitive cost climbs, the email goes into a mental “needs thinking” queue, and you get nothing for a week.

The rule is: one email, one decision. If you have three asks, send three short emails or, if they are genuinely related, structure the email with explicit subsections and separate CTAs (calls to action) so the reader can respond to each independently.

A related variant: the update that secretly contains an ask. You write a status update, and somewhere in the middle you slip in “let me know if this direction is okay.” That is not an update. That is an approval request wearing an update’s clothing. Name it honestly in the subject line so the reader does not have to excavate your intent.

The anatomy of a tight email

A well-structured email has four elements, in order:

Ask in the subject line. State what you need and when. If no deadline exists, say so explicitly — “no deadline, FYI” is more useful than leaving it ambiguous.

BLUF in the first line. One sentence that gives the reader the bottom line without reading further. If they read nothing else, they should still understand the situation and what you want.

Context, briefly. Two to four sentences of necessary background. If you need more than that, ask yourself whether the reader actually needs it to make the decision or whether you are writing it to make yourself feel thorough.

Bolded action and deadline. Somewhere in the email — typically at the end, after context — the specific ask appears again in bold. Not italic, not ALL CAPS. Bold, because that is where the eye goes when skimming. Please confirm the vendor contract by Friday 6 June, EOD IST. That is a complete action item.

Before and after

Here is the kind of email that clogs inboxes everywhere:

---

Subject: Follow-up on the vendor situation

Hi Priya, hope you are doing well. I wanted to follow up on our discussion from last week regarding the vendor selection process for the analytics platform. As you may recall, we had narrowed it down to two vendors and were waiting on revised pricing from Vendor B. We received that pricing yesterday and after reviewing it with the finance team, we believe Vendor A is actually the stronger option from a cost and support perspective, though Vendor B does have some features we liked. In any case, I thought it would be good to loop you in before we move forward, and was hoping to get your thoughts on whether we should proceed with Vendor A or whether you wanted to have a call to discuss further. Please let me know whenever you get a chance.

---

Count the problems. The subject line says nothing about what is needed. The first line is a greeting. The actual ask — approve Vendor A — does not appear until the second-to-last sentence. The phrase “whenever you get a chance” signals no urgency, so Priya will park it. The offer to have a call introduces a second decision before the first is resolved.

Now the same email, rebuilt:

---

Subject: Approve Vendor A for analytics platform — decision needed by Thu 5 June

We recommend proceeding with Vendor A for the analytics platform. After receiving Vendor B’s revised pricing yesterday, finance and I assessed both options; Vendor A wins on total cost of ownership and post-sales support. Vendor B has a slightly richer feature set in reporting but not enough to offset a 22% cost premium.

Please reply with your approval by Thursday 5 June, EOD, so we can issue the PO before the month-end freeze.

Happy to share the comparison sheet if useful — it is two pages.

---

Same information. The reader knows in four seconds what is being asked, why, and when. The offer to share detail is optional — it does not block the decision. The deadline is concrete and explains why it exists, which signals this is not an arbitrary push.

The diagram: before vs after

Why writers bury the ask

Understanding the cause helps you break the habit. Most people write email the way they think — chronologically. They replay the story in the order they lived it: here is the background, here is what happened, here is what I concluded, and therefore here is what I need. That feels logical to the writer because they needed all that context to arrive at the ask.

The reader does not have that journey. They need the destination first, then the route if necessary.

There is also a social factor, particularly strong in South Asian workplace cultures, where leading with a direct request can feel presumptuous or rude. The wrapping of context around the ask is a form of deference — “I am not just demanding, I am explaining myself.” That instinct is understandable. But in an asynchronous, high-volume communication environment, it works against you. Being clear is not the same as being aggressive. A precise subject line is not a demand; it is a courtesy to the reader’s time.

A third cause is uncertainty about whether the ask is legitimate. Writers pad out emails when they are not confident in what they are asking for. If you find yourself writing three paragraphs of justification before the ask, check whether you actually believe in the ask. If you do, lead with it. If you do not, sort that out before sending.

The reply-reducing question

Before you hit send, ask: what is the minimum the reader needs to say yes to this? If the answer is “just approve,” make sure the email makes that a one-word response. Add a line: “A simple reply of ‘approved’ is all I need.” This removes friction from the responder and signals that you respect their time. Managers are conditioned to write replies that explain their decision; permission to reply briefly often accelerates the response by a day.

If you genuinely need a discussion, say so: “I can walk through this in ten minutes — happy to schedule if you prefer that over email.” That is honest and efficient. What you should not do is leave the medium ambiguous, forcing the reader to decide whether to reply or call.

A note on length

Short emails are not always right. A genuinely complex situation, a sensitive personnel matter, a decision that carries real risk — these warrant more words. The rule is not “always be brief.” The rule is: every sentence should earn its place. If a sentence exists to make the writer look thorough rather than to help the reader decide, cut it.

The test: if you removed this sentence, would the reader be worse equipped to act? If no, remove it.

What this looks like in practice

Adopt this for one week on every email that requires a decision or approval. Change nothing else. At the end of the week, look at your sent folder and count the average number of back-and-forth rounds per thread. For most people, moving the ask to the subject line and the BLUF to line one cuts round-trips by thirty to fifty percent. Not because people suddenly become more responsive, but because the email does the work of routing itself to the right decision instantly.

Your senior manager will not tell you that your emails improved. She will just start replying faster. That is how you know it worked.