A business continuity plan is a documented strategy that keeps critical operations running during disruptions such as power cuts, cyberattacks, severe weather, or equipment failure. Today, almost every critical process depends on a working internet connection, from cloud software and VoIP phones to card payments and remote work.
This guide explains what a business continuity plan includes, how it differs from disaster recovery, and where internet connectivity fits in. You will also learn how to assess risk, choose backup connections, and test your plan so your business stays online when it matters most.
What Is a Business Continuity Plan?
A business continuity plan (BCP) is a written set of procedures that explains how a company will keep essential functions running, or restore them quickly, when something goes wrong. It covers people, processes, technology, facilities, and suppliers.
The goal is not to prevent every incident. The goal is to limit the damage and shorten the recovery time. Frameworks such as ISO 22301 (the international standard for business continuity management systems), NIST SP 800-34 (contingency planning guidance), and the Ready.gov business continuity resources from FEMA give organizations a structure to follow.
A good plan answers four simple questions: what must keep running, who is responsible, what resources are needed, and how fast service must return. To answer them, you first need to know what a BCP contains.
What Are the Key Components of a Business Continuity Plan?
Every effective BCP shares a core set of building blocks. Smaller businesses can keep each one short, as long as it is specific and current.
- Risk assessment: identifies threats such as fire, flooding, ransomware, power failure, and ISP outages.
- Business impact analysis (BIA): ranks processes by how much damage their downtime causes.
- Recovery objectives: sets targets for how fast and how completely systems must return.
- Response procedures: step-by-step actions for specific incidents.
- Communication plan: contact lists and messages for staff, customers, vendors, and regulators.
- Roles and responsibilities: names who makes decisions during a crisis.
- Alternate resources: backup sites, equipment, power, and connectivity.
- Testing and review schedule: keeps the plan accurate over time.
Many people confuse a BCP with a disaster recovery plan, so the difference is worth clarifying next.
How Is a BCP Different From a Disaster Recovery Plan?
A BCP covers the whole business, while a disaster recovery plan (DRP) focuses on restoring IT systems and data. The DRP is one part of the larger continuity effort.
| Feature | Business Continuity Plan | Disaster Recovery Plan |
|---|---|---|
| Scope | Entire organization | IT systems, data, and infrastructure |
| Main goal | Keep operations running | Restore technology after an outage |
| Includes | People, facilities, suppliers, processes, IT | Servers, backups, networks, applications |
| Typical timing | Before, during, and after an incident | Mostly after an incident |
| Example action | Move staff to remote work | Restore a database from backup |
Both plans depend on one shared resource that is easy to overlook: the internet connection.
Why Is Internet Connectivity Critical to Business Continuity?
Modern business runs on connectivity. When the connection fails, the impact reaches far beyond email.
Common internet-dependent functions include:
- Cloud applications: Microsoft 365, Google Workspace, Salesforce, and accounting platforms
- Communications: VoIP, unified communications as a service (UCaaS), and video meetings
- Payments: card terminals and e-commerce checkout, which must also meet PCI DSS rules
- Remote access: VPN connections for staff working off-site
- Security systems: IP cameras, access control, and alarm monitoring
- Cloud backups: offsite data protection that needs bandwidth to run
- Customer service: ticketing systems, chat, and call centers
Uptime numbers show how much one connection can cost you:
- 99% uptime allows about 87.6 hours of downtime per year.
- 99.9% uptime allows about 8.76 hours per year.
- 99.99% uptime allows about 52.6 minutes per year.
A single ISP often cannot promise more than the middle figure. That is why connectivity belongs in your BIA, which is covered next.
How Do You Include Internet Dependency in a Business Impact Analysis?
A business impact analysis measures how long each process can stop before the damage becomes serious. Adding internet dependency to this step shows you where connectivity gaps are most expensive.
- List critical processes. Include sales, payments, customer support, operations, and payroll.
- Map each process to its connection needs. Note the applications, bandwidth, and uptime each one requires.
- Estimate the cost of downtime. Consider lost revenue per hour, idle staff wages, missed deadlines, and customer impact.
- Set a Recovery Time Objective (RTO). This is the longest acceptable outage for a process.
- Set a Recovery Point Objective (RPO). This is the maximum acceptable data loss, measured in time.
- Identify single points of failure. Look for one ISP, one modem, one cable path, or one power source.
- Rank connectivity needs. Decide which services must stay online and which can wait.
Once you know your targets, you can match them to the right redundancy option.
Which Internet Redundancy Options Support a BCP?
The right option depends on your RTO, budget, and location. Reliable redundancy relies on connections that fail for different reasons.
| Option | How It Helps | Typical Recovery Time | Best For |
|---|---|---|---|
| Dual-WAN failover | Switches to a backup link when health checks fail | About 5 to 60 seconds | Small offices, retail |
| Second ISP on a separate path | Independent carrier and cable route | Seconds to minutes | Most businesses |
| 4G/5G cellular backup | Wireless path that bypasses wired outages | Seconds to minutes | Quick, low-cost protection |
| SD-WAN | Steers traffic by application quality | Sub-second to seconds | Multi-site organizations |
| Satellite (such as Starlink) | Works when local networks are down | Seconds to minutes | Remote or high-risk areas |
| Link bonding | Combines links into one tunnel | Near seamless | Live streaming, critical voice |
Pair a wired primary link with a wireless backup whenever possible, since one storm or construction crew can damage a cable path but rarely affects a cellular tower at the same time.
Choosing a backup is only one part of the design, so the next section shows how to build it into the plan.
How Do You Build Internet Resilience Into Your Plan?
Resilience comes from layers of protection, each documented in the BCP.
- Diversify carriers and paths. Use two ISPs and ask each about the physical route into your building.
- Automate failover. Use a dual-WAN router or SD-WAN so the switch does not depend on staff.
- Review ISP contracts. Check the service level agreement (SLA) for uptime guarantees, mean time to repair (MTTR), and support hours.
- Protect DNS and cloud access. Use more than one DNS provider and consider cloud-based phone systems that reroute calls.
- Plan for remote work. Confirm that staff have secure VPN access and a fallback, such as a mobile hotspot.
- Prioritize traffic. Use quality of service (QoS) rules so payments and voice get bandwidth first on a slower backup link.
- Document everything. Record account numbers, support lines, IP settings, and escalation steps.
Even the best network design fails without power, which is the next weak spot to address.
How Do Power and Physical Infrastructure Affect Connectivity?
An internet connection is only as reliable as the equipment that powers it. Many outages begin with electricity, not the ISP.
Protect these components:
- Modems, routers, switches, and firewalls: connect them to an uninterruptible power supply (UPS).
- Fiber terminals (ONTs) and cellular gateways: include them on the UPS circuit.
- Network closets: keep them cool, secure, and labeled.
- Generators: consider one for long outages, and check that it covers network gear.
- Cabling: use proper cable management so repairs are quick.
A UPS typically gives minutes to a few hours of runtime for networking gear, which is enough to ride through short outages or bridge to a generator. After the infrastructure is in place, the plan must be proven in practice.
How Often Should You Test and Update Your Plan?
An untested plan is an assumption. Test connectivity failover at least quarterly, and run a full continuity exercise at least once a year.
Useful test methods include:
- Tabletop exercises: walk through a scenario with key staff.
- Failover drills: unplug the primary link and measure recovery time.
- Full simulations: run operations on the backup connection for a set period.
Review the plan after any change in ISP, office location, software, or staff roles. Record the results, fix gaps, and update contact lists. Testing frequently reveals the common mistakes listed next.
What Are the Most Common Internet Continuity Mistakes?
- Relying on one ISP with no backup
- Choosing a backup on the same cable path as the primary
- Forgetting power protection for network equipment
- Ignoring cellular data caps and CGNAT limits on backup plans
- Never testing failover after setup
- Leaving contact details outdated
- Treating the plan as an IT-only task instead of a company-wide effort
Final Thought
A business continuity plan keeps your company operating through disruption, and your internet connection is one of its most important dependencies. Start by identifying which processes cannot stop, set clear recovery targets, and remove single points of failure with a second carrier, automatic failover, and protected power. Then test the plan on a schedule. A simple next step is to run a one-hour failover drill this month and write down what you learn.
FAQs
What Is The Main Purpose Of A Business Continuity Plan?
Its purpose is to keep essential business functions running, or restore them quickly, during a disruption. It reduces financial loss, protects customers and staff, and supports compliance. A strong plan covers people, processes, technology, facilities, and suppliers rather than IT alone.
What Should A Business Continuity Plan Include?
A solid plan includes a risk assessment, business impact analysis, recovery objectives, response procedures, communication plans, assigned roles, alternate resources, and a testing schedule. It should also list vendor contacts, ISP account details, and instructions for switching to backup connectivity.
How Does Internet Downtime Affect A Business?
Downtime stops cloud apps, payment processing, VoIP calls, and remote access. It leads to lost sales, idle employees, missed customer requests, and possible reputation damage. The cost grows with every hour, especially for e-commerce, healthcare, finance, and call center operations.
What Are Rto And Rpo, And Why Do They Matter?
Recovery Time Objective (RTO) is the longest acceptable time to restore a service after an outage. Recovery Point Objective (RPO) is the most data loss you can accept, measured in time. Together they guide how much you invest in failover, backups, and redundant connections.
Is One Internet Connection Enough For A Small Business?
Only if short outages will not hurt operations. Most small businesses that take card payments, use cloud software, or rely on VoIP benefit from a backup link. A low-cost 4G/5G failover device can provide strong protection without a large budget.
What Is The Best Backup For A Primary Fiber Connection?
A different type of connection from a different carrier works best, such as 5G cellular or fixed wireless. This avoids shared failure points like a single cable route. For locations with high uptime needs, a second wired ISP on a separate entrance path adds extra protection.
How Is A Business Continuity Plan Different From Disaster Recovery?
Business continuity covers the whole organization and focuses on keeping operations going. Disaster recovery is a subset focused on restoring IT systems, applications, and data. You need both, and both rely on dependable network access.
Does A Ups Keep My Internet Working During A Power Outage?
It can, for a limited time, if your modem, router, switch, and fiber terminal are all connected to it. Runtime depends on battery size and load, and usually ranges from several minutes to a few hours. For longer outages, pair it with a generator or a battery-backed cellular router.
How Often Should I Test My Continuity Plan?
Test network failover at least every quarter and conduct a broader continuity exercise at least once a year. Also retest after changes to your ISP, hardware, office layout, or software. Regular testing exposes outdated contacts, wrong configurations, and expired backup plans.
Who Should Be Responsible For The Business Continuity Plan?
Leadership should own it, with an appointed continuity coordinator managing updates and drills. IT, operations, HR, and finance should all contribute. Assigning a named person and a backup for each role avoids confusion when an incident occurs.