Free business continuity planning tool
Business Continuity Priority Planner
Rank the systems and business functions that should be restored first using business impact, recovery-time targets, dependencies, workaround capability and current recovery performance.
Simple continuity planner
Priority 1–4Rank six systems or functions by restoration priority
RatingsImpact / dependency: 1 low → 5 criticalWorkaround: 0 none → 4 strong
System / functionBusiness impactTarget RTOCurrent recoveryDependencyWorkaround
/5
hr
hr
/5
/4
/5
hr
hr
/5
/4
/5
hr
hr
/5
/4
/5
hr
hr
/5
/4
/5
hr
hr
/5
/4
/5
hr
hr
/5
/4
Simple methodPriority score = 35% business impact + 20% RTO urgency + 15% dependency criticality + 15% workaround weakness + 15% recovery gap. RTO urgency increases as the target recovery window gets shorter. Recovery gap rises when current recovery time exceeds the target RTO. Priority tiers are model labels, not regulatory classifications.
Simple sequence table
Highest priority firstPriority, RTO and current recovery gap
| Sequence | System / function | Priority tier | Priority score | Target RTO | Current recovery | RTO gap |
|---|
Advanced business-impact model
RTO + MTPD + capabilityRank ten systems and functions using continuity impact
Business context
Systems & functions
NameRevenue dependentOperational impactCustomer impactSafety / regulatoryDependency criticalityMTPDTarget RTOCurrent recoveryWorkaroundRecovery confidence
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
%
/5
/5
/5
/5
hr
hr
hr
/4
%
Advanced methodImpact score = 20% revenue dependence + 25% operational impact + 20% customer impact + 20% safety/regulatory impact + 15% dependency criticality. Priority score = 45% impact + 20% RTO urgency + 15% workaround weakness + 20% continuity gap. Continuity gap is zero when current recovery meets RTO, rises between RTO and MTPD, and reaches 100 when current recovery reaches or exceeds MTPD.
Restoration sequence
Highest priority firstBusiness functions ranked by recovery priority
| Sequence | System / function | Tier | Priority score | Impact score | RTO | MTPD | Current recovery | RTO gap | Confidence | Standalone revenue exposure |
|---|
Recovery capability sensitivity
All current recovery times scaled togetherPriority gaps as current recovery times improve or worsen
| Recovery-time scale | RTO misses | MTPD breaches | Priority 1 functions | Average continuity gap |
|---|
RTO sensitivity
All target RTOs scaled togetherPriority mix as target RTOs become tighter or looser
| RTO scale | RTO misses | Priority 1 | Priority 2 | Average priority score |
|---|
Workaround sensitivity
All workaround ratings shifted togetherPriority scores as manual workaround capability changes
| Workaround shift | Average priority score | Priority 1 functions | Highest-priority function |
|---|
Scope
Restoration order should be validated against real dependencies
This planner is a business-impact and prioritization model, not a complete business continuity plan. Actual sequencing can change because of technical dependency chains, safety constraints, people availability, vendor dependencies, building access, data integrity, cyber-containment requirements and recovery-resource bottlenecks. A lower-ranked system may need to be restored first if a higher-ranked function depends on it.