No Agreed Recovery Clock
You have backups, but no agreed time by which the business is running again (RTO) or how much data you can lose (RPO).
CLOSED BY RECOVERY ACCOUNTABILITY
✓
DISASTER RECOVERY PLANNING & TESTING
SERVICE FAMILY: RESILIENCE
If the business stops, who owns getting it running — and by when?
THE WRITTEN PROMISE
Beyond backup: a tested, governed recovery plan for your critical systems.
100% Written Scope Boundary
3 Tiers START · CORE · STRATEGIC
Named Senior Ownership
Designated Layer Mandate
Recovery Accountability
Contract Family
RESILIENCE
Delivery Model
Outcome-Based · Fixed Tier
Boundary Status
Inclusions & Exclusions Written
Escalation Point
Senior Cape Town Engineers
OPERATIONAL DIAGNOSTIC
Signs nobody owns this yet
Backup protects data; it does not guarantee your business is back up within a defined time. Recovery Accountability turns recovery into something designed, tested, and owned — not improvised on the day.
Single-Person Memory
The recovery plan lives inside one engineer’s head rather than a version-controlled, step-by-step runbook.
CLOSED BY RECOVERY ACCOUNTABILITY
✓
Never Rehearsed
Failover has never been tested under realistic conditions, so recovery would be improvised live on the day.
CLOSED BY RECOVERY ACCOUNTABILITY
✓
WRITTEN SCOPE ARCHITECTURE
What we own — and what stays separate.
Ambiguity is where IT partnerships break down. We publish both what is included in Recovery Accountability and what is scoped separately so your team never discovers a gap mid-incident.
[!] WHAT STAYS SEPARATE, AND WHY
Scoped separately: The underlying data backup (must already be contracted under Data Accountability) · business-continuity management · keeping staff productive during an outage · application redevelopment · recovery obligations of third-party vendors.
Disaster recovery governs the technical restoration of agreed workloads from verified backups; underlying backup and non-IT business continuity remain separate.
CONTRACTED INCLUSIONS (5 CORE MANDATES)
FAMILY: RESILIENCE
- A defined recovery scope and documented runbooks for critical business systems
- Recovery targets (RPO/RTO), scaling from best-effort up to per-workload contractual commitments
- Recovery testing, from an annual table-top exercise up to regular failover drills with signed evidence
- Assisted or orchestrated recovery execution during a formally declared incident
- Executive-level recovery reporting and priority recovery support STRATEGIC
THE 6-PART DR QUALIFICATION RULE
It’s only disaster recovery if all six are agreed: recovery targets (RPO/RTO) · recovery scope · documented runbooks · recovery location · who can declare a disaster · testing cadence and evidence.
Without all six, it’s backup and recovery — not disaster recovery.
OPERATIONAL REALITY CHECK
Coverage and ownership are not the same thing.
GOOD TO KNOW // OPERATIONAL BOUNDARY RULE
Priced in four parts: design & onboarding, monthly readiness retainer, testing (per test), and incident execution (charged only when a disaster is formally declared). We scope it properly rather than quote a single number upfront. Both Server Accountability and Data Accountability must be in place first.
SERVICE TIER ARCHITECTURE
Recovery Accountability Tiers
Three levels of disaster recovery governance, testing cadence, and execution commitment.
FOUNDATIONAL DR
START
Critical-systems scope, a runbook, best-effort recovery targets, and an annual test.
Includes an annual table-top or partial restore test and a written test report.
RECOMMENDED STANDARD
RECOMMENDED
CORE
Full DR design, versioned runbooks, recovery targets per workload, scheduled testing, and assisted recovery.
Designed for multi-server environments requiring defined RPO/RTO per workload tier and assisted failover during declared incidents.
MISSION-CRITICAL
STRATEGIC
Orchestrated recovery, committed targets per workload, regular drills, and priority recovery.
Includes regular failover drills with audit evidence, executive DR reporting, and priority recovery invocation.
Our services are deliberately modular. Network, backup, security depth, server and cloud are separate commercial decisions — never bundled implicitly into per-user pricing.
CONNECTED ACCOUNTABILITY LAYERS
What connects with Recovery Accountability
Every layer is modular by design and integrates cleanly with adjacent operational responsibilities.
QUESTIONS & CLARIFICATIONS
Recovery Accountability FAQs
Why is Disaster Recovery priced in four parts instead of a single monthly fee?
Because designing runbooks, keeping them updated monthly, running full technical restore rehearsals, and executing a live disaster failover are four distinct activities. Separating them keeps your monthly readiness retainer lean while ensuring tests and live invocations are properly resourced.
NEXT STEP