Define the result
Describe the completed outcome, why it matters and the evidence that will show it is done.
← All toolkits
Clarity and accountability
Delegation Brief
Transfer context, authority and checkpoints so work can move without constant founder intervention.
Use this when
Start with a live team problem.
- Delegated work returns for repeated clarification.
- A founder hands off activity but retains every decision.
- The team member and manager have different definitions of done.
How to use it
Move from context to one usable agreement.
Transfer authority
State what the owner may decide, spend or change without permission.
Agree on checkpoints
Choose review points based on risk and learning needs, not the manager’s anxiety.
Worked example
Transfer ownership of the monthly client report
Use the example to understand the level of specificity. Replace the content with evidence from your own team.
OUTCOME The monthly client report is accurate, useful and sent by the third business day. WHY IT MATTERS Clients need a clear view of progress, risks and decisions before the monthly review. DEFINITION OF DONE - Data reconciled against the source systems - Commentary explains material changes - Risks have an owner and next action - Report sent to the agreed distribution list AUTHORITY The owner can follow up data, edit commentary and adjust the production schedule. CONSTRAINTS Do not change reported definitions without Finance approval. CHECKPOINTS Draft reviewed in month one. Exceptions only from month two onward.
Blank template
Delegation Brief
Copy this into Docs, Notion or your existing workspace, or print it for a team conversation.
DELEGATION BRIEF Outcome owner: Due date or cadence: OUTCOME What result is being transferred? WHY IT MATTERS DEFINITION OF DONE - - - AUTHORITY The owner may decide or change: CONSTRAINTS - Budget: - Quality: - Risk: AVAILABLE SUPPORT - CHECKPOINTS - ESCALATE WHEN -
The System Folks · Free founder resource · thesystemfolks.com/resources/delegation-brief
Common mistakes
Keep the tool connected to real work.
- 01
Delegating responsibility while retaining all authority.
- 02
Adding so many checkpoints that the work is not truly delegated.
- 03
Assuming the context in the founder’s head is already understood.
Why this works
Evidence behind the resource
Reliable behaviour requires capability, opportunity and motivation, not instructions alone.
Read COM-B behaviour frameworkNeed help implementing it?
A template can reveal a bigger operating problem.
If delegation repeatedly fails because roles, standards or workflows are unclear, we can help rebuild the operating conditions around it.
Contact us when one costly workflow or team bottleneck needs diagnosis, build support and adoption.
Get implementation support Use another toolkit