Budget, Reserves, and Spend Tracking

Introduction

This lesson covers the first half of task 6 of the Process domain in the July 2026 PMP Examination Content Outline (Process carries 41% of the exam): analyze the financial needs of the project, estimate and aggregate costs, plan contingency and management reserves, quantify risk in the financial allocations, and plan how spend will be tracked and reported. The second lesson of this chapter covers monitoring financial performance with earned value, forecasting, and managing variances.

Finance questions on the exam are usually short scenarios with a calculation or a decision: which estimate technique fits, where a reserve belongs, who can use it, what the cost baseline contains. After this lesson you will be able to build a cost estimate from the bottom up, apply analogous, parametric and three-point methods, aggregate costs into a cost baseline and a budget, size reserves, and set up financial tracking and reporting that fit predictive, agile, and hybrid projects.

Learning objectives

• Identify the financial needs of a project from its business case, scope, and constraints.
• Apply analogous, parametric, bottom-up, and three-point estimating to a scenario.
• Aggregate costs from work packages to control accounts, the cost baseline, and the budget.
• Distinguish contingency reserves from management reserves, and say who controls each.
• Quantify risk in the financial allocation using expected monetary value.
• Plan funding limits, cash flow, and spend tracking.
• Adapt financial planning to agile projects with fixed capacity and to hybrid funding models.

1. Financial needs of the project

A project is funded because its expected benefits are worth more than its costs. Before estimating, the project manager clarifies what the organization needs from the finances:

• Business case and benefits. What value is expected, when, and how much can be spent to obtain it? A project with expected benefits of EUR 2 million over five years cannot sensibly cost EUR 1.9 million.
• Funding source and limits. Is the money from one budget line, several departments, an external grant, or a customer? Are there limits per year or per quarter (funding limit reconciliation)?
• Constraints. Currency, inflation, exchange rates, tax, capital versus operating expense, approval thresholds, and procurement rules.
• Level of accuracy needed. An early rough order of magnitude (ROM) estimate may be -25% to +75%. A definitive estimate near the end of planning may be -5% to +10%. The ranges narrow as information increases.
• Reporting rules. What the sponsor, the finance department, and the PMO expect: formats, frequency, and thresholds that trigger escalation.

The project manager does not own the corporate financial policy but must follow it. When in doubt, ask finance and the PMO rather than inventing a method.

Example: tying the budget to benefits

A manufacturer plans an energy monitoring platform expected to save EUR 400,000 per year starting in year 2. The sponsor accepts a payback of three years. If implementation costs EUR 700,000 and annual running costs are EUR 100,000, net savings are 300,000 per year from year 2. Cumulative net position: year 1 = -700,000 - 100,000 = -800,000; year 2 = -500,000; year 3 = -200,000; year 4 = +100,000. Payback takes about 3.7 years, longer than the accepted three years. The project manager must raise this with the sponsor: reduce the scope or cost, accept a longer payback, or revisit the benefits assumption. Planning a budget without testing it against benefits is a frequent weakness.

2. Estimating costs

Cost estimates cover all resources: people, materials, equipment, services, software, travel, training, facilities, and the cost of risk responses. Estimates should be in the currency and price level that the cost baseline will use.

Three-point estimates

• Triangular: (O + M + P) / 3.
• Beta (PERT): (O + 4M + P) / 6, which gives more weight to the most likely value.
• Standard deviation (PERT): (P - O) / 6; variance is the square.

Worked example: PERT cost estimate for a work package

Statement. A data migration work package has an optimistic cost of EUR 40,000, a most likely cost of EUR 55,000, and a pessimistic cost of EUR 100,000. Calculate the PERT expected cost, the standard deviation, and the range that covers about 68% and 95% of outcomes.

Reasoning.

