Separate Capacity from Availability
Capacity is the amount of workable time a person or team could contribute within a planning period. Availability is the portion that remains after leave, operational duties, meetings, training, support, and existing commitments. Treating the two as equal creates an optimistic plan before project work even begins.
Build capacity from the calendar and the team's real work pattern. Include recurring responsibilities that rarely appear in project schedules, such as mentoring, administration, incident response, and customer questions. Do not assume every remaining hour is assignable. People need space to coordinate, solve unexpected problems, and absorb normal estimation error. A plan that fills all visible time turns any interruption into a missed commitment.
Record capacity at the level the decision requires. Portfolio leaders may need a view by team or skill group, while a delivery lead may need named availability for a near-term task. Starting with individual detail across a distant horizon creates maintenance work and false precision. Use broad capacity bands farther out, then refine allocations as work approaches and uncertainty falls. Keep the source calendar and update owner visible so unexplained totals can be traced and corrected quickly.
Translate the Roadmap into Demand
Project demand should describe skills and timing before it names people. Break upcoming outcomes into the capabilities required, the likely effort window, the dependency sequence, and the consequence if support arrives late. This reveals when several initiatives depend on the same scarce expertise even if their total headcount appears manageable.
Distinguish committed work, likely work, and exploratory demand. Committed work deserves protected capacity. Likely work needs a provisional reservation and a decision date. Exploratory demand belongs in scenarios rather than the active allocation plan. Combining all three makes the organization look overloaded and encourages managers to negotiate against work that may never begin. Add confidence and an expiration point to provisional reservations so tentative projects do not block higher-confidence delivery indefinitely.
Account for nonlabor resources where they can govern the schedule. Specialized equipment, test environments, rooms, vehicles, or access windows can become the true constraint even when people are available. Give these resources owners and booking rules. If access is shared across projects, show the conflict in the same planning view so leaders can compare complete delivery choices.
Resolve Conflicts Through Explicit Priorities
When demand exceeds supply, the plan has done its job by revealing an impossible set of promises. The next step is not to divide every person into smaller fractions. Leaders must delay work, reduce scope, change sequencing, add qualified capacity, or accept a documented delivery consequence. The person maintaining the resource view should frame these options but should not silently choose business priorities.
Protect focus when allocating people. A specialist split across many initiatives loses time to context changes, status coordination, and competing urgent requests. Group related work where possible and establish a primary commitment for each planning window. Small advisory contributions can remain separate, but they should be visible so they do not accumulate into hidden workload.
Use skill coverage rather than job titles alone. Two people with the same title may have different domain knowledge, approval authority, or equipment access. Mark critical capabilities with limited backup and create a response such as cross-training, paired work, or revised sequencing. This makes the plan more resilient without treating people as interchangeable units.
Maintain a Living Resource View
Set a review rhythm that matches how quickly commitments change. The meeting should focus on exceptions: new demand, forecast movement, capacity loss, unresolved conflicts, and decisions approaching their deadline. Reconfirming every unchanged allocation wastes the attention needed for genuine tradeoffs. Keep a decision log so teams understand why a priority moved and who approved it.
Compare forecast demand with actual effort at a useful level, looking for patterns rather than policing individual hours. Repeated overruns may signal missing work, weak estimation, excessive interruption, or a skill mismatch. Repeated unused reservations may show that projects are holding scarce people too early. Adjust the planning assumptions instead of simply labeling either pattern poor performance. Archive earlier snapshots so planners can see which assumptions repeatedly moved and improve the next planning cycle.
Enter your own team and cost assumptions in the seat-cost planner on this page before proposing added capacity. Combine that estimate with the delivery consequence of doing nothing, since cost alone does not establish priority. A credible resource plan presents leadership with feasible scenarios and keeps the selected one current as projects, staffing, and operational demand change.
Resource forecasts are decision aids and should be revised when demand, capacity, or confidence changes.