all free tools

human review staffing calculator

Every agent workflow with a human checkpoint creates a queue. Divide the review hours by a working month and you get the naive answer, which misses the target every busy afternoon. This calculator uses Erlang C, the model contact centres staff with, to find the reviewers you need at the busiest hour to pick cases up on time, then adds shrinkage.

free, no sign-up, runs in your browseropen source on GitHub
the queue
the target
the team

5 on shift at peak, 7.1 people in total

5reviewers on shift in the busiest hour
7.1headcount after shrinkage
2.3the naive answer: workload alone
98.6%picked up within 30 min
3.7 minaverage wait
73%reviewer occupancy at peak
2,250reviews per month
$56,571review labour per month
$25.14cost per review
18.2reviews in the busiest hour

Erlang C queueing at the busiest hour. The gap between the naive workload figure and the headcount is the cost of answering on time, plus shrinkage. Cost assumes the peak headcount is held for every open hour, so it is an upper bound; staggered shifts bring it down. Occupancy above about 85% for long stretches burns people out.

questions

what is erlang c?

A queueing formula for work that arrives at random and is handled first come, first served by a pool of people. From the arrival rate, the handling time and the number of people, it gives the chance a case waits and how long. It is the standard way to staff contact centres and works the same way for review queues.

what is shrinkage?

The share of paid time people are not available to review: leave, sickness, training, meetings and breaks. 25–35% is common. Headcount is the reviewers needed on shift divided by one minus shrinkage.

why plan for the busiest hour?

Cases bunch up. If Monday mornings bring 1.6 times the average hour, staffing for the average means Monday's cases miss the target. Set the busiest-hour factor from your own arrival data.

what if the queue can wait a day?

Then set a long pick-up target, such as 480 minutes. The answer falls towards the plain workload figure, because a queue with a slow target can absorb peaks.

more free tools

Want the numbers checked against your own process? Book a 20-minute call.