1. Expected cost (PERT) = (40,000 + 4 x 55,000 + 100,000) / 6 = (40,000 + 220,000 + 100,000) / 6 = 360,000 / 6 = EUR 60,000.
2. Standard deviation = (100,000 - 40,000) / 6 = 10,000.
3. About 68% of outcomes fall within one standard deviation: 50,000 to 70,000.
4. About 95% fall within two: 40,000 to 80,000.
5. For comparison, triangular = (40,000 + 55,000 + 100,000) / 3 = 65,000.

Solution. PERT expected cost EUR 60,000, standard deviation EUR 10,000, 68% range 50,000-70,000, 95% range 40,000-80,000.

Why other answers are weaker. Using the most likely value (55,000) ignores the skewed risk toward the pessimistic side. Using the triangular mean gives too much weight to the extreme pessimistic value when the question asks for PERT. Using the optimistic and pessimistic values alone ignores the most likely one.

Example: parametric and analogous

A previous office fit-out cost EUR 1,200 per square metre. The new office is 2,500 square metres but has a more advanced security system, adding an estimated 10%. Parametric estimate: 2,500 x 1,200 = 3,000,000; adjusted: 3,000,000 x 1.10 = 3,300,000. This is quick, but it is only as good as the comparability of the two projects. An analogous estimate using the total cost of a similar earlier project is even rougher and is typically used before a work breakdown structure exists.

3. Aggregating costs: from work packages to the budget

The cost structure builds upward:

1. Activity or work package costs are estimated.
2. Control account costs are the sum of their work packages.
3. Contingency reserves for identified risks are added, producing the cost baseline.
4. Management reserves for unknown-unknowns are added to the cost baseline, producing the project budget.

Work package costs
+ Contingency reserves (identified risks)
= Cost baseline
+ Management reserves (unidentified risks)
= Project budget

The cost baseline is the approved time-phased budget used to measure performance (it excludes management reserves). It is shown as an S-curve of cumulative cost over time. The project budget is the total funding authorized, and it includes management reserves.

Funding limit reconciliation. If the sponsor can release only EUR 500,000 in a quarter but the plan needs EUR 650,000, the schedule or the spending plan must be adjusted, for example by moving work to the next quarter or phasing the procurement.

Cost of quality, indirect costs, and overheads. Prevention and appraisal costs (training, reviews, testing) and failure costs (rework, warranty) are part of the estimate. Indirect costs such as shared facilities and management overhead are allocated according to organizational policy, not chosen freely by the project manager.

Worked example: building the budget

Statement. A project has work package costs of EUR 820,000. Identified risks have a total expected monetary value (EMV) of EUR 48,000, and the risk plan sets the contingency at this EMV rounded up to EUR 50,000. The sponsor adds a management reserve of 5% of the cost baseline. What are the cost baseline and the project budget?

Reasoning.

1. Cost baseline = work packages + contingency = 820,000 + 50,000 = EUR 870,000.
2. Management reserve = 5% x 870,000 = EUR 43,500.
3. Project budget = 870,000 + 43,500 = EUR 913,500.
4. The project manager measures cost performance against 870,000. Using the 43,500 requires approval, because it is controlled outside the baseline.

Solution. Cost baseline EUR 870,000; project budget EUR 913,500.

Why other answers are weaker. 820,000 omits contingency, so the baseline would not cover identified risks. 913,500 as a baseline wrongly includes management reserve. Adding 5% to the work packages only (861,000) uses the wrong base.

4. Contingency and management reserves

Practical points:

• Contingency can be tied to specific risks (for example, EUR 12,000 for a supplier delay risk) or held as a general amount for the project. Tie it to the risk register so that it can be released when the risk expires.
• Do not hide padding in individual estimates. Padding is dishonest and hard to control. Reserves are visible, justified, and governed.
• When the project uses contingency, record it and update the risk register. When contingency is nearly gone while many risks remain, raise this with the sponsor early.
• A reserve for schedule (time contingency) exists too; the project manager should align the two reserve types.

Quantifying risk in the financial allocation

The expected monetary value (EMV) of a risk is probability x impact. Opportunities have positive impact, threats negative.

