Write a delegation brief and confirm shared understanding
Record agreed work and let the assignee correct its outcome, authority, timing, and support.
- Preparation
- One focused conversation and written follow-up
- Difficulty
- Moderate
- Task
- Delegate with clear boundaries
Before you start
Get what you need before you start
- Confirm the person has accepted responsibility and has capacity for the work.
- Gather the source context, known constraints, and the decision authority the role permits.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Write the agreed assignment
Record the outcome, context, one assignee, due date or checkpoint, collaborators, constraints, authority, evidence, and escalation route.
Why it matters: An actionable record makes hidden assumptions available for correction.
- Input
- The accepted responsibility and approved source context.
- Output
- A draft delegation brief assigned to one person.
Tools in this stepAsanaEvidence for this step
Asana documents task titles, one assignee, due dates, collaborators, descriptions, and routes to change ownership or timing.
Asana: “Setting due dates” through “Task etiquette”, accessed 26 September 2026Published ICO employment-record guidance requires employers to define their purpose and lawful basis, give workers privacy information, restrict access, keep records accurate, and set retention periods.
UK Information Commissioner's Office: “How long can we keep workers’ personal information?”, “How do we keep our records about workers’ personal information secure?”, and “What do we need to tell workers about the personal information we hold and how we are going to use it?”; published 5 February 2025, accessed 26 September 2026
Invite the assignee to correct it
Ask the assignee to restate the result and identify missing context, timing conflicts, authority gaps, dependencies, and help needed.
Why it matters: A task assignment and a nod do not prove agreement or comprehension.
- Input
- The draft brief and a private review conversation.
- Output
- A corrected brief and explicit acceptance, renegotiation, or decline.
Tools in this stepAsanaEvidence for this step
Asana documents task titles, one assignee, due dates, collaborators, descriptions, and routes to change ownership or timing.
Asana: “Setting due dates” through “Task etiquette”, accessed 26 September 2026
Review at the agreed checkpoint
Compare progress with the stated outcome and evidence, then record support, changes, escalation, or closure with the assignee.
Why it matters: The check should test the brief and conditions rather than infer ability or intent.
- Input
- The accepted brief and current work evidence.
- Output
- An agreed update, changed brief, escalation, or completed handoff.
Tools in this stepAsanaEvidence for this step
Asana documents task titles, one assignee, due dates, collaborators, descriptions, and routes to change ownership or timing.
Asana: “Setting due dates” through “Task etiquette”, accessed 26 September 2026Published ICO employment-record guidance requires employers to define their purpose and lawful basis, give workers privacy information, restrict access, keep records accurate, and set retention periods.
UK Information Commissioner's Office: “How long can we keep workers’ personal information?”, “How do we keep our records about workers’ personal information secure?”, and “What do we need to tell workers about the personal information we hold and how we are going to use it?”; published 5 February 2025, accessed 26 September 2026
Success checks
Check the result before you finish
- The assignee can state the result, authority, constraints, evidence, checkpoint, and escalation route.
- Changes are agreed with the assignee and remain visible in the task record.
Failure modes
Watch for these problems
- Pause if the person lacks capacity, authority, access, or a safe route to question the assignment.
- Do not infer performance or intent from silence, delay, or a different interpretation.
Tools
Choose the tools you need
Tool
Asana
A work-management tool for recording an assignment, one owner, timing, context, collaborators, and updates.
Check fit, limits and pricingSources
Read the sources behind this practice
Check what each source supports and where the advice has limits.
- Asana: Assign tasks to teammatesOfficial product documentation · Publication date unavailable
- UK Information Commissioner's Office: Collecting and keeping employment recordsPublished official UK employment-record guidance under review · Published 5 February 2025