Acquire Resources in PMBOK 8 — Complete Guide

Article updated in March 2026 for the PMBOK® Guide — Eighth Edition.

Acquire Resources in PMBOK 8 — Complete Guide

Formerly known as: Acquire Resources (PMBOK 6)

Three weeks before the critical path milestone, the project manager for a major financial system upgrade received a message she had been dreading: the senior database architect, whose name appeared on 14 RACI matrix assignments, had just accepted a position at another firm and would leave in two weeks. She had no backup. No documented alternative. No negotiated agreement with a consulting firm. The search for a replacement took six weeks, the project slipped by four months, and the cost overrun exceeded $180,000. Every team member who had been waiting for database architecture approvals had spent those weeks in partial productivity.

Acquiring resources is not an event — it is a process that must be managed with the same discipline as scope or schedule. In PMBOK 8, Acquire Resources is Process 2 of the Resources Domain. It is the process of obtaining the team, physical, and virtual resources necessary to complete the project work. The key benefit of this process is that it outlines and guides the selection of resources and assigns them to their respective activities. Without a structured approach to acquiring resources, every gap in the project team is a schedule risk waiting to materialize.

This complete guide covers everything a project manager or PMP candidate needs to understand, apply, and tailor the Acquire Resources process in PMBOK 8:

• What it is — definition, position in PMBOK 8, and key distinctions
• Why use it — benefits and the consequences of ad hoc resource acquisition
• Full ITTO — every input, tool, technique, and output explained
• Step-by-step application guide — from resource requirements to project team assignments
• When to apply it — triggers across the project lifecycle
• Two real-world examples — Project Phoenix and Project ProjectAdm
• Templates and tools — with free downloads
• Five common errors — and how to avoid each one
• Tailoring — predictive, agile, and hybrid approaches
• Process interactions — what feeds in and what depends on acquire resources
• Quick-application checklist — 10 items you can use today

1. What Is the Acquire Resources Process

Acquire Resources is the process of obtaining team members, physical resources, and virtual resources necessary to complete the project work, based on the activity list and the resource management plan. According to PMBOK 8, the key benefit of this process is that it outlines and guides the selection of resources and assigns them to their respective activities.

This process is performed periodically throughout the project as needed — not just at the beginning. Resources are acquired when the project schedule indicates they are needed and released when their contribution is complete. This periodic nature makes Acquire Resources one of the most continuously active processes in the Resources Domain, particularly in large projects where team composition changes as different phases require different specializations.

PMBOK 8 makes an important distinction within this process: acquiring human resources (team members) involves different considerations than acquiring physical or virtual resources (equipment, materials, software, infrastructure). Human resource acquisition involves negotiation with functional managers, selection criteria, onboarding planning, and interpersonal skill dynamics. Physical and virtual resource acquisition may involve procurement processes, vendor selection, delivery scheduling, and contract management. The resource management plan governs both dimensions.

When the required team members or physical/virtual resources are not available due to constraints — economic factors, competing projects, regulatory limitations — the project manager may be required to assign alternative resources with different competencies, features, or costs. Alternative resources are acceptable if risks are acknowledged and legal, regulatory, mandatory, or other specific criteria are not violated. This acknowledgment must be documented and approved.

2. Why Use the Acquire Resources Process

Structured resource acquisition is the difference between a team that can deliver and a team assembled from whoever was available. The direct benefits of applying this process rigorously include:

• Right-fit selection: Using multicriteria decision analysis, the project team selects resources based on competency, availability, cost, experience, and cultural fit — not just convenience. Right-fit resources reduce rework, reduce onboarding time, and increase team cohesion from day one.
• Documented assignments: Project team assignments and physical/virtual resource assignments create clear accountability records. When questions arise about who was responsible for a deliverable or who committed a specific resource, the answer is documented.
• Proactive conflict identification: The negotiation process for internal resources surfaces competing commitments before they become schedule conflicts. A conflict identified during negotiation can be resolved in days; the same conflict discovered during execution costs weeks.
• Calendar accuracy: Resource calendars produced by this process give the schedule model accurate availability data — vacation periods, part-time allocations, shared assignments, and planned absences. Schedules built on realistic resource calendars outperform those built on theoretical full-time availability.
• Contingency through virtual teams: Virtual team structures expand the talent pool beyond geographic constraints, enabling the project to acquire specialized resources that are not available locally.

3. Inputs, Tools & Techniques, and Outputs (ITTO)

The following table presents the complete ITTO of the Acquire Resources process as defined in PMBOK 8:

Inputs explained

