Email writing

How to Write a Professional Email

Professional email isn't about sounding formal — it's about being clear, being appropriately direct, and not accidentally sending a message that lands differently than you intended. Here's how to do it.

Start with the subject line

A good subject line tells the recipient what the email is about before they open it. That's it. No cleverness required.

Good subject lines are specific and short:

"Q3 report — feedback needed by Friday"
"Following up on our call yesterday"
"Question about the contractor agreement"

Weak subject lines are vague or missing entirely:

"Quick question" (quick for whom?)
"Following up" (on what?)
"Hi" (not a subject line)

If your email requires action, say so in the subject: "Action needed: approve budget by COB Thursday" is better than "Budget update."

Open without the filler

"I hope this email finds you well" and "I hope you're doing well" are the two most-written email opening lines in professional communication. They're also filler — written because people don't know how else to start, not because they add anything.

Start with the reason you're writing. That's what the recipient actually wants to know:

Avoid

I hope this email finds you well. I wanted to reach out about the project timeline and see if we could schedule some time to discuss it.

Better

I wanted to flag a potential delay in the project timeline before our next sync. Can we find 20 minutes this week to discuss?

If you have an existing relationship, a brief personal opener is fine — "Good to see you at the conference last week" — but it should be genuine and short, not a placeholder.

Get to the point in the first two sentences

Most professional emails bury the ask or the key information three paragraphs in. Readers skim; anything that's not immediately clear gets missed.

The first two sentences of your email should tell the recipient: (1) what this email is about and (2) what, if anything, you need from them. Everything else is context.

Avoid

As you may know, we've been working on the new onboarding flow for the past few months. There have been some challenges with the integration that the team has been working through. I wanted to let you know where things stand and discuss some options for how we might approach the remaining work given the timeline constraints we're facing.

Better

The onboarding flow integration is running two weeks behind schedule. I want to walk you through our options for recovering the timeline — can we meet Thursday?

Email etiquette in the workplace

Professional email norms vary by company culture, but these principles hold across most workplace contexts:

Reply to all — carefully. "Reply all" on a thread with 20 people when only one person needs your answer is one of the most reliable ways to irritate colleagues. Ask: does everyone on this thread actually need this reply?
CC sparingly. CC is for people who need to be informed but aren't required to act. If you're CCing someone to hold them accountable or to make a point, that's a different conversation that shouldn't happen over email.
Don't send emotional email. If you're frustrated, angry, or anxious when writing, wait. The email you write in that state will almost always be worse than the one you write an hour later.
One topic per email. Multi-topic emails get partial replies because recipients handle the first thing and forget the rest. If you need responses to three separate issues, send three short emails or use a numbered list.
Match the formality of the relationship. Emailing your manager's manager for the first time should feel different from emailing a colleague you've worked with for two years. Read the context.

Tone: where most professional emails go wrong

The most common professional email problem isn't structure — it's tone. Emails that seem clear to the writer land as terse, aggressive, passive, or unclear to the reader.

Common tone problems and what they look like:

Unintentionally terse. "Got it. Will do." — fine in Slack, reads as cold in email. Short emails need a little more warmth to avoid landing abruptly.
Passive-aggressive framing. "As I mentioned in my previous email..." — almost always reads as a rebuke, even when not intended that way. Just restate the information.
Over-hedging. "Just wanted to quickly check in to see if maybe you might have had a chance to look at this..." — hedging to the point of seeming unsure of your own request. Be direct; you can be polite and direct at the same time.
Overly formal. Using legal or overly corporate language ("please be advised," "pursuant to," "kindly") in everyday workplace email makes you sound stiff and creates unnecessary distance.

Before you hit send

Read the email out loud once before sending. If something sounds off when spoken, it'll sound off when read. This catches awkward phrasing faster than any other review method.

Ask: does this email say what I mean? Does the tone match the relationship? Is there anything here that could be read differently than I intend?

For high-stakes emails — to a new client, a senior stakeholder, or in a difficult conversation — it's worth an extra check before you send.

Send Ready

Run your draft through Send Ready before hitting send

Paste your email, pick your intent — cold outreach, follow-up, feedback request, delivering bad news — and get an AI tone check plus a copyable rewrite in seconds.

Try it free