5 exercises — identifying email parts (subject · context · CTA · closing), writing effective subject lines, and choosing the right professional tone.
Professional email anatomy
Subject: one-line summary — status keyword + topic + date/deadline if relevant
Greeting: "Hi [Name]," (informal) — "Dear [Name]," (formal) — never skip it
Context: What happened? Which system? Since when? Who is affected?
Call to Action: specific ask + who needs to do it + deadline
Closing: "Thanks," / "Best," / "Regards," — one word is enough
0 / 5 completed
1 / 5
A colleague sends you this email:
"Hi, I was wondering if maybe we could potentially fix the bug that's been causing some issues with the login flow at some point before the next release if it's not too much trouble?"
Which part of a professional email is most broken here?
The main problem is the call to action — the actual request is buried in uncertainty ("wondering if maybe", "potentially", "some issues", "at some point", "if it's not too much trouble"). A professional email CTA should be: specific (what needs to happen), scoped (which bug), and time-bound (by when). Better: "Could you prioritise the login-flow bug before the v2.4 release on Friday?" The five parts of a professional email: Subject · Greeting · Context/Body · Call to Action · Closing.
2 / 5
You need to email the team that the production deployment is delayed until tomorrow. Which subject line is most effective?
"DELAYED: Production deployment — rescheduled to 2026-03-17 09:00 UTC" — A good subject line should be a one-line summary that lets the reader decide urgency without opening the email. Best practices for IT email subjects: ① Start with a status keyword if relevant: DELAYED / ACTION REQUIRED / FYI / RESOLVED / REMINDER. ② Name the system or project. ③ Add a time or date if actionable. Option A is too vague. Option B assumes the reader knows the context. Option D is a full sentence — subject lines should be fragments, not sentences.
3 / 5
Read this email and identify which labelled section is the Context (background) rather than the Call to Action.
"[A] Hi Sam, [B] The staging environment has been returning 503 errors since the overnight deployment at 02:00 UTC. [C] Could you roll back the deployment and confirm once staging is stable? [D] Thanks, Alex"
Section B is the Context: it states what happened (503 errors), which system (staging environment), and since when (since the overnight deployment). Section A is the Greeting. Section C is the Call to Action ("Could you roll back…"). Section D is the Closing. The structure Greeting → Context → CTA → Closing is the baseline for clear professional emails. Good context sentences answer: What happened? Where? Since when? Who is affected? — so the reader has everything they need before the ask.
4 / 5
You need to tell a client that a feature they requested cannot be delivered this sprint. Which response is most professionally worded?
Option C is the most professional: it gives a reason ("outside current sprint scope"), takes clear ownership, and provides a next step ("added to backlog, prioritised for next release"). Professional declining emails: ① Acknowledge the request. ② Give a brief reason. ③ Offer an alternative or next step. Option A is too blunt — correct but sounds dismissive. Option B is short but gives no reason or next step. Option D over-apologises and sounds informal ("hopefully next time" is vague and unprofessional).
5 / 5
Which subject line correctly follows professional IT email conventions for an action-required message?
"ACTION REQUIRED: Review architecture proposal — deadline 2026-03-20" follows three conventions: ① Status prefix (ACTION REQUIRED) — tells the reader immediately that a response is expected. ② Clear topic (architecture proposal) — no need to open the email to know what it's about. ③ Deadline in subject line — a date in the subject is the single most effective thing you can do to get a timely response. Option A is good but lacks an urgency signal and deadline in the subject. Option C is too brief. Option D is vague and informal.