A resource management plan template is the file that records what and who the work needs, when it needs them, who approves an assignment, and what happens when two projects want the same person in the same week. Four tabs cover it: a resource register, a demand grid, a capacity line, and the rules. Everything else people bolt on is usually reporting that belongs somewhere else.
This page is the artifact. For the reasoning behind each section, what the plan is actually for, and where it sits in planning, read what a resource management plan contains first, then come back and build the file.
Key takeaways
- Four tabs: resource register, demand grid, capacity, rules. A fifth tab is nearly always a report that should live in your dashboard instead.
- Plan in named roles before named people. Name the person only where the work genuinely cannot be done by anyone else.
- Hours or FTE, pick one and use it everywhere. Mixed units is the single most common reason a resource plan quietly stops being trusted.
- The template is worthless without a capacity row underneath the demand. Demand with no supply line is a wish list.
- Write the conflict rule down before you have a conflict. Whoever arbitrates, name them by role in the file.
- Excel for anything with numbers in it. Word only for the narrative plan that goes in a project pack.
- Update it on the same cadence as your portfolio review, not when someone remembers.
Last updated July 2026.
What a resource management plan template contains
A resource management plan template contains the resources the work needs, the periods it needs them in, the capacity available in those periods, and the rules for resolving the gap. Below is the section list, and what earns each one its place in the file.
| Section | What goes in it | Why it earns a place |
|---|---|---|
| Plan header | Project or portfolio name, version, owner, date, review cadence | Resource plans get emailed around. Without a version and a date you will end up arguing from two different files. |
| Resource register | Every role and asset the work needs, with skill, source, rate and availability | The one list everything else references. Build it once, point at it everywhere. |
| Demand grid | Hours or FTE per role per period | This is the plan. Everything above is setup and everything below is governance. |
| Capacity line | Available hours per role per period, net of leave and run work | Turns the grid from a request into a decision. Without it nothing is ever infeasible. |
| Gap and actions | Shortfall per role, and the named response (hire, contract, defer, descope) | A red cell with no owner is a complaint. A red cell with an action and a date is a plan. |
| Roles and responsibilities | RACI for assignment, approval, escalation and release | Most resource fights are authority disputes wearing a scheduling costume. |
| Rules and assumptions | Conflict rule, booking horizon, utilization target, working hours assumed | The numbers mean nothing without the assumptions that produced them. |
The four tabs a resource management plan template needs
Build it as four tabs rather than one enormous sheet. Cross-tab lookups are easier to repair than a single grid that someone has merged cells into.
| Tab | Purpose | Key columns |
|---|---|---|
| 1. Register | The catalog of roles, people and assets available to the work | Resource ID, role, name (optional), skill, source, cost rate, weekly hours, start and end availability |
| 2. Demand | What the work needs, by role, by period | Resource ID, project or workstream, period columns (week or month), hours per period |
| 3. Capacity | What is genuinely available in the same periods | Resource ID, gross hours, leave, run and support allowance, net available hours, gap |
| 4. Rules | The governance that makes the numbers binding | RACI, conflict rule, escalation path, assumptions, change log |
Use the same Resource ID column on all four tabs. That single discipline is what lets you rebuild any view later without retyping anything, and it is what makes a resource breakdown structure easy to bolt on if the portfolio grows enough to need categories.
Resource register columns
The register is where people over-engineer. These columns are enough for a portfolio of thirty or forty projects.
| Column | Example | Note |
|---|---|---|
| Resource ID | R-014 | Never reuse an ID, even after someone leaves. |
| Role | Senior backend engineer | Plan in roles. Names come later and only where they matter. |
| Name | Blank, or the person | Leave blank for anything more than a quarter out. Named plans age badly. |
| Skill or specialism | Payments integration | The reason substitution is not always possible. This column prevents a lot of naive reshuffling. |
| Source | Internal, contract, vendor, shared service | Drives lead time. A contractor at six weeks notice is not the same resource as someone on the team. |
| Cost rate | Hourly or daily | Lets the same sheet produce a resource cost estimate without a second model. |
| Standard weekly hours | 40 | Write the assumption down. Half the disputes about utilization are really disputes about this number. |
| Available from / to | Dates | Covers ramp-up, notice periods, fixed-term contracts and known departures. |
The formulas that make the template work
Three formulas do almost all of the work. They are the same in Excel and Google Sheets.
Total demand per resource per period. On the capacity tab, pull the demand grid into one number per role per period:
=SUMIFS(Demand!$D:$D, Demand!$A:$A, $A2, Demand!$C:$C, D$1)
That reads: sum the hours column where the Resource ID matches this row and the period matches this column header. Keep periods as real dates in the header row, not text like "Wk 32", or every date function downstream will fail.
Net available capacity. Gross hours minus leave minus the standing allowance for run work and support:
=(Standard_Hours * Weeks_In_Period) - Leave_Hours - (Standard_Hours * Weeks_In_Period * Run_Allowance)
The run allowance is the number teams forget. If your engineers spend a fifth of their week on production support, planning against 100 percent of their hours guarantees the plan misses. Twenty to thirty percent is a common starting assumption, and you should replace it with your own measured figure as soon as you have one.
The gap. Capacity minus demand, formatted so a negative number is impossible to miss:
=Net_Available - Total_Demand
Then apply conditional formatting on the gap row: red below zero, amber between zero and ten percent of capacity, no fill above that. Do not color the demand cells themselves. Coloring demand tells you the plan is busy; coloring the gap tells you the plan is impossible, which is the only thing anyone needs to act on. If you want the same picture as a chart, that is a resource histogram.
A worked resource management plan example
Six roles, one quarter, monthly periods, hours. The numbers are illustrative, but the shape is what a real one looks like.
| Resource | Net capacity / mo | Jul demand | Aug demand | Sep demand | Worst gap |
|---|---|---|---|---|---|
| R-01 Backend engineer | 128 | 96 | 150 | 140 | -22 (Aug) |
| R-02 Backend engineer | 128 | 110 | 128 | 120 | 0 |
| R-03 Data engineer | 128 | 60 | 72 | 176 | -48 (Sep) |
| R-04 QA lead | 112 | 80 | 104 | 112 | 0 |
| R-05 Business analyst | 136 | 136 | 144 | 96 | -8 (Aug) |
| R-06 Solution architect | 64 | 72 | 80 | 40 | -16 (Aug) |
Read it the way a portfolio lead would. August is over-committed across three roles at once, which is a portfolio problem rather than a scheduling one, and no amount of moving tasks inside August fixes it. September is a single deep hole in one specialism, which is a different problem with different answers: hire, contract, or move the milestone that created the spike.
The gap column is also the honest input to your resource forecast. A shortfall you can name three months out is a hiring decision. The same shortfall found two weeks out is an escalation, and by then your options are down to descoping or paying a premium for contract cover.
The roles and responsibilities section
The tab most templates skip, and the one that decides whether the file survives contact with a real disagreement. Write four rows, name them by role, and get the resource owners to agree before you need it.
| Decision | Responsible | Accountable | Consulted |
|---|---|---|---|
| Assigning a person to a project | Resource or line manager | Functional head | Project manager |
| Approving over-allocation beyond the threshold | PMO lead | Portfolio owner | Line manager, project manager |
| Resolving a conflict between two projects | PMO lead | Portfolio owner | Both sponsors |
| Releasing a resource back to the pool | Project manager | Resource manager | Line manager |
The conflict rule needs one sentence, written in advance: when two projects need the same resource in the same period and neither can move, the higher-ranked project in the current portfolio ranking wins, and the other project logs a dated impact. That sentence is what stops the argument being settled by whoever emails hardest. Where that ranking comes from is a separate discipline, covered in how to prioritize a project portfolio.
Excel or Word: which format for a resource management plan template?
Both, for different jobs. The confusion comes from the plan being two things at once: a narrative document that explains the approach, and a model that holds numbers.
| Excel or Sheets | Word or Docs | |
|---|---|---|
| Best for | Register, demand, capacity, gaps, rates | Approach, assumptions, RACI, acquisition and release strategy |
| Updated | Weekly or monthly | Once per phase, or on material change |
| Read by | PMO, resource managers, project managers | Sponsor, steering committee, audit |
| Fails when | Nobody owns the refresh and it goes stale | It describes a process nobody follows |
If you only have appetite for one, build the spreadsheet. A stale narrative is embarrassing; a stale grid actively misleads people into committing work that cannot be delivered.
Is there an official PMI resource management plan template?
PMI does not publish a single official fill-in template that you must use. The PMBOK Guide describes the resource management plan as an output of planning and sets out what it should address (identifying, acquiring, managing and releasing resources, plus roles, responsibilities and team development), then leaves the format to you. Any "PMI resource management plan template" you download is somebody's interpretation of that content, which is fine, as long as you know that is what it is.
One naming point worth knowing, because it explains why half the templates online are called something else: earlier editions of the PMBOK Guide called this the human resource management plan. It was broadened and renamed to the resource management plan to cover equipment, materials and facilities alongside people. If you inherit a "human resource management plan template" from an older methodology, it is the same document with a narrower scope.
Common questions about resource management plan templates
What is a resource management plan template?
A resource management plan template is a reusable file, usually a spreadsheet, that structures how a project or portfolio identifies, acquires, allocates and releases resources. It holds a resource register, a demand grid by period, the available capacity, the resulting gaps, and the rules for who resolves a conflict when two projects need the same person.
What should a resource management plan include?
It should include the resources the work needs by role, the periods they are needed in, the capacity actually available in those periods, the gap between the two, the named response to each gap, and the roles and responsibilities for assignment, approval, escalation and release. Add the assumptions behind the numbers, especially assumed working hours and the allowance for run work.
Is a resource management plan the same as a human resource management plan?
Effectively yes, with a wider scope. The PMBOK Guide previously used "human resource management plan" for the people-focused version, then renamed and broadened it to "resource management plan" so it also covers equipment, materials and facilities. Templates carrying the older name are usually people-only, so check for an equipment and materials section before reusing one.
What is the difference between a resource management plan and a resource plan?
The resource management plan sets the approach: how resources will be estimated, acquired, assigned, controlled and released, and who decides. A resource plan is the resulting schedule of who is doing what, when. One is the rules of the game, the other is this season's fixture list, and the rules change far less often.
Should I plan in hours or FTE?
Pick one and use it in every cell. Hours suit shorter projects and detailed scheduling. FTE suits portfolio and quarterly planning, where hour-level precision is false confidence. Mixing them in one file is the fastest way to lose the trust of the people whose availability you are modeling, because two readers will compute different answers from the same sheet.
Who fills in the resource management plan template?
The project manager drafts the demand, the resource or line managers own the capacity and the register, and the PMO owns the consolidated view and the conflict rule. If one person fills in every tab, the capacity numbers are guesses, and everyone downstream will treat them that way.
How often should a resource management plan be updated?
Refresh the demand and capacity tabs on the same cadence as your portfolio review meeting, typically monthly, with a lighter weekly check on the current and next period. Update the rules and RACI tab only when the governance actually changes. Anything more frequent turns into administration nobody reads.
Where this file fits
The template is one artifact in a set. Feed the demand grid from your project schedules, feed the capacity from your line managers, and feed the resulting picture up into resource capacity planning across a portfolio, where the same numbers get compared against the portfolio you have committed to. If you need the multi-project version of the capacity tab specifically, the capacity planning template covers that build in detail.
Two neighboring pages are worth having open while you fill this in: resource allocation in project management for the assignment decisions, and resource leveling versus smoothing for what to do about the red cells once the gaps appear. If your utilization targets look implausible once the run allowance is in the sheet, resource utilization explains why the number you were given is probably wrong.