The RTO/RPO Worksheet gives BCM teams a practical structure for capturing decisions, evidence, ownership, and review dates without turning continuity work into heavy paperwork.
Use this template when a team needs a repeatable format for process, downtime, data loss, strategy, approval. Adapt the fields to your organization, operating model, sector, and approval requirements.
Purpose
This template helps teams ask consistent questions, keep recovery assumptions visible, and connect outputs to BIA, continuity plans, exercises, audit evidence, and management review.
When to use it
Use it during program setup, annual refreshes, major changes, exercises, incidents, audit preparation, supplier reviews, or technology recovery planning. It is most useful when the owner can update it after real operational change.
Practical structure
| Field | What to capture |
|---|---|
| process | Owner, value, source, last review date, and next action. |
| downtime | Owner, value, source, last review date, and next action. |
| data loss | Owner, value, source, last review date, and next action. |
| strategy | Owner, value, source, last review date, and next action. |
| approval | Owner, value, source, last review date, and next action. |
Example fields
- Business owner and alternate owner.
- Scope, exclusions, assumptions, and review trigger.
- Critical dependencies including people, sites, systems, suppliers, data, and records.
- Recovery expectations, minimum service level, communication need, and evidence source.
- Approval, open actions, risk acceptance, and next review date.
Common mistakes
- Using every possible field instead of the fields that support a decision.
- Failing to name an accountable owner.
- Copying old recovery targets without checking current capability.
- Storing the completed template where response teams cannot find it.
Related articles and tools
Use this with Business Impact Analysis Guide, Business Continuity Plan Guide, BCM Exercise and Drill Guide, and the BCM tools page.
FAQ
What is the main purpose of RTO/RPO Worksheet?
RTO/RPO Worksheet helps teams make disruption decisions before pressure arrives. It turns assumptions into documented ownership, evidence, recovery priorities, and improvement actions.
Who should own RTO/RPO Worksheet?
How often should RTO/RPO Worksheet be reviewed?
How does AI support RTO/RPO Worksheet?
What evidence makes RTO/RPO Worksheet credible?
Final summary
The best template is not the longest one. It is the one that makes ownership, evidence, assumptions, recovery limits, and next actions clear enough for a team to use during pressure.
End-to-end RTO/RPO worksheet
| Field | What to capture |
|---|---|
| Business service | Outcome/customer served and operating window |
| MTPD/MAO | Point where disruption becomes unacceptable and supporting evidence |
| RTO | Target elapsed time to required service state |
| RPO | Maximum tolerable data rollback expressed as a point in time |
| MBCO | Minimum transactions/capacity/features needed during disruption |
| Current capability | Latest measured end-to-end recovery and recoverable data point |
| Gap | Difference between requirement and proven capability |
| Owner/action | Who resolves or accepts the gap and by when |
Worked example
An order service has an 8-hour MTPD/MAO, 4-hour RTO, 30-minute RPO and MBCO of 50 priority orders per hour. A recent recovery test restored the application in 3h10m, but user authentication and the courier API were not operational until 4h25m. The correct current capability is therefore at least 4h25m for the end-to-end service, creating a 25-minute RTO gap. If replication showed 12 minutes of data loss, the RPO was achieved for that test.
The numbers are illustrative; use actual BIA and test evidence for your organization.