Resource Planning

Resource planning is the process of identifying who is available, when they are available, and which engagements they should be assigned to, converting a staffing plan into real, named allocations against live projects.

Done well, it prevents both over-allocation (burnout, quality risk) and under-allocation (bench cost). It is distinct from capacity planning, which works at the aggregate supply-and-demand level.

What resource planning covers

A complete resource planning process answers four questions for every active and upcoming engagement:

1. Who is needed, and at what seniority and skill level?
2. When are they needed, and for how many hours per week?
3. Are those people available, or are they already committed elsewhere?
4. What is the cost impact of the proposed assignment mix?

Resource planning operates at the individual level. It is not about whether the firm as a whole has capacity; that is capacity planning. It is about named people and named projects.

The planning horizon

Most firms run resource planning on a rolling 4-to-12-week horizon. Shorter windows are too reactive. Longer windows are too speculative unless the pipeline is highly contracted. A weekly resource review meeting is the operational heartbeat of any delivery-focused services firm.

Common failure modes

• Assigning by availability alone, ignoring skill fit or client relationship continuity
• Planning in a spreadsheet disconnected from live project data
• No single owner for resolving allocation conflicts across practices
• Ignoring soft allocations on pipeline deals until the deal closes, which creates a staffing scramble at contract start

The resource manager role exists to own this process and resolve conflicts before they reach the delivery team. Firms without a named owner for resource planning default to informal allocation, which causes double-booking, last-minute staffing scrambles, skill mismatches on projects, and unpredictable utilization rates.

Resource planning inputs

Resource planning draws from several data sources: the confirmed project plan and staffing model for each engagement, the pipeline of deals in late-stage negotiation where demand is likely but not yet contracted, individual availability calendars and current commitments, and skill profiles that map each consultant’s competencies and certifications to project requirements. The accuracy of the output is bounded by the quality of these inputs. A staffing plan built on stale pipeline data or out-of-date skill records produces allocations that break the moment the project starts.

The relationship to the statement of work

Resource planning and the statement of work interact directly. The SOW defines the roles, seniority levels, and hours required by the engagement. Resource planning translates those requirements into named people. When the actual assignment differs materially from what was scoped in the SOW (a more junior person, fewer hours, a different skill set), delivery risk increases and margin may erode.