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.
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.
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.
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.
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 like Wrivio can help: paste the rough version, pick the tone you're aiming for, and review exactly which words changed before you copy it back.
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.
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.
