A defined level of disruption that a firm can tolerate for an important business service under the relevant resilience framework.
Why the distinction matters
The rationale should relate to harm, not simply reuse a technical recovery target. Record assumptions, service boundaries and the measures used to test performance against the tolerance.
In the working file
Illustrative example
A restored application still has a payment backlog. The test considers the service outcome rather than stopping the clock at server recovery.
Use the term in context
Record the legal entity, activity, period and applicable source alongside the term. A familiar label does not remove the need to establish scope. Our operating playbook connects this definition to a practical process.
Read the related playbookSources & scope
Primary sources used for this research edition. Document dates and commencement dates are different fields. Recheck the issuing authority before acting.
- FCA: Operational resilienceGuidance · source reviewed 12 November 2026