How to write a professional email (that actually gets read and acted on)

The most common problem with professional emails: the important thing is buried.

You spend three sentences on context, two on background, one on caveats, and then finally in sentence seven you say what you actually need. By then, many readers have already moved on.

Good professional email writing is a specific skill.

The fundamental principle: lead with the ask

Most people write emails the way they think through problems: chronological, context-first, conclusion at the end. This mirrors how we internally process things, but it's the wrong structure for emails.

Readers scan. They decide within the first two seconds whether to read, skim, or defer. If your subject line and first sentence don't tell them what you need and why it matters to them, you've lost them before they start.

The right structure:

1. What you need (the ask)
2. Why it matters or what it's for (context)
3. What you've done so far / what you need from them specifically
4. By when

Context supports the ask. Not the other way around.

Subject lines

A subject line has one job: get the email opened by the right person. That means:

Be specific. "Quick question" is not a subject line. "Decision needed: launch date for Q2 campaign" is a subject line.

Include the action if there is one. "ACTION NEEDED: approve by Friday" or "FYI: project status update" sets expectations before they open it.

Don't tease. Subject lines that create mystery ("You might want to see this") work in marketing newsletters. They're annoying in professional contexts.

Bad: "Following up" Better: "Following up on the vendor proposal: decision needed by Thursday"

The opening line

Don't start with "I hope this email finds you well." It wastes the most valuable real estate in the email.

Don't start with extensive context. Lead with the reason you're writing.

Templates that work:

• "I'm writing to request approval for [X] by [date]."
• "Quick update on [project]: [one-sentence summary of where things stand]."
• "Following up on our conversation about [X]: I need [specific thing] to move forward."

How to write the body

One email, one ask. If you have multiple asks, either prioritize one or use numbered bullets to make each ask explicit. Never bury a second important request in the middle of a paragraph.

Paragraphs should be short. Three to four sentences maximum. White space makes emails easier to scan.

Use formatting when helpful. Bullet points for lists. Bold for the single most important thing. Never both bold AND italics: it looks like every word is fighting for attention.

Put dates in plain language. Not "end of week." "By 5pm Friday, March 21." Include time zones if there's any ambiguity.

Tone calibration

Professional email tone is not the same across all contexts. There's a spectrum:

Formal: New client, senior stakeholder you don't know, written record of a decision. Use complete sentences, no abbreviations, explicit subject and close.

Professional-casual: Colleague you work with regularly, follow-up on something you've already discussed verbally. Slightly shorter, less formal structure, still clear.

Direct: Internal team members, people you work with every day. Short sentences, sometimes even fragments when clarity is maintained. The goal is speed and clarity, not formality.

Match the tone to the relationship and the stakes, not your default.

Following up

The professional art of following up is underrated.

If you sent an email that needed a response and didn't get one, following up is not aggressive. It's responsible. Most non-responses are not rejections. People got busy and forgot.

A good follow-up: - References the original email specifically - Restates the ask briefly - Gives a clear deadline if there is one - Is short: three sentences maximum

Example:

"Following up on my March 15 email re: the vendor proposal. I need a go/no-go by Friday to hold the slot. Let me know if you have questions in the meantime."

One follow-up is always appropriate. A second is appropriate if the stakes are high. After three attempts with no response, escalate or move on. Don't keep sending the same email.

What not to do

Don't use passive voice for asks. "It would be helpful if you could..." is much weaker than "Please review and let me know by Thursday."

Don't apologize for sending. "Sorry to bother you, but..." undermines your ask before you make it.

Don't CC people unnecessarily. Every unnecessary CC creates noise and diffuses accountability. CC people who need to be informed. BCC is for blind copies. Use it sparingly.

Don't send an email when a conversation is better. If an issue has nuance, involves emotions, or has already bounced back and forth three times in writing: pick up the phone or schedule a 15-minute call. Some things are just faster spoken.

Re-reading before sending

Before you send, ask: - Would someone reading only the subject line and first sentence understand what this email is about? - Is my ask clear and specific? - Do I have a clear deadline or next step stated? - Is this email necessary at all, or would a Slack message do it?

The last question is worth taking seriously. If your ask can fit in one sentence and needs a quick yes/no, it's probably a message, not an email.

Practice professional communication drills with AI coaching. Get scored on clarity, directness, and how you handle high-stakes conversations. Free, no signup required.