Describe the actual work
List welcoming, reviewing reported content, answering practical questions, maintaining events and escalating serious issues. Identify which tasks are routine and which require an owner’s decision. A title alone does not tell the incoming volunteer what they are expected to do. Keep sensitive case details in the appropriate restricted system, not in a public onboarding guide.
Verify the required access
Check the current plan and role permissions for each responsibility. Use individual accounts and legitimate role assignment; do not share the outgoing moderator’s password. Record who can grant and revoke access. A successful role change in a dashboard is configuration evidence, while the incoming person completing the relevant task is separate acceptance evidence.
Transfer unresolved work explicitly
For each open case, preserve the minimum necessary context, current owner and next decision. Explain deadlines and limitations without promising an outcome the volunteer cannot control. Agree when the outgoing person’s access will be removed or reduced. Do not remove it before essential responsibilities have a verified replacement unless a safety issue requires immediate action.
A fictional handover
A volunteer leaves before the monthly event. The replacement can moderate discussions but cannot update the event owned by the former host. The group records that gap and establishes an authorised event-management solution. It does not call the handover complete merely because the new volunteer appears on a moderator list. The acceptance check follows the actual responsibilities that would otherwise be left unattended.
Before you close this task
Ask the incoming moderator to identify the route for a task they are not allowed to perform. Knowing when to escalate is part of readiness. Preserve the handover date, accepted responsibilities and any outstanding gaps so a later volunteer can tell whether a responsibility was deliberately deferred or accidentally left behind.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Mighty Networks administration — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty Networks pricing — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty privacy policy — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28