Write an assistant task brief with a testable outcome
A task brief that states the outcome, the source, the boundary, and the review date.
How to approach: Write an assistant task brief with a testable outcome
An assistant task brief should let the work start without a meeting. Name the outcome, the source, the boundary, and the review date. A brief that only lists steps leaves the hard choices to the assistant. Use the same format for every handover so the next reader can scan it.
Keep the brief to one page. A long brief usually means the outcome is not yet defined. Update the template when the same question appears twice. Keep the evidence with the record rather than in a separate log.
State the outcome and the source
Write the outcome as a result a reviewer can test. Name the system of record and the approved source. A brief that says use the usual file is not a source. 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. Test the rule on one real request before applying it to the queue. Keep the evidence with the record rather than in a separate log.
Set the boundary and the owner
Record what the assistant may decide and what needs approval. Name the person who resolves a scope or cost question. A boundary that lives only in a policy file will be missed. Keep the boundary visible in the place where the work is assigned.
Record the escalation path for missing information. The assistant should know who to ask and how quickly. A control that depends on memory is not yet a control. If the source is unclear, route the question instead of guessing.
Set the review
Write the first review date and the person who will review. A brief without a review cannot be scheduled. A short note with four fields is easier to use than a long narrative. A control that depends on memory is not yet a control.
Record what the reviewer will check. A review that is not specific cannot change the next draft. Keep the evidence with the record rather than in a separate log. Use the same format for every handover so the next reader can scan it.
Keep planning
Questions people ask
What should an assistant task brief include?
The outcome, source, boundary, owner, and review date.
How long should the brief be?
One page, with an example of acceptable work.
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.