Field note
Setting Recovery Objectives That Hold Under Pressure
How operations and IT teams in South Africa can agree recovery time and recovery point targets that reflect real downtime costs, not wishful numbers on a slide.
Recovery objectives fail when they are written for auditors and forgotten by the people who restore systems. A useful target names the workload, the maximum acceptable downtime, and the data loss window leadership can live with.
Start with revenue and safety impacts rather than tool defaults. A warehouse dispatch system and a marketing site rarely share the same urgency, yet many backup policies treat them identically.
Interview the owners of each critical process. Ask what a four-hour outage costs in overtime, missed deliveries, and customer commitments. Those answers ground recovery time objectives in operations, not theory.
Document the dependencies behind each objective. If payroll depends on identity services, the identity restore path must meet or beat payroll’s target. Cascading dependencies are where plans quietly break.
Revisit objectives after major change: new branches, cloud migrations, or seasonal peaks. A plan written in quieter months can understate December demand for retail and logistics firms.
Finally, pair each objective with a verification method. If you claim a two-hour restore, schedule a measured restore rehearsal and record the actual elapsed time.