How to Write a Professional Email in English at Work

Email is where most professionals do the majority of their English, and it is the easiest place to improve, because you have time to compose and edit. Writing a professional email in English is largely a matter of a fixed structure and a set of reusable phrases: once you have both, the daily writing load stops being a daily decision.

What is the structure of a professional email in English?

A professional email in English has six parts: subject line, greeting, purpose, context, detail and close. The purpose belongs in the first sentence rather than the third paragraph, because the reader is scanning for what you need before deciding how much attention the rest deserves.

The reason this matters is volume. Microsoft's 2025 Work Trend Index, based on usage data plus a survey of 31,000 knowledge workers across 31 markets, found that the average employee receives 117 emails a day alongside 153 chat messages, and is interrupted roughly every two minutes. Your email is competing with more than a hundred others for a few seconds of attention.

The working shape:

1. Subject line — the specific ask, with a date if there is one
2. Greeting — "Hi [name]," in most cases
3. Purpose — one sentence, first line
4. Context — two or three sentences of reasoning
5. Detail — bullets for dates, numbers, options
6. Close — next step, owner, sign-off

Fixing this shape has a particular benefit for second-language writers: you stop designing each message and start filling six slots. Most of the hesitation in work email comes from deciding what goes where, not from the English itself, and a fixed structure removes that decision entirely.

What makes a good subject line?

A good subject line names the action and the deadline, not the topic. "Q4 budget" tells the reader nothing about whether to open it now; "Approval needed: Q4 budget by Thursday" tells them exactly what happens if they do not, which is what determines whether it gets opened at all.

Patterns that work:

Purpose	Subject line
You need a decision	"Approval needed: Q4 budget by Thursday"
You need information	"Question: which supplier for the March order?"
You are informing only	"FYI: launch moved to 18 September"
You are following up	"Following up: contract review (sent 2 Sept)"
You need something urgently	"Today if possible: signed NDA for Deniz"
You are sending a deliverable	"Attached: final campaign brief for review"

Two habits help. Put the deadline in the subject line rather than burying it in paragraph three, and use a prefix — "Approval needed", "FYI", "Question" — so the reader can triage without opening. Both are standard in English-language business email and neither reads as pushy.

A third habit is worth adopting: change the subject line when the topic changes. Long reply chains where the subject no longer matches the content are almost impossible to search later, and they are one of the most common reasons a decision cannot be found six months on.

How do you open and close an email in English?

Use "Hi [name]," for colleagues and most clients, and "Dear [name]," for formal or first contact. Close with "Best regards" or "Kind regards", which are safe in nearly every professional context and carry no risk of sounding either cold or over-familiar to the reader.

Openings, from most to least formal:

• "Dear Ms Novak," — formal, first contact, external
• "Dear Deniz," — formal but warmer
• "Hi Deniz," — the default for most work email
• "Hi both," / "Hi all," — small groups
• "Deniz," — very direct; use only with people you know well

Closings:

• "Best regards," / "Kind regards," — safe everywhere
• "Best," — colleagues and familiar clients
• "Thanks," — when you have made a request
• "Yours sincerely," / "Yours faithfully," — formal letters only, rarely needed in email

Skip "I hope this email finds you well." It is not wrong, but it consumes the most valuable line in the message and experienced readers skip past it. If you want a warm opening, make it specific and short: "Hope the launch went well last week."

One regional note. Some markets expect noticeably more formality in first contact than others, and the safe strategy when you do not know is to open one notch more formal than feels natural, then match whatever register the other person replies with. Mirroring is a reliable rule and it costs you nothing.

Keep in mind who is on the other end. Ethnologue's 2025 language rankings put worldwide English speakers at about 1.53 billion, with roughly 390 million first-language speakers, so in most international correspondence your reader is also working in a second language. Plain vocabulary and short sentences are read as considerate, not as simple.

How do you make a request without sounding demanding?

