If you were unavailable tomorrow: a continuity plan

Imagine you were suddenly unable to work for a few weeks: a hospital stay, a family emergency, an accident. Your membership doesn't stop just because you have. Payments keep being taken, members keep logging in, support messages keep arriving and the domain renewal notice lands in an inbox nobody is reading. For a solo owner or a very small team, this is one of the biggest risks the business carries, and one of the least discussed.

A continuity plan is a short set of documents and arrangements that lets someone you trust keep things running, or pause them properly, if you can't. It doesn't take long to create, and you'll hopefully never need it. But if you do, it will protect your members, your income and the people who have to step in on your behalf.

Work out what would break first

Start by walking through what happens if you disappear for a day, a week, a month and longer. Be specific:

• A day: support messages go unanswered, but most members won't notice.
• A week: scheduled content may run out, live sessions are missed, failed payments aren't followed up and questions pile up.
• A month: members are paying for a membership that looks abandoned, complaints and cancellations climb, and critical renewals such as your domain, hosting or the card on file with key suppliers may lapse.
• Longer: decisions are needed about pausing billing, refunding members or even closing the business.

This exercise shows which tasks matter most in an emergency and in what order someone would need to handle them.

Choose a deputy and decide what they can do

Pick one person, and ideally a backup, who could step in. It might be a business partner, an assistant, a family member or a friend with some technical confidence. Talk to them in advance rather than surprising them with a folder when things go wrong.

Then decide clearly what they're allowed to do. Three levels work well:

1. Keep things ticking: answer support with prepared replies, post the member announcement, release scheduled content.
2. Pause: stop new sign-ups, pause billing or cancel live events.
3. Bigger decisions: refunds beyond the usual policy, selling or closing the business.

The third level involves legal and financial questions: who can sign for the business, access the bank account or make binding decisions. The answers depend on your business structure and location, so discuss them with an attorney and your accountant.

Arrange access without handing out passwords

Your deputy can't help if they can't get in. Equally, you don't want every login written on a sheet of paper in a drawer. Safer options include:

• A password manager with an emergency access feature, which lets a named person request access after a waiting period you set.
• Giving your deputy their own limited account on your platform and support tools now, so nothing needs to be shared later.
• A sealed, securely stored document holding the few master credentials that can't be delegated, with instructions for the second login step.

Whatever you choose, make sure two-step login codes don't depend solely on your personal phone, or your deputy will be locked out at the first screen.

Write the “if I'm unavailable” document

This is the heart of the plan: a short guide your deputy can follow under stress. Ines runs Northern Birders Network, a hypothetical membership for birdwatchers with guided online sessions and a busy forum. Her document fits on two pages:

If Ines is unavailable

First two days: post the prepared announcement in the forum and email it to members. Switch the support auto-reply to the emergency version. Cancel the next live session and post the notice.

First two weeks: answer support using the saved replies folder. Release the pre-recorded sessions in the backup folder, one a week. Check failed payments weekly.

Key accounts: platform, payment provider, email tool, domain registrar, hosting, bank. See the password manager emergency access instructions.

Renewals to watch: domain and hosting renewal months are marked in the shared calendar. Make sure the card on file is current.

People to contact: web developer, accountant and the two volunteer forum moderators.

If it's longer than a month: speak to the accountant about pausing billing. Do not close accounts or delete anything.

Link out to your existing procedures rather than repeating them. If you've already begun writing down how your membership runs, most of the detail is ready.

Prepare member messages in advance

Writing a calm message to members is hard for someone else to do in a crisis. Draft it now:

Hi everyone, Ines is unexpectedly away for a little while, and I'm helping keep things running in the meantime. Your membership continues as normal. The library and forum are open, and support messages will be answered within two working days. We'll let you know about live sessions as soon as we can. Thank you for your patience.

Prepare a matching auto-reply for the support inbox and a notice for cancelled events. A small stock of pre-recorded or pre-written content buys valuable time too, because the membership keeps delivering while your deputy handles everything else.

Test it and keep it current

A plan nobody has tried usually has gaps. Once a year, sit down with your deputy and walk through the document together, logging in to each account with them. Better still, take a short break and let them run things for a few days using only the plan. It's also a good moment to ask whether running the business alone is still the right arrangement; solo, partnership or team explores the trade-offs.

Build your plan

1. List what would break after a day, a week and a month without you.
2. Choose a deputy and a backup, and ask them.
3. Set up emergency access or separate accounts for them.
4. Write a short “if I'm unavailable” document.
5. Draft the member announcement, auto-reply and event notice.
6. Talk to an attorney and your accountant about authority over the business and its accounts.
7. Review the plan with your deputy once a year.