Capacity is the work a team can perform under stated availability, skill and timing constraints. Convert demand into workload using explicit assumptions, then compare it with usable capacity in matching units. Headcount alone hides leave, non-delivery work, specialist bottlenecks and uncertainty.
Translate demand into the work that must be done
Define the service unit and horizon: calls next week, inspections per shift or projects this month. Estimate workload using relevant task types and handling times rather than one unexamined average. Distinguish arrivals, completed work and backlog. New demand may be manageable while an old backlog still requires attention. Record whether rework and follow-up are included or measured separately.
Use observed time data carefully. Averages from completed easy cases may understate complex unresolved work. Identify collection gaps and changes in process or service mix. When handling time is uncertain, show a justified range and what it excludes. Do not convert an unsupported point estimate into a precise staffing requirement simply because the scheduling tool accepts decimal hours.
Calculate usable capacity by skill and time
Start with scheduled hours, then account for leave, breaks, training, administration and other commitments under the organisation's actual rules. Avoid double-deducting time already excluded from the roster. Separate roles where work is not interchangeable. Ten spare generalist hours cannot necessarily cover a five-hour task requiring a licensed specialist, and the specialist's availability may not coincide with the customer's deadline.
Compare demand and capacity at the interval relevant to the service. Weekly totals can conceal a Monday peak or an overnight coverage gap. Include constraints such as equipment, supervisor availability and maximum simultaneous appointments where material. A utilisation ratio is a planning measure, not a complete service guarantee. Variable arrivals and handling times can create waiting even when average workload is below average capacity.
Choose a response with explicit assumptions and safeguards
Review options such as rescheduling, cross-training, temporary support or reducing nonessential work. State which constraint each option addresses and any quality or access consequence. Overtime does not automatically create interchangeable capacity, and moving work may transfer a bottleneck to another stage. Use a reversible plan when uncertainty is material and define the observation that would trigger an adjustment.
Track the actual workload and service outcome against the assumptions after implementation. Separate a wrong demand estimate from unexpected absence or longer handling time. This makes the next plan more informative without treating people as a uniform production input. Assign ownership for the roster, demand estimate and decision, and retain the version used when commitments were made so later changes can be explained.
A fictional service desk capacity plan
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional desk expects 180 simple requests at ten minutes each and 30 complex requests at forty minutes each. Workload is 1,800 plus 1,200 minutes, or 50 hours. Four staff members are scheduled for 20 hours each, giving 80 scheduled hours. After 12 hours of leave and 18 hours of agreed non-request work, usable handling capacity is 50 hours.
The totals match, but only one person can handle complex requests and has 15 usable hours. Complex demand requires 20 hours, creating a five-hour skill-specific gap despite balanced overall hours. The manager checks whether a trained backup can cover that gap and whether requests arrive within their availability. If simple-request duration rises to twelve minutes, simple workload becomes 36 hours and total demand becomes 56. The plan therefore monitors both skill coverage and handling-time assumptions rather than calling four people sufficient on the basis of headcount. The remaining generalist time is not presented as a solution until the backup skill is verified. The review also checks whether complex requests can wait for the backup shift or require same-day handling. That timing constraint determines whether the proposed five-hour cover actually meets the service need.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define demand, backlog and service horizon.
- Use matching workload and capacity units.
- Separate skills and peak-time constraints.
- Monitor assumptions and service safeguards after changes.
Common questions.
Does 100% planned utilisation mean capacity is adequate?
Not necessarily. Variability, peaks and skill constraints can cause delays even when totals match.
Should all non-service time be treated as waste?
No. Training, breaks, supervision and essential administration can be necessary to sustain safe and effective service.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse Accuralytix.
Found an error or a missing qualification? Send an editorial correction.
Check my data readiness.
Use a practical tool to turn this idea into a clearer starting point.
Check my data readiness