Strategic
Appetite Breach Escalation Time
Measuring escalation time from breach detection to board notification.
Measuring whether breaches reach the board fast enough
An appetite breach is only useful as a control if it reaches the governing body quickly enough to act, and a policy that sets an escalation SLA must be measured against actual practice. Slow escalation means the board learns of a breach after the damage is done, undermining its King IV oversight role. AuditPro Core measures escalation time from breach detection to board notification against the policy SLA, exposing where the escalation chain is too slow.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Breaches escalated
18
Within SLA
11
61%
Breached SLA
7
slow escalation
Avg escalation days
9
SLA is 5
Average escalation days by quarter
Escalation against SLA
| Category | Breaches | Avg days | SLA met |
|---|---|---|---|
| Financial | 6 | 7 | Yes |
| Operational | 5 | 11 | No |
| Technology | 3 | 13 | No |
| Compliance | 2 | 5 | Yes |
| Strategic | 2 | 8 | No |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Escalation as a control
Detecting an appetite breach achieves nothing if the information stalls before reaching decision-makers. The escalation pathway is itself a control whose performance can be measured.
Detection-to-notification clock
The meaningful measure runs from the moment a breach is detected to the moment the board is formally notified. Measuring this end to end exposes delays buried in the middle of the chain.
SLA conformance
A breach-escalation policy that sets a time limit is only credible if conformance is tracked. Persistent SLA misses indicate the escalation process needs fixing, not just the underlying risks.
Bottleneck identification
Delays usually concentrate at a particular handoff, such as awaiting a committee sitting. Pinpointing the bottleneck lets the process be redesigned rather than blamed on individuals.
How AuditPro Core Bridges the Gap
- Escalation timestamping: detection and notification times are captured so elapsed escalation time is measured, not estimated.
- SLA tracking: elapsed time is compared against the policy SLA, flagging breaches that escalated too slowly.
- Bottleneck analysis: time-in-stage reveals where the escalation chain stalls for targeted fixing.
- Audit-ready export: escalation timeliness exports as evidence of an effective oversight process.
Key Takeaways
- Detection is worthless if escalation is too slow to allow action.
- Measure the full clock from detection to board notification.
- Track SLA conformance, not just whether breaches were escalated.
- Locate the bottleneck handoff to fix the process, not the people.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.