Skip to content
Staffing math

How many people does your coverage actually take?

Every coverage window has one honest arithmetic behind it: hours to staff, divided by hours a person can work. These pages show that work for the configurations teams actually run, including the ones where the honest answer is to change the plan.

Staffing to call volume instead?

When the driver is demand rather than a coverage window, the math changes from division to queueing. The call center ladder gives precomputed Erlang C answers for 25 to 1000 calls an hour and 100 to 2000 a day: agents on the phones, scheduled headcount, and what one agent either way does to the queue.

Open the call center ladder

The method behind every page

Each page follows the same worked arithmetic: coverage hours per week, divided into shifts, divided by what a person can sustainably work, then adjusted for the 20 to 25 percent of paid time that leave, sickness, and training consume. The numbers are computed, not copywritten, so the headline, the derivation, and the options table always agree.

Headcount is only half the decision. The other half is which rotation makes those hours livable, which is what the shift pattern library covers, with interactive calendars for the rotations these pages recommend. For demand-driven staffing (how many agents for the call volume, not the coverage window), start from the Erlang C calculator instead.

Your next schedule could take 2 minutes.

Import your team, set your rules, hit auto-fill. Most teams are live the same day.

Try Soon free

30 days free ยท No credit card required

Already have an account?Sign in