Resource management plan: The primary governing document for resource acquisition, defining the acquisition approach, selection criteria, onboarding process, and constraints. The resource management plan tells the project team exactly how resources should be acquired — which roles must be filled internally, which can be sourced externally, what skills are required, and what the approved budget envelope is for each resource category.

Procurement management plan: For physical and virtual resources that require formal procurement, the procurement management plan defines the procurement process, contract types, supplier selection criteria, and approval requirements. Integrating the procurement plan with the resource acquisition process ensures that physical resource acquisition follows the organization’s governance requirements and leverages established vendor relationships.

Cost baseline: The approved budget for the project constrains resource acquisition decisions. When the preferred resource exceeds budget, the project team must either negotiate a lower rate, identify an alternative resource, or submit a change request to adjust the cost baseline. Resource acquisition decisions that are not grounded in the cost baseline produce budget overruns that surprise sponsors at the worst possible moments.

Project schedule and resource calendars: The project schedule defines when each resource is needed and for how long. Resource calendars show the existing availability of candidate resources — their other commitments, planned absences, and allocation constraints. Aligning acquisition timing with the schedule prevents the common error of acquiring resources weeks before they are needed (paying for idle time) or acquiring them after they were needed (causing schedule delays).

Resource requirements: The output of the Estimate Resources process, resource requirements document the type, quantity, and characteristics of resources needed for each project activity. This document is the direct purchasing specification for the acquisition process: it tells the PM exactly what to ask for when negotiating with functional managers or issuing procurement requests.

Tools & Techniques explained

Multicriteria decision analysis: A structured evaluation technique that scores candidate resources against multiple weighted selection criteria. Typical criteria for human resource acquisition include: availability (can the person start when needed?); cost (is the rate within the approved budget?); experience (has the person done similar work before?); skill match (do they have the specific technical skills required?); cultural fit (are they aligned with the team’s working style?); and references or track record. Multicriteria decision analysis removes subjectivity from selection decisions and produces a documented, defensible rationale for every resource choice.

Negotiation: One of the most critical skills in resource acquisition. In matrix and functional organizations, the project manager does not have direct authority to assign team members — they must negotiate with functional managers who control their staff’s time. Effective negotiation in resource acquisition involves: clearly articulating the project’s requirements and impact; understanding the functional manager’s constraints and competing priorities; proposing solutions that meet the project’s needs without unreasonably burdening the functional manager; and documenting agreements in writing to prevent later disputes. Negotiation failures are one of the most common root causes of resource gaps in execution.

Problem-solving: When the preferred resource is unavailable, the project manager must solve the resource gap problem creatively. Solutions include: splitting the role between two part-time resources; training an internal resource to fill the gap; restructuring the work sequence to delay the need for the unavailable resource; engaging an external consultant; or formally adjusting the scope to remove work that requires the unavailable skill.

Preassignment: Some resources are designated for the project before the formal acquisition process begins — the sponsor may have committed specific individuals, the project may be part of a contractual obligation that specifies key personnel, or the project may be for a client who has named specific consultants. Preassigned resources are accepted as inputs to the acquisition process and documented in the project team assignments and resource calendars.

Virtual teams: Virtual team structures enable the project to acquire resources beyond geographic boundaries. Benefits include access to specialized skills not available locally, cost advantages from lower-cost talent markets, and extended working hours through time zone distribution. Challenges include communication coordination, building trust without face-to-face contact, and managing performance across multiple time zones. The resource management plan and team charter must explicitly address the virtual dimension when virtual teams are used.

Outputs explained

Project team assignments: The document that formally records which individuals are assigned to the project, their roles, the start and end dates of their assignment, and their allocation percentage. Project team assignments are the authoritative source for who is on the project team and in what capacity. They are used to build resource calendars, update the project schedule, and provide the basis for performance assessments.

Physical or virtual resource assignments: The equivalent document for non-human resources. This document records what physical and virtual resources have been assigned or procured for the project, when they are available, their specifications, and their costs. Physical or virtual resource assignments are used to update the project schedule, track actual versus planned resource usage in the Monitor and Control Resourcing process, and support procurement closeout at the end of the project.

Resource calendars: Updated resource calendars reflect the confirmed availability of all assigned resources — incorporating their actual working days, vacation periods, part-time allocations, shared assignments across multiple projects, and any other availability constraints. Accurate resource calendars are the foundation of realistic schedule models.

↓ Free resource assignments template and resource calendar template available at Project Team Assignments Template and Resource Calendars Template.

4. Step-by-Step Application Guide

Step 1 — Review resource requirements and create acquisition criteria

