How stable is territory coverage when one SDR is out?

Question and scope

This brief asks what happens to a territory when one owner is unavailable for a defined period. It looks at queue ownership, handoff time, and accounts with no named backup.

It does not measure revenue impact or individual performance. The purpose is to make coverage visible before an absence becomes a customer-facing delay.

Unit and ownership record

The unit is one account with an active queue item. Record the primary owner, the backup owner, the handoff time, and the period when neither owner had acted.

A backup named in a document but never enabled in the system is not coverage. Check the system assignment, not only the roster.

Definitions

Define unowned time as the interval after the primary owner becomes unavailable and before a backup opens or acknowledges the item. Pauses requested by the account are separate and should be recorded as pauses.

Decide whether a reassignment that happens after the first customer message counts as late. The definition should be written before the sample so the answer is not chosen after seeing the cases.

Sampling and collection

Sample absences rather than accounts where possible, then sample queue items within each absence. Include planned leave, unplanned absence, and a partial-day gap.

Record the source of the absence dates, the system assignment log, and the queue export time. If the roster and the system disagree, keep both and report the disagreement.

Limits and reporting

A small number of absences makes the result unstable, so report the count and the range rather than a precise average. One long absence can dominate a short window.

The cited public sources frame work-time and control practice; they do not provide a coverage benchmark. Report the observed pattern and the cases that created the largest unowned period.

Sources

1. U.S. Department of Labor, work hours
2. CISA, cybersecurity best practices
3. NIST Cybersecurity Framework

Apply the operating question

Use the finding to define one source, output, review owner, and exception path inside a real workflow.