PMP Exam Content Outline 2026

The July 2026 blueprint

The PMP Examination Content Outline (ECO) effective with the exam launched on 9 July 2026 is the current blueprint. It divides the exam into People (33%), Process (41%), and Business Environment (26%). The outline contains 26 tasks: eight People tasks, ten Process tasks, and eight Business Environment tasks. PMI describes the exam as spanning predictive and adaptive or hybrid approaches, with roughly 40% predictive and 60% adaptive or hybrid content. These are blueprint proportions, not a fixed item-by-item allocation.

The ECO states responsibilities and gives enablers that illustrate how a responsibility can appear in practice. It is more useful to study the task verbs and decisions than to memorize headings alone. The tasks cut across methods: scope, risk, communication, and value decisions can appear in a predictive, adaptive, or hybrid scenario. PMI also highlights outcomes, stakeholder engagement, AI, sustainability, and business impact. The ECO, rather than an older book’s chapter structure, should control your coverage map.

People domain: 33%

The People domain concerns the relationships and coordination needed to achieve project outcomes. Its eight tasks ask candidates to develop a common vision, manage conflicts, lead the project team, engage stakeholders, align stakeholder expectations, manage stakeholder expectations, help ensure knowledge transfer, and plan and manage communication. These tasks are distinct but often linked. A misunderstanding can require diagnosing the cause, restoring shared understanding, and changing how the team communicates.

Developing a common vision means helping key stakeholders understand the intended outcome and keeping that understanding current. Conflict management begins by identifying its source and context, then selecting a resolution strategy that can work for the people involved. Leading a team includes creating conditions for performance and addressing impediments to collaboration. Engagement asks what involvement a stakeholder needs; expectation management addresses what stakeholders believe will happen and how those beliefs should be aligned with project realities.

Knowledge transfer and communication planning require more than sending updates. Identify what knowledge must move, who needs it, when they need it, and whether the recipient can use it. A project nearing transition may need operational procedures, decision history, and training, not only a final status report. Communication should suit audience, urgency, language, and confidentiality.

Process domain: 41%

Process is the largest domain and covers planning, delivery, and control. The ten tasks are: develop an integrated project management plan and plan delivery; develop and manage project scope; help ensure value-based delivery; plan and manage resources; plan and manage procurement; plan and manage finance; plan and optimize quality of products or deliverables; plan and manage schedule; evaluate project status; and manage project closure.

Integrated planning connects approach, dependencies, resources, and business value. Scope work defines what is included, gains stakeholder agreement, and breaks work into a form the delivery approach can manage. Value-based delivery links priorities to stakeholder value, tests incremental delivery options, and tracks benefits throughout the project. Resource management plans for need and availability. Procurement includes selecting a sourcing approach and contract, negotiating, managing suppliers, and verifying agreement objectives.

Finance includes analyzing project needs, setting aside risk and contingency funding, tracking spending, forecasting challenges, and managing reserves through governance. Quality combines requirements, processes, reviews, compliance, cost of quality, and improvement. Schedule work includes estimates, dependencies, benchmarks, baselines where appropriate, coordination with other work, and analysis of variation. Project status calls for meaningful metrics and accessible, current artifacts. Closure verifies completion, stakeholder acceptance, readiness for transition, and closeout of lessons, contracts, finances, and resources.

These tasks depend on one another. A scope change can affect a forecast, supplier agreement, quality target, and benefit measure. The correct response is not to update every artifact mechanically; first assess the change and use the applicable authority. In an adaptive setting, a backlog may be reprioritized regularly, but value, dependencies, and stakeholder expectations still need to be considered.

Business Environment domain: 26%

Business Environment has eight tasks and a much larger share than in the prior PMP outline. The tasks are to define and establish project governance; plan and manage project compliance; manage and control changes; remove impediments and manage issues; plan and manage risk; support continuous improvement; support organizational change; and evaluate external business environment changes.

Governance identifies how decisions are made, who has authority, and what oversight is needed. Compliance work identifies obligations and builds them into the project rather than treating them as optional preferences. Change control makes changes visible and evaluates their effects. Issue management removes or escalates existing blockers; risk management addresses uncertain future events. Improvement uses lessons to adjust project or organizational processes.

Organizational change includes assessing culture and adoption effects, then identifying actions needed for transition. External business changes can include regulation, technology, geopolitical conditions, or market shifts. The project manager should keep watch for those changes, assess their impact on scope or backlog, and take the implications through governance. A project can be delivered efficiently and still fail if the organization cannot adopt it or if the business case no longer holds.

What changed from the previous outline

The three domains remain, but the weights shifted from People 42%, Process 50%, and Business Environment 8% to 33%, 41%, and 26%. The current ECO places far more visible weight on business context. It also consolidates task language and emphasizes outcomes and value. PMI highlights AI, sustainability, and stakeholder engagement. Candidates using older notes should update weights and map concepts to current tasks rather than discarding every enduring project-management principle.