Start with the resource requirements document and the resource management plan. For each required resource, define the acquisition criteria: minimum required skills, experience level, availability window, and budget constraint. Create a weighted evaluation scorecard for human resources that reflects the relative importance of each criterion in this project context.

Step 2 — Identify and evaluate internal candidates

For human resources, identify all internal candidates and evaluate them against the acquisition criteria using the multicriteria decision analysis scorecard. Meet with functional managers to confirm availability and negotiate allocation percentages. Document every negotiation outcome — commitments made, conditions, and any known constraints on the commitment.

Step 3 — Initiate procurement for external and physical resources

For resources that cannot be sourced internally, initiate the appropriate procurement process per the procurement management plan. Issue requests for proposals or quotations for physical materials and equipment. Engage staffing agencies or consulting firms for external human resources. Evaluate proposals against the multicriteria scorecard and document the selection rationale.

Step 4 — Document assignments and create resource calendars

Once resources are confirmed, create or update project team assignments and physical/virtual resource assignments. Build resource calendars for each assigned resource, incorporating all known availability constraints. Load the resource calendars into the scheduling tool to generate an updated, resource-constrained project schedule.

Step 5 — Update the risk register and project management plan

Where the acquired resources differ from what was planned (lower skills, partial availability, higher cost, alternative vendor), create or update risk register entries to document the impact. Submit change requests where the cost baseline or resource management plan requires formal updating. Communicate assignment confirmations to all team members and functional managers.

5. When to Apply This Process

Acquire Resources is performed periodically throughout the project, not just during initial planning. Key triggers include:

• Project startup: Initial acquisition of the core project team and key physical resources
• Phase transition: Acquiring specialized resources needed for the new phase (e.g., testing engineers for the testing phase)
• Resource departure: Replacement acquisition when a team member leaves the project
• Scope change: When approved scope changes require new skills or additional resources
• Sprint planning (agile): Confirming team capacity and availability for the upcoming sprint
• Planned resource release: Transitioning from one resource to another at a scheduled handover point

6. Real-World Examples

Example 1: Project Phoenix — Website Launch

For Project Phoenix, Alex Morgan used the resource requirements document to define seven acquisition needs: UX researcher, UX/UI designer, two front-end developers, one back-end developer with Shopify API experience, QA engineer, and project coordinator. Using multicriteria decision analysis, she scored all internal candidates across availability, skill match, and cost. The analysis revealed that the back-end developer requirement could not be filled internally — no one on TechCorp’s team had Shopify API integration experience. Alex negotiated a four-week part-time engagement with an external Shopify specialist at a rate that fit within the approved budget envelope.

The negotiation for the QA engineer with the functional manager revealed a critical constraint: the engineer was scheduled to be on parental leave during weeks 8 through 12 — exactly when integration testing was planned. Alex restructured the testing schedule to front-load as much testing as possible in weeks 5 through 7, and engaged a part-time QA contractor for weeks 10 through 12 to cover the absence. The resource calendar was updated to reflect the actual availability, and the adjusted schedule showed the project could still meet the client deadline.

Example 2: Project ProjectAdm — SaaS PM Platform

For Project ProjectAdm, Eduardo’s Acquire Resources process had to address both the 11-person development team and the cloud infrastructure resources. For the human dimension, the multicriteria analysis for each of the 11 team members was completed against a 10-criteria scorecard. Three team members had skill gaps that required training before assignment to their designated roles; Eduardo documented these gaps as acquisition conditions and included training milestones in the project schedule.

For the virtual resource dimension, Eduardo negotiated a reserved-instance AWS agreement that reduced cloud infrastructure costs by 34% compared to on-demand pricing — but required a 12-month commitment. He submitted a change request to lock the infrastructure budget commitment, documented the cost-benefit analysis, and obtained sponsor approval before signing the contract. The resource calendar for cloud environments was integrated into the project schedule, showing the provisioning dates for each environment and the lead times required. This integration prevented the common error of developers being assigned to environment-dependent tasks before the environments were available.

7. Templates and Downloads

• Project Team Assignments — Software Development — Template for documenting team assignments aligned with PMBOK 8.
• Resource Calendars — Software Development — Resource calendar template for project scheduling integration.
• Physical/Virtual Resource Assignments — Software Development — Template for tracking physical and virtual resource assignments.
• Resource Requirements — Software Development — Resource requirements specification template.

8. Five Common Errors

Error 1 — Accepting verbal commitments without documented assignments

A functional manager’s verbal commitment to provide a team member is not a resource assignment. Without a documented project team assignment that includes the start date, allocation percentage, and expected end date, the commitment has no formal standing. When competing priorities arise — and they always will — undocumented verbal commitments are the first casualty. Every resource agreement must be documented and distributed in writing.

