Business Continuity: What Happens When Your VA Is Sick or Leaves

Delegation has a quiet side-effect: it concentrates operational knowledge in one person who is not an employee, may live in another city or country, and can resign with an email. None of that is a reason to avoid VAs — it is a reason to plan continuity from the start, while everything is calm.

The single point of failure test

Ask yourself: if my VA were unreachable for a fortnight starting tomorrow, what would stop? If the honest answer includes things like invoicing, enquiry responses or appointment scheduling, and you could not pick them up smoothly, the engagement has drifted into fragility. The goal of continuity planning is that the answer becomes: nothing stops, some things slow down.

The four protections

1. The operations manual, again

Every continuity conversation returns to documentation. If processes, decision rules and templates live in a shared manual rather than the VA's head, then absence — planned or sudden — is an inconvenience rather than a crisis. A manual the VA maintains as part of the role is the cheapest business insurance you will ever arrange.

2. Access you control

All work happens in accounts you own: your task board, your document storage, your software, the VA present as an invited user. Then departure never takes the work with it. The inverse arrangement — files on the VA's personal drive, tasks in their private system, social accounts recoverable only through their phone — converts every resignation into a hostage negotiation, even a friendly one.

3. Agreed notice and handover terms

The engagement agreement should say what winding down looks like: notice period, a handover checklist, return or deletion of business data, transfer of any credentials. Most VAs are professionals and will honour this happily — but it is much easier to agree while nobody needs it.

4. A warm bench

Know where your next pair of hands would come from. That might be a second VA already doing a few hours a month on a different stream — the most robust option, since they already know your systems — or simply an up-to-date manual plus a shortlist of agencies or candidates. Businesses running genuinely critical streams through VAs sometimes deliberately split work across two contractors so neither absence is total.

Planned absences are the easy case

Good VAs take holidays like everyone else. Handle it like any small team would: advance notice in the agreement, a pre-absence handover note covering in-flight work, agreement on what waits and what gets covered, and — if the VA is part of an agency or has a trusted colleague — a briefed substitute for the truly time-sensitive streams. A fortnight of slower admin is survivable; a fortnight of silent unmonitored inboxes is not.

When it ends for real

Offboarding deserves the same professionalism as onboarding: revoke access on the agreed date, rotate any credentials the VA ever held, confirm data return or deletion in writing, pay the final invoice promptly, and update the manual with anything the departure surfaced. Then notice what the departure taught you — every gap you discover during a handover is a documentation task for the next engagement.

Key takeaways

• Continuity is designed before it is needed: manual, owned systems, agreed handover terms, and a known next option.
• If a fortnight of VA absence would stop core admin, reduce that fragility now.
• Work product belongs in accounts you control; departure should never remove the work.
• Splitting streams across two contractors is the strongest protection for critical admin.