What is resource capacity planning?
Resource capacity planning is the process of comparing the time and skills your team can supply with the work your organization expects to deliver. For a professional services team, that means understanding who is available, which projects need them, when the work will happen, and how much effort it is likely to require.
The purpose is not to fill every hour. It is to make delivery decisions early enough to protect clients, employees, and project economics. A useful capacity plan shows both sides of the equation: supply from people and demand from confirmed work, probable pipeline, internal commitments, and planned absence.
Capacity planning differs from scheduling. Scheduling places named people on specific work. Capacity planning looks further ahead and asks whether the organization has enough of the right roles and skills before every assignment is known. Teams need both views, connected to the same underlying data.
Start with a trustworthy capacity baseline
Begin with each person’s normal working hours for the planning period. Then subtract time that is genuinely unavailable, such as public holidays, approved leave, and agreed working-pattern changes. The result is the person’s available capacity.
Do not assume that contracted hours equal project capacity. Team leadership, sales support, learning, administration, and other internal responsibilities may be productive work even when they are not billable. Make those categories explicit so the plan reflects how the organization actually operates.
For example, someone who normally works 40 hours and has 8 hours of approved leave has 32 available hours that week. If 24 hours are assigned to client work and 4 hours to an internal initiative, the plan should show 4 hours still available rather than treating the person as fully occupied.
- Record working hours by person instead of applying one company-wide assumption.
- Subtract approved absence and holidays before calculating utilization.
- Separate billable, productive non-billable, and genuinely available time.
- Use weekly periods for operational decisions and longer horizons for hiring or contractor plans.
Translate projects and pipeline into demand
A project budget or revenue forecast does not automatically tell you which people the work requires. Convert each project into weekly demand by role, skill, date, and expected hours. This creates a planning unit that can be compared directly with team capacity.
Keep confirmed and potential demand separate. Signed projects belong in the committed plan. Late-stage opportunities can be included as probability-weighted demand or as visible scenarios. Early opportunities may remain outside the core forecast while still appearing as a risk. The distinction prevents the team from treating every sales possibility as certain work.
Where the scope is still unclear, use ranges or scenarios instead of false precision. A likely start window and an estimated role mix are more useful than a detailed plan that everyone knows will change.
- Name the role and essential skills before naming a preferred person.
- Estimate hours by week, because effort is rarely flat across a project.
- Keep confirmed, likely, and possible work visibly distinct.
- Assign an owner to refine demand as the opportunity or project develops.
Calculate utilization and the capacity gap
Once supply and demand use the same weekly units, the key calculations are simple. Planned utilization equals planned productive hours divided by available capacity. Billable utilization uses billable hours in the numerator. Available capacity is the time left after planned work, while a negative balance indicates overload.
Suppose a design team has 320 available hours next week and 280 hours of planned productive work. Planned productive utilization is 87.5%, with 40 hours still available. That does not mean any 40 hours can satisfy any new request. The remaining capacity must still be checked against role, proficiency, location, timing, and project context.
Review the figures at more than one level. An organization may look balanced overall while a specialist role is overloaded and another team has unused time. Capacity decisions become useful when totals can be traced back to the people, projects, and assumptions behind them.
Turn the forecast into a weekly decision process
A capacity plan becomes valuable when it drives a repeatable operating rhythm. Hold a short weekly review focused on exceptions rather than reading every row. Look for people above capacity, unfilled project roles, work starting without an approved team, material changes in pipeline demand, and forecasts that differ from actual effort.
Each issue should leave the review with an owner and a decision date. The action might be to move work, change a start date, adjust scope, develop an internal skill, bring in a contractor, or begin hiring. Recording the decision beside the demand preserves context when the plan changes again.
Use actual time as feedback, not as a replacement for the forecast. If a type of work repeatedly needs more effort than planned, update future assumptions. If time is consistently overestimated, release that capacity earlier. The aim is a planning model that learns from delivery.
- Review overload and unfilled demand first.
- Confirm what changed since the previous plan.
- Assign one owner and due date to every staffing action.
- Compare forecast and actual effort to improve the next estimate.
Avoid the most common capacity-planning mistakes
The first common mistake is planning only confirmed work. That makes the near-term view look safe until a likely opportunity closes and creates an immediate shortage. The second is combining all roles into one capacity total, which hides gaps in scarce skills. The third is measuring only historical utilization, which explains the past but cannot prevent next month’s conflict.
Another mistake is treating maximum utilization as the goal. A plan with no room for change is fragile: estimates move, clients respond late, employees take leave, and urgent work appears. Capacity targets should reflect the delivery model and the volatility of demand rather than forcing every person toward the same percentage.
Finally, avoid maintaining separate versions for sales, projects, leave, and staffing. Reconciliation consumes time and weakens trust. A connected model should let a change in project dates or approved absence flow into the capacity view without another round of copying.
A practical resource capacity planning checklist
A services team can start without designing the perfect model. Choose a planning horizon, define the minimum information required for people and demand, and run the process with one team. Improve the model when real decisions expose missing information.
KADO connects people, projects, weekly allocations, planned absence, resource requests, pipeline demand, and actual time in one workspace. That gives operations leaders and managers a shared view of the plan while employees retain clarity over their own work.
- Set working capacity and calendars for every person.
- Capture roles, skills, proficiency, and reporting relationships.
- Convert confirmed projects into weekly hours by role or person.
- Add probable pipeline as separate, confidence-based demand.
- Include approved leave and internal commitments.
- Review utilization, available capacity, overload, and unfilled roles weekly.
- Record staffing decisions and compare forecasts with actual effort.