Net EMV = -12,000 - 12,000 + 10,000 - 15,000 = -29,000. Many teams set contingency from the sum of threat EMVs (here -39,000) and treat opportunities separately and cautiously, because an opportunity is not guaranteed. A decision tree or simulation gives a more precise view when risks interact. The exam expects you to use EMV and to know that EMV is an average, not a prediction for a single event.

5. Planning spend tracking and financial reporting

The cost management plan sets the rules for measuring and controlling money. It typically defines:

• Units of measure and precision (euros, rounded to the nearest thousand).
• Control thresholds: for example, variance beyond plus or minus 10% triggers a corrective action or escalation.
• Rules of performance measurement: earned value management (EVM) with defined methods for measuring earned value (0/100 for short tasks, 50/50, weighted milestones, percent complete).
• Reporting formats and frequency: monthly cost report, dashboard for the sponsor, finance reconciliation.
• Process for cost changes and how reserves are drawn.
• Cash flow and invoicing rules: payment terms to suppliers, billing milestones to customers.
• Alignment with the accounting system: project codes, cost centres, and the calendar (financial year ends can create hard deadlines).

Example: cash flow and funding

A construction-fit-out project has a cost baseline of EUR 1,000,000 over 10 months with costs concentrated in months 4 to 8. The customer pays 20% upfront and then monthly invoices against accepted milestones with 45 days payment terms. A cash flow view shows that between months 5 and 8 the company must finance up to EUR 400,000 before payments arrive. The project manager works with finance on a credit line or renegotiates the payment schedule. Missing cash flow in planning is a common cause of project stress even when the total budget is fine.

Financial tracking tools

• Cost baseline S-curve against actual cost (AC) and earned value (EV).
• Cost variance and CPI (covered in detail in the next lesson).
• Commitment tracking: purchase orders raised and contracts signed count as commitments before they appear as actual costs. A report that only shows invoiced costs underestimates future spend.
• Accruals: work done but not yet invoiced should be estimated so that actual costs are not understated at month end.
• Change log and forecast: every approved change updates the forecast and, if approved as a baseline change, the baseline.

6. Agile and hybrid financial planning

Agile teams usually have a stable capacity, so the main cost driver is the team's cost per iteration. Budgeting is done differently from the cost of a defined scope:

• Capacity-based budget: budget = team cost per iteration x number of iterations. If a team of 7 costs EUR 56,000 per three-week sprint and the release is planned for 6 sprints, the budget is 336,000.
• Cost per story point (or per feature) can be derived from velocity: 56,000 / 40 points = EUR 1,400 per point. It is useful for rough forecasting but should not be used to compare teams.
• Incremental funding: funds are released per release or per quarter, with a review of delivered value before continuing. This limits loss when value is lower than expected.
• Fixed budget, variable scope: the budget is the constraint, and the product owner orders the backlog by value so that the most valuable items are done first.
• Hybrid approach: a predictive budget for infrastructure and procurement, and a capacity-based budget for the agile development part. Track both in one financial view.
• Contingency in agile: often held as scope flexibility (low-priority items removed) and as a reserve of sprints, plus a financial reserve for external risks.

Metrics suitable for agile cost tracking: burn rate, budget burn-up compared to value delivered, cost per feature, and forecast cost to complete based on remaining backlog and velocity.

7. Common pitfalls and exam tips

Pitfalls

• Estimating without a clear scope or a WBS and then presenting a single number as certain.
• Adding padding to each estimate instead of managing reserves openly.
• Confusing the cost baseline with the budget.
• Using management reserve without a change request.
• Ignoring commitments, accruals, and cash flow.
• Forgetting indirect costs, taxes, currency effects, or inflation on long projects.
• Letting contingency run out without telling the sponsor.
• Treating agile budgets as a fixed scope price and ignoring the value delivered.

Exam tips

