The professionals I teach are rarely held back by grammar. They are held back by register — the difference between English that is correct and English that lands the way you intended. "Send me the report" is grammatically perfect and will annoy a colleague in London. "I don't understand" in a meeting is accurate and makes you sound less competent than you are.
This guide covers the three situations your working English is judged on most: email, meetings and presentations. It is a phrase bank with reasoning attached, because phrases you do not understand are phrases you will misuse.
Register: the thing nobody teaches you
English encodes politeness mainly through indirectness and distance. The more words you put between the request and the verb, the softer it becomes. This is why direct translations from languages that mark politeness differently — with verb endings, particles or honorifics — so often land as brusque.
| Directness | Example | Use it when |
|---|---|---|
| Very direct | Send me the file. | Urgent, to someone who reports to you, in an established informal team. |
| Neutral | Could you send me the file? | Almost always safe. The default for colleagues. |
| Softened | Would you mind sending me the file when you get a moment? | A favour, a busy senior colleague, or a repeat request. |
| Very indirect | I was wondering whether it might be possible to see the file at some point. | Awkward requests, sensitive topics, or someone senior you do not know. |
The over-correction trap
Being too indirect has costs too. Wrap every routine request in three layers of hedging and colleagues start to find you hard to read — or, worse, miss that you have asked for something. Neutral is the correct default; escalate only when the situation genuinely calls for it.
Softeners worth having automatic
- Modals: could, would, might — "This could be an issue" rather than "This is a problem".
- Hedges: slightly, a little, somewhat, fairly — "I'm slightly concerned about the timeline".
- Distancing tenses: "I was hoping you could…" is softer than "I hope you can…".
- Negative questions: "Wouldn't it be better to…?" invites agreement rather than defending a position.
- Impersonal framing: "There seems to be a gap in the data" instead of "You missed some data".
Email: structure first, politeness second
Most difficult emails are difficult because they are badly organised, not because they are impolite. Fix the structure and the tone usually fixes itself.
The four-part email
- Purpose, in the first line. "I'm writing to ask about…" Readers decide whether to keep reading in about two seconds.
- Context, as briefly as possible. Only what the reader needs to act.
- The ask, on its own line. One sentence, with a deadline if there is one.
- Close. One line. No new information.
Before and after
Before: "Dear Sir, I hope this email finds you well. As you may know we have been working on the migration project since last quarter and there have been many challenges including the vendor delay and also the testing environment which was not ready and I wanted to update you and also ask something."
After: "Hi James — a short update on the migration, and one decision I need from you.
We're two weeks behind, mainly because the test environment wasn't available until the 14th.
Could you confirm by Thursday whether we should push the launch to 3 May, or cut the reporting module
from phase one?
Happy to talk it through if that's easier."
Subject lines that get opened
- Say what it is and what you need: Migration launch — decision needed by Thu
- Front-load the keyword: Invoice 4471 — query on line 3
- Avoid the empty ones: Quick question, Update, Following up.
Openings and closings by situation
| Situation | Opening | Closing |
|---|---|---|
| Routine colleague | Hi Ana, | Thanks — [name] |
| First contact, formal | Dear Ms Okafor, | Kind regards, |
| Chasing something | Hi Ana — just circling back on this. | No rush if it's in hand. Thanks, |
| Delivering bad news | Hi Ana, I'm afraid I've got some awkward news about… | Sorry to be the bearer. Happy to discuss options. |
| Declining | Thanks for thinking of me on this. | Sorry I can't be more helpful this time. |
Phrases that quietly damage you
- "Please do the needful." Widely understood in some regions, read as odd or curt elsewhere. Replace with a specific request.
- "Revert back to me." Means "return to a previous state". Use "get back to me".
- "I am writing this mail to inform you that…" Three redundant clauses. Just say the thing.
- "Kindly send…" Sounds formal to the writer and slightly commanding to many readers. "Could you send…" is safer.
- "As per my last email." Universally read as annoyance, whatever you intended.
Meetings: eleven moments and what to say
Meetings punish hesitation. By the time you have assembled the perfect sentence, the topic has moved. The fix is to have short, automatic phrases for the eleven moments that recur in every meeting, so the only thing you have to compose is the content.
| Moment | Say this |
|---|---|
| Interrupting politely | Sorry, can I jump in here? / If I could just add something… |
| Holding your turn | Just to finish that thought… / One more thing and then I'll stop. |
| Disagreeing | I see it slightly differently. / I take your point, but I'd argue… |
| Agreeing with a caveat | Broadly yes, with one reservation… |
| Not understanding | Sorry, could you unpack that a little? / Just so I'm clear — do you mean X or Y? |
| Buying time | That's a good question — let me think for a second. |
| Deferring | Can I come back to you on that after the call? |
| Bringing someone in | Priya, you've dealt with this before — what's your read? |
| Refocusing | Just conscious of time — shall we come back to the main decision? |
| Summarising | So where we've landed is… / To pull that together… |
| Closing with actions | Actions: I'll do X by Friday, Ana's picking up Y. Anything I've missed? |
Never say "I don't understand"
It puts the failure on you and gives the speaker nothing to work with. Say instead: "Could you unpack the second part?" or "Just so I'm clear — do you mean the Q3 figures or the forecast?" A specific question shows you were following closely.
The three-second rule for interrupting
In most English-speaking business cultures, the gap you are waiting for will not arrive. Speakers hand over by lowering their pitch at the end of a clause; if you wait for a full pause, someone else takes it. Start your interruption phrase as the pitch drops. It feels rude for about a week and then it feels normal.
Video calls specifically
- Say your name before you speak in larger calls: "Ravi here —". It removes half a second of confusion and marks you as organised.
- Use the chat as a backup. If you cannot get in, type the point. It still counts.
- Over-signal transitions. On video, people miss body language, so verbal signposting ("Two things — first…") does more work than it would in a room.
Presentations: signposting is the whole trick
Audiences forgive accent, hesitation and simple vocabulary. What they do not forgive is not knowing where they are. Signposting — telling people the structure and reminding them where you have got to — makes a presentation feel professional even when the English is imperfect.
The signposting skeleton
- Frame: "In the next ten minutes I'll cover three things: where we are, what's blocking us, and what I need from you."
- Transition: "That's the current position. Turning to the blockers…"
- Emphasis: "If you take one thing away from this slide, it's this."
- Data: "What this chart shows is… The important line is the orange one."
- Recap: "So, to bring that together…"
- Handover to questions: "That's everything from me — happy to take questions."
Handling questions you cannot answer
This is the moment professionals fear most, and it has a formula:
- Acknowledge: "That's a fair challenge."
- Say honestly what you know: "I don't have the figure in front of me."
- Commit: "I'll check and come back to you by tomorrow."
Three sentences, delivered calmly, read as authority. Bluffing reads as the opposite, and English-speaking audiences are unusually alert to it.
Rehearse the first ninety seconds only
Nerves peak at the start. If the opening is genuinely automatic — word for word, out loud, five times — you arrive at the body of the talk already settled. Rehearsing the whole thing to that standard makes you sound recited; rehearsing the opening does not.
Interviews and performance reviews
Both are situations where you must talk about your own work in a way that many cultures find uncomfortable. Two structures do most of the work.
STAR, for behavioural questions
Situation, Task, Action, Result. Keep situation and task to two sentences combined; spend most of the answer on action, and always finish with a result, quantified if you can.
"Our release process was taking four days and slipping most months (S/T). I mapped where the time went, found that two-thirds of it was waiting for manual sign-off, and proposed an automated check with a single approver (A). We got it down to under a day, and we haven't missed a release date since March (R)."
Talking about achievements without discomfort
- Use "we" for context and "I" for your action. Accurate and comfortable.
- Attach numbers. Numbers feel like reporting rather than boasting.
- Name the difficulty. "It was harder than we expected because…" makes the achievement credible.
- Avoid the reflexive minimiser. "It was nothing really" undercuts the whole answer, and in an interview it is heard literally.
Phrases for the awkward questions
| Question | Opening you can rely on |
|---|---|
| Your biggest weakness | "Something I've actively worked on is… Concretely, what I changed was…" |
| Why you left | "I'd got as far as I could in that role, and I wanted to move towards…" |
| Salary expectations | "Based on the scope you've described, I'd be looking in the region of…" |
| A failure | "The clearest one was… What I'd do differently now is…" |
| Any questions for us? | "Two, if that's all right. First…" |
How to practise this without a class
- Rewrite one of your own emails a week. Take something you sent, apply the four-part structure, and compare. Fifteen minutes, and it transfers immediately.
- Keep a phrase card open during calls. Six phrases, on screen. Use two per meeting. After three weeks you will not need the card.
- Record your next presentation rehearsal and count the signposts. Most people find they have one where they needed five.
- Collect language from your own inbox. The best business English textbook you will ever have is the correspondence of colleagues whose tone you admire. Note their openings, hedges and closings.
- Shadow one minute of a conference talk daily for rhythm and emphasis.
The gap between correct English and effective English at work is mostly a gap of a few hundred phrases used at the right moment. That is a very tractable problem — far more tractable than "improving my English", which is not a goal anyone can act on.
Questions people ask about this
Neutral is the safe default: a first-name greeting, a clear one-line purpose, a direct request phrased with “could you”, and a short close. Escalate formality for first contact, senior recipients outside your organisation, or sensitive subjects; relax it once the other person relaxes theirs.
Ask a specific question: “Could you unpack the second part?” or “Just so I’m clear — do you mean the Q3 figures or the forecast?” A precise question signals that you were following closely, whereas a blanket statement of confusion gives the speaker nothing to respond to.
It is widely understood in South Asian business contexts but reads as unusual or curt to many other English speakers. Replace it with a specific request — “Could you approve the invoice by Friday?” — which is clearer for everyone regardless of region.
Use a short signal phrase — “Sorry, can I jump in here?” — and begin it as the current speaker’s pitch drops at the end of a clause, rather than waiting for a full pause. In most English-speaking business cultures the pause you are waiting for never arrives.
Add signposting and rehearse only the first ninety seconds. Audiences tolerate imperfect grammar easily but lose patience when they cannot tell where they are in your argument; explicit structure phrases fix that faster than any vocabulary work.
No. Intelligibility, clear structure and appropriate register determine how you are received far more than accent does. Work on word stress and sentence rhythm, which affect intelligibility, rather than on imitating a particular national accent.
The short version
Effective business English is mostly register and structure. Default to neutral politeness, put the purpose in the first line of every email, keep automatic phrases ready for the eleven recurring meeting moments, and signpost presentations heavily. None of it requires advanced vocabulary.
