Coverage Stability Score

Definition

Coverage Stability Score = (time blocks meeting required coverage / total monitored blocks) x 100.

How to calculate it in 5 minutes

1. Pick your monitoring interval (usually 15 minutes).
2. Count total monitored blocks for the day.
3. Count blocks where each critical role met minimum coverage floor.
4. Divide covered blocks by total blocks and multiply by 100.

Example:

• 48 monitored blocks in a day
• 41 blocks at or above coverage floor
• Score = (41 / 48) x 100 = 85.4

Suggested operating bands

• 95-100: Stable. Keep monitoring and preserve current controls.
• 90-94: Watch zone. Inspect one high-risk window before next shift.
• 85-89: At risk. Run one same-day rebalance cycle now.
• <85: Unstable. Trigger escalation and protect critical streams first.

Diagnostic cuts that matter

Break the score by:

• Hour window (opening, lunch overlap, shift change)
• Role group (desk, triage, specialist, back office)
• Site or queue stream

If only one band is weak, fix the local operating rule before adding capacity.

What to do when the score drops

1. Identify the first time block where floor breaks.
2. Confirm owner visibility for that block.
3. Reassign one cross-trained role before deferring work.
4. Re-check queue-age trend 15 minutes later.
5. Log the trigger and response for next-day planning.

Weekly review questions

• Which 3 windows caused most score loss this week?
• Did we miss floor planning or fail live enforcement?
• Which rebalance move recovered fastest with least disruption?
• What one rule change should we carry into next week?

Metric pairings

Use Coverage Stability Score with:

• Coverage Floor Breach Rate to see early warning frequency.
• Queue Age SLA Hit Rate to confirm customer-facing impact.

Read together:

• Stability up + SLA down -> coverage may look stable but demand matching is weak.
• Stability up + breach rate flat -> local risk pockets still exist.

Anti-gaming checks

• Do not improve score by lowering coverage floors without service evidence.
• Do not hide weak windows by averaging only day-level totals.
• Do not mark windows as stable if ownership is unclear during active load.

Related guides

• Intraday Control Loop
• Same-Day Absence Response Playbook
• Real-Time Queue Rebalance Workflow

Where Soon helps

Soon makes coverage-floor breaks visible by role and time block so teams can recover score before service impact spreads.