Use case
Role transition
A project handoff has a boundary. A role handoff does not — it is forty small responsibilities, most of them undocumented, several of them invisible until they break.
How do you hand over a whole role?
Build a Brief around recurring responsibilities rather than projects: what happens weekly and monthly, which relationships you maintain, which approvals route through you, and which systems you own. The successor asks it as each obligation comes around for the first time, over their first quarter.
What breaks after someone leaves
- A monthly obligation nobody knew existed until it was missed.
- A vendor relationship with no named owner.
- An approval chain that silently stalls.
- A workaround everyone relied on and nobody documented.
Transferring a seat
- Step 1
Inventory the recurring
Weekly, monthly, quarterly. Calendar exports are an excellent source here.
- Step 2
Map the relationships
Internal and external, with what each is for.
- Step 3
Capture the workarounds
Paste the unwritten rules. This is the highest-value content in the whole Brief.
- Step 4
Leave it open for a quarter
The successor keeps asking as obligations surface.
What a successor needs
Cadence
- Recurring duties
- Deadlines
- Reporting obligations
Relationships
- Vendors
- Internal partners
- Escalation paths
Authority
- What you approve
- What you escalate
- Spend limits
What a successor asks in month two
Most of these only occur to someone once the obligation lands.
- Who normally signs this off?
- Has this vendor been renegotiated recently?
- What is the process when this fails?
- Why do we do it this way?
- Is this deadline real or convention?
Why it lasts a quarter
- The Brief keeps answering after you have gone.
- Unanswerable questions are surfaced as gaps rather than guessed at.
- You can revoke the link once the transition is complete.
Role transition checklist
- Recurring calendar export.
- Vendor and contract list.
- Approval authority.
- Escalation paths.
- A pasted note on the unwritten rules.
Common questions
- What information belongs in a Brief?
- Include the material that answers the questions the recipient will actually ask: who decides what, what has been agreed, what is still open, what the timeline is, and where the numbers came from. Source documents, decision emails, status notes and the current financial model matter more than polished summaries.
- How does a Brief work?
- You add sources, Brieflin extracts the structure, you review and correct what it understood, then you publish one link. Recipients open the link without an account and ask questions in plain language. Each answer is generated only from your sources and cites the passage behind it. You can revoke the link at any time.
Leave the seat in working order
Build the Brief in your notice period, not your last afternoon.