Lesson 12, Workplace & Professional Emails
The last type, and the one where pitching the register is hardest.
Assumes Lesson 6. This lesson covers only what’s different about workplace emails.
When you’ll see it
- “…write to your manager / supervisor…”
- “…inform your team that…”
- “…you are unable to attend the meeting…”
- “…request time off…”
- “…raise an issue with a colleague…”
Typical situations: requesting leave · notifying a manager of a problem or delay · declining a task or meeting · updating a team on a change · raising a workplace concern · handing over responsibilities before an absence.
What the bullets usually ask
| Bullet | Usually | Your paragraph must |
|---|---|---|
| 1 | Explain the situation | State the facts plainly and early |
| 2 | Describe the impact / give details | Show you’ve thought about consequences for others |
| 3 | Say what you propose | Offer a solution, this is what separates professional from merely correct |
The defining feature of a strong workplace email: you don’t just report a problem, you bring a proposal. A manager reading “the deadline will slip” learns something. A manager reading “the deadline will slip; here are two ways to handle it” learns something and gets help.
The register problem: two ways to get it wrong
Workplace is the trickiest register to pitch, because there are two failure modes pulling in opposite directions.
Too stiff
❌ “Dear Sir, I am writing to humbly request your gracious consideration of my application for annual leave. Your kind cooperation would be most appreciated.”
This is over-formal to the point of sounding archaic. It also wastes words.
Too casual
❌ “Hey Sarah, so I’m gonna need next Thursday off, hope that’s cool!”
This is a register failure with a manager, even a friendly one.
The target: professional but human
✅ “Dear Ms. Reyes, I am writing to request three days of annual leave, from 14 to 16 May. I have checked the team calendar and this period appears to be relatively quiet.”
The rule of thumb:
| Recipient | Register |
|---|---|
| Manager, senior colleague, HR, external client | Formal: no contractions, full name, “Dear Ms. Surname” |
| A teammate you work with daily | Semi-formal: first name, light contractions, no slang, warmer close |
Semi-formal is the register most people never practice. It’s worth knowing: warm enough to be a colleague, professional enough to be forwarded to someone else.
The tone rule: never make it someone else’s fault
Workplace questions often involve a problem, a delay, an error, a conflict. The instinct is to explain who caused it. Resist it.
| ❌ Blame-shifting | ✅ Professional |
|---|---|
| ”The delay was caused by the design team." | "The design stage took longer than anticipated, which has pushed the timeline back." |
| "Nobody told me about the change." | "I wasn’t aware the schedule had changed, which is something I’ll address by…" |
| "It’s not my responsibility." | "This sits slightly outside my area, but I’d suggest…” |
Neutral, factual, forward-looking. Describe what happened, not who failed. Raters reward the tone; so do real managers.
Model answer, FORMAL (to a manager)
Question: A project you are leading will not be finished by the agreed deadline. Write to your manager. • Explain the situation • Describe how it will affect the schedule • Say what you propose to do
Dear Ms. Reyes,
I am writing to let you know that the Kestrel report will not be ready by Friday as originally scheduled, and I wanted to flag this early rather than closer to the deadline.
The data-verification stage has taken considerably longer than anticipated. Two of the regional datasets arrived incomplete and had to be requested again, which added roughly a week to a stage we had allowed three days for.
The practical effect is that the full report would now be ready by the following Wednesday. I am conscious that this overlaps with the board pack deadline, which is why I did not want to leave it any later to raise.
I would propose one of two approaches. Either we deliver a partial report on Friday covering the three complete regions, with the remainder following on Wednesday, or we move the whole submission to Wednesday and I use the additional time to strengthen the analysis. I would be glad to proceed with whichever you prefer.
Happy to discuss further if it would be useful.
Regards, Tomás Herrera
196 words.
Why it scores: bad news stated in sentence one, with the reason for raising it early · completely neutral about cause: “the datasets arrived incomplete,” not “the regional teams failed to send them” · impact paragraph shows awareness of someone else’s deadline · bullet 3 offers two fully specified options and defers to the manager · formal throughout, full name.
Model answer, SEMI-FORMAL (to a teammate)
Question: You will be away from work for two weeks and a colleague will cover your responsibilities. Write to them. • Explain what you need them to cover • Give the details they’ll need • Offer to help them prepare
Hi Anika,
Thanks again for agreeing to cover while I’m away from the 8th to the 22nd, I really appreciate it, and I’ve tried to make it as painless as possible.
There are only two things that genuinely need attention. The first is the weekly client report, which goes out every Tuesday morning; the template is in the shared drive under “Reporting” and it’s mostly a matter of pulling the figures across. The second is the Halloran account, Marcus tends to email midweek, and he usually just needs a quick acknowledgement rather than a full response.
Everything else can safely wait until I’m back. I’ve put a short handover note in the team folder with logins, the reporting steps, and a few things to watch for.
Would you like to sit down for half an hour on Thursday so I can walk you through it? Easier to show you than to write it all out. And do message me if anything urgent comes up, I’d genuinely rather you did.
Thanks again, Joel
192 words.
Why it scores: pitched semi-formal: first name, light contractions, warm but entirely professional and safe to forward · scopes the work down (“only two things”) which is considerate and specific · gives genuinely usable detail (file locations, timing, who emails when) · bullet 3 offers a concrete meeting and ongoing support · a semicolon and complex structures keep the range up.
The pitfall unique to workplace emails
Reporting a problem without proposing anything.
The weak workplace email explains the situation clearly, describes the impact accurately, and then stops, leaving the manager to solve it. It technically covers three bullets but reads as passive, and bullet 3 ends up under-developed.
The fix: whenever the third bullet is “say what you will do” or “suggest what should happen,” give two options and defer the choice. It’s a small structural habit that consistently produces a fuller final paragraph and a more professional tone.
Second pitfall: apologizing excessively to a manager. One acknowledgement is professional; four is uncomfortable to read and eats the words you need for your proposal.
Grade your own workplace email
- Situation stated plainly in the first sentence: no burying
- Register correctly pitched: formal to a manager, semi-formal to a teammate
- Nothing blames anyone: neutral, factual, forward-looking
- Impact on others acknowledged
- Bullet 3 proposes a solution, ideally two options
- Choice deferred to the recipient where appropriate
- No excessive apologizing
- Specific, usable detail (dates, file names, names, times)
- At least two complex sentences
- 175–195 words
8+ ticks = Level 9 territory. All 10 = you’re competing for 11–12.
Your practice
Open one set on Celpora and put today’s lesson to work.
Practice Task 1: Email. 27 min · AI feedback on all four dimensions
