Free recovery-planning tool

Backup and Recovery Readiness Score

Estimate recoverability, compare backup and restore capability with RPO/RTO targets, and surface the recovery gaps that matter most.

Simple recovery screen

Measure whether backups can actually support recovery

0–100 readiness

Backup coverage & freshness

Critical data / systems backed up

Typical backup interval

hours

Target maximum data loss (RPO)

hours

Offline / immutable backup coverage

Restore confidence

Months since last restore test

months

Successful restore rate

Estimated full recovery time

hours

Target recovery time (RTO)

hours

Recovery operations

ControlMaturity

Backup monitoring & failure alerts0 = manual/unknown; 4 = automated monitoring, alert ownership and follow-up.

/ 4

Backup credential / admin separationBackup administration is separated from ordinary production access.

/ 4

Recovery runbook & assigned rolesRecovery order, owners, contacts and restoration steps are documented.

/ 4

SaaS, cloud configuration & identity backup coverageCoverage includes more than ordinary files and local servers.

Simple methodReadiness combines backup coverage, RPO freshness, offline/immutable protection, restore-test recency, restore success, RTO performance, monitoring, credential separation, recovery runbooks and cloud/SaaS/configuration coverage. Estimated recoverability is a separate model-based estimate driven mainly by coverage and demonstrated restore capability. It is not a probability that every system will recover.

Advanced recovery model

Score recoverability by critical workload

4 workload classes

Critical workloads

WorkloadImportanceBackup coverageBackup intervalRPORestore successRestore timeRTOLast test

Files & core business data

Applications & databases

Cloud / SaaS business data

Identity, configuration & infrastructure

Backup resilience & recovery operations

Offline / immutable copy coverage

Offsite / separate-failure-domain coverage

Recovery-environment readiness

/ 4

Backup monitoring & alerting

/ 4

Backup credential separation

/ 4

Recovery runbook / roles / restore order

/ 4

Advanced methodEach workload receives a recoverability score from backup coverage, freshness against RPO, demonstrated restore success, restore-test recency and recovery time against RTO. Workload scores are weighted by importance. A separate resilience-control score measures isolated/offsite copies, monitoring, credential separation, runbooks and recovery-environment readiness. Overall readiness = 75% workload recoverability + 25% resilience controls.

Workload breakdown

Recoverability by critical workload

Importance-weighted

Workload	Importance	Coverage	RPO score	Restore success	Test recency	RTO score	Recoverability

Recovery gaps

Highest-impact improvements

Largest modeled score improvement first

Priority	Recovery gap	Current score	Model weight	Potential readiness improvement

Restore-test sensitivity

Readiness as restore testing becomes more recent

All workload test ages scaled together

Test-age scale	Workload recoverability	Overall readiness	Recovery gap

Isolation sensitivity

Readiness as offline / immutable coverage changes

Other recovery assumptions unchanged

Isolation coverage	Resilience-control score	Overall readiness	Estimated recoverability

Scope

Backup readiness is not proof of recoverability

This score is a planning screen, not a disaster-recovery test, backup audit, cyber-insurance determination or guarantee that systems will restore after ransomware, hardware failure or cloud disruption. Actual recoverability depends on backup integrity, credentials, encryption keys, application dependencies, infrastructure capacity, vendor availability and the quality of recovery testing.

Framework note: the model emphasizes backup creation, protection, maintenance and testing, plus isolated recoverable copies and recovery procedures. These themes are consistent with current NIST CSF 2.0 recovery guidance and CISA ransomware guidance.