SLA Monitor
Every service level in the rate contract, how it has actually performed, and the penalty that follows from the schedule. Penalties are computed rather than negotiated — the point of writing them into the contract was to remove the negotiation.
₹9,91,020 in penalties across 7 breaches this quarter
The largest single contributor is Data Discovery & Classification — Dashboard refresh — meeting its target only 67% of the time. A service level that is missed this consistently is either wrongly set or wrongly resourced, and the answer determines whether the fix is contractual or operational.
Service levels
18
Measurements
60
Last three periods
Compliance
88%
Breaches
7
Penalty exposure
₹9,91,020
Breaches by service line
Breach counts concentrated in one service line usually indicate a delivery capacity problem rather than 24 independent failures.
Service level definitions
Targets and penalties as written into the rate contract. Editable here because a schedule that cannot be revised in the tool ends up being revised in a spreadsheet nobody can find.
Breaches this quarter
Each one is attributable to a specific entity and period, which is what makes a set-off defensible.
SL-07Revenue & Disaster…Incident acknowledgement · 2026-06 · target 1 hour, 24x7, actual 4 hours3 over₹75,000
SL-07Real Estate Regulatory…Board initial notification filed · 2026-08 · target 72 hours of discovery, actual 80 hours8 over₹8,00,000
SL-05Women & Child Development…Integration with Discovery and identity mapping · 2026-07 · target 7 days from kick-off, actual 10 days3 over₹15,000
SL-03Warehousing CorporationPlatform uptime · 2026-06 · target 99.5% per month, actual 101.5 percent2 over₹20
SL-07Citizen Services & Public…Post-Incident Review report · 2026-06 · target 30 days post-incident, actual 35 days5 over₹25,000
SL-02Citizen Services & Public…Data Principal request managed · 2026-08 · target 30 days, actual 37 days7 over₹70,000