Resource planning in project management is the process of working out which people, skills, tools and budget a project needs, when it needs them, and whether they are actually available. You then assign them to specific tasks. A good resource plan answers three questions before work starts: What do we need? Who is free to do it? What happens if they aren’t?
Effective resource planning keeps team members on the same page about who is working on what, protects project budgets, and gives you an early warning of potential resource shortages. This guide is for project managers and agency or consultancy leads who plan people across several client projects. It covers what a resource plan includes, a six-step resource planning process, a worked example you can copy, the techniques project managers use when resource demand and capacity don’t match, and how to choose resource planning software.
Key takeaways
- Resource planning turns a project scope into a schedule of named people, hours and costs.
- The hardest part is not listing resources. It is checking real resource availability, after meetings, leave and other projects.
- Plan with hours, not headcount: one person at 50% is not one resource.
- Compare planned hours with actual hours every week, and use the gap to estimate future projects.
What Is Resource Planning in Project Management?
Resource planning is a strategic process that sits between the project plan and day-to-day scheduling. The project plan says what will be delivered and by when. The resource plan says who and what will deliver it, in which weeks, and at what cost.
In project management, “resources” usually means four types:
| Resource type | Examples | What to plan |
|---|---|---|
| People (human resources) | Designers, developers, consultants, account managers | Skills, hours per week, availability, cost rate |
| Tools and equipment | Software licences, test environments, hardware | Quantity, when needed, lead time |
| Facilities | Meeting rooms, studios, site access | Booking dates |
| Financial resources | Labour budget, contractor budget, expenses | Spend by phase, contingency |
Equipment, facilities and money are tangible resources you can count. For most service teams, though, people are the constrained resource. Software can be bought in a day; a senior developer with the right skills can’t. That is why most of this guide focuses on planning people’s time, which overlaps with human resource management but is run by project managers, not HR.
Resource planning vs resource management vs capacity planning
These terms overlap, so it helps to separate them:
- Resource planning works out the resources required for a project and when.
- Resource allocation assigns specific people to specific tasks.
- Resource scheduling places those allocations on the calendar, week by week.
- Resource management is the whole cycle: planning, allocating, monitoring and adjusting across the project lifecycle.
- Resource capacity planning looks at the team level: how many hours the team has across all projects in the project portfolio, now and in future months. (See our guide to what capacity planning is.)
In short, resource planning in project management is about one project’s needs; capacity planning is about whether the team can take on the next one.
The PMBOK® Guide (6th edition) groups this work under Project Resource Management. Its processes start with Plan Resource Management and Estimate Activity Resources, then move to acquiring, developing, managing and controlling resources.
Why Is Resource Planning Important?
Projects rarely fail because nobody knew the scope. They fail because the people needed for that scope were already busy. Poor resource planning shows up as:
- Resource conflicts: two project managers book the same specialist for the same week.
- Resource shortages: a phase starts and the required skill isn’t available.
- Overload and burnout: the same few team members absorb every urgent task.
- Budget overruns: extra hours, contractors or rush work push project costs up.
- Resource bottlenecks: one overloaded reviewer or specialist holds up task progress for everyone else.
- Missed project milestones: one late hand-off delays everything after it.
Proper resource planning helps you:
- Deliver projects on time, because availability is checked before dates are promised.
- Control project budgets, because labour cost is estimated by role and hours, not guessed.
- Balance workloads, so work is spread across the project team instead of landing on the same people.
- Spot resource gaps early, while there is still time to hire, train or bring in a contractor.
- Plan future projects better, because actual hours from previous projects become your estimating data.
None of this guarantees project success, but it removes the most common reason projects slip: assuming people are available when they aren’t.
What Should a Resource Plan Include? Key Components
A resource plan does not need to be a long document. For most projects, one spreadsheet or tool view with these key components is enough:
| Component | What it answers | Example |
|---|---|---|
| Project objectives and deliverables | What are we resourcing? | Website redesign: discovery, design, build, launch |
| Resource requirements | Which roles and skills, how many hours? | UX designer, 72 hours over 6 weeks |
| Resource availability | Who is actually free? | Ana: 22 h/week after other projects and meetings |
| Allocation and schedule | Who does what, when? | Ana → wireframes, weeks 2–3 |
| Resource costs | What will it cost? | 72 h × cost rate |
| Risks and contingency | What if someone isn’t available? | Backup designer identified; 10% buffer |
| Monitoring plan | How will we track resource usage? | Weekly planned-vs-actual hours review |
Resource plan vs resource management plan
People often use these interchangeably, but they are different documents:
- A resource plan is the working schedule: roles, people, hours, dates and costs.
- A resource management plan is the rulebook. It describes how resources will be identified, acquired, managed and released, who approves changes, and how performance is reviewed. On formal or PMP-style projects, it is part of the overall project management plan.
Small teams usually only need the resource plan. Larger or regulated projects need both.
The Resource Planning Process: 6 Steps
Here is a resource planning process that works for a single project or for multiple projects that share the same team. Steps 1–3 are resource identification and estimation, steps 4–5 allocate and schedule resources, and step 6 is resource monitoring.
Step 1: Define the project scope and objectives
Start with the project requirements, not the people. Break the project deliverables into tasks using a work breakdown structure (WBS). For each deliverable, write down:
- What “done” looks like
- Which skills it needs
- Any fixed dates or project milestones
- What is out of scope
A clear project scope stops scope creep from silently eating your resource plan later.
Step 2: Estimate resource requirements
For each task, estimate the hours and the skill needed. Estimate in hours by role, not by person yet. For example, “Senior developer: 60 hours” rather than “Raj”.
Ways to estimate:
- Previous projects: the most reliable method. Look at the actual hours similar work took, not what was quoted.
- Expert judgement: ask the people who will do the work.
- Three-point estimates: best case, most likely and worst case, then use the average or a weighted average.
Add a contingency buffer. How large depends on how new the work is to your team. At the end of this step you should have a list of all the resources needed, with hours by role and week.
Step 3: Check real resource availability
This is where most resource plans go wrong. A person working 40 hours a week does not have 40 hours for your project. Subtract:
- Hours committed to other projects
- Recurring meetings and internal work
- Planned leave and public holidays
- Admin, sales or support time
What is left is their real resource capacity. Write it down per week, not per month, because project demands are rarely even. Then compare existing resources with what the project needs. Any shortfall is a resource gap you need to close by hiring, contracting, training or changing the plan.
Tip: Calendar data is one of the fastest ways to see real availability. If someone’s week already has 14 hours of recurring meetings, those hours are not available for project work, whatever the plan says.
Step 4: Allocate resources and build the schedule
Now allocate resources: match people to tasks. Resource allocation should be based on:
- Skills: who can do the work to the required standard?
- Availability: who has hours in those weeks?
- Cost: can a less senior person do part of it?
- Development: is this a chance for someone to learn a new skill under supervision?
Then place the work on the project timeline. Note dependencies, for example “design must finish before build starts”, because a delay in one person’s task moves everyone after them. A visual project schedule (a Gantt chart or a weekly allocation grid) makes conflicts easy to see.
If you plan in a spreadsheet, our free resource allocation template for Excel gives you a weekly grid with formulas that flag over-allocation.
Step 5: Resolve conflicts with leveling and smoothing
When you lay the allocations side by side, some weeks will be over 100% for some people. You have three main options:
| Technique | What it does | Effect on end date | Use when |
|---|---|---|---|
| Resource leveling | Moves tasks so no one is over-allocated | May push the end date out | People are the hard limit |
| Resource smoothing | Moves tasks only within their float (slack) | End date stays the same | The deadline is fixed |
| Reallocation or adding resources | Gives work to someone else, or brings in a contractor | Can protect the date, but adds cost | Budget allows and skills exist |
If none of these work, the honest option is to change the scope or the date and tell stakeholders now, not in week six.
Step 6: Monitor resource utilization and resource performance
Once work starts, the plan is a forecast. As the project progresses, compare each week:
- Planned hours vs actual hours by person and task
- Resource utilization: hours worked on project tasks ÷ available hours
- Remaining work against remaining capacity
If a task is running over, decide early whether to add hours, move a date or cut scope. Keep the actual hours. They are the best input you will have for estimating the next project. (Our guide to calculating utilization rate explains the formulas.)
Resource Planning Example: A 6-Week Website Project
Here is a simple example of resource planning for a small agency project. The numbers are illustrative.
Project: Redesign a client website in 6 weeks. Team: a project manager, a UX designer, two developers and a copywriter.
Step 2 – Estimated resource requirements (hours by role):
| Role | Discovery (wk 1) | Design (wk 2–3) | Build (wk 4–5) | Launch (wk 6) | Total |
|---|---|---|---|---|---|
| Project manager | 8 | 8 | 8 | 8 | 32 |
| UX designer | 10 | 50 | 10 | 2 | 72 |
| Developer (×2) | 2 | 10 | 120 | 20 | 152 |
| Copywriter | 4 | 24 | 6 | 2 | 36 |
Step 3 – Real availability check:
| Person | Contract hours/week | Other projects | Meetings and admin | Available for this project |
|---|---|---|---|---|
| Ana (UX) | 40 | 10 | 8 | 22 |
| Raj (Dev) | 40 | 12 | 6 | 22 |
| Mia (Dev) | 40 | 0 | 6 | 34 |
What the plan shows:
- Design is over-allocated. Ana is needed for 50 hours in weeks 2–3 but has only 44 (22 × 2). Options: start design work in week 1, move 6 hours of UI work to a developer, or push design out by two days (resource leveling).
- Build is over-allocated. The two developers have 112 hours in weeks 4–5 (56 × 2) against 120 hours of work. Mia has more room than Raj, so she takes the larger share, and the extra 8 hours either use the week 6 buffer or come from a small scope cut agreed with the client.
- Budget. Multiply each role’s hours by its cost rate to get the labour budget, then add contingency.
Without step 3, this plan would have looked fine on paper and slipped in week 3.
Resource Planning Techniques and Best Practices
1. Plan capacity before you commit to work
Check team capacity before a proposal or quote goes out, not after the contract is signed. If the team is already at 90% for the next two months, a new project means hiring, contractors or a later start date.
2. Plan by role first, then by person
Estimating by role (“senior designer, 40 hours”) keeps the plan valid if a specific person leaves or is reassigned. Assign names at step 4.
3. Don’t plan anyone at 100%
People need time for email, internal meetings, support and context switching. Planning project work at 100% of contract hours guarantees overruns. Use each person’s real availability from step 3.
4. Use one shared view to manage resources across multiple projects
When several project managers draw on the same pool of team members, a separate project plan for each creates hidden resource conflicts. Keep one shared view of who is booked where, even if it’s a simple shared spreadsheet. Whoever owns it acts as the team’s resource planner.
5. Review weekly, not at the end
A weekly 15-minute review of planned vs actual hours catches problems while they are still small. Quarterly reviews only tell you what already went wrong.
6. Feed actuals back into estimates
Teams that track actual time per project and task estimate the next project from evidence, not memory. Over time, this is the single biggest improvement to resource planning accuracy.
Common Resource Planning Challenges (and Fixes)
| Challenge | Why it happens | Fix |
|---|---|---|
| Inaccurate estimates | Based on quotes, not actual hours | Use time data from previous projects |
| Hidden availability | Meetings and other projects aren’t in the plan | Check calendars and other bookings at step 3 |
| Shifting priorities | People get pulled onto urgent work | Agree priority rules for shared resources upfront |
| Too many projects at once | Sales commits without checking capacity | Make a capacity check part of every proposal |
| No visibility across teams | Each PM plans in a separate file | Use one shared resource view |
Resource Planning Tools: What to Use
The right resource planning tools depend on team size and how many projects share the same people. Here are the main resource management software options, from simplest to most complete.
| Option | Good for | Watch out for |
|---|---|---|
| Spreadsheet (Excel or Google Sheets) | One team, a few projects, simple weekly allocation | Manual updates; breaks down with many projects |
| Project management software (a project management tool with workload views) | Teams that already plan tasks there | Workload views are often basic; actual hours may be missing |
| Dedicated resource management software (for example Float, Runn, Resource Guru) | Many projects sharing a pool of people; forecasting future demand | Another tool to keep updated; cost per user |
| Time and calendar data | Seeing actual hours and real availability | Shows what happened; you still need a schedule |
Features worth looking for in resource planning software:
- A view of availability across multiple projects
- Skills or role filters, so you can match resources to tasks
- Planned vs actual hours, or an integration with your time tracking
- Forecasting for future projects and tentative work
- Utilization reporting by person and team
For a side-by-side comparison of 14 options, see our guide to resource capacity planning tools.
Where Tackle fits (our product)
Tackle is our product, so take this section with that in mind.
Tackle is not a resource scheduler. It doesn’t replace a Gantt chart or a booking tool like Float or Runn, and if you need drag-and-drop scheduling, a dedicated resource management tool is the better choice. What Tackle does is give your resource plan real data for steps 2, 3 and 6:
- Actual hours from calendars: Tackle reads Google Calendar and Outlook Calendar events. For Google Calendar, access is read-only, and Tackle never edits or deletes events.
- Time by client, project and activity: keyword rules tag events automatically (for example, any event containing “acme” goes to Client: Acme), so you can see where time went without timesheets.
- Past and future commitments: because calendars include upcoming meetings, you can see how much of next week is already booked before you allocate work. See how Tackle supports resource planning.
- Exports: send the data to Google Sheets, Excel, CSV or PDF, or into your planning spreadsheet.
Tackle is SOC 2 Type II certified.
Frequently Asked Questions
What is a resource plan for a project?
A resource plan lists the people, skills, tools and budget a project needs, when they are needed, who will provide them and at what cost. At minimum it includes resource requirements by role, availability, allocation by week, and a budget.
What are the three main stages of resource planning?
Most frameworks group it into three stages: (1) identify and estimate the resources needed, (2) allocate and schedule them against real availability, and (3) monitor and adjust as the project progresses.
What are the steps of resource planning?
Define the scope, estimate resource requirements, check real availability, allocate and schedule, resolve conflicts with leveling or smoothing, then monitor resource utilization and adjust.
What is the difference between resource allocation and resource leveling?
Resource allocation assigns people and tools to specific tasks. Resource leveling comes afterwards: it moves tasks so that no one is over-allocated, even if that pushes the end date out.
Can you give an example of resource planning?
A six-week website project needs 72 hours of UX design, mostly in weeks 2–3. The designer has only 22 hours a week free after other projects. The resource plan shows the shortfall before the project starts, so the PM can start design earlier, share UI work with a developer, or move the date.
How often should a resource plan be updated?
Review it weekly while the project is running, and whenever scope, priorities or team members change.
What is the 80/20 rule for project managers?
The Pareto principle says roughly 80% of results come from 20% of causes. In resource planning, it usually means a few constrained roles or people drive most delays, so plan and protect their time first.
What is the best tool for resource planning?
There is no single best tool. Small teams often start with a spreadsheet. Teams running many projects with shared people usually move to dedicated resource management software and connect it to actual time data.
Conclusion
Effective resource planning in project management comes down to one discipline: matching the work you have promised with the hours your people really have. Define the scope, estimate by role, check real availability, allocate, resolve conflicts and review weekly. Then keep your actual hours, because they make the next plan more accurate.
Want to see where your team’s time is really going before you plan the next project? Try Tackle for free.