Write a task brief someone can use
QUICK REFERENCE
A task brief connects a request to a usable result. Before asking a teammate or an AI chat to help, explain who needs the work, what they will use it for and how you will check it. You can start with six lines; a long document is optional.
When to use this
Use this when a request sounds like “make a presentation”, “research this” or “sort out the process”, but nobody has said what a satisfactory result looks like.
Know these three terms
Outcome
The change or decision the work should support.
Deliverable
The actual thing you will hand over, such as a one-page comparison.
Constraint
A real limit: time, access, format, tools or a confirmed requirement.
A practical way to do it
Name the user and decision
Write who will use the result and what they need to decide or do. “Help the coordinator choose a workshop format” is clearer than “research workshops”. If the decision-maker is unknown, record that gap.
Describe the smallest useful output
Choose a deliverable that fits the decision. State its format, necessary contents and exclusions. Separate confirmed requirements from preferences so a suggestion does not quietly become a promise.
Agree on the check
Explain what someone should be able to verify in the finished work. Include sources, dates or approval only where they are required and confirmed. Keep an unanswered question visible instead of filling the brief with guesses.
At a glance
| Part | Vague request | More usable brief |
|---|---|---|
| Purpose | Research venues | Compare two available venues for a 12-person workshop. |
| Output | A report | One page with access, capacity and questions still open. |
| Check | Make it good | The coordinator can see the trade-off and choose what to confirm. |
A small example
Fictional example: Noor asks for a workshop-venue comparison. The room capacity is known, but availability has not been checked. A useful brief asks for a comparison and an availability enquiry; it does not ask the writer to name a confirmed venue before that enquiry happens.
Copy this working template
Use the fields directly in your own notes. AI is optional; check any AI-prepared version against your facts.
Who will use this:
Decision or task it supports:
Deliverable and format:
Confirmed facts and requirements:
Limits and exclusions:
Open questions:
How we will check the result:Check before moving on
- The person receiving the work is named or explicitly unresolved.
- The deliverable is concrete enough to inspect.
- Preferences and unconfirmed dates are labelled.
- The finishing check tests usefulness rather than polish alone.
Common questions
What if I do not know enough to write the brief?
Make the first task a clarification task. List what is missing, who can answer and which decision depends on it. Do not assign production work on the assumption that someone else will discover the purpose.
Can I use this with AI?
Yes. Paste only the non-sensitive details and ask the AI to identify gaps before drafting. Review any inferred requirements; a confident draft cannot confirm a requirement on behalf of another person.
Continue with your task
Browse the other quick references below.