The shift matters when you decide where to spend study time. Someone who already understands schedule and cost still needs meaningful coverage of governance, compliance, external changes, adoption, and benefits. Conversely, a candidate should not ignore People or Process because their weight decreased. People and Process together still comprise nearly three-quarters of the domain weighting.

How to use the task list

Turn each task into a question about evidence and action. For “evaluate project status,” ask which measures show actual progress, whether artifacts are current and accessible, and how to communicate a forecast. For “manage and control changes,” ask who may authorize a change, what impact evidence is required, and how the approved decision reaches the plan or backlog. This makes the outline an applied study tool rather than a vocabulary list.

Use the domain percentages to check balance, not to calculate a guaranteed number of questions. There are 170 scored items, but pretest items are mixed into the 180-item exam and PMI does not publish a simple raw passing percentage. A study allocation can roughly reflect the weights, then adjust for your diagnostic performance. Record weak tasks specifically; “I need more Process” is less useful than “I miss schedule variance questions when dependencies shift.”

Cross-domain scenarios

Scenario 1: A new privacy requirement affects a feature already planned for release. The candidate should recognize compliance and external change issues, assess scope and delivery impacts, involve the relevant authority, and communicate the effect on value and timing. This can involve Business Environment, Process planning, and People communication in one case.

Scenario 2: Two teams disagree about a release because the integration test is failing. A useful first move is to bring the relevant people together around the test evidence, identify the defect’s source and impact, and agree on ownership and acceptance criteria. That links conflict management, quality, project status, and issue removal. “Escalate immediately” may be necessary in some cases, but it is not a substitute for examining facts that the team can assess.

Scenario 3: A sponsor asks the team to continue after a market change has removed the benefit that justified the project. The project manager should validate the benefit assumptions and present options through governance. Past expenditure is not evidence of future value. The sponsor or authorized body decides whether to continue, redirect, or stop.

Map a study resource to the current ECO

Check the publication date, domain weights, and task coverage before using a course or book. A resource that says Business Environment is 8% is based on the previous weighting and is not an adequate map for the July 2026 exam. A resource may still explain useful concepts, but add coverage for the current tasks and item formats. Make a simple matrix with the 26 tasks as rows and your learning materials as columns. Mark each task only when you can explain and apply it, not merely because a chapter mentions a similar word.

The PMBOK Guide is a professional standard, while the ECO specifies exam domains and tasks. The documents serve related but different purposes. Do not assume that reading one reference in sequence guarantees complete ECO coverage. Use the outline to identify what to learn, then choose sources that teach the underlying concepts and practice their application.

The 26 tasks at a glance

People tasks: develop a common vision; manage conflicts; lead the project team; engage stakeholders; align stakeholder expectations; manage stakeholder expectations; help ensure knowledge transfer; plan and manage communication. Process tasks: develop an integrated project management plan and plan delivery; develop and manage scope; help ensure value-based delivery; plan and manage resources; plan and manage procurement; plan and manage finance; plan and optimize quality; plan and manage schedule; evaluate project status; manage project closure. Business Environment tasks: define and establish governance; plan and manage compliance; manage and control changes; remove impediments and manage issues; plan and manage risk; support continuous improvement; support organizational change; evaluate external business environment changes.

Distinguish adjacent tasks

Some task pairs sound alike but ask different things. Aligning stakeholder expectations means reaching a shared understanding; managing expectations means keeping them realistic as facts evolve. A project issue is already occurring, while a risk is uncertain. Change control asks how a requested change is assessed and authorized; external-environment evaluation looks for a change in the surrounding context that may require project response. Understanding these distinctions helps select the task that fits the decisive scenario fact.

How the weightings should shape study

Process receives the largest weight at 41%, but People at 33% and Business Environment at 26% are both material. Do not skip a domain because it seems familiar or abstract. If study time is limited, allocate a baseline amount to every task, then give additional sessions to tasks your diagnostic shows are weak. A candidate strong in schedule control may need more practice with benefits, governance, compliance, organizational change, and external conditions.

New themes are applications, not slogans

AI and sustainability do not create a shortcut answer. For AI-assisted analysis, consider data quality, human review, privacy, security, bias, and who is accountable for the resulting decision. For sustainability, examine lifecycle effects, stakeholder priorities, procurement, cost, and applicable requirements. A project choice may improve one measure while worsening another. Explain the trade-off using the facts given rather than choosing a technology or sustainability label automatically.

Task-based revision exercise

Choose one task each day and write a short case with a clear decision. For schedule, give a dependency and a forecast variance; ask what the manager should analyze. For finance, provide a reserve and an unexpected cost; ask what must be reported or governed. For communication, give two stakeholder groups with different information needs. Answer the case, identify the decision owner, and record why the closest alternative fails. Rotate through all 26 tasks before repeating your strongest topic.