Resource Management in Projects: A Field Checklist
Poor resource management is one of the most consistent causes of project overruns — not because project managers do not know resources matter, but because resource decisions are rarely made with full information and are almost never revisited often enough once a project is underway. This checklist covers the four phases of the resource management lifecycle and the specific actions that make each one work in practice.
Phase 1: Plan — Know What You Need Before You Start
Decompose scope to the work-package level before estimating resources. Resource estimates made against high-level deliverables are almost always too low.
Identify the specific skills required for each WBS element, not just the number of people. "Developer" is not a skill specification; "back-end developer with API integration experience" is.
Identify skill gaps explicitly. If the project requires capabilities the organisation does not currently have, that gap must be surfaced in planning — not discovered at execution.
Plan for learning curves on new technology or methodology. A team member moving from a familiar platform to an unfamiliar one will not be productive at full capacity on day one. Build ramp-up time into the schedule.
Document resource assumptions. When estimates change, you need to know what assumptions drove them.
Phase 2: Acquire — Secure Resources With Enough Lead Time
Decide early whether each role will be filled internally or externally. The lead time for a competitive procurement can be eight to twelve weeks; waiting until you need the resource to start the process guarantees a delay.
For internal resources, confirm availability with functional managers before the resource is named in the project plan. A name on a RACI chart does not equal a commitment.
For contract resources, include clear deliverable definitions and acceptance criteria in the statement of work. Vague scope leads to disputes at invoicing time.
Identify back-up options for key roles. If a single expert is critical to the schedule and they become unavailable, you need a plan B.
Phase 3: Monitor Use and Plan the Release
Review resource utilisation at every status meeting, not just at milestones. Over-allocation is much easier to correct early than late.
Track actual hours against the plan at the work-package level, not just at the project level. Aggregate numbers hide where the overruns are happening.
Address over-allocation immediately. A team member booked at 120 per cent of capacity will not deliver at 120 per cent — they will burn out, make errors, or both.
Update forecasts when actual data diverges from the plan by more than ten per cent. A project plan that has not been updated to reflect reality is not a plan; it is a fiction.
Plan the release of each resource before the project closes. A team member who has nowhere to go at the end of a project is either idle (wasted capacity) or will extend the project unnecessarily.
Conduct a resource debrief: what skills were harder to find than expected? What learning curves were longer than planned? These findings should feed the next project's resource planning.
Return shared resources to the resource pool with adequate notice, and communicate their availability to the resource manager or PMO so they can be redeployed.
Capture lessons learned on resource decisions as a formal project close-out activity.
One discipline that pays outsized dividends is tracking resource utilisation by role type across a portfolio, not just within individual projects. When a PMO can see that senior business analysts are consistently over-allocated across the portfolio while junior analysts have capacity, it can make better decisions about hiring, training, and project scheduling. Resource management at the portfolio level also makes it easier to sequence projects in a way that avoids the destructive pattern of starting everything simultaneously and finishing nothing on time.
XNM Consulting supports organisations in building project management disciplines that stick. Learn more about our program and project delivery services.