[Company name]
Business Continuity Plan
| Organization | [Company name] |
|---|---|
| Document | Business Continuity Plan |
| Document owner | [Owner name], [Owner title] |
| Approved by | [Approver name], [Approver title] |
| Effective date | [Effective date] |
| Version | [Version] |
| Review frequency | Reviewed [Review frequency] and after any significant change |
| Classification | Internal use |
1. Purpose and Scope
This Business Continuity Plan ("the Plan") describes how [Company name] will continue its most important business functions during and after a disruption, with a focus on the technology, communications, and vendor dependencies those functions rely on.
The Plan applies to all locations, including [Primary office address], and to all employees. It works together with:
- The IT Disaster Recovery Plan, which covers restoring systems and data, including the hurricane annex
- The Incident Response Plan, which covers cyberattacks and data breaches
- The Data Backup Plan and Policy, which covers how data is protected and restored
Life safety always comes first. Nothing in this Plan requires employees to put themselves at risk to protect property or equipment.
2. Planning Assumptions
This Plan is designed for disruptions such as:
- Loss of access to the office for days or weeks (hurricane, flood, fire, building damage, or closure)
- Extended power or internet outage
- Failure or compromise of a critical system, including ransomware
- Outage at a key cloud provider or vendor
- Unavailability of key people because of illness, evacuation, or departure
The Plan assumes that most staff can work from home with a company laptop and internet access, that core systems are available from the cloud or can be restored there, and that at least one leadership member is reachable at all times.
Drafting note: Test these assumptions. If some roles cannot work remotely (for example, front desk, shipping, or clinical staff), document how those functions will be handled in Section 7.
3. Roles and Responsibilities
| Role | Assigned to | Responsibilities |
|---|---|---|
| Continuity coordinator | [Continuity coordinator] | Activates the Plan, coordinates the response, tracks progress, and decides when to return to normal operations. |
| Executive sponsor | [Approver name], [Approver title] | Makes major decisions: closing or relocating, emergency spending, and client commitments. |
| IT lead | [IT contact] ([IT provider / MSP]) | Restores systems, enables remote access, and supports alternate work arrangements. |
| Communications lead | [Owner name] | Sends staff, client, and vendor communications; updates website and voicemail. |
| HR / people lead | [HR contact] | Tracks staff safety and availability; handles payroll and leave questions. |
| Department leads | One per team | Carry out continuity procedures for their functions and report status. |
4. Business Impact Analysis
The business impact analysis (BIA) identifies which functions matter most and how quickly the impact grows when they stop. It is reviewed [Review frequency] with department leads.
| Business function | Impact after 4 hours | Impact after 1 day | Impact after 1 week | Priority |
|---|---|---|---|---|
| Serving customers / clients | Moderate: delayed responses | High: missed appointments or orders | Severe: lost clients and revenue | 1 |
| Receiving calls and email | Moderate | High | Severe | 1 |
| Billing and collections | Low | Moderate: delayed cash flow | High | 2 |
| Payroll | Low | Low | High near pay dates | 2 |
| Paying vendors | Low | Low | Moderate | 3 |
| Marketing and sales | Low | Low | Moderate | 3 |
For each function, consider financial loss, contractual or legal penalties, customer impact, reputation, and safety.
5. Critical Functions and Recovery Targets
The table below lists the critical functions, the maximum acceptable downtime (RTO), the maximum acceptable data loss (RPO), and the minimum resources needed to perform each function in a degraded mode.
| Critical function | Systems relied on | RTO | RPO | Minimum resources to operate | Manual workaround |
|---|---|---|---|---|---|
| Client service and scheduling | [Main line-of-business application], email, phones | 4-8 hours | 1 hour | 2 staff, laptops, internet, access to [Main line-of-business application] | Printed schedule for next 2 days; take messages by phone |
| Phones and email | [Email / productivity platform], [Phone / VoIP provider] | 4 hours | 1 hour | Mobile phones, laptop with internet | Forward [Main business phone number] to mobiles |
| Billing and invoicing | Accounting system | 2 days | 24 hours | 1 staff, laptop, accounting access | Record charges in a spreadsheet; invoice later |
| Payroll | Payroll provider | 3 days before pay date | 1 pay period | Payroll provider access, prior period data | Repeat prior payroll through provider |
| Accounts payable | Accounting system, bank portal | 5 days | 24 hours | Bank portal access with MFA | Pay critical vendors directly from bank portal |
Drafting note: The RTO and RPO values must match what your IT systems can actually deliver. Confirm them against the IT Disaster Recovery Plan and your backup tests.
6. Dependencies
Critical functions depend on more than computers. The Plan identifies these dependencies and how each is protected:
| Dependency | Primary | Backup / contingency |
|---|---|---|
| Internet connectivity | [Internet service provider] | Secondary ISP or cellular failover device; staff hotspots |
| Power | Utility | UPS on network and servers for graceful shutdown; generator if available; work from powered locations |
| Phones | [Phone / VoIP provider] | Call forwarding to mobiles; softphone apps on laptops and phones |
| Email and files | [Email / productivity platform] | Access from any internet-connected device; third-party backup |
| Core application | [Main line-of-business application] | Vendor support; restore from backup; printed critical data |
| IT support | [IT provider / MSP] | Remote support; backup contact at provider |
| Banking | Primary bank | Online banking access for two authorized people |
| Key people | Named role holders | Cross-trained backups and documented procedures |
7. Alternate Work Arrangements
Remote work
- Employees who can work remotely do so using company laptops, protected by MFA and managed through [Device management (MDM) tool].
- Staff take laptops, chargers, and MFA devices home when a disruption is forecast (for example, a storm watch).
- Employees without reliable home internet are given hotspots or directed to the alternate site.
- Remote work follows the Remote Work and BYOD Policy; personal devices are used only as that policy allows.
Alternate site
If the office is unavailable and remote work is not enough, staff will work from [Alternate work location]. The continuity coordinator confirms availability of the alternate site at least [Review frequency], including internet access, desk space, printing, and secure storage.
Phone forwarding
- Log in to the [Phone / VoIP provider] portal or call the provider.
- Forward [Main business phone number] to the designated answering person's mobile, or to a hunt group of mobiles.
- Update the voicemail greeting and after-hours message with current status.
- Record forwarding changes so they can be reversed when normal operations resume.
Manual workarounds
- Keep a printed or offline copy of the next few days' schedule, key client contacts, and open orders, refreshed daily during storm season or when a disruption is forecast.
- Use paper forms or a spreadsheet to record transactions; enter them into systems after recovery.
- Keep blank forms, a list of account numbers for critical vendors, and a printed copy of this Plan in the continuity kit (Section 11).
8. Plan Activation
The continuity coordinator, [Continuity coordinator], activates the Plan when a critical function is disrupted, or is expected to be disrupted, longer than its RTO, or when the office is closed. If the coordinator is unavailable, any member of leadership may activate it.
- Confirm the safety and whereabouts of all employees.
- Assess which critical functions are affected and for how long.
- Notify the continuity team and the IT lead.
- Decide on the operating mode: normal with workarounds, remote, alternate site, or temporary closure.
- Communicate the decision to staff, clients, and vendors (Section 9).
- Set a regular status meeting (for example, 9 a.m. and 3 p.m. daily) until normal operations resume.
9. Communication Plan
| Audience | Method | Responsible | Timing |
|---|---|---|---|
| Employees | [Staff emergency notification method], personal mobile, personal email | [HR contact] | Within 2 hours of activation, then at each status change |
| Leadership | Phone call / group chat | [Continuity coordinator] | Immediately |
| Clients / customers | Email, website notice, voicemail greeting, social media | [Owner name] | Within 4 hours if service is affected |
| Key vendors | Phone / email | Department leads | As needed to reschedule deliveries or services |
| Insurer | Phone / claims portal | [Approver name] | As soon as a loss is likely |
Sample client message
"Due to [event], [Company name]'s office at [Primary office address] is temporarily closed. Our team is working remotely and we are continuing to serve clients. You can reach us at [Main business phone number] or by email as usual. We will post updates at [website] and will contact you directly about any scheduled appointments or deliveries."
Sample staff message
"[Event] update: The office is closed on [date]. Please confirm you are safe by replying to this message. If you are able to work, sign in remotely as usual. Next update at [time]. Contact [Continuity coordinator] at [Continuity coordinator mobile] with any questions."
Drafting note: Keep an up-to-date staff contact list (personal mobile, personal email, emergency contact) outside company systems, and review it every time someone joins or leaves.
10. Key Vendor List
Keep this list current and available offline. Include account numbers and support contract details so anyone on the team can call for help.
| Vendor | Service provided | Account number | Support phone / email | Contract / SLA notes |
|---|---|---|---|---|
| [IT provider / MSP] | IT support and management | [IT contact phone] / [IT contact email] | ||
| [Internet service provider] | Internet service | |||
| [Phone / VoIP provider] | Phones / VoIP | |||
| [Email / productivity platform] | Email and productivity | |||
| [Main line-of-business application] vendor | Core business application | |||
| [Backup solution / provider] | Backup and recovery | |||
| [Cyber insurance carrier] | Cyber / property insurance | [Insurer claims / breach hotline] | ||
| Bank | Banking and payments | |||
| Landlord / property manager | Facility |
11. Emergency Supplies and Equipment
The continuity coordinator maintains a continuity kit, checked at least twice a year and before June 1 each year:
- Printed copy of this Plan, the IT Disaster Recovery Plan, and contact lists
- At least one spare laptop, enrolled and updated, with chargers
- Cellular hotspot or cellular failover device with an active plan
- Portable battery packs and car chargers for phones
- Power strips and surge protectors
- Blank paper forms and printed client schedules for manual workarounds
- List of account numbers and support contacts for key vendors
- Waterproof bags or containers for documents and small equipment
12. Hurricanes and Severe Weather
Hurricanes are the most likely wide-area disruption for [Company name]. Detailed technology preparation, shutdown, and restart steps are in the hurricane annex of the IT Disaster Recovery Plan. From a continuity perspective:
- Before June 1, review this Plan, update staff contacts, confirm remote work readiness, and check the continuity kit.
- When a storm watch is issued, staff take laptops home each night and print the next week's schedule.
- Decisions about closing the office follow official evacuation orders and staff safety, never deadlines.
- After the storm, confirm staff safety first, then follow the restart steps in the DR Plan and resume operations function by function in priority order.
- Expect that staff may be dealing with damage to their own homes. Build flexibility into schedules and cross-train so fewer people can cover more work.
13. Prolonged Staff Absence and Key-Person Risk
An illness outbreak, evacuation, or sudden departure can leave the business without the people who know how things work. To reduce this risk:
- Each critical function has a primary and at least one cross-trained backup person.
- Important procedures are documented in a shared location, not only in someone's head or personal files.
- Administrative access to critical systems (email admin, domain registrar, bank, payroll, IT provider portal) is held by at least two people, and credentials are stored in [Company password manager].
- If a large share of staff are unavailable, the continuity coordinator prioritizes Priority 1 functions and pauses lower-priority work.
- Remote work arrangements allow people who are well but cannot come to the office to keep working.
14. Return to Normal Operations
- Office or systems confirmed safe and fully working
- Data entered manually during the disruption has been entered into systems
- Phone forwarding and temporary voicemail messages reversed
- Clients and vendors notified that normal operations have resumed
- Temporary accounts, devices, and access removed or secured
- Costs, damage, and receipts documented for insurance
- Debrief held and this Plan updated within 10 business days
15. Training, Exercises, and Maintenance
| Activity | Frequency | Owner |
|---|---|---|
| Brief new employees on their continuity role and where to find the Plan | At onboarding | [HR contact] |
| Test staff notification method | Twice a year | [Continuity coordinator] |
| Remote work test day (everyone works remotely) | Annually, before hurricane season | [Continuity coordinator] |
| Tabletop exercise with leadership | Annually | [Continuity coordinator] |
| Update BIA, critical functions, and vendor list | [Review frequency] | [Owner name] |
| Check continuity kit | Twice a year and before June 1 | [Continuity coordinator] |
The Plan is also updated after any activation, a change in office location, the addition or loss of a key vendor or system, or significant changes in staff.
16. Revision History
| Version | Date | Description of change | Author |
|---|---|---|---|
| [Version] | [Effective date] | Initial adoption of this Business Continuity Plan | [Owner name] |
17. Approval
This Business Continuity Plan has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.
| Signature: | Name / title: [Approver name], [Approver title] | Date: |
| Signature: | Name / title: [Owner name], [Owner title] | Date: |
Template adapted from the free Business Continuity Plan template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.
