WFM guideSchedule quality

Contact centre schedule effectiveness

Q: What is the difference between schedule adherence and schedule effectiveness?

Schedule adherence measures whether agents are doing what the schedule says they should be doing at each moment: are they on a call when scheduled to be on a call, on break when scheduled for a break, in a meeting when scheduled for a meeting? A high adherence rate (e.g. 90%+) means agents are following the schedule reliably. Schedule effectiveness measures a different question: if agents followed the schedule perfectly, would the resulting staffing position meet the SL target at the forecast volume? A schedule can have 95% adherence and still fail to meet SL if: (1) the staffing requirement was calculated from an incorrect forecast — the schedule was built for 400 contacts per hour but 520 arrived; (2) the shift start times were wrong — enough agents are scheduled for the day, but they all start at 08:00 when the morning peak is 07:00–08:00; (3) the shrinkage allowance was insufficient — the schedule assumed 20% shrinkage but actual shrinkage is 28%, so on-phone agents are fewer than planned despite high adherence to the off-phone schedule; (4) the interval-level staffing model was wrong — total headcount matches the plan but coverage is concentrated in the wrong half-hours. The operational implication: if adherence is high but SL is still missed, the schedule is the problem. Coaching agents on adherence will not fix a scheduling error.

95% schedule adherence and missed SL targets are not contradictory. If the schedule itself was built wrong — wrong intervals, wrong shrinkage, wrong AHT assumptions — improving adherence will not fix the problem. Schedule effectiveness is the upstream measurement.

Adherence vs effectiveness: diagnosing the right problem

High adherence, missed SL → schedule problem

If agents are following the schedule closely (adherence 90%+) but SL is consistently missed, the schedule itself is the issue. Possible causes: wrong shift start times for the volume profile; under-estimated shrinkage; incorrect AHT assumption; total headcount below the net staffing requirement. The intervention is a schedule review, not an adherence coaching programme.

Good schedule, missed SL → adherence problem

If the scheduled staffing position is sufficient to meet SL at the forecast volume (coverage efficiency ratio 90%+) but SL is being missed, the agents are not following the schedule. Possible causes: agents starting late, taking extended breaks, spending time in unscheduled non-phone activities. The intervention is an adherence improvement programme, not a schedule rebuild.

Both low: schedule and adherence failing simultaneously

The worst diagnostic outcome — both the schedule and the adherence are failing, making it impossible to isolate the dominant cause from aggregate SL data alone. Requires an interval-level analysis comparing scheduled agents vs. required agents vs. actual agents present in each interval to separate the two failure modes.

Both good, SL still missed → forecast problem

The schedule is well-built and agents are following it, but SL is missed because actual volume exceeded the forecast. The schedule was correctly built from a wrong input. The intervention is a forecasting accuracy review, not a schedule or adherence issue.

Four schedule effectiveness metrics

Coverage efficiency ratio

What it measures

The percentage of half-hour intervals in the operating day where the scheduled on-phone agents were sufficient to meet the SL target at the forecast volume. Measures schedule design quality at interval level.

How to calculate

Count the number of intervals where scheduled agents ≥ Erlang C requirement at the forecast volume. Divide by total operating intervals. Multiply by 100.

Target

85%+ of intervals at or above the Erlang C staffing requirement. Below 85% indicates either insufficient shift diversity (wrong start times) or insufficient total headcount.

When below target

Rebuild the scheduling model with updated shift start time constraints. If the coverage ratio is consistently low for specific interval windows (e.g. every Monday 08:00–09:00), this is a systematic scheduling gap, not a random error.

Scheduled vs. required interval variance

What it measures

The average difference (in agents) between the scheduled on-phone position and the Erlang C-required position across all intervals. Positive variance = overstaffed; negative variance = understaffed.

How to calculate

For each interval: (scheduled agents − required agents). Average across all intervals. Report separately for positive (over) and negative (under) intervals.

Target

Overall average variance within ±1 agent. Peak-interval variance should not exceed −2 agents (understaffed by more than 2 agents at peak is a schedule design failure).

When below target

A persistent negative peak variance indicates the schedule is not covering the peak. Root causes: shift start times are too late for the peak; shrinkage is under-estimated; total scheduled headcount is below the net staffing requirement.

Shrinkage realisation rate

What it measures

The ratio of actual shrinkage to the shrinkage allowance built into the schedule. A shrinkage realisation rate above 1.0 means actual shrinkage is higher than planned — on-phone agents are fewer than the schedule assumed.

How to calculate

Actual shrinkage % ÷ Planned shrinkage % in the schedule. Example: actual shrinkage 28%, planned 22% → realisation rate = 1.27 (27% more shrinkage than planned).

Target

Shrinkage realisation rate 0.90–1.10 (within 10% of planned). Above 1.15 consistently indicates the shrinkage assumption in the schedule must be updated.

When below target

Update the scheduled shrinkage assumption and rebuild the staffing model. A shrinkage realisation rate of 1.27 means every 100 agents scheduled produces only 78 on-phone agents, not the 78 assumed (at 22% shrinkage) — instead 72. The gap compounds across every interval.

Scheduled AHT accuracy

What it measures

The ratio of actual AHT to the AHT assumption used in the staffing model. An AHT realisation rate above 1.0 means calls are taking longer than planned — fewer contacts are handled per agent-hour than the schedule assumed.

How to calculate

Actual AHT ÷ Scheduled AHT assumption. Example: actual AHT 7.2 minutes, scheduled assumption 6.5 minutes → realisation rate = 1.11.

Target

AHT realisation rate 0.95–1.05 (within 5% of planned). Above 1.10 consistently means the schedule is producing less capacity per agent-hour than planned.

When below target

Investigate AHT drivers — is actual AHT higher due to contact complexity (a mix shift), agent capability (skill gap), or process friction (a system issue)? Update the AHT assumption in the staffing model for the next scheduling cycle.

Schedule effectiveness questions

What is the difference between schedule adherence and schedule effectiveness?

Adherence measures whether agents are doing what the schedule says they should be doing moment to moment. Schedule effectiveness measures whether the schedule, if followed perfectly, would produce the target SL. A schedule with 95% adherence can still miss SL if: the forecast was wrong; shift start times are misaligned with the volume profile; shrinkage is underestimated (so fewer agents are on-phone than the schedule assumed); or AHT is higher than planned (so each agent handles fewer contacts per hour). The operational diagnostic: if adherence is high but SL is missed, investigate the schedule. If the schedule is well-constructed but SL is missed, investigate adherence. If both are good and SL is still missed, investigate the forecast.