This guide covers everything you need to know about resource requirements in PMBOK 8. Resource requirements document what resources — in what types, quantities, and time periods — are needed to complete each project activity and the project as a whole. They are the bridge between the project schedule and the resource acquisition process.
What Are Resource Requirements?
Resource requirements are the identified types and quantities of resources required to perform each scheduled activity or work package. They specify what human skills, what physical assets, and what virtual resources are needed, for how long, and with what level of capacity. Resource requirements answer the fundamental staffing and procurement question: “What do we need, and how much of it?”
Resource requirements are expressed at the activity level (what does this specific task need?) and then aggregated to the work package, phase, and project level. This aggregation enables the project manager to identify peak demand periods where resource needs exceed available supply — resource conflicts that must be resolved before the schedule can be finalized.
Resource requirements are also the primary input to cost estimation: once you know what resources are needed and for how long, you can calculate the resource cost by applying unit rates and hours.
Resource Requirements in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, resource requirements belong to the Resources Performance Domain and are produced during the Estimate Resources process. PMBOK 8 treats resource estimation as an integrated activity that must consider not just what resources are theoretically needed but what resources are realistically available given organizational constraints.
Resource requirements feed into resource acquisition (confirming what needs to be procured or assigned), cost estimation (translating resource needs to cost), and the project schedule (validating that planned activities have the resources needed to execute on schedule).
Key Elements of Resource Requirements
Well-structured resource requirements typically include:
- Activity or Work Package Reference — the scope element the requirements apply to
- Resource Type — human (role/skill), equipment, material, or virtual resource
- Quantity and Unit — hours, days, units, licenses needed
- Required Start and End Dates — when the resource is needed
- Required Skills or Specifications — the qualifications or technical specifications the resource must meet
- Basis for Estimate — how the requirement was derived
Resource Requirements Example — Project Phoenix
The Project Phoenix resource requirements were developed through bottom-up estimation at the activity level and then aggregated by WBS package. The Development package required the highest human resource load: 200 hours of frontend and full-stack development (Sam Lee) and 120 hours of backend development (John Tran) over an eight-week sprint period. The Design package required BrightFrame’s designer for approximately 180 hours over six weeks, plus 24 hours of Alex Morgan’s coordination time.
The peak resource demand period was weeks 7-12 (the development sprint), when Sam Lee was at 90% allocation, John Tran was at 60% allocation, and Alex Morgan was at 80% allocation managing execution and communications. This peak was identified during resource requirements estimation and resolved by confirming Sam Lee’s manager’s approval of the 90% allocation before the schedule was baselined. The resource requirements document was used directly as the input to both the resource acquisition conversations and the cost estimation workbook.
You can download the complete filled-in example below — it shows exactly how resource requirements were estimated and documented for a real project.
Download Free Resource Requirements Template and Example
We have prepared two free resources to help you estimate and document resource requirements on your own projects:
- Download the Resource Requirements Template — PMBOK 8 (blank, ready to fill in)
- Download the Resource Requirements Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Resource Requirements — Best Practices and Common Mistakes
Estimate resource requirements collaboratively with the team members who will do the work — they know better than anyone how many hours a task actually requires. Aggregate requirements to identify peak demand periods and resolve resource conflicts during planning, not during execution. Document the basis for each estimate so that requirements can be updated defensibly when scope changes.
The resource requirements document is most effective when it is integrated with the project schedule so that resource loading can be visualized over time. Teams that skip or rush resource estimation often find themselves with resource shortfalls mid-project that were entirely predictable.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Free Template & Filled-In Example
Apply what you’ve learned with these two free resources:
- Download the Free Resource Requirements Template (PMBOK 8) — Ready-to-use blank template for your next project.
- Download the Filled-In Example — Project Phoenix — See exactly how this document was completed for a real $72K website launch project.
Project Management