. .

Setting Impact Tolerances: A Practical Guide for Operational Resilience Implementation
OR BB P2S3_ITO_06

[OR] [P2] [S3] [ITo] [C6] Methodology for Setting Impact Tolerance

New call-to-action

Setting impact tolerance is one of the most important implementation activities in operational resilience.

It translates the organisation’s resilience ambition into measurable thresholds that define how much disruption to a Critical Business Service (CBS) can be tolerated before customer harm, regulatory breach, financial loss, reputational damage, or systemic impact becomes unacceptable.

Unlike traditional recovery metrics, impact tolerance is not set only by technology teams, business continuity teams, or operational risk teams. It requires a service-wide view that includes business owners, process owners, technology teams, cyber teams, third-party managers, compliance, risk, and senior management.

This chapter provides a practical step-by-step methodology for setting impact tolerances in a structured, repeatable, and evidence-based manner.

New call-to-action

Moh Heng Goh
Operational Resilience Certified Planner-Specialist-Expert

Impact Tolerance

[P2] [S3] Chapter 6

New call-to-action

Methodology for Setting Impact Tolerance

Introduction

[OR] [P2] [S3] [ITo] [C6] Methodology for Setting Impact Tolerance

0205 Supervisory Scrutiny on Tolerance LimitsSetting impact tolerance is one of the most important implementation activities in operational resilience.

It translates the organisation’s resilience ambition into measurable thresholds that define how much disruption to a Critical Business Service (CBS) can be tolerated before customer harm, regulatory breach, financial loss, reputational damage, or systemic impact becomes unacceptable.

Unlike traditional recovery metrics, impact tolerance is not set only by technology teams, business continuity teams, or operational risk teams. It requires a service-wide view that includes business owners, process owners, technology teams, cyber teams, third-party managers, compliance, risk, and senior management.

This chapter provides a practical step-by-step methodology for setting impact tolerances in a structured, repeatable, and evidence-based manner.

Purpose of the Chapter

The purpose of this chapter is to provide a practical methodology that enables organisations to:

  • Identify the relevant CBS and Sub-CBS for tolerance setting
  • Understand dependencies and resources supporting service delivery
  • Define the impact dimensions that matter most
  • Assess how the disruption severity increases over time
  • Establish maximum tolerable thresholds
  • Validate and approve tolerances through governance
  • Refine tolerances iteratively as the organisation matures

Step 1: Identify CBS and Sub-CBS

The starting point for setting impact tolerance is the identification of Critical Business Services and their supporting Sub-CBS.

A CBS represents an end-to-end service that delivers value to customers, markets, regulators, or other key stakeholders. A Sub-CBS breaks the service into more specific service components that can be assessed and measured.

For example, a bank may define:

CBS Code

Critical Business Service

Sub-CBS Examples

CBS-1

Deposit and Account Services

Account opening, deposit transactions, withdrawal processing, and account servicing

CBS-2

Payments and Funds Transfer Services

Payment initiation, authentication, clearing, settlement, notification

CBS-3

Lending and Credit Services

Loan approval, disbursement, repayment processing, and collateral monitoring

Impact tolerance should be set at the level where disruption can be meaningfully measured. In many cases, this means setting tolerances at both the CBS and Sub-CBS levels.

Step 2: Map Dependencies and Resources

Once the CBS and Sub-CBS have been identified, the organisation must map the dependencies and resources required to deliver each service.

This step links directly to OR-P2-S2: Map Processes and Resources, where organisations identify the people, processes, technology, third parties, facilities, data, and interconnections that support critical service delivery.

A practical mapping table may include:

Sub-CBS Code

Sub-CBS

Processes

People

Technology

Third Parties

Upstream / Downstream Dependencies

1.1

Customer Onboarding

Application capture, screening, approval

Branch staff, onboarding team, compliance

CRM, core banking, eKYC platform

eKYC provider, credit bureau

