Example
How to leave a long-running volunteer role without taking the institution home
A shared-drive handover cannot transfer what only George knows, and remaining endlessly available prevents the successor from owning the role. George must choose a live handover, written handbook, or records-only exit; all three end access on the same date.
Transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility
Purpose, boundaries, and the definition of enough
Hold the mission and boundary: transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility
The decision and preparation that deserve attention next
Hold the live choice—whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing—so George can decide from the evidence in this Room
Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed
Complete this as owned preparation; if another person must answer, keep it as an unsent draft until it is actually sent
Use the result of the first owned action to update the Succession-boundary brief; record the finding, not merely the effort
The visible proof behind the plan—not a vague feeling of readiness
Supply the evidence for the Succession-boundary brief: place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
In You.one’s Superboard view, the Volunteer succession Board separates the successor promise, transfer work, institutional evidence, real successor replies, and responsibility genuinely owned elsewhere.
Open Live handover, handbook, or records-only exit as the Room with the Succession-boundary brief and every annual judgment mapped before access ends.
After an explicit request, Ava can organize only the visible records but cannot transfer authority, grant or remove access, contact members, or appoint a successor. George owns his boundary and transfer work; the club and successor own institutional succession.
Volunteer succession has one live choice: Live handover, written handbook, or records-only exit
The mission is specific: Transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility.
The consequential choice is not something a board or an AI should quietly make: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
You.one can keep the work, evidence, and “Live handover, written handbook, or records-only exit” decision visible through its Superboard view. Authority does not move to the software: George, as the treasurer ending twenty years with a community club, owns the preparation and the decision about whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
Available today
Volunteer succession: the working map
The Volunteer succession Board gives this mission one durable operating picture. George can use familiar language instead of translating the situation into project-management jargon. Its three Lists separate the kinds of attention this situation actually requires.
The Lists separate what George can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Successor promise | Purpose, boundaries, and the definition of enough |
| Transfer next | The decision and preparation that deserve attention next |
| Institution evidence | The visible proof behind the plan—not a vague feeling of readiness |
Available today
Open one decision: Live handover, written handbook, or records-only exit
Opening the Card gives the visible item durable depth. Stage can hold Succession-boundary brief: Place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: George will decide whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Live handover, written handbook, or records-only exit” from the visible evidence. Ava can work from the context George deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
George's call remains explicit: George, as the treasurer ending twenty years with a community club, owns the preparation and the decision about whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Succession-boundary brief: Place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing |
| Chat | Keep George's request and Ava's attributed response with the work |
| Pulse | Open decision: George will decide whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing |
Useful Ava requests, with the boundary intact
These requests stay with the facts George has made visible around “Live handover, written handbook, or records-only exit.” George supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent George, watch other work on her own, or contact anyone.
George, as the treasurer ending twenty years with a community club, owns the preparation and the decision about whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing. Ava may help only inside this Card Room; she cannot decide, represent anyone, contact people, or act elsewhere.
George finishes “List what only George currently knows before choosing a handover mode,” keeps “Annual rhythm map and final access date” beside “Live handover, written handbook, or records-only exit,” and does not treat “Draft the successor-question prompt” as completed or sent before doing the work.
- Request idea: compare the options on the Live handover, written handbook, or records-only exit Card using only the context visible in this Card Room. Tell me what is missing; do not choose, submit, book, buy, or message anyone.
- Request idea: use only the Succession-boundary brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Live handover, written handbook, or records-only exit,” show which visible fact could reverse the current choice
The limit of a shared drive handover
A shared drive handover can be enough while the situation stays simple: the annual rhythm, final access date, successor questions, member expectations, and one agreed handover mode are already explicit.
It starts to break when partly digital files, annual judgment, indefinite fallback requests, and the final access date must inform the same exit choice.
The Volunteer succession Board earns its place only when the familiar tool—a shared drive handover—can no longer keep the reason, Succession-boundary brief, conversation, current state, decision, and history connected.
A practical way to start the Volunteer succession Board
George should rename every List or Card that feels artificial. This recipe succeeds when “Live handover, written handbook, or records-only exit” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
Swipe or scroll sideways to see every column.
| Step | Action |
|---|---|
| 1. Write the mission | Transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility |
| 2. Open the live choice | Put “Live handover, written handbook, or records-only exit” in a Room of its own |
| 3. Attach the evidence | Succession-boundary brief: Place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing. |
| 4. Keep the work owned | Keep “Draft the successor-question prompt” in owned work and name the next visible move |
| 5. Take the first owned action | List what only George currently knows before choosing a handover mode |
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not governance, fiduciary, financial, access-control, relationship, or succession advice; the club and successor own the real transfer and George owns his final boundary.
- It does not show Ava completing external actions or contacting anyone for George.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.