Failover + Connectivity Resilience Checklist

A practical checklist and test plan for internet failover, resilience assumptions, and evidence that backup connectivity actually works.

Connectivity Failover Continuity Ops
Why this exists
Many organisations have a backup connection or failover feature but have never tested what really happens when the main link fails.

1) Quick checks

CheckWhat good looks likeStatus / notes
Primary and backup links documentedYou know who provides each link, what equipment is involved, and who owns support.
Automatic or manual failover understoodThe business knows what “failover” actually means in practice.
Critical apps listedYou know which systems must work during an outage.
Test history existsThere is evidence from at least one controlled failover test.

2) Controlled failover test plan

  1. Choose a low-risk test window and advise key users.
  2. List the 3–5 critical things to validate during failover.
  3. Trigger failover or simulate primary-link loss in the approved way.
  4. Record what worked, what degraded, and how long recovery took.
  5. Return to normal, document lessons, and assign actions.

3) Failover evidence log

DateTesterScenarioTime to switchCritical apps validatedResultActions
Pass / Fail / Partial
Pass / Fail / Partial

4) Questions to ask your IT person / MSP

QuestionWhy it matters
What actually happens if the main internet link fails?“We have failover” is not the same as knowing the real outcome.
Which apps are expected to keep working?Business expectations need to match technical reality.
When did we last test it?Untested failover is an assumption, not a control.

5) Common gotchas

Note: This document is general operational guidance and does not replace legal advice. It helps you establish a practical baseline and reduce common privacy risks.
👉 Free 30-minute consultation

No hard sell - just clarity and practical next steps.

hello@virtusgroup.biz
virtusgroup.co.nz
0800 847 887 (VIRTUS)

Book now