Business English: Politeness Is Structure, Not Words

When people say business English is hard, what they experience is one of two failures. Both are register errors and they look like opposites.

1. Too blunt. You write Send me the file. The grammar is perfect, but in English that sentence belongs to a manager addressing a subordinate, or to someone who is annoyed. Sent to a client it reads as rude — or, more damagingly, as the English of someone who does not have much English, after which your other opinions start getting weighed more lightly.
2. Too stiff. You overcorrect: I would like to kindly request that you please confirm the attached document at your earliest convenience. Nothing in it is wrong. It simply does not sound like a person, and readers answer it the way they answer an automated notice.

The second failure is more common than people think, because most business English teaching is twenty years out of date. Please be advised that, herewith, as per our conversation, Please do not hesitate to contact me — still printed in textbooks, largely gone from real offices. Use them and you are not being formal, you are being dated, which is a different and less flattering thing.

Underneath both failures sits one mechanical fact: English carries politeness in sentence structure, not in vocabulary. Many languages mark it elsewhere — in verb endings, in pronoun choice, in a separate honorific register. English has almost none of that. There is no polite form of send. So the politeness machinery those speakers are used to has nowhere to go, and what lands on the page is a bare imperative; the learners who notice reach for decoration, and that is how failure one becomes failure two. The machinery English actually uses is four devices: modal verbs, tense, sentence form, and hedges. That is the whole system.

Before the devices, a demonstration. Here is one request — get me that file — at five settings. No new vocabulary appears anywhere.

• Send the file. — an instruction. Fine from your manager, fine in a long-running group chat, wrong almost everywhere else.
• Can you send the file? — a colleague you know. Neutral, slightly casual.
• Could you send the file over? — the default. Safe with clients, strangers and your boss alike. If you learn one, learn this.
• Would you be able to send the file by Thursday? — for a request that costs the other person something, or where you are imposing a deadline.
• I don’t suppose you could send the file? — genuinely awkward asks, or asking a second time.

Five levels, one verb. Now the harder moves, the ones learners avoid entirely because they have no template for them:

• Pointing out a mistake. Not This part is wrong. but I think this part might need a second look. English deletes the person: you correct the document, not the author.
• Saying no to a deadline. Not It is difficult because the schedule is tight. but That’s going to be tight on our side — could we look at Monday instead? An English refusal arrives with an alternative attached; a bare no reads as the end of the conversation.
• Chasing a non-reply. Just following up on this. / Any update on the invoice? / Bumping this up your inbox — I still need the PO number by Thursday. None of these is rude. Three days for the first chase, then weekly.

Every fix above is built from words you learned in your first year: could, might, I think, a second look, on your side. What changed was the skeleton — imperatives became questions, assertions became guesses, and people left the subject position. For a wider stock of moves organised by function rather than situation, useful English expressions covers the general-purpose set.

Here are the devices themselves. Learn these and the phrasebook becomes unnecessary, because you can generate the phrase you need instead of remembering it.

1. Modal verbs — the distance dial. Can → could → would be able to, as in the ladder above. The rule of thumb: could for requests, would for proposals (Would Friday work?), might for criticism (This might need another pass), should only when you have the standing to say it.

2. Past tense — distance, not time. The device almost nobody is taught, and the one that changes the most. In English the past tense doubles as a politeness marker: put a present-tense intention into the past and the sentence steps backwards out of the reader’s space.

• I want to check one thing. → I wanted to check one thing.
• I wonder if you can help. → I was wondering if you could help.
• I hope to have it by Friday. → I was hoping to have it by Friday.

Every sentence on the right refers to right now. The past form is not describing an earlier moment, it is taking the pressure off. I was wondering if you could… is probably the most-used polite request frame in English offices, and is worth learning as one unbreakable chunk rather than as grammar.

3. Question form — leaving room to refuse. Turning an instruction into a question creates formal space for a no. The other person will almost never use it; offering it is what politeness consists of. Let’s do it Friday. → Would Friday work for you? / Fix the numbers on page 3. → Could we double-check the numbers on page 3? Note the we there: a second device stacked on the first, converting their error into a shared task.

4. Hedges — turning assertions into impressions. a bit, slightly, just, I think, it seems, might, a quick. There is a problem. → There seems to be a slight issue. / You’re wrong. → I’m not sure I follow — could you walk me through it? / This is late. → This is running a bit behind.

And the warning that has to come with all of this, because it is where enthusiastic learners end up: stack all four in one sentence and you are back at failure two. I was just wondering if you might possibly be able to perhaps take a quick look? does not read as polite, it reads as anxious — and at work, anxious reads as junior. One device per sentence, two at most. The goal is not maximum softness, it is the right amount.

You can fix every sentence and still produce an email that feels foreign, because what is wrong is the structure rather than the grammar.

Put the subject in the subject line. Not a greeting, not your name, not Hello from Acme. The reader should know what this is before opening it: Invoice 4021 — missing PO number, Quick question re: Thursday deadline, Deck for Friday review — draft attached. A subject line naming the thing and the action gets answered faster than a polite one.

