Skip to main content
ISO 22301

How to Define Recovery Time Objectives (RTOs) for Critical Functions: A Step-by-Step Method

Set each critical function's RTO from a business impact analysis: measure impacts over time, fix the MTPD, derive a shorter RTO, check dependencies, approve and test it.

Team ResiPlan9 min
RTO
MTPD
MBCO
RPO
BIA
ISO 22301
DORA
NIS2

Short answer: set the recovery time objective (RTO) of each critical function through a business impact analysis (BIA). Measure how impacts escalate over time, then fix the maximum tolerable period of disruption (MTPD). The RTO is the target time to resume the function at an agreed minimum level, and it must be shorter than the MTPD. Validate it with the business owner and test it: ISO 22301 and EU rules such as DORA and NIS2 expect recovery capabilities to be documented and exercised.

An RTO is a decision, not a measurement. It states how fast you intend to recover, and it drives your recovery strategies and their cost. This guide details the BIA-to-RTO part of a business continuity programme; the full implementation is covered in ISO 22301 in 10 steps.

What is a recovery time objective, and how does it differ from MTPD, RPO and MBCO?

The four terms come from the ISO business continuity vocabulary (ISO 22300) and are used in the BIA requirements of ISO 22301:2019 (clause 8.2.2). In substance:

  • MTPD (maximum tolerable period of disruption): the time it would take for the adverse impacts of not delivering a product or service, or not performing an activity, to become unacceptable.
  • RTO (recovery time objective): the period following an incident within which a product, service or activity is resumed, or resources are recovered. ISO 22301 clause 8.2.2 asks for prioritised time frames for resuming activities at a specified minimum acceptable capacity, set within the MTPD.
  • MBCO (minimum business continuity objective): the minimum level of products or services that is acceptable to the organisation to achieve its business objectives during a disruption.
  • RPO (recovery point objective): the point to which the information used by an activity is restored so that the activity can operate on resumption, in other words the data loss you accept, expressed as time.

The central rule: RTO < MTPD, with a margin for detecting the incident and deciding to activate the plan.

TermQuestion it answersWho sets itRelation to the others
MTPDAfter how long does the impact become unacceptable?Top managementAbsolute ceiling
RTOHow fast must the function be resumed?Business owner and continuity manager, approved by managementMust be shorter than the MTPD
MBCOAt what minimum level must it be resumed?Business ownerReached when the RTO expires
RPOHow much data loss is acceptable?Business owner with ITSet together with the RTO; drives the backup strategy

Sources: ISO 22300 (vocabulary), ISO 22301:2019, ISO/TS 22317:2021. The difference between RTO and RPO is explained in more detail on our RTO and RPO page.

Which functions should be treated as critical?

Start from the scope of the organisation: the products and services it delivers and the obligations it must meet (contractual, legal, regulatory). Then apply the frameworks that bind you:

  • Financial entities under DORA: Article 3(22) of Regulation (EU) 2022/2554 defines a critical or important function as one whose disruption would materially impair the entity's financial performance, or the soundness or continuity of its services and activities, or whose failure would materially impair its continuing compliance with the conditions of its authorisation or its other obligations under financial services law.
  • Essential and important entities under NIS2: Article 21(2)(c) of Directive (EU) 2022/2555 lists business continuity, such as backup management and disaster recovery, and crisis management among the cybersecurity risk-management measures. See also NIS2 essential and important entities.

Map each critical function down to what it runs on: function → processes → applications → suppliers. That map is what Step 4 checks against the RTO.

Step 1: How do you run the business impact analysis?

ISO 22301:2019 clause 8.2.2 sets the requirements; ISO/TS 22317:2021 gives guidelines for carrying out a BIA.

  1. Define impact categories: financial, regulatory, client, safety, reputational.
  2. Build one rating scale shared by every function, and have management validate it, including what "unacceptable" means on each category.
  3. With each function owner, rate the impact at fixed time steps, for example 1 hour, 4 hours, 24 hours, 72 hours and 1 week.

Templates and a full method: business impact analysis guide and BIA template.

Step 2: How do you set the maximum tolerable period of disruption?

Find the first time step at which an impact reaches the "unacceptable" level of your scale, with regard to the organisation's risk appetite. That point is the MTPD.

The MTPD is a management decision, not a technical estimate. Record the reasoning (which impact crosses the line, at which time step) and who validated it, because auditors and supervisors will ask for it.

Step 3: How do you derive the RTO from the MTPD?

Work backwards from the MTPD:

maximum RTO = MTPD − (detection + escalation + activation decision + switchover time)

For example, with hypothetical figures: if the MTPD of a function is 24 hours and you estimate 2 hours to detect, escalate and decide, the RTO must be under 22 hours, and the business may choose a tighter target. The figures to use are your own, taken from your incident history and exercises.

For each RTO, also state:

  • the MBCO: the minimum level of service expected when the RTO expires (for example, which transactions, for which clients);
  • the RPO of the data the function uses, set at the same time, since it conditions the backup strategy.

For financial entities, Article 12(6) of DORA asks them to take into account, when setting recovery time and recovery point objectives for each function, whether it is a critical or important function and the potential overall impact on market efficiency. Article 11(5) requires a business impact analysis of their exposure to severe business disruptions.

