Business Email Writing

Emails That Get Acted On

Most advice about business email tells you to be clear and concise, then stops. The hard part is the doing. I keep one sentence taped to the side of my monitor, copied out of an old paperback I have owned since college: "A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts." William Strunk Jr. wrote that in 1918, and E.B. White kept it when he revised The Elements of Style in 1959. Strunk was talking about prose. It works just as well on a Tuesday-afternoon email asking three people to confirm a date.

Here is the uncomfortable truth about the inbox you are writing into. The person on the other end is not reading. They are triaging. Most of us decide whether an email gets a careful read, a fast skim, or the archive button in a few seconds, off the subject line and the first line of the body. So the question that matters is not "Did I write well?" It is "Will this survive the skim?" That one reframing changes how you build a message: you stop polishing the third paragraph and start fighting for the first sentence. None of it is about being curt. It is about respecting that the reader is busy and the inbox is loud.

The U.S. Army figured this out before the rest of us. Army Regulation 25-50 standardized a convention called BLUF, "bottom line up front," with the phrase entering the regulation in its 2001 revision. The idea is plain: lead with the conclusion or the request, then put the supporting detail underneath. Soldiers adopted it because, as the guidance put it, the biggest weakness in bad writing is that it fails to transmit a focused message quickly. If a busy reader gets only your first two lines, those two lines should still do the job.

I am not neutral on length, either, and the data backs me up. Boomerang studied more than 40 million emails in 2016 and found the 50-to-125-word range pulled the strongest response rates, peaking near 51 percent at 75 to 100 words. Go much shorter and you read as abrupt; go much longer and the response rate sags, then falls off a cliff past roughly 2,000 words. The sweet spot is long enough to be human, short enough to be answered. For broader fundamentals see our guide to English communication skills, and for async work the remote communication guide.

One more thing before the how-to. Email strips out tone. Albert Mehrabian's much-quoted 1967 research is usually mangled into "words are only 7 percent of communication," which was never the claim and applied only to spoken expressions of feeling. The kernel underneath, though, matters here: in person your face and voice carry the warmth, and in writing they are gone. A line you would say with a smile lands flat, or worse, cold. That gap is why a hasty email reads as rude when you meant nothing of the kind.

Which is the best argument for the one habit I will not skip. For sensitive or high-stakes messages (feedback, a complaint to a client, a position in a negotiation) I write the draft, walk away for half an hour, and read it back as the recipient. Maybe a third of the time I change something, and that half hour has saved me from more bad days than any grammar checker ever has. See also our guides to workplace communication, leadership communication, and remote team communication.

Email in the Age of AI Assistants

People keep predicting email's death, and email keeps not dying. Slack and Teams took the quick back-and-forth, but the things that need a paper trail still go by email: the contract, the proposal, the formal notice, the note to someone three companies away who has never heard of your Slack workspace. Email is where professional life keeps its receipts.

What has genuinely changed is how the words get on the page. A lot of us now ask an AI assistant to draft the thing, and I do it myself for the dull stuff. Here is where I will plant a flag: the skill is no longer writing the email, it is directing the draft and then catching what the draft got wrong. A model will happily hand you a paragraph that is grammatical, confident, and slightly off: the wrong tone for this recipient, a number it half-invented, a closing that sounds like a press release. The fundamentals did not disappear; they moved up a level. Knowing that the subject line is the headline and the first sentence states the purpose is what lets you look at a draft and say "no, lead with the decision" instead of shipping whatever came out. The tool got faster. The judgment is still yours.

Match the Format to the Job

Not every email wants the same shape. A two-line nudge and a decision memo are different animals, and forcing them into one house style is how you end up with a follow-up that reads like a thesis. The BLUF principle from earlier — conclusion first, detail underneath — bends to fit each type. Here is how I think about the common ones, with the rough length I aim for.

A Seven-Step Habit for Writing Emails That Get Answered

Good email is a habit, not a gift. I have watched plain writers outperform clever ones simply because they ran the same disciplined sequence every time. Here is the sequence I use. The order is doing real work, so resist the urge to skip steps when you are in a hurry.

