II.6 — Plan and Manage Finance

II.6 · Last updated: 11/10/2026

The task that dropped the word "budget"

II.6 — Plan and Manage Finance is the sixth task in the Process domain of the 2026 ECO, and that domain carries 41% of the exam. The ECO places seven enablers under it:

• Analyze project financial needs
• Quantify risk and contingency financial allocations
• Plan spend tracking throughout the project life cycle
• Plan financial reporting
• Anticipate future finance challenges
• Monitor financial variations and work with the governance process
• Manage financial reserves

The word "budget" appears nowhere in that list, and the omission looks deliberate. In 2021 the task spoke of budget, in 2026 it speaks of finance, and its scope grew along with the name. As the sections below show, PMBOK 8 now looks at what a project earns as well as what it spends.

Old "II.5" and old "II.6"

Two traps overlap on this task. The first is a split. In 2021, II.5 was a single task that planned and managed budget and resources together. In 2026 that work was divided, with finance coming to this page (II.6) and resources going to II.4 — Plan and Manage Resources. Any question tagged "II.5" in older material therefore has to be read on its own before it can be mapped.

The second trap is the number itself. In 2021, II.6 meant the schedule, a topic that now sits in II.8, so an older question tagged "II.6" is far more likely to be about scheduling than about money.

Taken together, the two traps produce a result that runs backwards. To find this page's subject in older material you look under the old II.5, while the old II.6 sends you somewhere else entirely. Match on the title when mapping. The wider picture is in what changed in the 2026 PMP exam.

Finance covers more than cost

PMBOK® 8 calls the relevant performance domain Finance, and its reach goes past cost. According to the Guide, the Finance performance domain deals with the processes and tools for the use and allocation of monetary resources coming from inside and outside the performing organization, and financial performance relates to costs, funding, and in some cases the project's value proposition (PMBOK® 8, Guide p.58).

The clearest sign of the wider scope is the definition of the domain's first process. Plan Financial Management is the process of defining how the project's revenues and expenses will be estimated, budgeted, managed, monitored, and controlled, in alignment with project objectives and organizational strategy (PMBOK® 8, Guide p.61). "Revenues" is the word that matters there, because the financial side of a project is no longer reduced to a record of what was spent on what. The ECO's switch from budget to finance reflects the same widening.

Four processes in the domain

The Finance performance domain holds four processes (PMBOK® 8, Guide pp.61-62, Figure 2-26):

• Plan Financial Management defines how revenues and expenses will be managed. The benefit the book names is guidance and direction on how project finances will be managed throughout the project.
• Estimate Costs develops an approximation of the cost of the resources needed to complete project work.
• Develop Budget aggregates the estimated costs of individual activities or work packages to establish an authorized cost baseline.
• Monitor and Control Finances monitors the project's financial status, updates project finances, manages changes to the cost baseline and revenue forecasts, and keeps the deliverables financially viable throughout their life cycle.

That fourth definition answers two of the ECO's enablers at once, since it covers both monitoring variations and anticipating future challenges.

Two reserves for two kinds of uncertainty

Reserves are the subject the exam returns to most often on this task. The book separates the two reserves by their purpose, by who has the authority to use them, and by the kind of risk they cover (PMBOK® 8, Guide p.60). The contingency reserve is time or money allocated in the schedule or cost baseline for known risks with active response strategies, and it is usually included in the initial project budget. The management reserve is time or money that management sets aside outside the schedule or cost baseline and releases for unforeseen work that still falls within the project's scope.

Elsewhere the Guide draws the same line in the vocabulary of risk. Contingency reserves are treated as the budget within the cost baseline that is set aside for identified risks, an allowance for the known-unknowns that could affect the project (PMBOK® 8, Guide p.192). The management reserve is held to cover unknown risks (PMBOK® 8, Guide p.102).

Two of the ECO's enablers split this distinction between them. Quantifying risk and contingency financial allocations is the planning side, and managing financial reserves is the execution side.

Does the cost baseline include the reserves?

The question that follows from the reserve distinction most often is what the cost baseline actually contains. The classic answer in the book is that the cost baseline includes the projected expenditures plus the contingency reserves, and the total funds required are the cost baseline plus management reserves, if any (PMBOK® 8, Guide p.126). In this model the contingency reserve sits inside the baseline and the management reserve sits outside it.

PMBOK 8 does not offer that model as the only possibility. The Guide sketches two scenarios for building up a budget (PMBOK® 8, Guide pp.60-61, Figure 2-25). In the first, the initial budget contains the approved work package costs together with the contingency reserve and the management reserve, and the reserves are managed implicitly. In the second, the initial budget contains only the approved work cost estimates, while both reserves are managed explicitly and separately. The cost baseline follows suit and may leave out either the management reserve alone or both reserves, and the book adds that further variations can arise from organizational preferences and external factors.

For the exam the safe assumption is still the classic model, so unless a question says otherwise, treat the contingency reserve as inside the baseline and the management reserve as outside it. That model has a practical consequence. Because the cost baseline can be changed only through formal change control procedures (PMBOK® 8, Guide p.118), releasing money from the management reserve into the work changes the baseline itself, and that change has to pass through the formal process. Drawing on the contingency reserve, which is already part of the baseline, leaves the baseline as it was. The change process itself is covered in III.3 — Manage and Control Changes.

The Guide's passage on project funding requirements, where the classic answer above comes from, makes two further points. Funding often arrives in incremental amounts that may not be spread evenly across periods, and the budget at completion (BAC) is the sum of all the budgets established for the work to be performed (PMBOK® 8, Guide p.126).

Spend tracking and the funding limit

Two separate enablers ask for the monitoring side of planning, one for spend tracking across the life cycle and one for financial reporting. Their PMBOK counterparts appear among the tools of the Develop Budget process (PMBOK® 8, Guide p.64). The list includes cost aggregation, reserve analysis, review of historical information, funding limit reconciliation, and financing, and the process produces the cost baseline and the project funding requirements as outputs.

Funding limit reconciliation deserves a closer look. When money comes in increments and unevenly from one period to the next, the planned spending curve has to fit the funding limit of each period. A project whose total budget is sufficient can still find that there is no money available this month, and that is a real project problem with practical consequences.

Finance works alongside governance

One enabler reaches straight into another domain by asking you to monitor financial variations and work with the governance process. The book gives that a clear footing. At the organizational level, coordinated governance allows the authorized allocation of human, financial, and physical resources based on expected performance and benefits (PMBOK® 8, Standard p.10).

The project's context also affects how cautious its finances need to be. The Guide says a public sector project faces a higher demand for fiscal accountability and greater risk aversion because of public accountability and regulatory requirements, which is why its budget reserves should be evaluated with a greater buffer (PMBOK® 8, Guide p.66). The same page notes that tailoring the financial processes together with the procurement strategy in purchasing decisions reduces the risk of cost overruns. The other end of that connection is on the page for II.5 — Plan and Manage Procurement.

How the governance framework is set up therefore bears directly on the finance task. Its details belong to III.1 — Define and Establish Project Governance.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p. X
• A Guide to the Project Management Body of Knowledge — cited as Guide p. X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page describes the book; it does not replace it.