Step 4: How do you check dependencies and third parties against the RTO?

  1. List what the function needs: applications, infrastructure, key staff, premises, data and ICT providers.
  2. Compare each dependency's own recovery time with the function's RTO.
  3. Treat every dependency that recovers more slowly as a gap: renegotiate the contract, add a workaround or redundancy, or, if the business accepts it, revise the RTO within the MTPD.

A supplier whose recovery time is longer than the RTO of the function it supports is a gap, not a detail. Under DORA, this ties into ICT third-party risk management (Articles 28 to 30), including the key contractual provisions of Article 30. Our DORA guide and DORA register of information guide cover these obligations.

Step 5: Who approves the RTO and how is it tested?

Approval. The function owner proposes the RTO, the continuity manager challenges it against the MTPD and the dependencies, and top management approves it, in line with the leadership requirements of ISO 22301 (clause 5).

Testing. ISO 22301 clause 8.5 requires a programme of exercises and tests. For financial entities, Article 11(6) of DORA requires ICT business continuity plans and ICT response and recovery plans to be tested at least yearly, and after substantive changes to ICT systems supporting critical or important functions. Commission Delegated Regulation (EU) 2024/1774 details the content of the ICT business continuity policy and its testing.

Record the gap between the target RTO and the recovery time observed in each exercise, and turn each gap into a corrective action. Exercise ideas: 10 crisis exercise scenarios.

Common mistakes when defining RTOs

  • RTO set by IT alone, from what the systems can do today, without the business.
  • The same RTO for every function.
  • An RTO longer than the MTPD, or with no margin for detection and decision.
  • External dependencies forgotten: ICT providers, shared services, key people.
  • No review after a major change in activities, systems or suppliers.
  • An RTO that has never been tested.

How often should RTOs be reviewed?

ISO 22301 requires the BIA and risk assessment to be reviewed at planned intervals and when significant changes occur (clause 8.2), and the management system to be reviewed by top management (clause 9.3). For financial entities, Article 6(5) of DORA requires the ICT risk management framework to be documented and reviewed at least once a year (periodically for microenterprises), and after major ICT-related incidents.

A practical rule: review RTOs at least once a year with the BIA, and whenever an event triggers it (new activity, new system, change of supplier, major incident or failed exercise).

In ResiPlan, the BIA module records the RTO and RPO of each activity, a process whose RTO is shorter than what an upstream dependency can deliver is flagged, and exercise results are compared with the BIA targets. Try it with the RTO/RPO calculator or see pricing.

Frequently asked questions

What is the difference between RTO and MTPD?

The MTPD is the time after which the impact of a disruption becomes unacceptable; it is a ceiling set by management. The RTO is the target time to resume the function at its minimum acceptable level, and it must be shorter than the MTPD, with a margin for detection and decision.

Who should approve recovery time objectives?

The function owner proposes the RTO, the continuity manager checks it against the MTPD and the dependencies, and top management approves it. An RTO set by IT alone does not reflect the business need.

Can an RTO be longer than the recovery time offered by an ICT provider?

Yes, that is the safe direction: the provider recovers before the function needs it. The reverse is the problem: if the provider's recovery time is longer than the function's RTO, the RTO cannot be met as it stands, and the gap must be treated through the contract, a workaround or redundancy.

Does DORA require financial entities to set recovery time objectives?

Article 12(6) of Regulation (EU) 2022/2554 refers to the recovery time and recovery point objectives that financial entities determine for each function, taking into account whether it is critical or important. Article 11 requires a business impact analysis and yearly testing of ICT business continuity plans. Entities under the simplified ICT risk management framework of Article 16 follow different rules.

How often should recovery time objectives be reviewed?

At least once a year with the BIA, and after any significant change or major incident. ISO 22301 requires reviews at planned intervals and on significant change; DORA requires a yearly review of the ICT risk management framework.

Sources

  • ISO 22301:2019, Security and resilience — Business continuity management systems — Requirements, clauses 5, 8.2, 8.5 and 9.3 (iso.org).
  • ISO/TS 22317:2021, Security and resilience — Business continuity management systems — Guidelines for business impact analysis, iso.org.
  • ISO 22300, Security and resilience — Vocabulary, iso.org.
  • Regulation (EU) 2022/2554 (DORA), Articles 3(22), 6(5), 11, 12, 16 and 28 to 30, EUR-Lex.
  • Commission Delegated Regulation (EU) 2024/1774 (RTS on the ICT risk management framework), EUR-Lex.
  • Directive (EU) 2022/2555 (NIS2), Article 21(2)(c), EUR-Lex.
Found this useful?
Share it with your team.

Try ResiPlan for free

14-day trial, no credit card. Import your risks and plans in minutes.

BCMS

BIA Guide 2026: The Complete Business Impact Analysis Playbook

The complete BIA methodology for ISO 22301, DORA and NIS2: 7-step process, a worked example with real numbers, the columns of a BIA register, the regulatory cross-walk and a 30-day implementation plan.

ISO 22301

ISO 22301 in 10 Steps: Implementing a Compliant BCMS

Practical 10-step method to deploy a business continuity management system compliant with ISO 22301, from context to continuous improvement.

BCMS

RTO vs RPO 2026: Matrix + Sector Benchmarks + NFR Calibration

Recovery Time Objective vs Recovery Point Objective explained: definitions, differences, criticality matrix, 2026 sector benchmarks (banking/health/industry), NFR template. Calibrate without guesswork.