Reader situation
You’ve been hosting a Circle, organizing events or moderating discussions for a community, and it’s time to step back. Someone has agreed to take over. Much of what you do is in your head: recurring tasks, open commitments, useful contacts and the reasons behind how things are done. Without a clear handover, the new volunteer has to rediscover it all, and members notice the gap.
Central idea
A volunteer role becomes easier to continue when the next person understands its purpose, responsibilities and current commitments. Prepare a concise handover, and transfer access through approved processes.
Practical steps
- Describe role purpose. Start with why the role exists and what it achieves for the community. “The welcome lead makes sure new members find a relevant first conversation within their first week” is more useful than a list of tasks, because it helps the new volunteer make good judgments when something unexpected comes up. Include what you’ve learned about doing it well: what members value, what makes the role easier and any mistakes worth avoiding.
- List recurring duties. Write down the tasks the role involves and how often: weekly, monthly, quarterly or as needed. For each, note roughly how long it takes and any templates, guidelines or tools you use. This gives the new volunteer a realistic picture of the time involved and saves them building tools from scratch. Mark which duties are essential and which are optional. A new volunteer may want to start with the essentials and add others later.
- Record open commitments. List anything currently in progress or promised: events already scheduled, members waiting for a reply, introductions you’ve offered, discussions you said you’d follow up. Include who’s involved, what was promised and by when. Open commitments are the most likely to be lost in a handover, and they’re the ones that affect members’ trust. If you can complete some commitments before handing over, do so. For those you can’t, tell the people involved who will be picking them up.
- Transfer authorized access. Arrange for the new volunteer to receive any access they need, such as host or moderator permissions, shared documents or community accounts, through the community’s approved process. Usually that means asking the community owner or administrator to grant it, rather than sharing your own login details. Once the handover is complete, ask for your own access to be removed or reduced if you no longer need it. Don’t hand over personal information about members, such as private messages or contact details, unless the role requires it and the community’s policies allow it.
- Arrange an introduction and check-in. Introduce the new volunteer to the people they’ll work with most, such as co-hosts, the community owner and regular contributors. A short message to members announcing the change helps too. Then agree a check-in, perhaps a few weeks later, where the new volunteer can ask questions. Make clear you’re available for a limited time afterwards, and for how long.
Worked example
Fictional example
The people and details are invented to illustrate an approach. It reports no outcomes.
Tomas has hosted a Circle for nonprofit finance managers for 18 months. He’s stepping back because of a new role, and Asha has agreed to take over.
Tomas writes a one-page handover. He describes the role’s purpose: giving finance managers at small nonprofits a place to compare practical approaches. He lists recurring duties: posting a discussion question every two weeks (about 30 minutes), welcoming new members (about 15 minutes a week) and hosting a quarterly huddle (about two hours including preparation). He marks the quarterly huddle as optional for the first three months.
He records open commitments: a huddle scheduled for next month with a guest member, two new members awaiting welcome messages and a promise to share a budgeting template. He completes the welcome messages himself before handing over.
He asks the community owner to grant Asha host permissions, and to remove his after two weeks. He posts a short message in the Circle introducing Asha and thanking members. He and Asha agree to a 20-minute call after a month. On the call, Asha asks two questions about the huddle format, and Tomas confirms he’ll answer occasional questions for another month.
Companion tool: Volunteer handover checklist
Role: ________
Purpose: ________
What I’ve learned about doing it well: ________
Recurring duties
| Duty | How often | Time | Tools or templates | Essential? |
|---|---|---|---|---|
| ☐ | ||||
| ☐ |
Open commitments
| Commitment | Who’s involved | Due | Status |
|---|---|---|---|
Access ☐ Access requested for new volunteer through the approved process ☐ My access to be removed or reduced on: ________
Introductions: ________
Check-in date: ________
I’m available for questions until: ________
Boundaries
- Never share passwords or log-in details. Transfer access through the community’s approved process.
- Don’t pass on members’ private information beyond what the role needs.
- Give enough notice for a proper handover where you can. If you must step back suddenly, a brief handover is better than none.
Member action
Prepare a one-page handover for one community responsibility you hold. Share it with the community owner as well, so the knowledge isn’t held by only one person.
Discussion prompt
What’s the most useful thing someone told you when you took over a role from them?
