Reader situation
You host a recurring community activity, such as a weekly discussion question, a monthly huddle or a newcomer welcome. You’re going to be away for a few weeks, or you might be unexpectedly. Without a plan, the activity stops, members wonder what happened and restarting it takes effort.
Central idea
An activity should have a manageable continuity plan when its usual host is unavailable. Agree what can continue, who is willing to help and what should pause until the host returns.
Practical steps
- Identify essential activities. List the recurring activities you’re responsible for and decide which are essential to keep going. Welcoming new members may be essential, because a missed welcome affects someone’s first experience. A monthly huddle may be fine to pause for one month. Be realistic: not everything needs to continue in your absence. For each activity, note what it involves and how much time it takes. This helps a backup decide whether they can help, and it gives you a clearer picture of how much you do.
- Ask for backup support. Ask a co-host, a volunteer or a trusted regular member whether they’d be willing to cover specific activities. Make the request clear and limited: “Would you be able to post the weekly question for the three weeks I’m away?” Explain what’s involved and that it’s fine to say no. Ask in advance, before you need it. For unplanned absences, it helps to have an agreement already in place that someone can step in for a short period.
- Define authority. Agree what the backup can decide on their own and what should wait for you or the community owner. For example, a backup might post discussion questions and welcome members, but not change Circle guidelines, approve new co-hosts or remove members. If moderation is part of the role, agree how they should handle problems and who to contact. If the backup needs extra permissions, arrange them through the community’s approved process, and agree when they’ll be removed.
- Prepare brief instructions. Write short notes for each activity the backup will cover: what to do, when, any templates or examples and where to find them. Include a list of upcoming items, such as questions already planned or members expected to join. Keep it brief; a page is usually enough. Instructions help the backup feel confident and keep the activity consistent for members.
- Communicate any pause. For activities that will pause, tell members in advance: “The monthly huddle will pause in August and return in September.” A brief note prevents confusion and shows the activity hasn’t been abandoned. Members are usually understanding about a planned pause; what unsettles them is an unexplained silence. If someone else is covering, let members know who to contact. When you return, thank the backup publicly if they’re comfortable with that, and pick up any open items they’ve noted.
Worked example
Fictional example
The people and details are invented to illustrate an approach. It reports no outcomes.
Rafaela hosts a Circle for early-career researchers. She’s taking three weeks of leave and lists her activities: a weekly discussion question, welcome messages for new members and a monthly huddle.
She decides that the weekly question and welcomes are essential, and the huddle can pause. She asks a regular member, Kwame, whether he’d post the weekly question and welcome any new members while she’s away. He agrees.
They define authority: Kwame can post questions and welcomes, and can remove obvious spam, but will contact the community owner about any other moderation issue. The owner grants Kwame temporary moderator permissions for three weeks.
Rafaela writes a one-page note with three discussion questions already drafted, a welcome message template and the owner’s contact details. She posts in the Circle: “I’m away for three weeks. Kwame will be posting our weekly questions and welcoming new members. The monthly huddle will return on the 12th.”
When she returns, Kwame has posted all three questions and welcomed four new members. Rafaela thanks him in the Circle and asks whether he’d be willing to be her regular backup. He agrees, and they keep the one-page note for next time.
Companion tool: Host absence plan
Host: ________
Absence dates: ________
| Activity | Essential? | Continue or pause | Backup | Time needed |
|---|---|---|---|---|
| ☐ | ||||
| ☐ |
Backup authority Can do: ________
Should wait for host or owner: ________
Who to contact with problems: ________
Temporary permissions requested: ☐ Yes ☐ Not needed Permissions end on: ________
Instructions prepared: ☐ Yes (where to find them: ________)
Message to members: ________
Boundaries
- Backups should agree voluntarily, and their commitment should be limited and clear.
- Don’t share personal log-in details. Arrange temporary access through the approved process.
- A continuity plan doesn’t make the backup responsible for problems they couldn’t reasonably handle.
Member action
Agree a backup arrangement for one recurring community activity. Set it up now, before you need it.
Discussion prompt
What happens to activities in your community when the person who runs them is away?
