Build a task brief the assistant can start from
A task brief with the outcome, the source, the boundary, and the owner so the assistant can start without a meeting.
How to approach: Build a task brief the assistant can start from
A task brief should give the assistant enough to start and enough to stop. Name the outcome, the source, the boundary, and the owner. A brief that only names the task leaves the hard questions unanswered. Write the deadline as a date and a local time. The review should leave one owner and one date. The assistant should record the owner and the date before the next shift.
Keep the brief to one page. A long brief is usually a sign that the work is not yet defined. If the brief needs a meeting to explain, split the task. If the source is unclear, route the question instead of guessing. The evidence should stay with the record, not in a private note. A control that depends on memory is not yet a control.
State the outcome and the source
Write the outcome in one sentence that a reviewer can test. Name the system of record and the approved sources. A brief that says use the usual file is not a source. Record the exception and the person who approved it. The brief should name what is approved and what needs a question. A control that depends on memory is not yet a control.
Include an example of acceptable work if one exists. An example is faster than a paragraph of description. Remove any confidential detail before sharing it. Update the template when the same question appears twice. The assistant should record the owner and the date before the next shift. The review should leave one owner and one date.
Set the boundary and the owner
Record what the assistant may change and what requires approval. Name the person who decides a scope, cost, or timing change. A boundary that is only in a policy file will be missed. Review the first few notes together before the process expands. A control that depends on memory is not yet a control. The assistant should record the owner and the date before the next shift.
Include the escalation path for missing information. The assistant should know who to ask and how quickly. Escalation is a normal step, not a failure. Separate what was observed from what was assumed. The evidence should stay with the record, not in a private note. A control that depends on memory is not yet a control.
Set the review and the deadline
Write the deadline as a date and a local time. Distinguish the first draft from the final version. A brief without a deadline cannot be scheduled. Ask whether a new reviewer could act on the record without a conversation. A control that depends on memory is not yet a control. The evidence should stay with the record, not in a private note.
Decide how the work will be reviewed and who attends. A first-draft review is different from a final approval. The brief should say which one applies. Test the rule on one real request before applying it to the queue. The review should leave one owner and one date. The brief should name what is approved and what needs a question.
Review the brief after the task
Ask the assistant what was unclear and update the template. A brief that improves after each use is more valuable than a perfect template. Keep the change small. Keep the evidence with the record rather than in a separate log. The assistant should record the owner and the date before the next shift.
Share the best briefs with the team. A short example teaches more than a policy. The goal is a brief the assistant can start from, not a longer document. Write the deadline as a date and a local time. A control that depends on memory is not yet a control. The review should leave one owner and one date.
Keep planning
Questions people ask
What should a task brief include?
The outcome, the source, the boundary, the owner, the deadline, and the review step.
How long should the brief be?
One page, with an example of acceptable work if one exists.
Reference notes
These links are a starting point for general context. They are not custom legal, tax, hiring, or cybersecurity advice.
- U.S. Small Business Administration: Public guidance consulted for general context.