Coverage vs requirement

Deep-dive lesson · about 10 minutes · short quiz at the end

ccPlanning academy · scheduling · deep dive

Coverage vs requirement

The one chart every scheduler lives by.

The two lines

Requirement and coverage, interval by interval.

The requirement is how many staff you need each interval. Coverage is how many your schedule actually puts there. Plot both and the whole quality of a schedule is visible at a glance.

Reading the gap

The space between the lines is the story.

Coverage below the line = understaffed. Above = overstaffed (idle, paid time).

Why totals lie

You can be “100% staffed” and badly wrong.

Add up the day’s required hours and the day’s scheduled hours and they can match perfectly — while you’re drowning at 10am and idle at 3pm. The totals net to zero; the intervals don’t.

The asymmetry

Under and over don’t cancel.

An hour understaffed does service damage that an idle hour elsewhere can’t undo — the abandoned calls don’t come back. Coverage is not a balancing act around a total; it’s about minimising the understaffed intervals first.

Net staffing

Coverage means net, not gross.

The people on shift aren’t all available — some are on breaks, in training, at a meeting. Coverage is the net bodies actually handling contacts in that interval, after shrinkage. Schedule gross; cover net.

Shaping coverage

Move the blocks, change the shape.

Every lever — later start times, staggered lunches, a part-time shift over the peak — reshapes the amber line. Scheduling is iterating those moves until the coverage line hugs the requirement.

The peak problem

Peaks are where schedules break.

A sharp midday peak is the hardest thing to cover with whole shifts — you either overstaff the shoulders to reach the peak, or under-cover the peak. This is exactly where part-time and split shifts earn their place.

Honesty check

Coverage charts expose wishful schedules.

A schedule that looks fine on a headcount summary often shows ugly gaps once plotted against requirement by interval. The chart is the truth-teller — build the habit of looking at it, not the daily total.

Why “100% staffed” fools people

The day that balances and still fails

Required hours for the day: 300. Scheduled hours: 300. The summary says 100% — perfect. Yet at 10am you’re 8 short and queues build, while at 3pm you’re 8 over and paying for idle time.

The two errors net to zero on the total, but the abandoned 10am calls never come back. Only the interval chart sees it.

The takeaway

Hug the line, interval by interval.

Plot net coverage against requirement, attack the understaffed intervals first, and remember the totals can match while the shape is wrong. The gap between the two lines is the only scorecard that matters.

Now test yourself ↓

1 / 10

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: the one chart every scheduler lives by

Two lines tell you almost everything about a schedule. The requirement is how many staff you need each interval to hit service; coverage is how many your schedule actually puts there. Plot both, interval by interval, and the entire quality of the schedule is visible at a glance — the space between the lines is the story. Coverage below the line means understaffed and queuing; above means overstaffed and paying for idle time. Everything a scheduler does is an attempt to make the coverage line hug the requirement line.

Why the daily total lies

Add up the day’s required hours and the day’s scheduled hours and they can match perfectly while you’re drowning at 10am and idle at 3pm — the totals net to zero, but the intervals don’t. Worse, under and over aren’t symmetric: an hour understaffed does service damage that an idle hour elsewhere can’t undo, because the abandoned calls don’t come back. So coverage isn’t a balancing act around a total; it’s about minimising the understaffed intervals first. And the coverage that matters is net, not gross — the people on shift aren’t all available, because some are on breaks, in training or at a meeting, so you schedule gross and cover net after shrinkage.

Shaping the line, and where it breaks

Every lever reshapes the coverage line: later start times, staggered lunches, a part-time shift dropped over the peak. Scheduling is iterating those moves until the line fits. The hardest place is a sharp midday peak — covering it with whole shifts means either overstaffing the shoulders to reach it or under-covering the peak itself, which is exactly where part-time and split shifts earn their keep. Above all, build the habit of looking at the chart rather than the headcount summary: a schedule that looks fine on a daily total often shows ugly gaps once plotted against requirement by interval. The chart is the truth-teller.

The principle to remember: hug the line, interval by interval. Plot net coverage against requirement, attack the understaffed intervals first, and never trust a total — it can match while the shape is wrong.

Coverage vs requirement