II.6 — Plan and Manage Finance

II.6 · Last updated: 24/08/2026

Where this task sits

II.6 — Plan and Manage Finance is the sixth task in the Process domain of the 2026 ECO. The domain carries 41% of the exam.

It has seven enablers:

• 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" does not appear once. That is not accidental — both the task's name and its scope widened in 2026.

🔴 A renumbering and a split at once

This task carries both traps.

First, the split. In 2021, II.5 was a single task: plan and manage budget and resources. In 2026 that work divided — finance came to this page (II.6), resources went to II.4 — Plan and Manage Resources. Every item tagged "II.5" in older material has to be read individually before it can be mapped.

Second, the number. In 2021, II.6 was schedule; that topic is II.8 in 2026. So an older question tagged "II.6" is most likely about schedule, not finance.

Put together: to reach this page's subject you have to look at the old II.5, not the old II.6. Match on the title, never the number; for the general shape of the trap see what changed in the 2026 PMP exam.

"Finance," not "Cost" — and the difference is more than the name

PMBOK® 8 calls the performance domain for this subject Finance, and its scope runs wider than cost.

The Guide defines it: the Finance performance domain addresses processes and tools related to the use and allocation of monetary resources, both internally and externally, to the performing organization. Financial performance relates to costs, funding, and, in some cases, the value proposition (PMBOK® 8, Guide p.58).

The clearest evidence of the widening is in the first process definition: Plan Financial Management is the process of defining how the project revenues and expenses will be estimated, budgeted, managed, monitored, and controlled, ensuring alignment with project objectives and organizational strategy (PMBOK® 8, Guide p.61).

The word revenues is decisive there. The old "cost management" frame looked only at spending; PMBOK® 8 brings the project's revenue side into the domain. The ECO renaming the task from "budget" to "finance" reflects exactly that.

The domain's four processes

The Finance performance domain carries four processes (PMBOK® 8, Guide p.61 — Figure 2-26):

• Plan Financial Management — defines how revenues and expenses will be managed. Its benefit is providing guidance and direction on how project finances will be managed throughout the project; it is performed once up front or at predefined points (PMBOK® 8, Guide p.61).
• Estimate Costs — the process of developing an approximation of the cost of resources needed to complete project work (PMBOK® 8, Guide p.61).
• Develop Budget — the process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline (PMBOK® 8, Guide p.62).
• Monitor and Control Finances — the process of monitoring the project's financial status, updating project finances, managing changes to the cost baseline and revenue forecasts, and ensuring that project deliverables maintain their financial viability throughout the life cycle (PMBOK® 8, Guide p.62).

That fourth definition covers two ECO enablers at once: monitoring variations and anticipating future challenges.

Two reserves, two different kinds of uncertainty

The most frequent exam question on this task is about reserves, and the distinction fits in one sentence each.

Contingency reserve is for known risks. The Guide says known risks are factored in by providing sufficient floats, contingency reserves, or alternate activity network strategies such as secondary plans (PMBOK® 8, Guide p.58).

Management reserve is held to cover unknown risks (PMBOK® 8, Guide p.102).

The book draws two scenarios for how the budget is built up (PMBOK® 8, Guide p.60–61 — Figure 2-25): in one, the initial project budget contains the sum of approved work package cost estimates, contingency reserve, and management reserve, with reserves managed implicitly. In another, the initial budget contains only approved work cost estimates while contingency reserve and management reserve are managed explicitly. Variations may exist based on organizational preferences or external influences.

The ECO's "quantify risk and contingency financial allocations" enabler is the planning side of that distinction; "manage financial reserves" is the execution side.

What the cost baseline includes — and what it does not

This is the consequence of the reserve distinction that generates the most questions.

The Guide is explicit: the cost baseline includes the projected expenditures plus the contingency reserves. The total funds required are those included in the cost baseline plus management reserves, if any (PMBOK® 8, Guide p.126).

So contingency reserve sits inside the cost baseline and management reserve sits outside it. The practical consequence: using contingency reserve does not change the baseline; touching management reserve requires the baseline to change — and that is a formal change process, see III.3 — Manage and Control Changes.

The same page adds two more things: funding often occurs in incremental amounts and may not be evenly distributed; and the budget at completion (BAC) is the sum of all budgets established for the work to be performed (PMBOK® 8, Guide p.126).

Spend tracking and financial reporting

Two separate ECO enablers ask for the monitoring side of planning: plan spend tracking throughout the life cycle, and plan financial reporting.

Their PMBOK counterparts show up among the tools of the Develop Budget process: reserve analysis, funding limit reconciliation, and financing. The process outputs are the cost baseline and the project funding requirements (PMBOK® 8, Guide p.64).

Funding limit reconciliation is especially worth noting: in a world where funding arrives incrementally and unevenly, the planned spend curve has to fit within the funding limits. "The budget is sufficient but there is no money this month" is therefore a real project problem.

Finance is not the project manager's job alone

One ECO enabler points directly at another domain: monitor financial variations and work with the governance process.

Its footing in the book is explicit. At the organizational level, coordinated governance allows for the authorized allocation of human, financial, and physical resources based on expected performance and benefits (PMBOK® 8, Standard p.10).

Context shifts the expectation too. The Guide notes that public sector projects carry a higher demand for fiscal accountability and risk aversion due to public accountability and regulatory requirements, so budget reserves should be evaluated with a greater buffer. Where financial flexibility is limited, a conservative approach to budgeting with contingency and management reserves is crucial to mitigate risks and ensure project stability (PMBOK® 8, Guide p.66).

How the governance framework is set up therefore bears directly on this task — see III.1 — Define and Establish Project Governance.

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ 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 explains the book; it does not replace it.