Coverage Floor Breach Rate

Definition

Coverage Floor Breach Rate measures how often monitored intervals fall below defined minimum staffing floors.

Formula:

Coverage Floor Breach Rate = (intervals below floor / total monitored intervals) x 100

Why this KPI matters

This is your early-warning metric.

A rising breach rate usually appears before queue-age SLA misses and before escalation volume increases. It helps teams act before customer impact spreads.

How to calculate it in 5 minutes

1. Define coverage floors by role and hour window.
2. Pull monitored intervals (for example, every 15 minutes).
3. Count intervals where any critical role is below floor.
4. Divide by total monitored intervals and multiply by 100.

Example:

• 72 monitored intervals
• 11 intervals below floor
• Breach Rate = (11 / 72) x 100 = 15.3%

Suggested operating bands

• 0-3%: Strong coverage reliability.
• 4-7%: Manageable risk; one repeated window likely exposed.
• 8-12%: Material risk; existing controls are not holding.
• >12%: High instability; immediate operating-rule correction required.

Segment cuts that matter

Break breach rate by:

• Role group (front desk, triage, specialist, support)
• Time window (opening, handover, lunch overlap)
• Trigger type (absence, delay, break overlap, demand spike)
• Site or service stream

If one role drives most breaches, prioritize cross-training and ownership for that role before broad staffing changes.

Instrumentation notes

Track:

• Coverage floor target by role/window
• Actual staffed count by role/window
• Breach start and end timestamp
• Named owner at breach detection
• First correction action

Common logging failures:

• Undefined floor targets for specific windows
• Counting planned staffing instead of actual live staffing
• Missing owner field at breach time

What to do when breach rate rises

1. Find the top two repeat breach windows.
2. Assign explicit owners for those windows.
3. Add one pre-committed rebalance move for each dominant trigger.
4. Tighten live checks in those windows to 15-minute cadence.
5. Review handover and break policies contributing to breach clusters.

Weekly review questions

• Which role contributed most breach intervals this week?
• Which window repeats despite previous corrections?
• Did breaches recover quickly or remain unresolved across cycles?
• What one rule change will reduce breaches by at least 3 points next week?

Related guides

• Coverage Handover Workflow
• Same-Day Absence Response Workflow
• Coverage Stability Score
• Queue Age SLA Hit Rate
• Time to Coverage Recovery (MTTR-C)

Where Soon helps

Soon highlights floor breaches in real time by role and window so teams can act quickly, document ownership, and reduce repeated exposure.