Writing Work Emails in English as a Second Language
If English is your second language, the hard part of a work email is rarely vocabulary. It is shape, register, and how direct to be. Those three things are learnable, and they do not require a bigger vocabulary. They require a small set of patterns you reuse.
This guide covers the shape of a work email in English, how formal to be, the sentence patterns that cover most situations, and the mistakes that are worth fixing.
Start with the shape, not the words
Nearly every work email in English has the same six parts, in this order:
- Subject line: what this is about, and what you need.
- Greeting: "Hi [name]," in almost every case.
- One line of context: why you are writing.
- The ask or the update: the actual point, in one or two sentences.
- Logistics: dates, files, links, next steps.
- Close: "Thanks," or "Best," and your name.
Written out, that is short:
Subject: Invoice 1042 is missing a PO number
Hi Ana,
We received invoice 1042 this morning, but it has no PO number, so finance cannot process it.
Could you send a corrected invoice with the PO number by Thursday?
The PO is 4471. Happy to re-send the original order if that helps.
Thanks, Marek
Once the shape is automatic, you stop translating a whole email and start filling in a form. That is also why English work email often feels blunt to speakers of languages with longer opening formulas: the form has no slot for them.
How formal to be
English work email sits lower than business register in German, Japanese, Korean, or Romanian, and higher than chat. A few defaults:
- Greeting: "Hi [first name]," is standard, including with people senior to you. "Hello [name]," is slightly more formal. "Dear [name]," is for first contact, applications, and formal or legal matters. "Dear Sir or Madam" reads as dated, so use a name if you can find one.
- Close: "Thanks," "Best," and "Best regards," all work. "Kind regards," is fine and common in British and European English. "Yours faithfully" and "Yours sincerely" belong in letters, not email.
- Titles: most English-speaking workplaces use first names immediately. Following the other person's lead is always safe.
If you are unsure, copy the register of the last message you received from that person. Matching is more reliable than guessing.
Be direct, it is not rude
The politeness in English requests is carried by the verb form, not by the number of softening words around it. "Could you" is already polite. Adding more does not add courtesy:
Before
I am sorry to disturb you and I hope this is not a problem, but I was wondering if it might perhaps be possible for you to maybe have a look at the attached document, if you have time?
After
Could you review the attached document by Friday?
The second version is polite, and the reader knows exactly what to do. The first version reads as anxious and takes three readings to find the request.
Five patterns that cover most emails
Learn these as fixed frames and change only the details.
Asking for something
Could you [do X] by [day]? [One line of why.]
Following up
Following up on [thing]. Do you have an update? Happy to help if something is blocking it.
Saying no
I can't take this on this week. I can start on [date] if that still works.
No apology loop, no invented excuse. A date makes a refusal cooperative.
Apologising
Sorry for the delay. [Then the actual content.]
One sentence, then move on. Repeating the apology at the end undoes it.
Confirming what was agreed
To confirm: [X] by [date], and I'll handle [Y]. Let me know if I've got anything wrong.
This last one is worth using often. It converts a long ambiguous thread into one checkable sentence, and it protects you when memories differ later.
Mistakes worth fixing
Literal translations of set phrases. These are grammatical but read as non-native or, in some regions, unintentionally curt:
- "Please do the needful" → "Could you [the specific thing]?"
- "Kindly revert" → "Let me know" / "Reply when you can"
- "I have something to discuss with you" → "I'd like to discuss the Q3 timeline"
- "I will inform you" → "I'll let you know"
- "Please be informed that" → delete it and say the thing
Over-apologising. Common for speakers of Japanese, Korean, and several European languages, where an opening apology is normal courtesy. In English it reads as a lack of confidence. One apology, or none.
"There's" with plurals. "There's a few issues" should be "There are a few issues". Spoken English breaks this rule constantly; written work email should not.
Capitalisation. Languages, nationalities, months, and days are capitalised in English: English, Romanian, March, Tuesday. Job titles and seasons are not, unless they come before a name.
Present perfect vs past simple in updates. Use the present perfect when the result matters now ("I've sent the file", meaning it is with you now), and the past simple when the time is stated ("I sent the file on Monday").
Articles. a, an, and the are the hardest part of English for speakers of languages without articles, and they are also the least costly mistake. They rarely change meaning. Spend your editing time on the ask and the dates instead.
Read it aloud before sending
Read the email out loud, slowly. If a sentence is hard to read aloud, it is too long, too abstract, or too indirect. Split it in two. This one test catches more problems than any grammar rule, and it works in any language.
Draft in your own language, then convert the paragraph
Writing the first version in the language you think in is a legitimate workflow, not a shortcut. You get the content right first, then deal with the English.
BlinkWrite supports 36 languages and detects the language you are writing in, so its corrections and suggestions come back in that language by default. To convert a paragraph:
- Put your cursor in the paragraph.
- Double-tap Tab to open rephrasing.
- Choose Custom and type an instruction such as "Translate this into English" or "Rewrite this in English, two sentences, keep the dates".
- Press Enter, review the result, and press Tab to apply it.
As you write in English, corrections appear as you go and use the surrounding thread to fit the fixes to what you meant, rather than applying rules blindly. Every suggestion is a preview. Nothing changes until you press Tab.
For the tone side of the same problem, see how to make an email sound more professional.
Common questions
Should I say my English is not perfect?
No. It draws attention to the language instead of the content, and it lowers how your message is read. Write the clearest version you can and let it stand.
Is it better to write short sentences?
Yes, and not only for second-language writers. Short sentences are harder to get wrong and easier to read. Two clear sentences always beat one long one with a grammar mistake in the middle.
Which English should I use, British or American?
Pick the one your company or your reader uses and stay consistent inside a message. The differences that matter in work email are small: organise/organize, cheque/check, and date order. Write "12 March 2026" or "March 12, 2026" rather than the ambiguous 12/03/2026.
Will an AI assistant make my writing sound like someone else?
It can, if you let it rewrite whole messages. Rephrasing one paragraph at a time, starting from what you actually wrote, keeps your structure and your facts and changes the wording around them. Review each suggestion before you accept it.