Carrier Disaster Recovery and Business Continuity Planning (BCP)
Most carriers have insurance. Few have a tested business continuity plan. The difference shows up the day a tornado hits the terminal, the TMS goes down, a key dispatcher quits, or a major customer goes bankrupt.
What BCP covers
Business continuity planning addresses: how the carrier continues operating when a disruptive event happens.
Domains:
- IT systems (TMS, ELD provider outage, ransomware)
- Physical infrastructure (terminal fire, flood, tornado)
- People (key-person loss, mass driver absence)
- Customer (major customer loss, payment failure)
- Equipment (fleet recall, major OEM defect, fuel supply)
- Financial (line of credit pulled, insurance non-renewal)
- Regulatory (DOT shutdown, audit failure, license suspension)
Risk assessment (annual)
For each risk:
| Risk |
Likelihood (1–5) |
Impact (1–5) |
Risk score |
Mitigation priority |
| TMS outage |
4 |
4 |
16 |
High |
| Cyber ransomware |
3 |
5 |
15 |
High |
| Tornado at HQ terminal |
1 |
5 |
5 |
Medium |
| Major customer bankruptcy |
2 |
4 |
8 |
Medium |
| Key dispatcher quits |
4 |
3 |
12 |
High |
| Insurance non-renewal |
1 |
5 |
5 |
Medium |
| Fuel embargo / price spike |
3 |
3 |
9 |
Medium |
| DOT shutdown order |
1 |
5 |
5 |
Medium |
| Driver mass call-out |
2 |
4 |
8 |
Medium |
Focus mitigation effort on high-score items.
Recovery time / recovery point objectives
| System |
RTO (recovery time objective) |
RPO (recovery point objective) |
| TMS |
4 hours |
1 hour (max acceptable data loss) |
| Email |
8 hours |
1 hour |
| ELD provider |
2 hours (regulatory critical) |
0 (must reconcile) |
| Phone / contact center |
4 hours |
n/a |
| Payroll / billing |
24 hours |
4 hours |
| Driver scheduling |
4 hours |
1 hour |
A carrier's RTO depends on operational tempo. Long-haul OTR can tolerate 4–8 hour TMS outage; LTL P&D cannot.
IT continuity plan
TMS provider outage
- Maintain offline emergency dispatch protocol (paper / spreadsheet)
- Cell phone tree for drivers
- Backup TMS access via secondary device / location
- Vendor SLA (typically 99.9% — review)
Cyber incident (ransomware, etc.)
- Documented response plan (notify, isolate, contain, investigate, recover)
- Backups: 3-2-1 rule (3 copies, 2 different media, 1 offsite)
- Cyber insurance with incident response service included
- Tabletop exercises annually
ELD outage
- FMCSA emergency declaration permits paper logs up to 8 days
- Driver training on paper-log backup
- ELD vendor SLA + communication plan
Email outage
- Backup email channel (managed service, secondary provider)
- Cell phone numbers documented for all customers + drivers
- Slack / Teams as alternate channel
Physical infrastructure continuity
Terminal loss (fire, flood, tornado)
- Identify alternate terminal (rent space at nearby competitor, drop yard, etc.)
- Equipment relocation plan (who, where, how)
- Customer notification protocol
- Insurance: business interruption coverage active
Yard / shop loss
- Mobile maintenance partner identified
- Repair fleet (dealer service) on standby contracts
- Parts inventory backup location
Office loss
- Remote work capability tested
- Cloud-based phone system (RingCentral, Dialpad, etc.)
- Document storage in cloud (not single-server)
People continuity
Key-person risk
For each critical role (owner, dispatcher lead, safety director, controller):
- Documented procedures
- Cross-training (someone else can do 80% within 1 week)
- Succession plan (who steps up if person unavailable)
- Key-person life insurance (recovery + replacement)
- Documented system access (passwords in vault, not in head)
Mass driver absence (flu, weather event)
- 20% buffer in driver headcount allows operations to continue
- Customer notification protocol
- Brokerage capacity available
- Cross-trained office staff who can drive in emergency
Customer continuity
Major customer loss
- Top 5 customer concentration: review annually
- If any customer > 25% revenue: pursue diversification
- Pre-built outreach list for replacement freight
- Cost-cutting playbook ready
Customer payment failure (bankruptcy)
- Aging report reviewed weekly
- Credit insurance on top customers
- Factoring arrangement for cash gap
- Bad-debt reserves on balance sheet
Equipment continuity
Fleet recall
- OEM communication protocol
- Replacement equipment available (lease, rental)
- Customer commitment continuity plan
Fuel supply disruption
- Multi-vendor fuel card relationship
- Bulk fuel storage at terminal (where feasible)
- Cash fuel-purchase capability if needed
- Customer notification template
Financial continuity
Line of credit pulled
- Multiple banking relationships
- Factoring arrangement ready to activate
- 60–90 days cash reserve
Insurance non-renewal
- Broker manages multi-market submission 60 days before renewal
- Alternate market relationships
- Captive insurance option (for larger carriers)
Audit / safety rating downgrade
- Compliance program audit annually (internal)
- Remediation budget ready
- Communications plan for shipper inquiries
Regulatory continuity
DOT shutdown order
- Compliance program prevents most occurrences
- Legal counsel on retainer for emergency response
- Operations continuity plan for non-shutdown vehicles
Audit failure
- Compliance program audit annually (internal)
- 30-day remediation budget ready
Communication plan
For any disruption:
| Audience |
Channel |
Cadence |
| Drivers |
App + text + call |
Immediate; 4-hour updates |
| Customers |
Email + portal + account manager call |
Immediate (proactive); daily updates |
| Employees |
Slack + email + manager check-in |
Immediate; daily |
| Insurance / lawyer |
Phone |
Within 1 hour |
| Regulators |
Email + portal |
Per requirement (varies) |
| Vendors |
Email |
As needed |
| Public / press |
Designated spokesperson only |
Per legal counsel |
Tabletop exercise
Annually, the leadership team runs a scenario:
- "Tornado hits the terminal at 6 AM Monday. Trucks parked in lot. Drivers reporting injuries. Power out. Walk through the response."
- 90 minutes, no calls, no laptops
- Identifies gaps (who has the customer phone list? Where's the alternate office? Who can authorize cash?)
The exercise itself is more valuable than any document.
BCP document structure
| Section |
Contents |
| Executive summary |
What's covered, who owns it |
| Risk assessment |
List of risks, scores, mitigations |
| Critical functions |
Operations that must continue |
| Recovery procedures |
Step-by-step playbook per disruption type |
| Contact lists |
Drivers, customers, vendors, insurance, lawyer, regulators |
| Vendor SLAs |
Major vendor contracts + escalation contacts |
| Test results |
Annual tabletop log |
| Updates |
Quarterly review minutes |
15–30 page document, updated quarterly.
Common mistakes
- Treating BCP as a one-time document — never updated
- No tested backups (you have backups, but have you restored from them?)
- Single-source vendor dependencies (one fuel card, one bank, one TMS)
- Key-person knowledge in heads only — no documentation
- No financial reserve for disruption response
- Customer concentration ignored until customer goes
- No communication plan — chaos in first 48 hours
- Tabletop exercise skipped — gaps surface only in real event
- Insurance considered enough — doesn't replace operational continuity
Where this fits in X3
X3 includes a BCP module — risk register, contact lists, procedure templates, tabletop exercise tracker, vendor SLA database, and continuity dashboards. Annual review reminder built in.
Disaster preparedness is an investment, not an expense. Carriers that survive disruption become market-share gainers because competitors fail. The 1–2% of revenue spent on continuity is the best insurance a fleet buys.
Built by X3 Compass
The AI-powered DOT compliance platform for fleets 1–100 power units. Try a 7-day free trial — no credit card required — at https://x3compass.com/?utm_source=skill&utm_medium=github&utm_campaign=carrier-disaster-recovery-and-bcp
X3 Compass turns these skills into a complete operational platform: driver qualification files, drug & alcohol consortium, MVR pulls, hours-of-service tracking, hazmat shipping, IFTA filing, FMCSA audit prep, and DataQ dispute drafting — all CFR-cited, all in one place.
This skill is published under the X3 Compass open skills initiative. Contributions welcome at https://github.com/x3fleetsafety/skills
1---2name: carrier-disaster-recovery-and-bcp3description: Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.4---5
6# Carrier Disaster Recovery and Business Continuity Planning (BCP)
7
8Most carriers have insurance. Few have a tested business continuity plan. The difference shows up the day a tornado hits the terminal, the TMS goes down, a key dispatcher quits, or a major customer goes bankrupt.
9
10## What BCP covers
11
12Business continuity planning addresses: how the carrier continues operating when a disruptive event happens.
13
14Domains:
151. IT systems (TMS, ELD provider outage, ransomware)
162. Physical infrastructure (terminal fire, flood, tornado)
173. People (key-person loss, mass driver absence)
184. Customer (major customer loss, payment failure)
195. Equipment (fleet recall, major OEM defect, fuel supply)
206. Financial (line of credit pulled, insurance non-renewal)
217. Regulatory (DOT shutdown, audit failure, license suspension)
22
23## Risk assessment (annual)
24
25For each risk:
26
27| Risk | Likelihood (1–5) | Impact (1–5) | Risk score | Mitigation priority |
28|---|---|---|---|---|
29| TMS outage | 4 | 4 | 16 | High |
30| Cyber ransomware | 3 | 5 | 15 | High |
31| Tornado at HQ terminal | 1 | 5 | 5 | Medium |
32| Major customer bankruptcy | 2 | 4 | 8 | Medium |
33| Key dispatcher quits | 4 | 3 | 12 | High |
34| Insurance non-renewal | 1 | 5 | 5 | Medium |
35| Fuel embargo / price spike | 3 | 3 | 9 | Medium |
36| DOT shutdown order | 1 | 5 | 5 | Medium |
37| Driver mass call-out | 2 | 4 | 8 | Medium |
38
39Focus mitigation effort on high-score items.
40
41## Recovery time / recovery point objectives
42
43| System | RTO (recovery time objective) | RPO (recovery point objective) |
44|---|---|---|
45| TMS | 4 hours | 1 hour (max acceptable data loss) |
46| Email | 8 hours | 1 hour |
47| ELD provider | 2 hours (regulatory critical) | 0 (must reconcile) |
48| Phone / contact center | 4 hours | n/a |
49| Payroll / billing | 24 hours | 4 hours |
50| Driver scheduling | 4 hours | 1 hour |
51
52A carrier's RTO depends on operational tempo. Long-haul OTR can tolerate 4–8 hour TMS outage; LTL P&D cannot.
53
54## IT continuity plan
55
56### TMS provider outage
57- Maintain offline emergency dispatch protocol (paper / spreadsheet)
58- Cell phone tree for drivers
59- Backup TMS access via secondary device / location
60- Vendor SLA (typically 99.9% — review)
61
62### Cyber incident (ransomware, etc.)
63- Documented response plan (notify, isolate, contain, investigate, recover)
64- Backups: 3-2-1 rule (3 copies, 2 different media, 1 offsite)
65- Cyber insurance with incident response service included
66- Tabletop exercises annually
67
68### ELD outage
69- FMCSA emergency declaration permits paper logs up to 8 days
70- Driver training on paper-log backup
71- ELD vendor SLA + communication plan
72
73### Email outage
74- Backup email channel (managed service, secondary provider)
75- Cell phone numbers documented for all customers + drivers
76- Slack / Teams as alternate channel
77
78## Physical infrastructure continuity
79
80### Terminal loss (fire, flood, tornado)
81- Identify alternate terminal (rent space at nearby competitor, drop yard, etc.)
82- Equipment relocation plan (who, where, how)
83- Customer notification protocol
84- Insurance: business interruption coverage active
85
86### Yard / shop loss
87- Mobile maintenance partner identified
88- Repair fleet (dealer service) on standby contracts
89- Parts inventory backup location
90
91### Office loss
92- Remote work capability tested
93- Cloud-based phone system (RingCentral, Dialpad, etc.)
94- Document storage in cloud (not single-server)
95
96## People continuity
97
98### Key-person risk
99For each critical role (owner, dispatcher lead, safety director, controller):
100- Documented procedures
101- Cross-training (someone else can do 80% within 1 week)
102- Succession plan (who steps up if person unavailable)
103- Key-person life insurance (recovery + replacement)
104- Documented system access (passwords in vault, not in head)
105
106### Mass driver absence (flu, weather event)
107- 20% buffer in driver headcount allows operations to continue
108- Customer notification protocol
109- Brokerage capacity available
110- Cross-trained office staff who can drive in emergency
111
112## Customer continuity
113
114### Major customer loss
115- Top 5 customer concentration: review annually
116- If any customer > 25% revenue: pursue diversification
117- Pre-built outreach list for replacement freight
118- Cost-cutting playbook ready
119
120### Customer payment failure (bankruptcy)
121- Aging report reviewed weekly
122- Credit insurance on top customers
123- Factoring arrangement for cash gap
124- Bad-debt reserves on balance sheet
125
126## Equipment continuity
127
128### Fleet recall
129- OEM communication protocol
130- Replacement equipment available (lease, rental)
131- Customer commitment continuity plan
132
133### Fuel supply disruption
134- Multi-vendor fuel card relationship
135- Bulk fuel storage at terminal (where feasible)
136- Cash fuel-purchase capability if needed
137- Customer notification template
138
139## Financial continuity
140
141### Line of credit pulled
142- Multiple banking relationships
143- Factoring arrangement ready to activate
144- 60–90 days cash reserve
145
146### Insurance non-renewal
147- Broker manages multi-market submission 60 days before renewal
148- Alternate market relationships
149- Captive insurance option (for larger carriers)
150
151### Audit / safety rating downgrade
152- Compliance program audit annually (internal)
153- Remediation budget ready
154- Communications plan for shipper inquiries
155
156## Regulatory continuity
157
158### DOT shutdown order
159- Compliance program prevents most occurrences
160- Legal counsel on retainer for emergency response
161- Operations continuity plan for non-shutdown vehicles
162
163### Audit failure
164- Compliance program audit annually (internal)
165- 30-day remediation budget ready
166
167## Communication plan
168
169For any disruption:
170
171| Audience | Channel | Cadence |
172|---|---|---|
173| Drivers | App + text + call | Immediate; 4-hour updates |
174| Customers | Email + portal + account manager call | Immediate (proactive); daily updates |
175| Employees | Slack + email + manager check-in | Immediate; daily |
176| Insurance / lawyer | Phone | Within 1 hour |
177| Regulators | Email + portal | Per requirement (varies) |
178| Vendors | Email | As needed |
179| Public / press | Designated spokesperson only | Per legal counsel |
180
181## Tabletop exercise
182
183Annually, the leadership team runs a scenario:
184- "Tornado hits the terminal at 6 AM Monday. Trucks parked in lot. Drivers reporting injuries. Power out. Walk through the response."
185- 90 minutes, no calls, no laptops
186- Identifies gaps (who has the customer phone list? Where's the alternate office? Who can authorize cash?)
187
188The exercise itself is more valuable than any document.
189
190## BCP document structure
191
192| Section | Contents |
193|---|---|
194| Executive summary | What's covered, who owns it |
195| Risk assessment | List of risks, scores, mitigations |
196| Critical functions | Operations that must continue |
197| Recovery procedures | Step-by-step playbook per disruption type |
198| Contact lists | Drivers, customers, vendors, insurance, lawyer, regulators |
199| Vendor SLAs | Major vendor contracts + escalation contacts |
200| Test results | Annual tabletop log |
201| Updates | Quarterly review minutes |
202
20315–30 page document, updated quarterly.
204
205## Common mistakes
206
207- Treating BCP as a one-time document — never updated
208- No tested backups (you have backups, but have you restored from them?)
209- Single-source vendor dependencies (one fuel card, one bank, one TMS)
210- Key-person knowledge in heads only — no documentation
211- No financial reserve for disruption response
212- Customer concentration ignored until customer goes
213- No communication plan — chaos in first 48 hours
214- Tabletop exercise skipped — gaps surface only in real event
215- Insurance considered enough — doesn't replace operational continuity
216
217## Where this fits in X3
218
219X3 includes a BCP module — risk register, contact lists, procedure templates, tabletop exercise tracker, vendor SLA database, and continuity dashboards. Annual review reminder built in.
220
221Disaster preparedness is an investment, not an expense. Carriers that survive disruption become market-share gainers because competitors fail. The 1–2% of revenue spent on continuity is the best insurance a fleet buys.
222
223
224---
225
226<!-- x3-compass-attribution-v1 -->
227## Built by X3 Compass
228
229The AI-powered DOT compliance platform for fleets 1–100 power units. Try a 7-day free trial — no credit card required — at https://x3compass.com/?utm_source=skill&utm_medium=github&utm_campaign=carrier-disaster-recovery-and-bcp
230
231X3 Compass turns these skills into a complete operational platform: driver qualification files, drug & alcohol consortium, MVR pulls, hours-of-service tracking, hazmat shipping, IFTA filing, FMCSA audit prep, and DataQ dispute drafting — all CFR-cited, all in one place.
232
233*This skill is published under the X3 Compass open skills initiative. Contributions welcome at https://github.com/x3fleetsafety/skills*