A team can have enough people on paper and still be unable to start an engagement. The missing element may be a specialist skill, a release date or a working pattern that does not match the plan. Capacity planning should make those constraints visible before a commitment is made.
Headcount is not usable capacity
A team of twenty people does not provide twenty interchangeable units of capacity. Leave, part-time schedules, existing assignments and skill requirements change what can be committed. Begin with the working calendar and calculate capacity for the period in which the work must happen.
Build the planning baseline
Agree the treatment of holidays, internal work and reserved allocations before comparing teams. Keep planned allocation separate from actual time. One tells you what has been committed; the other tells you what happened. Both are useful, but they answer different questions.
- Calendar: working hours, holidays and planned leave.
- Commitments: confirmed, tentative and internal allocations.
- Requirement: skill, proficiency, duration and location.
- Exception: over-allocation, uncovered demand or uncertain release.
Calculate capacity before comparing people
Consider a four-week planning period with eight consultants working 40 hours per week. Gross capacity is 1,280 hours. Existing delivery commitments consume 800 hours, planned leave consumes 80 and internal responsibilities consume 120. That leaves 280 hours available for additional work. A new engagement requiring 320 hours creates a 40-hour gap, even though a headcount report shows eight people on the team.
The aggregate gap is only the first test. If 120 of those required hours need a specialist who has only 60 hours free, the specialist shortage is 60 hours. Surplus capacity elsewhere cannot automatically cover it. Check whether the work can be sequenced, paired with a developing colleague or supported externally before committing the start date.
Illustrative operating example; this is not a reported customer result or a product performance claim.
Expose the shortfall by skill and week
In an illustrative week, a person has forty working hours and eight hours of leave. After a confirmed twenty-four-hour assignment, eight hours remain before any internal commitments. A second project needing sixteen hours cannot be staffed by calling that person partly available without examining the gap.
Keep the plan current without rebuilding it
Review changes to demand, leave and releases at a regular cadence. Give tentative bookings expiry dates and owners. When a project slips, check both the extended commitment and the work that expected to use the released capacity. That is where a current plan becomes more useful than a static allocation sheet.
Work through a four-week staffing decision
Imagine a consultancy preparing a discovery engagement that needs an architect for sixteen hours each week. The architect has eight uncommitted hours in week one, sixteen in week two and no availability in week three. Averaging those weeks produces a number that looks manageable but cannot support the promised workshop schedule. The resource manager needs a dated plan, not a monthly percentage.
Start by separating activities that require that specialist from activities another team member can perform. Ask whether workshops can move, whether a second architect can take over without expensive handovers, or whether the proposed start date must change. Record the selected option against the requirement. This preserves the reason behind the commitment when someone reviews the plan later.
Make the weekly review small enough to maintain
A useful capacity review starts with exceptions: new demand, changed start dates, releases that have slipped and allocations that exceed available hours. It does not require every manager to read the entire staffing sheet aloud. Give each exception an owner and a date by which the uncertainty must be resolved.
Keep a short planning horizon detailed enough for individual assignments and a longer horizon grouped by skill or practice. Confirm the exact horizons with your sales and delivery cycles. Reconcile the near-term plan with leave and project commitments before approving another booking; otherwise, the same apparently available hours can be promised twice.
Know whether the process is improving
Track how often confirmed demand remains uncovered near its start date, how frequently allocations are changed after approval and which skills repeatedly create shortfalls. These measures tell you more about planning reliability than an overall headcount total. Compare like periods and explain changes in the demand mix.
If a gap persists, choose a response explicitly: recruitment, development, external capacity or a different delivery commitment. Capacity planning earns its place when it changes one of those decisions before a customer promise becomes difficult to keep.
Explore the relevant Clousys workflow: Resource Management. Bring a current requirement to the walkthrough so the discussion can cover your records, responsibilities and configuration needs.
A practical checklist for your team
Define the calendar
Choose weekly periods, agreed working hours and the treatment of leave, public holidays and internal responsibilities. Record these rules beside the capacity view so two teams do not calculate different answers.
Separate confidence levels
Keep confirmed assignments separate from tentative demand. Review a committed baseline and a stretch scenario; do not silently add every opportunity into the staffing plan.
Decide and revisit
Record the selected staffing option, remaining gap, accountable owner and next review date. Recalculate when a start date, release or absence changes, rather than waiting for the next monthly report.
How often should a capacity plan change?
Refresh it when commitments change and use a regular weekly review to resolve exceptions. A stable project may need little intervention; a scarce skill serving several opportunities needs closer attention. The review cadence should reflect how quickly decisions can become outdated.
Put these ideas into your operating model.
Explore a focused Clousys walkthrough built around your current systems, handoffs and leadership priorities.









