Key takeaways: to calculate a workload forecast, multiply the forecast volume of each activity by its unit handling time, then add up all activities. Work that arrives continuously, such as calls, must also be divided by an occupancy rate, because an agent can never be busy 100% of the time. You then convert total workload into headcount by dividing it by the truly productive hours of one person. Example: 6,000 calls of 6 minutes, 2,400 emails of 8 minutes and 900 cases of 15 minutes add up to 1,251 hours for the week, or 52 full-time equivalents (FTEs). The result is only reliable if handling times are measured, not estimated.
Knowing how to calculate a workload forecast means turning an activity estimate ("we expect a lot of calls next week") into a number of hours, then into a number of people. Most scheduling gaps don't come from the volume forecast itself but from this conversion: an underestimated handling time, deferred work treated like inbound work, a forgotten occupancy rate. Here is the method, activity by activity, with a complete worked example.
What is workload?
Workload is the number of hours needed to handle the activity of a given period. It is different from two related concepts it is often confused with.
- Activity volume: a number of units (calls, emails, cases, customers). It says nothing about the time required: a complaint call doesn't weigh the same as a simple information request.
- Workload: volume multiplied by unit handling time, expressed in hours. This is what you schedule.
- Capacity: the hours your team can deliver. Comparing workload with capacity is covered in our article on capacity planning.
The workload calculation formula
For a single activity, workload is calculated as follows:
- Workload (in hours) = forecast volume × unit handling time ÷ 60, if the time is in minutes.
- For continuous inbound work: workload ÷ target occupancy rate, often 80 to 85% in customer service.
- Total workload = sum of the workloads of all activities in the period.
The formula is simple. Its reliability depends entirely on the quality of its two inputs: forecast volume and unit handling time. Volume forecasting is covered in detail in our guide to contact volume forecasting; this article focuses on converting volume into workload.
Measuring unit handling time
Unit handling time is the input most often estimated by gut feeling, and the one most often wrong. It must include all the time spent on one unit, not just the visible part.
The components of handling time
- Contact time: the conversation, reading the email, the exchange at the front desk.
- After-contact work: data entry, updating the case, sending a document. It often accounts for a large share of the total, and it is the part most often forgotten.
- Research and transfers: checking with a colleague or a knowledge base, putting the customer on hold.
Where to find the data
Telephony and ticketing tools record average handling time by queue or by request type. If you don't have that, timing the work over a few representative days gives you a first order of magnitude. Calculate one time per activity type, not a single overall average that blends very different requests.
Inbound work, deferred work, schedulable tasks: three different calculations
Not all activities are calculated the same way. What sets them apart is the time frame within which they must be handled.
| Work type | Examples | Response time frame | Workload calculation |
|---|---|---|---|
| Inbound (real-time) | Calls, chat, front desk | Immediate | Volume × time ÷ occupancy rate, interval by interval |
| Deferred (non-real-time) | Emails, letters, tickets | A few hours to a few days | Volume × time, spread over the time frame, accounting for the existing backlog |
| Schedulable | Back office, quality checks, follow-ups | Set by the organization | Volume × time, placed in off-peak intervals |
This distinction changes everything. Inbound work has to be covered the moment it arrives, so its workload is calculated per 15- or 30-minute interval. Deferred work can be smoothed over its time frame, so its workload is calculated per day or per week, adding the previous day's unhandled work, known as the backlog.
Worked example: a customer service team's weekly workload
Take a customer service team that handles three activities. The target occupancy rate for calls is 85%. The figures are for illustration only: replace them with your own.
| Activity | Forecast volume | Unit handling time | Raw workload | Workload to schedule |
|---|---|---|---|---|
| Calls (inbound) | 6,000 | 6 min | 600 h | 706 h (÷ 0.85) |
| Emails (deferred) | 2,400 | 8 min | 320 h | 320 h |
| Cases (schedulable) | 900 | 15 min | 225 h | 225 h |
| Total | 1,145 h | 1,251 h |
From workload to full-time equivalents (FTE calculation)
One person on a 35-hour week with 30% shrinkage (vacation, absence, training, meetings, breaks) delivers 35 × 0.70 = 24.5 productive hours per week. You therefore need 1,251 ÷ 24.5 = 51.1, or 52 full-time equivalents after rounding up.
How to read it: without the occupancy rate on calls, the calculation would have given 1,145 hours and 47 people. The 5-person gap is exactly the unavoidable idle time between two calls. It is the most common mistake in spreadsheets.
Choosing the right level of detail
A weekly workload is enough to size the team. It is not enough to build the schedule, because activity is never spread evenly.
- Weekly or monthly: for budgeting, hiring and vacation planning.
- Daily: for deferred work and back-office tasks.
- Every 15 or 30 minutes: for inbound work, because that is the scale at which queues build up.
Mistakes that distort your workload forecast
- A single average time for all requests: it underestimates workload on days when complex requests dominate.
- Forgetting after-contact work: workload is underestimated by the same amount, and delays pile up at the end of the day.
- Treating emails like calls: you overstaff the morning for no reason instead of smoothing the work over the response time frame.
- Ignoring the backlog: the previous day's unhandled work adds to today's workload.
- Not comparing with actuals: if you don't track the gap between forecast and actual workload, handling times never get corrected.
Automating workload forecasting
In a spreadsheet, this calculation quickly becomes heavy: one row per activity, per channel and per interval, to redo with every new data point. Software like m-work Planner pulls historical data through integrations with your telephony and ticketing tools, forecasts volumes by 15-minute, 30-minute or hourly interval, and calculates the number of agents needed per channel and per interval. It handles real-time and deferred work alike, includes the backlog and non-queue activities, and lets you adjust productivity factors.
Calculating a workload forecast comes down to one formula, volume multiplied by unit handling time, applied activity by activity with the right treatment for each type of work. Start by measuring your actual handling times, then apply the method to a typical week and compare the result with your current headcount. To automate this calculation and connect it to your schedules, discover m-work's activity and workload forecasting software.
FAQ
How do you calculate workload?
Multiply the forecast activity volume by the unit handling time of each activity, then add up the results. For work that arrives continuously, such as calls, also divide by an occupancy rate, often 80 to 85%, to account for idle time between two contacts. Workload is expressed in hours over the chosen period.
How do you convert workload into FTEs?
Divide total workload by the number of truly productive hours of one person over the period. For someone on a 35-hour week with 30% shrinkage, that comes to 24.5 hours per week. A workload of 1,251 hours therefore requires 52 full-time equivalents, after rounding up.
What is the difference between real-time and deferred work in a workload calculation?
Real-time work, such as calls or chat, must be handled immediately: its workload is calculated interval by interval, with an occupancy rate. Deferred work, such as emails or letters, can be handled within a set time frame: its workload is smoothed over that time frame and added to the previous day's backlog.
How do you measure the handling time of an activity?
Telephony and ticketing tools record average handling time by queue or by request type. The time must include the contact itself, after-contact work and research. If you have no data, timing the work over a few representative days gives you a first order of magnitude, which you then refine with actuals.
How often should you recalculate workload?
Recalculate workload with every new volume forecast: every quarter for annual sizing, every week for schedules, and every day to adjust staffing. Review unit handling times regularly too, especially after a change in tools, processes or offering.






