Skip to main content

A Community Co-host Handoff Checklist for a Week Away

A community should not need its founder online every day to keep an ordinary discussion moving. Before a week away, give a co-host a small, bounded job: ke

A community should not need its founder online every day to keep an ordinary discussion moving. Before a week away, give a co-host a small, bounded job: keep the current activity understandable, notice requests that need attention, and know when to pause.

This is a practical handoff checklist, not a promise that a volunteer can replace a trained moderator. Start with the broader community-building guide if the purpose and participation rules are still unclear.

Define the minimum useful week

Write down the one activity that should continue and the activities that can wait. A small community might keep its weekly question open while postponing a new workshop. That is a hypothetical example, not a recommended quota.

Choose the minimum based on the time the co-host actually agrees to give. Ask what they can cover; do not assume that accepting a title means accepting constant availability. Make the return date and the end of their responsibility explicit.

A useful handoff starts with three sentences: what continues, what pauses, and who members can contact. Put those facts somewhere members can find without reading a private conversation.

Transfer context without exporting private conversations

The co-host needs operating context, not a dump of member messages. Share the published guidelines, current activity links, known technical limitations and an escalation route. Use the access controls available on your platform and grant only the permissions needed.

For an unresolved member request, ask whether it can be transferred with the member's knowledge. Avoid copying sensitive details into an ordinary planning document. If you cannot share enough context appropriately, keep that issue with its existing owner and explain the delay.

A compact handoff record can contain:

  • Current activity and its public link.
  • What a successful ordinary week looks like.
  • Co-host availability and the end of the assignment.
  • Questions the co-host may answer using published guidance.
  • Decisions that must wait.
  • Urgent escalation route and fallback if nobody replies.

This is an operating checklist, not legal or safeguarding advice. Communities handling sensitive matters need appropriate specialist processes.

Separate routine decisions from exceptional ones

Give the co-host permission to do a few specific things. They might point someone to an existing guide, clarify an activity's instructions, or postpone a scheduled prompt when a technical problem makes participation difficult.

Also name the limits. A temporary co-host should not have to invent refund terms, promise new services, decide complex disputes, or speak for the business on an unfamiliar issue. If those situations arise, the useful response may be to acknowledge the request and explain when the responsible person can respond.

Do not promise an escalation response time unless someone has accepted that coverage. “We will review this when the owner returns on Monday” is clearer than an unsupported promise of immediate attention.

Run one ordinary scenario together

Before leaving, walk through a harmless example. A member cannot find this week's discussion. Can the co-host locate the link, explain the next action and identify whether the problem is access or confusing instructions?

Then try an exception: someone asks for an unannounced event. Can the co-host explain that no event is currently scheduled without making a new commitment?

Use these examples to find missing information. Do not turn the exercise into secret testing of members or a test of the volunteer's loyalty.

Give members a clear continuity note

A simple announcement can state who is hosting, what remains available, what pauses and when the normal schedule returns. Include only contact routes that are actually staffed.

Avoid saying that nothing will change if the handoff reduces coverage. A smaller, clear service is easier to understand than a broad promise the co-host cannot keep.

For activity design, use the existing weekly community rituals planner. Choose the ritual before assigning somebody to maintain it.

Close the handoff when you return

Review what happened with the co-host: questions they could answer, unclear instructions, decisions they deferred and access that is no longer needed. Remove temporary permissions through the platform's normal process when the role ends.

Thank them for the agreed work without using public praise as pressure to keep doing it. Update the checklist based on observed problems, rather than turning one quiet week into a claim that the system is proven.

The reusable outcome is a small record of responsibility and limits. Keep it alongside your community planning resources, ready for the next absence.