Add one softener to the request and keep the ask specific. English carries politeness in modal verbs and hedging phrases rather than in verb endings, so a direct translation from many languages can be grammatically correct and still read as an order rather than a request.

Requests, from softest to firmest:

• "Whenever you have a moment, could you take a look at the draft?"
• "Could you send me the numbers by Thursday?"
• "I'd appreciate it if you could confirm today."
• "I need the signed copy before Friday to keep the date."

All four are professional. The difference between them is urgency, not politeness, and choosing the right level is a judgement about the situation rather than about English. One softener is enough; stacking three makes the actual request hard to find.

Always name the deadline and the reason:

"Could you confirm the venue by Wednesday? The caterer needs 48 hours' notice."

The reason is what turns a demand into a shared problem, and it also pre-empts the reply asking why. In a second language, every exchange you avoid is time saved and one less opportunity for misunderstanding.

Avoid one common overcorrection: apologising for the request itself. "Sorry to bother you, I'm really sorry but could you possibly..." signals that you think the request is unreasonable, which invites the reader to agree.

How do you say no in an English email?

Give a reason, offer an alternative, and close warmly. A bare refusal reads as a wall in English, whereas this three-part structure declines the specific request while protecting the relationship and leaving the wider conversation open for a different version of the same ask.

The pattern:

"Thanks for thinking of me. I can't take this on before the 20th — the migration is taking all my capacity this month. Could Deniz cover it, or would the week of the 22nd work?"

Useful phrases for the refusal itself:

• "That's difficult on this timeline."
• "I won't be able to get to this before [date]."
• "I'd rather not commit to that until we've seen the legal response."
• "That's outside what we agreed in the scope — happy to quote for it separately."

Note that none of these says "no" directly, and none is evasive either. Each states a real constraint, which is what makes the refusal credible and hard to argue with. A refusal without a reason invites negotiation; a refusal with a specific constraint usually ends the exchange.

The alternative you offer does not have to be a full solution. Naming a later date, a different person or a smaller version of the request is enough to show you are trying to solve the problem rather than avoid it.

How do you follow up without sounding pushy?

Reference the original message with a date and repeat the ask in one line. A follow-up that assumes good faith — the reader is busy, not ignoring you — keeps the tone neutral while still creating a record that you asked twice, which matters if the delay later causes a problem.

Three escalating levels:

• First follow-up (3–4 days): "Just following up on my note from Tuesday — do you need anything from me on the budget?"
• Second (a week): "Checking in on this again. Is the 18th still realistic, or should I plan for a later date?"
• Third (escalating): "I haven't been able to move this forward without the approval. Deniz, copying you in case there's a faster route."

The third adds a person rather than adding pressure, which is usually the more effective move and does not damage the relationship with the original recipient. Note that it also gives them an easy exit: they can reply immediately rather than explain the delay.

Two details make follow-ups work. Always include the original date, because it converts a vague nudge into a factual record. And always restate the ask in one line rather than saying "see below" — the reader should not have to scroll to remember what you wanted.

How do you build a personal phrase bank?

Save the sentences that work. When you receive an English email whose tone you want to copy, paste the phrasing into a running file organised by situation: requests, refusals, follow-ups, bad news, thanks. Within a few months this becomes a template library shaped by your own job.

This is the Word Bank step in the Worklish method applied to writing, and it is more efficient than studying vocabulary lists because every entry came from a real message sent to you, in your industry, at your level of seniority. Generic lists teach you phrases you will never need; your inbox teaches you the ones you need weekly.

The phrases you collect will also be role-specific. An export documentation email and a code review comment need different registers, different tolerances for hedging and different levels of precision, and Worklish organises written scenarios by industry and role at five levels for exactly that reason.

EF's English Proficiency Index 2025, which assessed writing alongside speaking across 123 countries and 2.2 million test takers, found speaking to be the weakest skill for most learners — which makes writing the natural place to build phrases before you need them out loud.

For the wider set of written formats — status updates, reports, channel choice and tone — see our complete guide to business English writing.