1. Know what you actually want before you type. Two questions answer this: what do I need from this person, and what do they need to know to give it to me? When I cannot answer the first in a single sentence, the email is not ready — and honestly, half the time it turns out to be unnecessary once I have done the thinking.
2. Write the subject line first, and write it like a headline. Mailchimp's benchmark research found roughly 47 percent of people decide whether to open a message off the subject line alone. So treat it as the most important line you will write, not an afterthought. "Q3 marketing budget — approval needed by Mar 28" beats "Quick question" because it gives the reader the topic, the action, and the clock. Vague subjects get buried; specific ones get answered.
3. Put the point first. This is BLUF again. State the ask or the decision in the opening line or two, then add context underneath. If someone reads only your first paragraph — and many will — that paragraph should still get them to act. Burying the request under three paragraphs of windup is how requests die.
4. Build it to be scanned. Short paragraphs, two or three sentences each. Bullets when you are listing. Bold on the names, dates, and action items, because a skimming eye snags on bold. If you need a separate answer to several things, number them. Nobody reads your email the careful way you wrote it, so design for the way they actually read.
5. Tune the tone to the person, not the template. Mirror how they write to you. First names and casual greetings mean you can relax; formal salutations and full titles mean you should match. Unsure? Lean a notch more formal than feels natural — it is easy to warm up later and awkward to walk back a message that came off too familiar. Writing to someone in another culture, hold the jokes; irony rarely survives the trip.
6. Close by naming what happens next. End on something specific and dated: "Please reply with your approval by end of day Thursday." The soft closers — "let me know your thoughts," "looking forward to hearing from you" — feel polite but invite drift. Tell the reader exactly what you need and when, and you will get it more often.
7. Read it three times, then sit on the hard ones. Once for sense, once for tone, once for the dumb stuff: spelling, the attachment you forgot, the right name in the greeting. For anything with stakes, add the half-hour pause from earlier. Drafts you send the moment you finish them are the ones you wish you could unsend.

I keep a running, unscientific log of my own subject lines, and one pattern holds up year after year: a plain question ("Free Tuesday at 2?") gets a faster reply than a label like "Meeting request." The worst performer in my inbox, by a wide margin, is anything that opens with "FYI." Half of those never get opened at all, which tells you precisely how much information people expect behind that particular flag.

The Mistakes That Actually Cost You

The errors that hurt your reputation are almost never typos. They are structural and tonal. Hitting reply-all on something one person needed to see. Firing off an email when a ninety-second call would have settled it. And the quiet killer, passive-aggression dressed up as professionalism: "as per my previous email" reads to most people as "you ignored me, and now I am being icy about it." Say what you mean instead, and if the deadline slipped, name it without the dig. Cross-cultural email is its own hazard here. Humor and informality that play as friendly in your office can read as careless somewhere else, and you rarely find out until the relationship has cooled. Writing across a border, strip out the irony and lean courteous and plain.

Reading the Room: Etiquette by Situation

Who you are writing to changes the rules more than people admit. In a leadership role your email sets a tempo for the whole team, and there is a trap: the short, direct note that signals efficiency can tip into curt if you are not careful. Writing up the chain, lead with the decision or the number and keep the backstory thin; senior readers are the most ruthless skimmers in the building. Writing down to your reports, do the opposite — give them enough context to act on their own so you are not pulled into a follow-up call you could have prevented.

Client email is its own balancing act, polished and personal at once. That means the client's actual name, a reference to their actual situation, and none of the flavorless boilerplate that screams "you are recipient number forty in a mail merge." People can feel a template through the screen, and feeling like a template is the fastest way to feel unimportant.

On a remote or hybrid team, email stops being just correspondence and becomes the official memory. The decisions a co-located office would catch in a hallway have to be written down somewhere, and email is usually that somewhere. So distributed teams need their emails a notch more explicit: the deadline in the reader's own time zone, a clear note on where to follow up, and a quick acknowledgment when something important lands, because you cannot read a nod through a wall you do not share. Our workplace communication guide goes deeper on building these norms.

Working With an AI Draft Without Getting Burned

I use AI to draft email, so I am not going to scold you for doing the same. For routine messages it is genuinely faster, and when you are staring at a blank reply with no idea how to start, a serviceable first draft beats a blinking cursor. But I have been burned, and the burns are instructive. The model writes with total confidence whether or not it should, which means the dangerous output is not the obviously wrong paragraph. It is the smooth, plausible one that is subtly off for this reader, on this day, about this touchy subject.

So treat the draft as raw material, never the finished email. Let the tool rough out the structure, then read it as the recipient and fix what it cannot judge for itself. Does the formality fit the person, or does it sound like a brochure to someone you have known for years? Are the facts right, or did the model fill a gap with a confident guess? Has it kept any warmth, or sanded the message down to something correct and lifeless? Models turn a messy thought into a clean outline well. They are bad at the things that depend on context they never had — the history between you and the reader, the office politics, the joke that will or will not land. That part is yours, and it always will be.

Questions People Actually Ask Me About Email

Treat the templates and frameworks here as starting points, not commandments. The right email is the one that fits your reader and your culture. Terms of use.

Last reviewed: 2026-05-24