KYC, account approval, digital access

1.6

Deposit Transactions

Deposit capture, validation, posting

Operations, branch, digital banking team

Core banking, ATM switch, mobile app

ATM network, payment gateway

Account balance, reporting, and reconciliation

2.7

Clearing and Settlement

Clearing file submission, settlement posting

Payments operations, treasury

Payment switch, RTGS interface

Clearing house, correspondent bank

Liquidity, reconciliation, customer notification

Dependency mapping is essential because impact tolerance cannot be set realistically without understanding what enables the CBS to operate.

Step 3: Identify Impact Dimensions

The next step is to define the dimensions of impact that will be assessed during disruption.

Common impact dimensions include:

Impact Dimension

Description

Customer Impact

Harm to customers, inability to access funds, delayed transactions, and service frustration

Regulatory Impact

Breach of laws, regulations, reporting obligations, supervisory expectations

Financial Impact

Direct loss, compensation, penalties, lost revenue, liquidity impact

Reputational Impact

Loss of public confidence, media exposure, and social media escalation

Operational Impact

Backlog, manual workaround limits, staffing strain, and control failure

Systemic Impact

Impact on market stability, payment systems, counterparties, or wider ecosystem

Data Impact

Loss, corruption, delay, or unavailability of critical data

These dimensions should be tailored to the organisation’s business model, sector, jurisdiction, and customer base.

For financial institutions, customer harm and systemic impact are especially important because regulators expect impact tolerances to reflect more than internal recovery capability.

Step 4: Define Disruption Scenarios

Impact tolerance must be assessed against realistic and challenging disruption scenarios.

These scenarios should be severe but plausible, meaning they are demanding enough to test the resilience of the service but still credible given the organisation’s operating environment.

Examples include:

Scenario Type

Example

Technology Failure

Core banking outage affecting deposit and withdrawal services

Cyber Incident

Ransomware attack disrupting digital payments

Third-Party Failure

Cloud service provider outage affecting online banking

People Unavailability

High absenteeism among payments operations staff

Facility Denial

The main operations centre is inaccessible due to a fire or a security incident

Data Integrity Issue

Incorrect account balances are displayed to customers

Market-Wide Disruption

Payment network outage affecting multiple banks

The purpose of defining scenarios is not to set different tolerances for every possible incident. Instead, scenarios help the organisation understand how quickly harm escalates and whether existing capabilities can keep disruption within acceptable limits.

Step 5: Assess Impact Severity Over Time

Impact tolerance is time-sensitive. A disruption that is tolerable for 30 minutes may become unacceptable after four hours or one business day.

Organisations should assess how the impact severity changes over time.

A typical assessment may use time bands such as:

Time Band

Assessment Focus

0–30 minutes

Initial disruption, service alerts, and early customer inconvenience

30 minutes–2 hours

Increased customer calls, transaction delays, and operational backlog

2–4 hours

Material customer harm, regulatory concern, media attention

4–8 hours

Significant service disruption, possible breach of tolerance

8–24 hours

Severe customer, financial, operational, or systemic impact

More than 24 hours

Potential crisis, prolonged service failure, major regulatory escalation

For each time band, the organisation should assess impact across the agreed dimensions. This helps identify the point at which disruption becomes unacceptable.

Step 6: Determine Maximum Tolerable Thresholds

The maximum tolerable threshold defines the point beyond which the disruption is no longer acceptable.

Impact tolerances may be expressed using one or more measurable criteria, such as:

Tolerance Type

Example

Time-Based Threshold

CBS must not be unavailable for more than 4 hours

Volume-Based Threshold

No more than 5,000 failed transactions

Value-Based Threshold

No more than SGD 10 million in delayed payments

Customer-Based Threshold

No more than 10% of active customers affected

Service-Level Threshold

At least 80% of normal transaction capacity is maintained

Data-Loss Threshold

No more than 15 minutes of data loss

Backlog Threshold

