The Maximum Tolerable Period of Disruption is the ISO 22301 name for the time after which the impact of a disruption becomes unacceptable. The term exists so that a certified continuity management system works with one agreed boundary under one definition. For executives, the MTPD answers a single question: how long can this process stay down before the damage crosses the line the business cannot accept. Everything else in the recovery strategy is sized against that answer.
In practice the MTPD is set exactly as an MAO is: BIA workshops trace impact over time, the process owner proposes the value, management approves it, and it is documented in the BIA. A hospital laboratory may set an MTPD of 4 hours because beyond that patient care degrades unacceptably, so the RTO is set at 2 hours. Since MTPD and MAO name the same limit in different frameworks, an organisation should pick one term, define it in the programme glossary and use it consistently. Recovery targets must always sit inside the MTPD with margin.
A recurring error is running MTPD and MAO as two different numbers for the same process because two documents followed two frameworks — plans and audits then chase conflicting targets. The fix is terminological discipline, not more analysis. ERGP module M3, Impact analysis and the economics of recovery, shows how to keep the metric set consistent.
The MTPD comes out of the impact curve, not out of a preference. In a BIA workshop the process owner walks the impact of downtime hour by hour and day by day across five dimensions: money lost, obligations breached, regulatory exposure, safety, and reputation. The MTPD is the point where any one dimension crosses from painful to unacceptable — the contract terminates, the licence condition is breached, the patient is at risk. Because «unacceptable» is a judgement about the business, the number is proposed by the owner and approved by management; technology has no vote at this step. Only afterwards are the RTO and the recovery arrangements sized to fit inside it.
| Activity | Typical MTPD | What usually sets the line |
|---|---|---|
| Payments and treasury | Hours | Settlement windows, central bank rules |
| Hospital and clinical services | 2–6 hours | Patient safety |
| Production and logistics | 1–3 days | Contract penalties, perishables, restart cost |
| Payroll | Days, until the pay date | Staff trust and labour law |
| Regulatory reporting | Until the deadline | The calendar, not the technology |
The MTPD is the ceiling of the whole metric set. The RTO must sit below it with a visible safety margin — an RTO equal to the MTPD is a plan to arrive exactly at the moment the damage becomes unacceptable. The MBCO defines what minimum level of service must be running again inside that window, and the RPO caps the data loss. The four are compared side by side, with a worked example, in MBCO vs MTPD vs RTO vs RPO.
None in substance. MTPD is the ISO 22301 term, MAO (maximum acceptable outage) is used by other frameworks for the same boundary. Pick one term for your programme, define it in the glossary and use it consistently.
No. The MTPD is the ceiling — the time beyond which damage is unacceptable. The RTO is the target the organisation commits to, and it must sit below the MTPD with a margin.
The process owner proposes it from the impact analysis and executive management approves it, because deciding what level of damage is «unacceptable» is a business judgement, not a technical one.
This term is part of the working language of ERGP — the first resilience governance certification fully available in Arabic, also in English. 94 chapters, six modules, a verifiable certificate.
Explore the ERGP programme