Most work emails fail before the recipient finishes the first sentence. They bury the request, hedge the ask, or make the reader do the work of figuring out what's actually needed. Writing a clear email isn't about sounding formal — it's about respecting the reader's time.
Lead with the ask
The single biggest improvement you can make: put the request in the first two sentences. Not the background, not the apology for writing — the request.
- Weak: "Hope you're doing well! I wanted to touch base regarding the project we discussed a few weeks ago, as there have been some developments..."
- Strong: "Can you approve the revised budget by Thursday? Context below."
If the reader only sees the preview line in their inbox, they should already know what you need.
This inverts how most people write, which is chronologically — here's what happened, here's what followed, therefore here's what I need. That order works when you're speaking and fails on the page, because the reader is deciding whether to keep reading during the part where you haven't said anything yet.
One email, one topic
Emails with three unrelated asks get one answered and two forgotten. If you genuinely need three things from the same person, number them explicitly — or better, send the unrelated ones separately so each can be forwarded, delegated, or resolved on its own thread.
Separate threads also survive the real life of an email: one gets forwarded to finance, one gets answered and closed, one stays open for a fortnight. Bundled into a single message, all three are hostage to the slowest.
Make the subject line do work
"Quick question" and "Following up" are dead subject lines. Compare:
- "Budget approval needed by Thu 6/12"
- "Draft contract attached — two clauses flagged"
- "No action needed: June metrics summary"
That last pattern — explicitly marking FYI emails — builds enormous goodwill. People learn your subject lines mean something.
Front-load the important words. Mobile inboxes truncate at roughly forty characters, and a great many recipients triage on a phone before they ever open anything.
Format for scanning, not reading
Nobody reads work email top to bottom. They scan. Help them:
- Keep paragraphs to three lines or fewer.
- Use bullets for anything list-shaped.
- Bold the deadline or the key number, sparingly.
- Put details, background, and links below the ask, not above it.
For anything long, open with a two-line summary under a "Short version:" label, then the detail beneath. The people who need depth read on; everyone else gets what they needed in five seconds. This single habit does more for a long email than any amount of tightening.
Be specific about who does what
"Can someone look at this?" addressed to six people gets looked at by nobody — the diffusion of responsibility is entirely predictable and entirely avoidable. Name the person. If several people have actions, put each name against its action.
Use To for people who must act and Cc for people who only need to know, and honour the distinction consistently enough that recipients can rely on it. Cc'ing someone's manager to add pressure is noticed, resented, and remembered.
Match tone to the relationship, not the template
Stiff, over-formal email reads as cold or passive-aggressive to a close colleague; breezy email reads as careless to a new client. The words are only half the message — the register is the rest. If you find yourself rewriting the same message five times trying to hit the right tone, a dedicated rewriting tool can help: paste the rough version, pick the tone you're aiming for, and review exactly which words changed before you copy it back.
Watch the phrases that carry more edge than intended. "As previously mentioned," "per my last email," "just following up on this again," and "as I'm sure you're aware" all read as reprimands regardless of intent. If a sentence performs patience, it is not being patient.
Close with a clear next step
End with who does what by when. "Thoughts?" is not a next step. "If I don't hear back by Friday, I'll proceed with option A" is — it converts silence into progress instead of a stall.
That construction is worth using deliberately. It gives a busy person permission to not reply, removes the follow-up chase from your week, and makes the decision either way.
Attachments and formatting that survive the trip
If you're attaching a document whose layout matters — a proposal, an invoice, a signed agreement — send a PDF rather than a Word file. Word documents reflow depending on the recipient's fonts and version, so the carefully balanced page you sent may not be the page they open. See PDF vs Word.
Name the file so it makes sense in a downloads folder: 2026-06-05_Proposal_Acme.pdf, not draft final v3.pdf. And mention the attachment in the body — attaching without saying so means half of recipients miss it, and forgetting to attach at all is the most common email mistake there is.
The 30-second reread
Before sending, reread the email once pretending you're the recipient seeing it cold. Is the ask visible in the first two lines? Could any sentence be cut entirely? Is there anything that could be misread as blame? That half-minute pass catches most of what makes email go wrong.
Add recipients last, after the message and the attachment are both done. It costs nothing and it prevents the two worst email accidents — the half-written message sent early, and the right message sent to the wrong autocompleted name.
