How to Teach Business Email Writing (A Practical Framework)
Teach business email writing by giving students a four-move framework — purpose in line one, context, an ask with a deadline, and a sign-off that matches the relationship — plus coded feedback limited to three to five errors per draft. Email is the highest-stakes writing your professional learners do: it is short, high-frequency, and judged within seconds by people making decisions.
Why is email the highest-stakes writing genre?
An email is the only document most professionals write daily that real colleagues judge immediately. That combination — high frequency, real audience, instant consequences — makes it a better target for writing lessons than essays, reports or cover letters.
Three properties create the pressure:
- It is short. A typical work email runs 80–150 words. There is nowhere to hide: every sentence is visible, and there is no introduction paragraph to warm up in.
- It is frequent. A project manager can send 40 emails a day. Small weaknesses — a vague ask, a wrong tone — are not occasional errors; they are habits repeated dozens of times a week.
- It is judged instantly. A recipient decides within seconds whether the writer is competent and whether the email deserves a reply. A buried request means the deadline passes. Over-formality reads as distant; over-familiarity with a new client reads as careless.
And unlike a class essay, failure has teeth: the meeting does not get scheduled, the invoice does not get paid, the client quietly goes elsewhere. That is why professionals will pay for this training even when they are sceptical about "English lessons".
What are the four moves of a professional email?
Every effective professional email, regardless of length, does four things in order. Searches for how to teach business email writing mostly surface lists of formulaic phrases; the skeleton below travels further. Teach structure first, style later.
- Purpose in line 1. The subject line names the topic and the action ("Q3 report — move deadline to Friday?"), and the first sentence states why you are writing. No "I hope this email finds you well" — professional readers treat warm-up paragraphs as noise to skim past.
- Context. Two or three sentences of background the reader needs and nothing more. Context answers: what happened, and what should I know before evaluating the request?
- The ask, with a deadline. One action, stated explicitly, with a date: "Could you approve the invoice by Thursday 12 June?" Vague asks — "let me know your thoughts", "at your earliest convenience" — reliably produce vague responses.
- Sign-off register. The sign-off is a dial, not a rule: "Best regards" for formal contexts and first contact; "Thanks" or "Cheers" for established, warm working relationships. Matching the relationship matters more than matching a textbook.
Students can apply this skeleton to their real work emails the same day, which is exactly what makes it worth teaching before anything finer-grained.
How does register differ across business cultures?
Research on international business communication documents consistent tendencies in how different cultures frame written requests — tendencies, not laws, with individuals varying more than cultures do. (Erin Meyer's The Culture Map is the accessible summary of that research.) Three patterns come up constantly with learners:
UK. Indirectness functions as politeness. Requests are hedged ("I was wondering whether it might be possible…"), refusals are softened ("I'm afraid that won't be workable"), and understatement carries weight — "that's not quite what we agreed" can mean "you breached the contract". The risk: American and non-native readers may miss the message entirely.
US. Directness with positive framing. Get to the ask quickly and soften with warmth rather than hedging: "Quick one — can you send the deck by 3pm?" Negatives exist but are shorter, and the general register is friendlier and less formal than UK business English.
German and Japanese conventions. German business culture tends to value directness and precision — a blunt "this is not possible" is often meant as efficient rather than rude, and UK-style hedging can read as unclear or even evasive. Japanese business communication leans the other way: more reliance on shared context, refusals rarely stated outright ("that would be difficult" usually means no), and explicit demands risking abruptness.
Teach these as diagnostic tools, not scripts. The skill is reading the recipient: a Japanese learner writing to a Berlin supplier should not export Japanese indirectness, and a German learner writing to a London client should not export German bluntness. Discussing where their own culture sits — and what feels "rude" to them in other people's emails — is one of the most valuable conversations you can have with a professional learner.
What does a good rewrite actually look like?
The fastest way to teach the four moves is a before-and-after, rebuilt live. Here is a typical learner draft:
Subject: Report
Hi John,
I hope you are well and you had a nice weekend with your family. I am writing because I wanted to ask about the possibility of having some more time for the report that we talked about in the meeting last Tuesday, because as you know I have been working on the Henderson account and it has been taking a lot of time, and also my colleague was sick on Monday so I had to do her part of the presentation too.
So if it is possible, maybe I can send you the report on Friday instead of Monday? Sorry for the inconvenience and thank you very much in advance.
Best regards,
Maria
Notice what is actually wrong: almost nothing at sentence level. The grammar is passable. It fails on structure and register — the purpose arrives in line six, the context is a maze, the apology is unearned, and the reader has to excavate the ask. Now the four moves applied:
Subject: Q3 report — move deadline to Friday?
Hi John,
Could the Q3 report go to you on Friday instead of Monday?
The Henderson account has taken longer than planned, and I covered a colleague's presentation on Monday.
Happy to talk it through if Friday causes problems.
Thanks,
Maria
Every fix is structural: purpose moved to line 1, context cut to two sentences, the ask placed first with the deadline attached, and the sign-off relaxed to match a familiar colleague. One live rebuild like this teaches more than an hour of error correction.
How should you give feedback on drafts?
Correct drafts with codes, not rewrites — and cap it at three to five errors per piece. A full rewrite shows the student a perfect email but not the distance between theirs and yours, and a draft covered in red ink teaches them that their writing is hopeless rather than that it is editable.
Use a small, consistent code set: T tense, WO word order, WF word form, P preposition, ^ something missing, X unnecessary, R register problem. Mark the location; let the student supply the fix. Then run a second draft, and only compare versions at the end.
Which errors to mark? Recurring ones and high-stakes ones — a register failure that would offend a client outranks a comma. If everything is marked, nothing is learnt.
In live lessons, do the coding together on a shared document — ten minutes of co-editing a real email beats an annotated PDF returned cold. A collaborative document in your virtual classroom makes this natural, and the wider drafting-and-feedback sequence is covered in how to teach writing skills online.
Six practice tasks that cover the professional range
A task bank beats random prompts, because each task trains a specific communicative challenge. These six cover the situations professional learners meet most often:
| Task | The challenge it trains | Level |
|---|---|---|
| Chase an unpaid invoice | Polite persistence — build it as a three-email sequence, gentle to firm | B1+ |
| Decline a meeting invitation | Saying no without damage; offering a concrete alternative | B1+ |
| Ask for a deadline extension | Owning a problem early without over-apologising | B1+ |
| Introduce yourself to a new client | One memorable sentence about yourself; inviting a next step | A2+ |
| Escalate a problem to a supplier | Fact-led complaint; stating impact; requesting specific action | B2+ |
| Follow up a quote that went quiet | Recovering a stalled deal without nagging; giving an easy exit | B2+ |
Two of these pair directly with the register section: the invoice chase works as an escalating sequence where the third email is deliberately firmer, and declining a meeting is a masterclass in cultural indirectness — try it addressed to a London client, then to a Berlin one, and compare what changes. For one-to-one work with senior professionals, where much of this lands hardest, the specifics are covered in teaching business English to executives.
Frequently asked questions
What level do students need before studying business email writing?
Around B1 for the full framework: register work and hedging language need a reasonable base of grammar and vocabulary. Below that, you can still teach the skeleton — purpose in line 1, one clear ask with a deadline — using short, simple emails. Structure improves an email at any level.
Should I correct every error in a student's email draft?
No — cap it at three to five per piece, and prioritise recurring errors and register problems over one-off slips. Mark them with codes rather than corrections so the student does the fixing. A draft covered in red ink teaches a student that their writing is hopeless; five well-chosen codes teach them to edit.
How formal should a business email be?
As formal as the relationship, not the genre. First contact with a senior person or a new client leans formal; a colleague you email daily should be short and plain. The most common learner mistake is permanent maximum formality — every sign-off "Best regards", every sentence hedged — which reads as distant and even insincere.
How long does it take to see improvement in email writing?
Structure improves fast: the four moves are teachable in one lesson, and students can apply them to their real work emails immediately. Register takes longer — expect six to eight weeks of regular drafting and feedback before a student reliably adjusts tone to the reader. Both improve fastest when students bring in their real emails.
Can I teach business email writing to group classes?
Yes, with peer review doing the heavy lifting. Students draft individually, then swap drafts and check each other against the four moves: is the purpose in line 1, is the ask specific, does the register match? Peer review scales your feedback, and reading other learners' drafts builds the same evaluation eye that coded correction develops.