Error 2 — Building schedules on theoretical resource availability

The project schedule is only as accurate as the resource calendars it is built on. Schedules built on the assumption that all team members work 8-hour days, 5 days per week, with no vacations, no other project commitments, and no availability constraints, are fiction. Before finalizing any resource-constrained schedule, every assigned resource’s actual availability must be confirmed and entered in their resource calendar.

Error 3 — Failing to document alternative resource decisions

When the preferred resource is unavailable and an alternative is used, PMBOK 8 explicitly requires that the risks associated with using the alternative be acknowledged and documented. Assigning a junior developer to a senior role without documenting the skills gap and the associated quality and schedule risk is not resource acquisition — it is risk concealment.

Error 4 — Acquiring all resources at the beginning and paying for idle time

One of the most expensive resource management mistakes is acquiring resources before they are needed. A QA engineer brought onto a project in week 2 when testing does not begin until week 8 represents six weeks of cost with minimal productive output. Resource calendars and rolling-wave resource acquisition plans prevent this waste by aligning acquisition timing precisely with the schedule.

Error 5 — Neglecting physical and virtual resource acquisition timelines

Software licenses, cloud environments, specialized hardware, and testing infrastructure all have procurement and provisioning lead times. A development team that is ready to begin work on day 1 but is waiting for software licenses to be approved and provisioned loses productive days. Physical and virtual resource acquisition must be planned with the same timeline discipline as human resource acquisition, with lead times explicitly incorporated into the project schedule.

9. Tailoring This Process

Predictive approach: Acquisition occurs primarily at the start of the project, with planned acquisition events at phase transitions. The multicriteria decision analysis is formal and documented. Preassignment is common for key roles identified during initiation.

Adaptive approach: Team composition is defined at the project level during planning, but individual capacity is confirmed sprint by sprint. Virtual teams are common in agile contexts. The focus shifts from formal role-based acquisition to capacity-based planning — ensuring the team has the collective skills to handle the upcoming sprint’s work.

Hybrid approach: The overall team structure is acquired predictively, while specific resource assignments for adaptive work packages are confirmed iteratively. Procurement for physical resources follows the predictive approach.

Global projects: Virtual teams are central to the acquisition strategy. Cultural fit and language proficiency become explicit acquisition criteria. Time zone distribution requires explicit planning in resource calendars and the team charter.

10. Process Interactions

Acquire Resources is tightly integrated with the surrounding process ecosystem:

Inputs from: The Plan Resources process provides the resource management plan that governs acquisition. The Estimate Resources process provides the resource requirements that define what must be acquired. The Initiate Project or Phase process provides the project charter that defines the authority to commit resources. The Integrate and Align Project Plans process ensures acquisition decisions are consistent with the overall plan.

Outputs to: The Lead the Team (Develop Team) process receives the project team assignments as its starting point. The Monitor and Control Resourcing process uses physical/virtual resource assignments and resource calendars as baselines. The project schedule is updated with actual resource availability from resource calendars. The risk register receives updates when acquired resources differ materially from planned resources.

For a comprehensive view of all PMBOK 8 processes, see the PMBOK 8 Guide Index.

11. Quick-Application Checklist

• ☐ Resource requirements reviewed and acquisition criteria defined for all resource types
• ☐ Multicriteria decision analysis scorecard created for human resource selection
• ☐ Internal candidate evaluations completed and negotiation meetings scheduled
• ☐ Functional manager commitments documented in writing
• ☐ External procurement initiated for resources not available internally
• ☐ Project team assignments document created and distributed
• ☐ Physical/virtual resource assignments document created
• ☐ Resource calendars updated with actual availability for all assigned resources
• ☐ Project schedule updated with resource-constrained model
• ☐ Risk register updated for any resource gaps or alternative resource decisions

Call to Action:

References

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Eighth Edition. Newtown Square, Pennsylvania, USA: Project Management Institute, 2025.

PMBOK Guide 8: The New Era of Value-Based Project Management. Available at: https://projectmanagement.com.br/pmbok-guide-8/

Disclaimer

This article is an independent educational interpretation of the PMBOK® Guide – Eighth Edition, developed for informational purposes by ProjectManagement.com.br. It does not reproduce or redistribute proprietary PMI content. All trademarks, including PMI, PMBOK, and Project Management Institute, are the property of the Project Management Institute, Inc. For access to the complete and official content, purchase the guide from Amazon or download it for free at https://www.pmi.org/standards/pmbok if you are a PMI member.