Guide series
Professional Writing
At work, how you write is how you're read. These guides help ESL professionals write business English that sounds clear, direct, and natural — fixing the recurring mistakes, structuring emails and reports, and calibrating tone for a US workplace without losing your voice.
At work your writing arrives before you do. The email gets read by six people, three of whom have never met you, and it forms an opinion whether or not it deserves to.
These guides are for professionals whose English is fluent but whose writing keeps landing at the wrong temperature: too formal, too tentative, too long, or accidentally blunt.
- 01
Slack, Teams, and Workplace Chat: Tone Rules for ESL Professionals
Email has rules you can learn. Chat feels lawless, emoji, fragments, silence that might mean anything. Here's how US workplace chat tone actually works, and how to sound natural without guessing.
Read guide → - 02
How to Write Clear Business Reports in English (an ESL Guide)
If English isn't your first language, business reports can feel like a trap of formal words and long sentences. They shouldn't. Here's a plain, repeatable structure for reports that get read, understood, and acted on.
Read guide → - 03
Business Email Structure for ESL Professionals
A practical guide to business email structure for ESL professionals, sound clear, direct, and natural in US workplaces without being stiff or over-apologetic.
Read guide → - 04
Common ESL Business Writing Mistakes (and How to Fix Them)
A practical guide to the most common ESL business writing mistakes: articles, run-ons, over-formality, and false cognates, with clear wrong-to-right fixes.
Read guide →
The sixty-second check before you hit send
Not a style guide. Just the six things that go wrong most often in the emails we get sent.
- The ask is in the first three lines. Context can wait; a busy reader may never get to line eight.
- There is exactly one ask. Two requests in one email reliably produce one answer.
- The deadline is a date, not "as soon as possible".
- No sentence runs past about twenty-five words. Long sentences are where non-native and native writers both lose the thread.
- Nothing is hedged twice. "I was just wondering if you might possibly" is four hedges and reads as anxiety.
- The subject line would still make sense to someone searching their inbox in March.
The email builder walks through this for six common situations, and the clarity checker flags the long sentences and filler for you.
Tone: what it sounds like versus what you meant
Directness translates badly between languages. These three patterns account for most of the misreadings we see in US offices.
Reads as Please do the needful and revert by EOD.
Try Could you send the updated file by 5pm today? Happy to help if anything is unclear.
Both are polite in their own register. Only one reads as polite in a US inbox.
Reads as I am afraid I must inform you that the report will unfortunately be delayed.
Try The report will be late. I can have it to you Thursday morning, and here is what pushed it.
Formality is not the same as professionalism. Bad news reads better plain, with a new date attached.
Reads as You did not send me the numbers I requested last week.
Try I think the numbers may have got lost. Could you resend when you have a moment?
Accurate, but it puts the reader on trial. Softening the accusation while keeping the request is the whole skill.
Clear is not the same as simple
A common worry among ESL professionals is that plain writing will make them sound less capable, so the sentences get longer and the vocabulary gets heavier. It has the opposite effect. Senior people at US companies write short. It reads as confidence, because only someone who knows the subject can afford to be brief about it.
What actually signals expertise is precision: the right noun, a real number, a specific date. "We saw a significant improvement" says less than "response time dropped from 400ms to 90ms", and it takes more words to say it.
The two places this matters most are recurring: the emails covered in business email structure, and the longer documents in how to write clear business reports. If the recurring mistakes are what you want to fix first, common ESL business writing mistakes is the shortest route, and workplace chat tone covers Slack, where the rules are different again.
For a document that matters, a person is still better than a checklist. Professional Writing Clarity is a structured edit of something you already wrote, aimed at clarity and tone rather than grammar policing.
Common questions from ESL professionals
Will plain English make me sound less educated at work?
It does the opposite in a US workplace. Short, direct sentences read as senior. Dense, formal phrasing reads as either junior or translated, and it slows the reader down, which is the one thing an email should never do.
How do I sound polite without sounding uncertain?
Keep the softener, drop the stack. One hedge is courtesy: "could you", "when you have a moment". Three hedges in one sentence reads as apology. Ask directly, then be warm at the end rather than tentative at the start.
Do you correct grammar or rewrite the document?
Neither, exactly. We edit for structure, clarity, and tone, and we explain the changes so the next document needs less help. If you want a text rewritten from scratch in someone else's voice, we are the wrong service.