A lot of people assume "professional" means longer words, more formality and extra padding. So they write "Per my previous correspondence, I would like to kindly request..." and end up sounding like a legal notice. In practice, the emails that come across as most professional respect the reader's time. They get to the point, take responsibility, and make the next step obvious.

Below are five principles that cover most of it, each with a before-and-after example based on the kinds of emails people send every day.

1. Lead with the point

If your request is buried in the third paragraph, the reader has to dig for it. Say what you need in the first two sentences and put the context after.

Before

"Hi Sarah, I hope you're doing well! I've been meaning to reach out for a while now. As you may know, we've been working on the quarterly report, and there have been a number of challenges with the data pipeline that I won't get into here. Anyway, the reason I'm writing is that we might need a bit more time..."

After

"Hi Sarah, I'd like to request a two-day extension on the quarterly report, to Thursday the 18th. The data pipeline issue from last week set us back, and I'd rather send you verified numbers than rushed ones. Everything else is on track."

The second version answers "what do you want?" straight away, gives one relevant reason, and confirms nothing else is slipping. It takes a few seconds to read instead of most of a minute.

2. Replace hedging with a clear position

Hedges like "I think maybe," "sort of" and "I could be wrong but" feel polite when you write them, but they make you sound unsure. You can stay open to pushback without undercutting your own point.

Before

"I think maybe we should possibly consider moving the launch? I could be totally wrong here, but it sort of feels like the testing window might be a little tight?"

After

"I recommend moving the launch by one week. The current plan leaves three days for testing, and our last two releases each needed five. Happy to walk through the numbers if useful."

The "happy to walk through" stays as a real offer. Everything else becomes a clear recommendation backed by evidence.

3. Focus on next steps, not blame

When something goes wrong, spend one sentence on what happened and the rest on what happens next. Blaming someone in writing, even fairly, almost always comes across worse than you meant it to.

Before

"This is the third time the design team has sent us assets in the wrong format, which is why the page is broken again. We can't keep working like this."

After

"The page broke again because the assets arrived in the wrong format, the same issue as the last two sprints. To stop this from recurring, I'd like to set up a shared export checklist with the design team. Could we get 15 minutes this week to agree on it?"

The facts and the firmness are the same, but the effort goes into fixing it, and a manager could forward this email without wincing.

4. Cut the filler

"Just circling back," "quick question," "sorry to bother you," "when you get a chance." Each one is harmless alone, but together they suggest even you don't think the email matters. Cut them and say what you need.

Before

"Sorry to bother you again! Just circling back on this real quick, no worries at all if you're busy, but whenever you get a chance, it would be great to maybe get your thoughts!"

After

"Following up on the proposal below. Could you send your feedback by Friday? That keeps us on schedule for the client review on Tuesday."

The second version also explains why there's a deadline. Giving a reason makes it a request instead of a demand.

5. End with a clear request

Make every email easy to reply to. If the reader gets to the end and can't tell whether you need a decision, a document or just an acknowledgment, the email will sit in their inbox. They probably do care, but replying would take effort.

Before

"Anyway, those are the three options. Let me know your thoughts!"

After

"Of the three options, I recommend B: lowest cost, and it doesn't block the mobile work. Could you confirm by Thursday so I can brief the vendor Friday morning?"

A recommendation, a deadline and the reason for the deadline. The reader can reply in one word.

Phrases to replace

Common phrases that weaken emails, and what to write instead:

When not to formalize

Don't apply all of this to a colleague you chat with every day. If your teammate sends you two-line messages with emoji and you reply with structured memos, the formality itself sends a message, and they'll read it as distance or annoyance. How formal you should be depends on the relationship and the stakes, and a thread with your closest collaborator can be casual and still professional. For more on getting that balance right, see the formal vs. casual tone guide.

Related guides

Want to improve a specific sentence from your draft? Type it into BetterWayOfSaying.com and get three alternatives.