A resource management plan is the document that sets the rules for how an organization estimates, acquires, assigns, develops, and releases the people and physical resources its projects need. It is not the schedule of who is doing what this week; it is the governing document that says how those weekly decisions get made, who owns them, and what happens when two projects want the same person. Get it written once at the portfolio level and every project stops reinventing the rules.
Key takeaways
- A resource management plan defines how resources are estimated, acquired, allocated, developed, and released, plus who is accountable for each decision.
- It is a governing document, not a live assignment sheet. The plan sets the method; capacity plans and allocation sheets carry the numbers.
- At its core sit roles and responsibilities (often a RACI), the acquisition approach, resource calendars, the estimation method, and an escalation path for conflicts.
- At portfolio level, one shared plan lets every project pull from the same resource pool on the same rules, which is what makes cross-project capacity decisions possible at all.
What is a resource management plan?
A resource management plan is a component of project or portfolio planning that describes how resources will be identified, acquired, managed, and released across the work. Resources here means both people (roles, skills, and the individuals who fill them) and physical resources (equipment, facilities, and materials). The plan answers process questions rather than assignment questions: how do we estimate what a project needs, how do we get those resources, how do we resolve it when demand exceeds supply, and how do we free people up cleanly when a project ends.
The distinction that trips people up is plan versus data. The resource management plan is the method; the actual numbers, who is booked at what percentage next month, live in a capacity planning template or an allocation sheet that the plan governs. Write the plan once and it stays fairly stable; the data underneath it changes every week.
What does a resource management plan include?
There is no single mandated format, but strong plans across PMOs share the same components. Treat this as a checklist.
| Component | What it defines |
|---|---|
| Roles and responsibilities | The roles the work needs, the skills each requires, and who is accountable, often as a RACI. |
| Resource estimation method | How the effort and headcount for a project are estimated, and to what precision. |
| Acquisition approach | How resources are obtained: internal assignment, hiring, or contracting, and who approves each. |
| Resource calendars | When named people and equipment are available, including leave, holidays, and other commitments. |
| Allocation and leveling rules | How people are assigned to work and how over-allocation is resolved. |
| Team development | Training, onboarding, and how skills gaps are closed. |
| Control and reporting | How utilization and availability are tracked, and how often the plan is revisited. |
| Release plan | How resources are freed when work finishes, so they return to the pool cleanly. |
Not every project needs all eight in depth. A small internal project might cover roles, a calendar, and a release note in half a page. A portfolio-level plan that many projects draw on justifies real detail on acquisition and conflict rules, because those are the decisions that bite when several projects compete for the same scarce specialist.
Roles and responsibilities: the RACI at the center
The component teams argue over most is roles and responsibilities, and the tool most reach for is a RACI matrix: for each significant activity, who is Responsible, Accountable, Consulted, and Informed. The value is not the grid itself but the conversation it forces, because ambiguity about who owns a decision is where resource conflicts actually start. A plan that names an accountable owner for resolving contention between projects has solved half the problem before it happens.
How to build a resource management plan
Building the plan is a sequence, not a form to fill in. Work through it in this order.
1. Identify the resources the work needs
Start from the demand side: what roles, skills, and physical resources do the projects in scope require, and at what rough volume. At portfolio level this is an aggregate view across projects, which is where hidden contention first shows up, two projects both assuming they own the same architect.
2. Estimate and match against supply
Turn the required roles into estimated effort, then compare that demand against the people and equipment you actually have. This is the point where the plan connects to resource and capacity planning, the method that tests whether the portfolio's demand is even feasible against supply before anyone is assigned.
3. Decide the acquisition approach
For any gap between demand and supply, decide how it will be closed: reassign internally, hire, or contract, and record who approves each route. Making this explicit up front prevents the default of quietly overloading the people you already have until delivery breaks.
4. Set the assignment and conflict rules
Define how named people get assigned to work and, crucially, what happens when they are over-allocated. This is where the plan points to resource allocation for the assignment mechanics and to resource leveling and smoothing for the two ways of resolving the over-allocations that assignment always produces.
5. Plan control, development, and release
Finish with how you will track that the plan is working (utilization and availability reporting), how skills gaps get closed, and how people are released back to the pool when work ends. A missing release step is why some organizations feel permanently short of people who are, on paper, no longer assigned to anything.
Resource management plan vs capacity plan
These two are often confused because they cover the same resources from different angles. The resource management plan is the governing document: it sets the rules, the roles, and the process. A capacity plan is a live comparison of demand against supply over time, usually a spreadsheet, that tells you whether the portfolio is over-committed right now. The plan is stable and qualitative; the capacity plan is dynamic and numeric.
| Resource management plan | Capacity plan | |
|---|---|---|
| What it is | The document that defines how resources are managed. | A live view of demand versus available supply. |
| Changes | Rarely, once set for a project or portfolio. | Continuously, as work and availability shift. |
| Form | A written plan or section. | Usually a spreadsheet or tool view. |
| Answers | How do we make resource decisions? | Do we have enough people right now? |
Common questions about resource management plans
What should a resource management plan include?
A resource management plan should include the roles and responsibilities the work needs (often as a RACI), the method for estimating resources, the approach for acquiring them, resource calendars showing availability, the rules for assigning and leveling people, plans for team development, how utilization is tracked, and how resources are released when work ends. Not every project needs all of these in depth, but a portfolio-level plan should address each.
What is the difference between a resource management plan and a resource plan?
A resource management plan is the governing document that defines how resources will be managed: the roles, rules, and processes. A resource plan is usually the narrower output, the actual list of who and what is assigned to a project over time. In short, the management plan sets the method and the resource plan carries the assignments, though in practice teams use the terms loosely and sometimes interchangeably.
Who owns the resource management plan?
On a single project the project manager owns the resource management plan, usually with input from resource or functional managers who control the people. At portfolio level the plan is typically owned by the PMO or a dedicated resource manager, because the value of a shared plan is precisely that it applies the same rules across projects that are competing for the same pool. Ownership matters most for the conflict-resolution rules, which need a named accountable decision maker.
How often should a resource management plan be updated?
The plan itself, the rules and roles, should be stable and only revisited when the operating model changes, for example when the organization adds a shared resource pool or changes how it contracts. The data it governs, the calendars and allocations, updates continuously. A good sign the plan needs a rewrite is recurring resource conflicts that the current escalation rules cannot settle, which means the process, not just the numbers, is out of date.
Where the plan fits
The resource management plan is the layer that makes the rest of resource management repeatable. Underneath it, capacity planning tests feasibility, allocation assigns the named people, leveling and smoothing resolve the clashes, and utilization tells you afterward whether the assumptions held. Without the plan, each of those happens differently on every project and the portfolio can never compare its people decisions on a common basis. Write it once, at the level where the resource pool is actually shared, and the weekly decisions get faster and more defensible.