• Baseline = work packages + contingency. Budget = baseline + management reserve.
• Contingency belongs to the project manager within the rules; management reserve needs approval and a change request.
• Three-point PERT: (O + 4M + P) / 6. Standard deviation: (P - O) / 6.
• Bottom-up is the most accurate but needs a detailed scope; analogous is the quickest and least accurate.
• When the question says "unknown-unknowns", think management reserve. When it says "identified risks", think contingency.
• If spending is above the funding limit in a period, adjust the plan; do not just ask for more money without analysis.
• In agile, forecast with velocity and remaining backlog, and fund by increments.

8. Mini case study

Situation. A bank is building a customer onboarding app over 9 months. The team has estimated the work packages by bottom-up at EUR 1,150,000. The risk register lists three threats and one opportunity: a regulatory change (probability 25%, impact EUR 120,000), a key supplier delay (30%, EUR 50,000), a security finding that requires rework (40%, EUR 75,000) and a cheaper cloud tariff (50%, saving EUR 30,000). The CFO wants a fixed management reserve of 8% of the cost baseline, and the bank's funding limit is EUR 450,000 per quarter. The plan shows spend of EUR 520,000 in quarter 2 because of a large procurement.

Questions. Calculate the contingency, cost baseline, and project budget. How should the project manager handle the funding limit?

Commented solution.

1. Threat EMVs: 0.25 x 120,000 = 30,000; 0.30 x 50,000 = 15,000; 0.40 x 75,000 = 30,000. Total threats = 75,000.
2. Opportunity: 0.50 x 30,000 = 15,000. The team decides, prudently, not to reduce contingency for the opportunity until the tariff is contractually fixed.
3. Contingency = EUR 75,000.
4. Cost baseline = 1,150,000 + 75,000 = EUR 1,225,000.
5. Management reserve = 8% x 1,225,000 = EUR 98,000.
6. Project budget = 1,225,000 + 98,000 = EUR 1,323,000.
7. Funding limit: quarter 2 exceeds the limit by EUR 70,000 (520,000 - 450,000). Options: split the procurement with a staged payment, move part of the delivery to quarter 3 if the schedule has float, or negotiate payment terms with the supplier. Present the options with their schedule and risk effects to the sponsor and update the baseline through change control if the schedule changes.
8. Tracking: include commitments from the procurement, set a variance threshold of plus or minus 10%, report monthly to the sponsor, and review contingency at each risk review.

Why not add the opportunity to reduce the baseline? The saving is uncertain until contracted. Why not ask the CFO to raise the limit? Analysis of the options should come first, since changing the plan may solve the problem at no cost. Why not hide the 70,000 in the estimates of other quarters? It would conceal a funding conflict instead of managing it openly.

Key terms

• Rough order of magnitude (ROM): early, wide-range estimate.
• Analogous, parametric, bottom-up, three-point: main estimating techniques.
• PERT: (O + 4M + P) / 6 expected value; standard deviation (P - O) / 6.
• Control account: management point that groups work packages for cost and schedule control.
• Cost baseline: approved time-phased budget excluding management reserve.
• Project budget: cost baseline plus management reserve.
• Contingency reserve: funds for identified risks, in the baseline.
• Management reserve: funds for unidentified risks, outside the baseline, released by approval.
• EMV: probability x impact.
• Funding limit reconciliation: adjusting spend to funding availability by period.
• Commitment and accrual: costs committed but not yet paid, and work done but not yet invoiced.

Summary checklist

• I can link the budget to the business case and funding limits.
• I can choose and apply analogous, parametric, bottom-up, and three-point estimates.
• I can compute the cost baseline and the project budget from work packages and reserves.
• I can distinguish contingency from management reserve and who controls each.
• I can calculate EMV for risks and size the contingency.
• I can plan cost thresholds, reporting, commitments, and cash flow.
• I can budget an agile team by capacity and fund by increments.
• I can resolve a funding limit conflict by analysing options with the sponsor.

Official sources

• PMI, PMP Examination Content Outline (July 2026): https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
• PMI, PMP certification: https://www.pmi.org/certifications/project-management-pmp (opens in a new tab)
• PMI, PMP exam change: https://www.pmi.org/blog/pmp-exam-change (opens in a new tab)