Service level · Tower to function
Hire-to-Retire escalation response
Hire-to-Retire Tower
Committed level
60 min
response-time at or below target · per escalation, business hours
Attainment
95.9%
worst period 93.5%
Consequence of a miss
No consequence
Reported and discussed. Nothing changes hands.
Breaches
2
2 with remediation still open
Credit
$0
$0 of it actually paid
The commitment
Who owes what to whom
TypeOperational level
Owed byAI GBS — Hire-to-Retire Tower
Owed toHuman Resources
Measurement windowPer escalation, business hours
Effective fromJan 20, 2026
Next reviewOct 1, 2026
Signature
Named and dated
Signed byPriya Raman
RoleChief People Officer
Signed onJan 16, 2026
A signature makes this level a commitment somebody can be held to. Without one it is a target that reads like a commitment.
How it is measured
From the work ledger
Escalation opened to first human action, taken from the escalation ledger.
no source system named
What a miss costs
No consequence
No clause. Response time is tracked and reported but carries no consequence.
None.
There is no credit, no fee at risk and no other consequence attached to this level. A miss produces a report and a conversation. That is stated plainly here because a service level with no consequence behaves like a target, and calling it a commitment does not change how it behaves under pressure.
Attainment by period
6 measured periods · floor at 95%
2025 Q4
94.6%
62.7 mins · target missed
2026 Q1
96.0%
60.0 mins · target met
2026 Q2
97.6%
56.9 mins · target met
Jun 2026
93.5%
64.8 mins · target missed
Jul 2026
98.5%
55.2 mins · target met
Aug 2026
95.1%
61.7 mins · target missed
The bar scale starts at 85% rather than zero, because every value on a service level sits in the last few points and a zero-based axis would flatten the only part of the range anyone argues about. The floor line is attainment below 95%, which is what opens a breach.
Breach history
2 recorded misses
BRC-0011Jun 2026 · occurred Jun 5, 2026 · detected 2 months ago
measured 64.8 against 60.0
missed by 8.0%
1,609 units affected
open 18.0 hrs
Agent throughput was inside plan. The approval queue was not: two of the four named approvers were unavailable in the same week and no delegate had been nominated.
contributing: Detection lag of 2 hours before anyone was paged · Measured from the work unit ledger
Human reviewers unavailableNo clause to invokeRemediation open
Ravi Menon, Finance Business Partner, Commercial · remediation due Jul 20, 2026 · still open
Roster a named releaser for the intake quarantine queue across weekends during peak periods.
BRC-00102025 Q4 · occurred Dec 29, 2025 · detected 8 months ago
measured 62.7 against 60.0
missed by 4.5%
2,157 units affected
open 20.3 hrs
Intake quarantine held 340 items over the weekend because the release decision needs a named human and none was rostered.
contributing: Detection lag of 20 hours before anyone was paged · Measured from the work unit ledger
Intake data qualityNo clause to invokeRemediation open
Marcus Weill, VP Total Rewards · remediation due Feb 12, 2026 · still open
Roster a named releaser for the intake quarantine queue across weekends during peak periods.
What this record is, and what it is not
Drill results are measured against a modeled estate on a rehearsal calendar of our own making. Recovery times here are real measurements of a simulation, not evidence that a customer's production estate recovers in the same time.
Attainment, breach detail and credit on this record are modeled. The structure — a named counterparty, a measurement basis that can be checked, a signature, a review date, a consequence, and a breach ledger that records the cause rather than the excuse — is the part intended to survive contact with a real estate.