Skip to content
Glossary

SLA Breach

An SLA breach occurs when work misses a commitment defined in a service-level agreement, such as a response or resolution deadline. Detecting and escalating breaches automatically keeps accountability visible and ensures at-risk work reaches the right people before commitments are missed.

Synonyms: service level breach, SLA violation, missed SLA, deadline breach

An SLA breach is the operational signal that a commitment is slipping. Because each WorkItem tracks its own timers, the system can warn as a deadline nears and record a breach the moment it is crossed, rather than discovering it in a retrospective report. Proactive escalation — reprioritizing queues, notifying owners, or routing to an approver — converts breach risk into timely action. Capturing breaches and their causes also feeds analytics, helping teams see where time is lost and which workflows need more capacity or automation.

Frequently asked questions

How are SLA breaches detected automatically?
Each WorkItem carries its commitment timers, and the system watches elapsed time against thresholds, raising escalations as a deadline approaches and recording the breach if it is missed.
What happens when a breach is imminent?
Policy can escalate the WorkItem, notify owners, or reprioritize the queue so attention shifts to at-risk work before the commitment is actually missed.