A useful work email makes the purpose and next action clear. Before writing, decide what the recipient needs to know, what you are asking them to do and whether email is the right approved channel for the information.
This guide concerns an operational workplace request. It is not a job-application template or a substitute for urgent reporting, a formal approval system or a conversation required by the circumstances.
Put the purpose in the subject and opening
Use a subject that identifies the work and requested action. “Booking summary: cancellation instruction needed” is more useful than “Quick question” when the recipient handles several processes.
Open with the reason for writing and the decision or information needed. Add only the context required to understand the request. A long history can be linked or summarised if it is relevant and appropriate to share.
Comcare’s effective communication guide discusses shared understanding about work. Clear writing should allow the recipient to respond accurately, including identifying something that needs clarification.
Make the request specific
State the requested action, relevant timing and what depends on the response. Distinguish a firm approved deadline from a preferred response time.
If several people receive the message, identify who needs to act and who is included for information. Do not assume copying a manager into an email transfers responsibility or grants approval.
Check the person’s authority for the decision requested. A helpful colleague may be able to explain the process without being authorised to approve a booking, purchase or change.
A fictional email
“Subject: Booking guide — cancellation decision for review
Hi Sam,
The revised booking guide is ready for review except for the cancellation section. Please confirm which of the two options in the approved project folder should be used, or identify any further information you need.
A decision by Tuesday would allow the coordinator to prepare the planned distribution. The guide remains a draft until the required approval is complete.
The options are in [verified internal reference]. Please let me know if you cannot access the document.
Thanks, Lee.”
This invented example needs the real recipient, timing and reference before use. It makes the question and dependency visible without presenting a requested decision as already made.
Check recipients, attachments and tone
Confirm the actual recipient address, attachment and permissions. Avoid relying only on autocomplete or attaching a document with a familiar name without opening it.
Use a tone suited to the relationship and task. Direct language can remain courteous. Remove sarcasm, unsupported allegations or unnecessary personal information, particularly where a wider group may receive the message.
If the subject is sensitive or complicated, consider whether a discussion followed by a factual written record would work better, using the organisation’s approved process.
Close the loop
If a response is incomplete, ask a precise follow-up rather than forwarding the entire chain with “please advise”. Record formal decisions in the appropriate system; an email exchange should not leave the team unsure which instruction applies.
When the matter is resolved, confirm the next action and owner where needed. A successful work email helps the recipient understand the request and leaves the sender able to track what happened afterwards.
For applications, the guide to showing work skills with evidence can help you describe a communication result without sharing confidential workplace emails.