Manual backlog must be cleared within one business day

A strong impact tolerance statement combines measurable thresholds with service context.

Example:

“Payments and Funds Transfer Services must be restored or maintained to a minimum of 80% processing capacity within four hours, with no more than 5,000 delayed customer transactions and no breach of regulatory reporting obligations.”

This statement is more useful than a simple recovery time because it reflects customer impact, operational capacity, and regulatory consequences.

Step 7: Validate with Stakeholders

Impact tolerances must be validated with stakeholders who understand the service, its dependencies, and its consequences.

Key stakeholders include:

Stakeholder

Validation Role

Business Service Owner

Confirms service criticality and customer impact

Operations Owner

Confirms practical delivery and manual workaround limits

Technology Owner

Confirms system recovery capability and infrastructure constraints

Risk Management

Reviews risk appetite and tolerance alignment

Compliance / Legal

Reviews regulatory and legal implications

Third-Party Risk Owner

Confirms vendor dependencies and contractual constraints

Finance

Reviews financial loss and liquidity implications

Crisis Management / BCM

Confirms escalation, recovery, and continuity arrangements

Senior Management

Challenges assumptions and confirms acceptability

Validation should test whether the tolerance is:

  • Realistic
  • Measurable
  • Defensible
  • Aligned to risk appetite
  • Supported by current capability
  • Acceptable from a customer and regulatory perspective

Step 8: Obtain Governance Approval

Once validated, impact tolerances should be submitted for governance approval.

This ensures that tolerances are formally recognised, owned, and embedded into the organisation’s resilience framework.

Approval should include:

Governance Element

Requirement

Service Ownership

Named the accountable owner for each CBS

Tolerance Approval

Senior management or Board-level approval, where appropriate

Evidence Base

BIA, dependency mapping, scenario analysis, risk assessment

Remediation Actions

Actions required where the current capability falls short

Review Cycle

Defined frequency for review and update

Escalation Trigger

Process for escalation when tolerance is breached or likely to be breached

Governance approval turns impact tolerance from an analytical output into an organisational commitment.

Integration with BCM Institute’s Plan → Implement Lifecycle

The methodology for setting impact tolerance should be integrated into BCM Institute’s broader operational resilience lifecycle.

BCM Institute Lifecycle Stage

Relevance to Impact Tolerance

Plan

Establish governance, confirm risk appetite, and define methodology

Implement

Identify CBS, map dependencies, and set impact tolerances

Test

Validate tolerances through severe but plausible scenarios

Improve

Address gaps, refine tolerances, update capabilities

Within the operational resilience implementation phase, setting impact tolerance sits after CBS identification and dependency mapping, and before scenario testing.

This sequence is important:

  1. Identify what is critical
  2. Map what supports it
  3. Define how much disruption is tolerable
  4. Test whether the organisation can remain within tolerance
  5. Improve where gaps are identified

Iterative Refinement Approach

Impact tolerance setting should not be treated as a one-time exercise. It must be refined as the organisation’s services, systems, risks, customers, and regulatory expectations evolve.

Tolerances should be reviewed when there are:

  • New or changed CBS
  • Major technology changes
  • New third-party arrangements
  • Regulatory changes
  • Lessons from incidents or exercises
  • Significant changes in transaction volumes or customer expectations
  • Mergers, acquisitions, outsourcing, or cloud migration

A mature organisation improves its tolerance over time by using:

Input

How It Refines Tolerance

Scenario Testing Results

Confirms whether tolerances are achievable

Incident Data

Shows actual disruption patterns and weaknesses

Customer Complaints

Highlights harm thresholds and service pain points

Regulatory Feedback

Clarifies supervisory expectations

Audit Findings

Identifies documentation or control gaps

Technology Metrics

Improves understanding of recovery and capacity limits

Third-Party Performance

Tests dependency reliability and contractual resilience

Practical Output: Impact Tolerance Methodology Summary