Put the ask in the first paragraph. This is the big structural difference and it costs people real money. In many business cultures an email builds: context, apology for the intrusion, then the request somewhere around line nine. English-language readers do not read email, they scan it — and a request on line nine is a request that did not happen. Invert it. Paragraph one: what you need. Two: why. Three: by when. Leading with the ask is not rude, it reads as respect for the reader’s time.

Stop apologising for existing. Sorry to bother you, but…, Apologies for the trouble… — used once these are fine, used as a default opener they lower your status, and lower-status requests genuinely get actioned later. Try Quick one for you — or One thing before Friday: instead. Save the apology for when you have something to apologise for, and then do it properly; how to say sorry in English covers getting the strength right, which matters more than the frequency.

Attachments and sign-offs. Please find attached the document. is not wrong, just old. I’ve attached the deck — changes are on slide 4. is how people write now. Sign-offs in order of distance: Sincerely (letters, rarely email any more) → Best regards / Kind regards (first contact, external) → Best (the default) → Thanks (when you have asked for something) → Cheers (British, informal). If you want one for every occasion, use Best.

Match, don’t guess. The cheapest register trick in email is to copy the other person. If they opened with Hi Sarah, do not reply with Dear Ms. Chen — that pushes the distance back out and they will notice. Their greeting, sign-off, contractions and paragraph length are a free specification for how to answer them.

Email gives you time. Meetings do not, which is why people who write competent English freeze in them. Four problems account for nearly all of it.

Not interrupting. In plenty of workplace cultures cutting in is rude; in an English-language meeting, never cutting in reads as disengagement. Stay silent to the end and you are not remembered as courteous, you are remembered as someone without a view — and across a year of reviews that compounds. Three sentences fix it: Can I jump in here? / Sorry, just to add to that — / Before we move on, can I check one thing? All three are entirely normal and native speakers use them several times a day.

Not disagreeing. So people either say nothing or, on a brave day, say I disagree, which lands harder than they intended. English disagreement starts with agreement and then turns the angle: That makes sense — my only concern is the timeline. / I see it slightly differently. / Could we look at it from the client’s side for a second? Avoid opening with an apology; apologising while you object makes the objection sound retractable.

Not buying time. The hardest three seconds in a second language is the silence while you assemble a sentence. Fill it on purpose with something prepared: Good question — let me think about how to put this. / Give me a second on that one. / So, two things. That last one is unusually useful, because it starts you talking while also giving your answer a shape to walk into.

Letting a missed word go. Saying Sorry? gets you the same sentence again, louder. Ask specifically and you get back only the fragment you lost: Sorry, did you say Tuesday or Thursday? / Could you spell the company name? / I missed the last part — what’s the deadline? People who ask precisely understand far more than people with better ears and no repair strategy.

Two additions. The small talk before a meeting is part of the meeting, not a waste of it — going straight to the agenda reads as cold rather than efficient. And phone calls are a level harder than meetings because you lose the face: telephone conversation in English has scripts for the calls you cannot avoid.

Finally, how to get this into your hands rather than your notes. Five hundred memorised phrases do not arrive when you need them. Thirty of your own do.

Use your own mailbox as the corpus. Open the last ten work emails you wrote in any language and write down only the move each one made: request, refuse, report a delay, confirm, reschedule, apologise, chase, share. Almost everyone lands on eight or fewer. Situations are infinite; moves are not. Write each of your eight at three settings — casual, default, formal — and you have twenty-four sentences covering most of your working life. Keep a folder of well-written incoming mail too: it is a free corpus matched exactly to your industry, which no textbook can be.

Run the register drill. Once a day, take one sentence and write it three times: rudely, neutrally, very formally. Then write down what you changed — modal, tense, sentence form, hedge. It sounds trivial and it is the only exercise that trains register directly, because it forces you to manipulate the four devices rather than recognise them. Two weeks and the dial starts moving without conscious effort.

Record a two-minute status update. Say out loud what you did this week and what is blocked, then listen back. That two minutes is the most frequently demanded speaking task in working life and unprepared it collapses every time. If interviews are also ahead, English job interview phrases drills the same muscle under more pressure.

Then check it against a person. This is where solo practice runs out. Register has no answer key — it is confirmed only by someone’s reaction. Whether Could you send it over? is too light here, or Would you be able to is laying it on, is not in any book. Use your prepared requests on a real person and watch their face; awkwardness is visible almost immediately. CoffeeTalk pairs you with native speakers for short conversations, and fifteen minutes twice a week is enough to calibrate.

One last expectation to reset, because it stops people noticing their own progress. Getting better at business English does not feel like acquiring impressive phrases. It feels like the opposite: plain words, the email finished in three minutes instead of twenty, the reply coming back at the temperature you aimed for. Four structures get you there. The other four hundred and seventy phrases were never the point.