To estimate workload hours, multiply the number of tasks by the average time per task and divide minutes by 60. For mixed work, calculate each task category separately and add the results. Then compare workload with productive capacity over the same period. The result is a capacity estimate, not a guarantee of service speed.
Calculate each work category
Suppose a team expects 600 requests averaging eight minutes each and 120 reviews averaging 15 minutes each during a week. Requests need 4,800 minutes, or 80 hours. Reviews need 1,800 minutes, or 30 hours. Total expected workload is 110 hours.
| Work type | Volume | Minutes per item | Hours |
|---|---|---|---|
| Requests | 600 | 8 | 80 |
| Reviews | 120 | 15 | 30 |
| Total | 720 | Mixed | 110 |
Define whether handling time includes preparation, after-work notes and rework. If eight minutes already includes those activities, adding them as a separate allowance would count them twice. Use a representative measurement period and keep unusually complex work visible rather than hiding every variation in one average.
Convert workload into a staffing equivalent
If one full-time employee is scheduled for 40 hours and 25% is unavailable for the modeled work, productive capacity is 40 × 0.75 = 30 hours per week. The workload equivalent is 110 ÷ 30 = 3.6667 full-time schedules under those assumptions.
If staffing can only be added as whole identical full-time schedules, four would provide 120 productive hours. That leaves ten hours of modeled capacity. It does not prove four people can meet every deadline: the work may arrive in peaks, require different skills or have simultaneous demands.
Check the denominator for double counting
If the measured handling time already includes waiting or administration, and the productive-hours denominator also removes those same activities, the model may overstate staffing. Define the boundary on both sides. Workload hours and available hours must describe the same type of work.
Use either a productive-capacity denominator or a separate availability adjustment consistently. Dividing by 30 productive hours and then inflating the result again for the same 25% shrinkage applies the allowance twice.
Run a meaningful sensitivity check
If the 600 requests take ten minutes instead of eight, request workload rises to 100 hours. Combined with 30 review hours, total demand becomes 130 hours. At 30 productive hours per employee, the requirement is 4.3333 schedules, not 3.6667.
This comparison shows why time-per-item assumptions deserve review. Keep the original estimate and actual results so the model can improve. For work requiring immediate responses, add an interval-level or queueing analysis; a weekly average does not describe waiting times.
Frequently asked questions
Should I round every task category's FTE up?
Not if the same staff can perform the categories interchangeably. Add compatible workload hours first. Separate genuinely different skill or coverage requirements before deciding how to staff them.
Does 3.6667 FTE mean exactly four employees?
Only under the stated whole-full-time scheduling assumption. Part-time arrangements, skill limits and coverage needs can produce a different headcount.
Related calculators and guides
- FTE & Headcount Calculator
- Staffing Shrinkage and Productive Capacity Calculator
- FTE vs. Headcount: Calculator, Formula and Examples
Explore more in Workforce Planning Calculators and Guides.