Written English is where politeness is easiest to get wrong, because tone has nowhere to hide. A direct sentence that sounds efficient in your language can read as an order in English.
Email is where second-language politeness is hardest to control, because tone has nowhere to hide. In speech, a direct request is softened by your face and your voice. In writing, the same words arrive bare — and a sentence that reads as efficient in your language can read as an order in English.
The good news is that professional English email is highly formulaic. A small set of structures and phrases covers almost everything you will need to write.
The skeleton
- Subject line — specific, and ideally actionable.
- Greeting
- Opening line — context or acknowledgement.
- Purpose — why you are writing, in one sentence.
- Detail — the content, kept short.
- Action — what you want and by when.
- Closing
Most weak emails fail at steps 4 and 6: the reader finishes without knowing why they received it or what they are supposed to do.
Subject lines
"Question" · "Hello" · "Urgent!!"
"Invoice 2024-114 — payment query" · "Design review: feedback needed by Friday" · "Meeting moved to Thursday 10:00"
A reader should be able to decide from the subject alone whether this needs them today.
Greetings, by formality
- Formal, name unknown: "Dear Sir or Madam," (rare now) — better: "Dear Hiring Team,"
- Formal, name known: "Dear Ms Patel,"
- Standard professional: "Hi Anna," or "Hello Anna," — the default in most workplaces.
- Group: "Hi all," / "Hi team,"
Two traps. "Dear Mrs" assumes marital status — use "Ms" unless you know otherwise. And "Dear Anna Patel" (title-less full name) sounds odd; use either the first name or the title plus surname.
Opening lines
"I hope you're doing well." — standard, safe, slightly empty, perfectly acceptable.
"Thanks for your quick reply." — better when it is true.
"I'm writing to ask about…" — when you want to get straight to it.
"Following up on our call yesterday…" — the best opening, because it gives context.
Making requests without sounding rude
This is the heart of it. English scales politeness through grammatical distance — the longer and more indirect the structure, the softer it sounds.
| Level | Phrasing |
|---|---|
| Direct | "Send me the report." |
| Neutral | "Could you send me the report?" |
| Polite | "Could you please send me the report when you get a chance?" |
| Very polite | "I was wondering if you could send me the report." |
| Softest | "Would you mind sending me the report when you have a moment?" |
The first row is not wrong, but between colleagues of equal rank it reads as brusque. Default to the middle rows. Adding "please" to an imperative does less work than learners expect: "Please send me the report" is still an instruction.
Softeners worth knowing
- "When you get a chance" · "at your convenience"
- "Just checking…" · "Quick question —"
- "It would be great if…" · "If possible, could we…"
- "I may have misunderstood, but…" — excellent for pointing out someone's error.
- "Sorry to chase, but…" — the standard opening of a polite reminder.
Delivering bad news or saying no
English tends to cushion a refusal rather than state it flatly.
"No, we can't do that by Friday."
"Unfortunately, Friday isn't going to be possible — the earliest we could manage is Tuesday. Would that work for you?"
Pattern: acknowledge, state the constraint, offer an alternative. Offering the alternative is what keeps a refusal from sounding like a wall.
Chasing without irritating
A first reminder should assume the best. "Just following up on the email below — I know things are busy. Any update on the timeline?" A second can be firmer and should mention consequence: "I wanted to flag that we'll need this by Thursday to keep the launch on schedule."
Closings
- Standard: "Best regards," · "Kind regards," · "Best,"
- Formal: "Yours sincerely," (named recipient) · "Yours faithfully," (unnamed) — mostly British and now uncommon outside formal letters.
- Warm professional: "Thanks," · "Many thanks," · "Thanks again,"
"Thanks in advance" is efficient but can read as presuming agreement. "Thank you for looking into this" is safer.
Small things that cause real misunderstandings
- "by" vs "until": "Send it by Friday" (before Friday) is not "I'll be here until Friday" (continuously up to).
- "next Friday": genuinely ambiguous to native speakers too. Write the date.
- Time zones: always state one. "15:00 CET" not "3pm".
- ALL CAPS reads as shouting.
- Exclamation marks: one is friendly, three look frantic.
- Phrasal verbs: fine in a normal email, less so in formal reports — see the fifty you need most.
Three templates to adapt
Request: "Hi Anna, I hope you're well. I'm writing about the Q3 budget — could you send the updated figures when you get a chance? We need them by Thursday to finalise the report. Thanks very much, Dev"
Apology: "Hi Tom, Apologies for the delay in replying — I was out of the office last week. To answer your question: yes, we can support that format. I'll send the specification tomorrow. Sorry again for the wait. Best, Dev"
After an interview: "Dear Ms Patel, Thank you for your time yesterday. I enjoyed learning about the team's plans for the new platform, and the conversation confirmed my interest in the role. Please let me know if you need anything further from me. Kind regards, Dev"
Written English improves fastest when it is connected to spoken practice, because the same politeness patterns operate in both. If you are preparing for work in English more broadly, see English for job interviews, and for the error patterns that surface most in writing, twenty common grammar mistakes.