A project manager I edit for once spent an hour on a single email: she drafted it, slept on it, revised it over coffee, and had a colleague check its tone. The result ran about 340 words, warm and careful. The actual request, a one-line answer about a delivery date, surfaced in paragraph four, phrased as "if you get a chance, absolutely no rush."
The recipient never replied. He read it, made a mental note to deal with it later, and forgot, because the email was built to be admired rather than answered.
Unanswered email is rarely a politeness problem; it is an engineering problem. The ask is buried, the deadline is implied, and the subject line says nothing. The fixes are mechanical, and mechanical things can be learned.
The subject line is a sorting decision
Nobody reads email in order. They triage, sorting each message into now, later, or never, and your subject line is the only text guaranteed to be read. Treat it as the headline of the message, not a formality standing between you and the send button.
A working subject line does two jobs: it names the topic specifically enough to act on, and it stays findable when someone searches for the thread in two weeks. "Quick question" fails both tests; it is the written equivalent of clearing your throat. "August ticket volume, need a rough number by Thu" delivers topic, request, and deadline before anything gets opened.
Searchability matters more than writers expect, because inboxes are searched rather than browsed, and a thread filed under "Hi Sarah" is functionally lost to both of you. If your team uses prefixes like [ACTION] or [FYI], honor them, and write subjects in sentence case rather than Title Case Like A Press Release; our guide to title case versus sentence case covers when each fits.
| Weak subject | Stronger subject | What changed |
|---|---|---|
| Quick question | August ticket volume by Thu | Topic and deadline visible unopened |
| Following up | Re: August ticket volume | Survives the inbox search box |
| Q3 report | Q3 report: need August numbers | Says what you want, not just what it concerns |
The three-sentence ask
Once the email is open, the body has one job: produce a reply. The most reliable shape is three sentences, in this order.
Context: why this email exists, from the reader's side of the desk. "We're finalizing the Q3 report this Friday."
Request: exactly what you need, phrased so it could be answered in one line. "I'm missing one number: support ticket volume for August."
Deadline: when you need it, and what happens then. "A rough figure is fine; could you send it by Thursday noon?"
Then stop. Every paragraph after the third is one more reason to defer.
The deadline sentence is where people flinch, so it deserves a defense: a date is not pressure, it is scheduling information. "Whenever you get a chance" forces the reader to guess your urgency, and busy people guess by ignoring. "No rush" is worse, because readers believe you. Write it, and you have donated your deadline to the void.
Cut the hedges while you are at it: "just wondering," "sorry to bother you," "if possible at all." Cutting filler words does more for an email's tone than any sign-off, because a message that knows what it wants never apologizes for wanting it.
One email, one topic
Two requests in one email is a reliable way to get one answered: the reader handles the easy one, feels productive, and closes the thread. The second question now lives in a buried conversation under a subject line about something else. If a second topic is urgent, send a second email; if it is not, park it out loud: "(The vendor contract is a separate question; I'll email about that next week.)"
Replies deserve the same discipline. Reply to all only when your answer changes what other recipients do next. When half a thread stops needing you, one courteous line, "Moving you to BCC to spare your inbox," lets you drop them cleanly; secret BCC, by contrast, has a habit of surfacing in an ill-considered reply-all later. And when you forward a thread, write the sentence at the top that says why. "FYI" is not a sentence.
Write for the skimmer
Your email will be read on a phone, in a hurry, by someone doing something else.
Short paragraphs, one idea each; white space is pacing, not waste. Put the ask in the first two lines, then whatever background the reader genuinely needs, which is usually less than you think. Anything enumerable, whether dates, options, or steps, belongs in a list, because paragraphs hide what lists reveal.
Bold exactly one line, the ask. One bolded line is a signpost; five bolded lines are wallpaper, and the reader stops seeing any of them.
Write dates in full, because "09/04" is April in some countries and September in others, while "Thursday 4 September" means itself everywhere. The habit is part of writing for a global audience, and the whole approach borrows from writing for the web, where readers hunt rather than read.
Deliver bad news first, and follow up without apologizing
Bad news obeys a rule that feels brutal and works: sentence one carries it. Burying bad news does not soften it; it moves the pain to paragraph four and adds the sting of having been managed. Give the reason and one concrete option in the same email, because a problem without a proposed fix is homework you are assigning to someone else.
Apologize once, at most. Apology inflation, the "so sorry, really sorry about this" reflex, reads as panic and spends credibility you will want for the next ask.
The follow-up is where polite writers fold. Waiting two or three business days is fine; apologizing for existing is not. "Just checking in" restates no information and re-asks nothing; it transfers your anxiety into the reader's inbox. A follow-up earns its keep by adding one new fact, whether the deadline moved, the reason firmed up, or an alternative appeared.
If the second email also sinks, change the channel: a two-minute call resolves what a third email cannot. Silence is usually triage, not a verdict.
A before-and-after rewrite
Here is a Monday-morning email of the kind every manager receives, followed by the same message rebuilt.
What changed? The compliment went, because Dan's launch can be praised in the hallway, and in email it reads as a cushion. The apology for the dashboard went too, since raising Dan's tooling delay only made the ask feel heavier to grant. The second question got its own future email instead of dying inside a thread about something else, and "no rush" became a real deadline with a built-in out, which makes saying yes easier, not harder.
Frequently Asked Questions
How long should a professional email be?
As short as the ask allows, which for most business email means five sentences or fewer. If a draft needs twelve, it contains two emails or a meeting request in disguise. Split it, or book the meeting.
Should I open with "Dear" or "Hi"?
Match the reader. "Dear" survives in formal first contact, legal correspondence, and cultures where formality is expected; "Hi" with a first name works nearly everywhere else. What matters is matching the register the other person already uses.
How long should I wait before following up?
Two or three business days for internal requests, closer to a week for external ones. Follow up once with new information, then pick up the phone rather than sending a third nudge.
Is it rude to send a very short email?
No. Short reads as confident, and busy readers are grateful for it; the rude email is the one that makes someone hunt for its point. Spend a clause on warmth, not three paragraphs.
What is the best sign-off?
"Thanks," "Best," or your name alone. Sign-off inflation, the "warmest regards and many thanks in advance" reflex, adds words and subtracts sincerity. Pick one and stop worrying about it.
Read it as Dan before you send
Before your next email goes out, reread it the way Dan will: on a phone, skimming, hunting for the reason it exists. If the ask is not findable in ten seconds and answerable in one line, keep cutting until it is. Run it through a grammar checker once, then send. The whole craft fits in one sentence: make replying the easiest thing your reader does all day.