Step

Activity

Key Output

1

Identify CBS and Sub-CBS

CBS register

2

Map dependencies and resources

Dependency and resource map

3

Identify impact dimensions

Impact assessment criteria

4

Define disruption scenarios

Severe but plausible scenario set

5

Assess impact severity over time

Time-based impact profile

6

Determine maximum tolerable thresholds

Draft impact tolerance statement

7

Validate with stakeholders

Stakeholder-reviewed tolerance

8

Obtain governance approval

Approved impact tolerance register

Banner [Summing] [OR] [E3] Establish Impact Tolerance

A structured methodology is essential for setting meaningful impact tolerances. Without a disciplined approach, tolerances may become arbitrary, unrealistic, or disconnected from actual service delivery capability.

The methodology outlined in this chapter begins with Critical Business Services, moves through dependency mapping and impact assessment, and concludes with validated and approved tolerance statements. It ensures that impact tolerances are not merely compliance artefacts but practical thresholds that guide resilience investment, scenario testing, incident response, and management decision-making.

Ultimately, impact tolerance setting is an iterative capability. As the organisation’s risk environment changes, its tolerances must be reviewed, challenged, and refined to ensure that critical services remain resilient under severe but plausible disruption.

New call-to-action

C1 C2 C3 C4 C5 C6
[OR] [P2] [S3] [ITo] [C1] Introduction to Impact Tolerance [OR] [P2] [S3] [ITo] [C2] Regulatory and Standards Landscape [OR] [P2] [S3] [ITo] [C3] Understanding Impact Tolerance in Context [OR] [P2] [S3] [ITo] [C4] Linking Impact Tolerance to Critical Business Services (CBS) [OR] [P2] [S3] [ITo] [C5] Key Components of Impact Tolerance [OR] [P2] [S3] [ITo] [C6] Methodology for Setting Impact Tolerance
C7 C8 C9 C10 C11 C12 
[OR] [P2] [S3] [ITo] [C7] Impact Tolerance Assessment Framework [OR] [P2] [S3] [ITo] [C8] Scenario-Based Calibration of Impact Tolerance [OR] [P2] [S3] [ITo] [C9] Role of Dependency Mapping in Impact Tolerance [OR] [P2] [S3] [ITo] [C10] Governance, Ownership, and Accountability [OR] [P2] [S3] [ITo] [C11] Integration with Operational Resilience Framework [OR] [P2] [S3] [ITo] [C12] Testing and Validation of Impact Tolerances
C13 C14 C15 C16 C17 C18
[OR] [P2] [S3] [ITo] [C13] Monitoring, Metrics, and Continuous Improvement [OR] [P2] [S3] [ITo] [C14] Common Challenges and Pitfalls [OR] [P2] [S3] [ITo] [C15] Practical Case Study (Banking Sector Example) [OR] [P2] [S3] [ITo] [C16] Future Trends in Impact Tolerance [OR] [P2] [S3] [ITo] [C17] Key Takeaways and Call to Action [OR] [P2] [S3] [ITo] [C18] Back Cover

 

More Information About OR-5000 [OR-5] or OR-300 [OR-3]

To learn more about the course and schedule, click the buttons below for the OR-300 Operational Resilience Implementer course and the OR-5000 Operational Resilience Expert Implementer course.

BL-OR-3 Register Now BL-OR-3_Tell Me More BL-OR-3_View Schedule
BL-OR-5_Register Now BL-OR-5_Tell Me More  [BL-OR] [3-4-5] View Schedule
[BL-OR] [3] FAQ OR-300

If you have any questions, click to contact us.Email to Sales Team [BCM Institute]

FAQ BL-OR-5 OR-5000
OR Implementer Landing Page

New call-to-action

New call-to-action

 

Comments:

 

CTA Banner_OR

CTA Banner_ORA

CTA Banner_BCM

CTA Banner_ITDR

CTA Banner_CM