Business
Staffing Capacity Calculator
This page is designed for monthly workforce capacity planning where workload can be expressed in labor hours. It keeps paid headcount, productive hours, buffered demand, overtime policy, uncovered hours, required core FTE, and staffing cash separate so a short-term overtime response is not mistaken for permanent capacity.
Decision view
Buffered workload capacity bullet
| Paid staff available | Productive hours per FTE | Regular productive capacity | Demand including reliability buffer | Buffered demand above regular capacity | Policy maximum overtime hours | Overtime used within policy cap | Productive capacity including planned overtime | Buffered demand still uncovered | Core FTE required without overtime | Additional core FTE required | Buffered demand covered after overtime | Loaded payroll plus planned overtime |
|---|
How to use Staffing Capacity Calculator
- Forecast workload in labor hours for the same month and service scope as the staffing roster.
- Enter paid FTE hours, nonproductive shrinkage, and productive utilization from observed scheduling data.
- Set a service buffer and overtime policy, then review the hour shortfall and core-FTE requirement separately.
Calculator guide
Understanding Staffing Capacity Calculator
Size operational staffing from workload hours, not from revenue per employee. The calculator converts paid hours into productive capacity after leave, meetings, training, rework, and utilization, then tests regular capacity and policy-capped overtime against demand plus a service buffer.
Detailed calculation process
Convert paid staffing into buffered workload coverage
The default has 14 paid FTE, 160 hours per FTE, 18% shrinkage, 78% productive utilization, 1,850 forecast hours, a 12% service buffer, and 80 planned overtime hours.
What each symbol means
Worked substitution with the default inputs
The default plan covers 73.01% of buffered demand after overtime, leaves 559.296 hours uncovered, and requires 21 core FTE without overtime.
Capacity interpretation
Read the capacity bullet as an operating decision
The visualization is an hour-based safety check, not a financial threshold chart.
Worked situations
Practical examples
- With 160 paid hours, 18% shrinkage, and 78% productive utilization, one FTE supplies 102.336 productive hours rather than 160.
- Fourteen FTE plus 80 planned overtime hours supply 1,512.704 hours, below the default buffered workload of 2,072 hours.
Better inputs
Useful tips
- Convert paid hours into productive hours after meetings, leave, training, rework, and unavoidable idle time.
- Model skills or service channels separately when staff are not interchangeable across the workload.
- Compare required capacity with peak-period demand, not only the monthly average.
Before relying on the result
Limitations and common mistakes
- The model assumes every counted FTE has the same paid hours, shrinkage, utilization, and workload productivity.
- Queue waiting-time behavior, hourly arrival variation, service-level probability, skill routing, and schedule coverage are not simulated.
- Employment law, fatigue, overtime premiums, recruiting lead time, and part-time arrangements require a roster-level plan.
Reference
Key terms
- Shrinkage
- Paid time unavailable for direct workload because of leave, meetings, training, rework, or other planned and unplanned activity.
- Productive utilization
- Share of the hours remaining after shrinkage that can actually be assigned to productive demand.
- Service buffer
- Additional planned workload capacity above the point forecast to absorb uncertainty and protect service.
Important note
Do not combine materially different skills or shifts into one FTE pool unless work can actually be reassigned among them.
Frequently asked questions
Why are shrinkage and utilization multiplied?
Utilization applies after nonproductive paid time is removed; adding the percentages would overstate the lost capacity.
Why does required core FTE ignore overtime?
It answers the permanent-capacity question. The separate overtime result shows a temporary scheduling response.
Can I enter cases instead of hours?
Convert cases to workload hours using a validated average handle time, ideally by case type.
Is the service buffer a safety factor?
It is a planning allowance, not a statistical service-level calculation.