In this unit, students control register (formal ↔ informal) and adjust tone (direct, polite, diplomatic, firm) in professional emails and meetings. Focus: precise wording, softening, and credible professional voice.
Fine for close colleagues and quick messages, but may sound too casual or urgent.
Clear, polite, and efficient for most workplaces.
Useful for external clients, sensitive situations, or hierarchy.
could you… · would you mind… · when you have a moment… · if possible… · just to confirm… · for your reference…
I see your point; however… · That’s a fair concern. My view is… · I’m not sure that approach would… · Another way to look at this is…
Please let me know if… · If you’re happy with this, I’ll… · Could you confirm by…? · I’ll follow up on…
Just to clarify… · When you say ___, do you mean ___? · Could you expand on…? · What’s the key priority here?
I understand the rationale; however… · I’m not fully convinced that… · My concern is… · Could we consider an alternative?
So, to summarize… · The takeaway is… · We’ve agreed to… · Next steps are… · Let’s assign owners for…
If I could just finish my point… · Let me come back to that… · Can we park that for later? · I’d like to hear ___’s view.
Label each as: too blunt / too casual / too vague / good tone.
1) “Send me the report now.”
2) “Heyyy can u send the report lol”
3) “It would be great if the report could maybe be sent soon.”
4) “Could you send the report by 2 PM? Thanks.”
Rewrite in: (a) informal, (b) neutral, (c) formal.
“We can’t approve this because it’s missing key information.”
Role-play a meeting. Use 6 phrases:
clarify · disagree · propose · summarize · assign · close
Subject → greeting → context → request → next steps → thanks/close
A project is behind schedule. The team must decide priorities, adjust timelines, and communicate risks. Each student has a role (manager / analyst / client / operations).
One student delivers a 30–45 second meeting summary using formal-neutral register.
“I want” → “I’d like to…”
“You must” → “We’ll need to…” / “Could we…?”
“This is wrong” → “I’m concerned that…” / “It may be worth reconsidering…”
Swap placeholders with real file paths. Keep links consistent:
/levels/c1/assets/.