WORKING TOGETHER
Write a task brief that is easy to follow
A useful brief explains the outcome and the boundaries of a task. It helps reduce repeated questions and gives you a clear basis for reviewing the work.
01
Explain the purpose and the output
Start with why the task matters, then describe the finished result. Include the person or team who will use it. If there is a template or a previous example, share it and point out what should stay consistent.
- Purpose: prepare the team for the weekly project check-in.
- Output: an updated tracker and a short list of blockers.
- Example: last week’s tracker with the required columns.
02
Name the source of truth
Identify the folder, calendar, document, or approved system that holds the current information. Avoid leaving the assistant to guess which version is correct. Share only the access needed for the agreed task through an appropriate access process.
- Where the source information lives.
- Where the finished work should be saved.
- Which naming conventions or templates to use.
03
Set deadlines and decision rules
Specify the date, time zone, and review point. Explain what can be handled independently and what needs to come back to you. For customer or lead communication, provide approved wording and a clear route for questions outside the brief.
- Due date and any earlier review deadline.
- Approval needed before sending or publishing.
- Who to contact when information is missing.
- How to flag an urgent issue.
04
Improve the brief after the first delivery
Review the output against the instructions. Give specific feedback: which part worked, what needs changing, and an example of the preferred result. Add that learning to the brief so the next cycle is easier to repeat.
LET’S MAKE ROOM FOR WHAT’S NEXT
Your next step starts
with a conversation.
Tell us where the work is piling up. Share your priorities, tools, and timing so we can discuss the support that fits.
Request support