In this guide
Decide what should be different after the message
Name the intended result: a decision understood, a task begun, a risk surfaced or a behaviour corrected. Identify the audience and what they already know. One message should have one primary job even when supporting context is required.
If you cannot state the requested action, the communication is not ready. Do not ask people to decode a long explanation to discover what matters.
Lead with the point and relevant context
State the decision, change or purpose early. Then explain why it matters and which context affects execution. Use plain language and define necessary terms. Digital.gov’s guidance emphasises writing for the reader and placing information around what the audience needs.
Avoid beginning with a complete history unless the history changes the decision. Give readers a route to deeper detail when they need it.
Separate facts, interpretation and decision
Label what is known, what it may mean and what has been decided. This prevents an early interpretation from appearing as fact and helps the team challenge assumptions responsibly.
When information is incomplete, say what is unknown and when it will be reviewed. Confidence in delivery should not create false certainty in content.
Make ownership and standards observable
Specify the outcome, owner, deadline, quality standard, dependencies and escalation route. Replace ‘please prioritise this’ with the concrete commitment and the trade-off it requires.
Ask the owner to explain the next step in their own words. This is a check for shared meaning, not a test of obedience.
Fictional example
Vague: Please improve the weekly stock report as soon as possible.
Clear: Maya will send the verified exception report by Thursday at 15:00. It must cover the five agreed categories and identify unresolved figures as [CHECK]. If the source file is late by noon, notify me and use the confirmed sections only.
Choose the channel for the communication risk
Use conversation for sensitive, ambiguous or emotionally significant issues. Use written communication to record decisions, instructions and reference material. Combine them when people need both discussion and a reliable record.
Do not manage a complex disagreement through an escalating message chain. Move to an appropriate conversation, then document the agreement in line with workplace policy.
Invite questions that improve execution
Ask specific questions: ‘Which dependency is unclear?’ ‘What could prevent Thursday’s deadline?’ ‘What information would change this decision?’ General invitations such as ‘Any questions?’ often produce silence without confirming understanding.
Create conditions where people can surface bad news early. Thank them for relevant warnings, examine the evidence and adjust when warranted. Clarity includes a route for correction.
Close the loop and improve the system
After the message, observe the work. Repeated misunderstanding may signal a vague standard, crowded channel or conflicting priority rather than individual carelessness. Correct the immediate issue and the communication system behind it.
Review important messages using five questions: point, evidence, action, owner and feedback route. Keep useful templates, but adapt them to the audience and situation.
Before you move on
- The communication has one primary job and audience.
- The point appears before unnecessary history.
- Facts, interpretation, uncertainty and decisions are distinguishable.
- Outcome, owner, standard, deadline and escalation route are visible.
- The channel fits the sensitivity and complexity of the issue.
- Questions test understanding and expose execution risks.
- Follow-up examines both performance and communication design.
Sources and further reading
These official resources informed the guardrails and practical method in this guide.
This preview uses fictional examples where indicated. Read our editorial approach.