Monitor and Control Finances in PMBOK 8 — Complete Guide

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

Monitor and Control Finances in PMBOK 8 — Complete Guide

Formerly known as: Control Costs (PMBOK 6)

The CFO called the project manager on a Thursday with a single question: “How much of the project budget is left?” The project manager knew the answer was “we’ve spent $280,000 of the $340,000 budget.” But the CFO’s next question was the one that exposed the problem: “Is that the right amount to have spent at this point in the project?” There was a long pause. The project manager had been tracking spending, but not performance. She knew what had been spent — she did not know whether the value delivered justified that spending. Two months later, the project finished $68,000 over budget and two months late. The financial performance data that would have enabled early intervention had never been collected.

Tracking spending is not financial management. Financial management requires comparing what was spent to what was planned to be spent for the work actually accomplished — and then using that comparison to predict where the project will end up. Monitor and Control Finances is Process 4 of PMBOK 8’s Finance Domain, and it provides the systematic framework for transforming financial data collection into financial performance management.

This guide covers everything you need to master Monitor and Control Finances:

• What it is — definition, PMBOK 8 position, and what changed from PMBOK 6
• Why use it — direct benefits and the cost of failing to control finances
• Full ITTO — from the official PMBOK 8 PDF
• Step-by-step application guide
• When to apply it
• Two real-world examples — Project Phoenix and Project ProjectAdm
• Templates and downloads
• Five common errors
• Tailoring — predictive, agile, and hybrid
• Process interactions
• Quick-application checklist

1. What Is Monitor and Control Finances

Monitor and Control Finances is the systematic process of overseeing and managing a project’s financial health by continuously tracking expenditures, updating financial records, adjusting the cost baseline and revenue forecasts as needed, and implementing corrective actions to address financial risks. This effort ensures that the project remains financially viable and aligned with budgetary goals throughout its entire life cycle.

Financial monitoring includes variance analysis — comparing actual costs against planned costs to identify and address deviations. The key benefit of this process is that the cost baseline is maintained throughout the project, as well as any anticipated revenue or cost savings projections associated with project outcomes. This process enables proactive decision-making to address deviations, optimize resource allocations, and ensure alignment with financial goals.

Monitor and Control Finances is performed throughout the project, ensuring that costs remain under control and that the project is realizing financial benefits, if relevant. PMBOK 8’s renaming from “Control Costs” to “Monitor and Control Finances” signals the same conceptual expansion as the renaming of the planning process: this is not just about cost control, it is about full financial performance management including revenue tracking, cost savings monitoring, and value realization assessment.

What changed from PMBOK 6 to PMBOK 8

2. Why Use Monitor and Control Finances

Direct benefits

• Early detection of cost overruns: CPI and CV measurements applied at each reporting cycle identify negative cost performance trends while corrective options are still available. A CPI of 0.88 in month 3 is manageable with targeted corrective actions. The same CPI sustained to month 9 without intervention may produce an overrun that cannot be recovered without fundamental project restructuring.
• Accurate financial forecasting: Earned value analysis produces mathematically derived forecasts (EAC, TCPI) that are far more reliable than subjective assessments of “how much more we think we’ll spend.” Accurate forecasting enables the sponsor to make informed decisions about resource allocation, contingency consumption, and scope trade-offs.
• Revenue and cost savings tracking: For projects that generate revenues or cost savings, PMBOK 8’s Monitor and Control Finances explicitly includes tracking these financial benefits against the business case projections. A project delivering below its projected revenue run rate or cost savings rate is a financial performance problem that cost monitoring alone would never reveal.
• Maintained cost baseline integrity: Approved financial changes are incorporated into the cost baseline through formal change control. This ensures the baseline remains an accurate reference for performance measurement throughout the project.
• Stakeholder financial transparency: Regular financial performance reporting — communicating CPI, SPI, EAC, and financial trend data in the agreed format — provides stakeholders with the financial visibility they need to make governance decisions. Stakeholders who do not receive regular financial performance data lose confidence in the project’s financial management.

The cost of failing to control finances

• Budget exhaustion before scope completion: Projects that do not monitor financial performance systematically often discover late in the project that they are significantly over budget, with insufficient funds to complete the remaining scope. At that point, the options are scope reduction (eliminating planned deliverables), emergency funding requests (requiring governance intervention), or project cancellation — all significantly more disruptive than early corrective action would have been.
• No early warning for funding crises: Projects with milestone-based funding (payments triggered by deliverable acceptance) that fail to monitor their payment pipeline may exhaust available cash before the next milestone payment is triggered. Financial monitoring that tracks both expenditures and the timing of revenue inflows prevents cash flow crises.
• Invisible value erosion: For projects expected to generate business value (revenue, cost savings, strategic benefits), the absence of financial performance monitoring means value erosion goes undetected. A project that is on schedule and on budget but is not delivering its projected ROI is a financial failure that cost monitoring alone cannot identify.

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

The following table presents the complete ITTO of Monitor and Control Finances as defined in PMBOK 8 (Figure 2-30, p.170):

Inputs explained

Cost baseline: The time-phased budget against which actual financial performance is measured. The cost baseline provides the planned value (PV) for each time period, which is the essential reference for earned value calculations. A properly developed, time-phased cost baseline is the prerequisite for meaningful financial performance monitoring.

Performance measurement baseline: The integrated scope-schedule-cost baseline that provides the complete context for financial performance analysis. Cost performance cannot be interpreted in isolation from schedule performance: a project with CPI = 0.90 and SPI = 0.90 has different implications than a project with CPI = 0.90 and SPI = 1.05.

Work performance data: Raw financial data from project execution: actual costs incurred (AC); actual hours worked; invoices received; expenses committed but not yet invoiced; and revenue received (for revenue-generating projects). Work performance data must be collected from the organization’s financial systems, not from project team estimates, to ensure accuracy and alignment with organizational accounting records.

Project funding requirements: The time-phased funding availability document produced in Develop Budget. Comparing actual expenditures against funding availability is a distinct monitoring activity from comparing expenditures against the cost baseline. A project can be performing well against its cost baseline while simultaneously experiencing a funding availability crisis if milestone-based payments are delayed or funding tranches are not released on schedule.

Tools & Techniques explained

Earned value analysis: The core analytical technique for financial performance monitoring. Key EVA metrics for financial management:

• Planned Value (PV): The authorized value of work scheduled to be completed by a specific date (from the cost baseline).
• Earned Value (EV): The authorized value of work actually completed by a specific date (from the WBS completion status).
• Actual Cost (AC): The actual cost incurred for work accomplished in a given time period (from financial records).
• Cost Variance (CV = EV − AC): Negative value indicates cost overrun; positive value indicates cost underrun.
• Cost Performance Index (CPI = EV / AC): Values below 1.0 indicate that more money was spent than the value earned; values above 1.0 indicate more value was earned than money spent. CPI is the primary financial health indicator.
• Estimate at Completion (EAC): The forecasted total cost of the project based on current performance. Multiple calculation methods available; the most conservative for a project in cost overrun is EAC = BAC / CPI.
• Variance at Completion (VAC = BAC − EAC): The projected final cost variance. Negative VAC indicates expected overrun; positive VAC indicates expected underrun.

To-complete performance index (TCPI): The required CPI to complete the remaining project work within the budget (either the original BAC or the revised EAC). TCPI = (BAC − EV) / (BAC − AC). If the TCPI required to meet the original BAC is significantly higher (e.g., 1.25) than the current CPI (e.g., 0.88), completing within the original budget is practically impossible and a realistic EAC should be established and presented to the sponsor. The TCPI prevents the common organizational pattern of holding the PM to a budget target that is mathematically unachievable based on current performance data.

Reserve analysis: Assessment of the current contingency and management reserve levels relative to the project’s remaining risk exposure. As the project advances, completed risks are removed from the risk register and their associated contingency provisions may be released. Reserve analysis determines whether the current reserve level is appropriate for the remaining risk profile, and whether any reserve release or supplementation is warranted.

Trend analysis: Examination of CPI values across multiple reporting periods to identify performance trends. A CPI that has been consistently in the 0.88–0.92 range for four months is a stable underperformance that requires a corrective action plan and a revised EAC. A CPI that dropped sharply from 0.98 to 0.82 in a single period indicates a specific cost event that requires immediate root cause analysis.

Outputs explained

Revenue and cost forecasts: PMBOK 8’s explicit addition of revenue forecasting to this process reflects the Finance Domain’s broader scope. Revenue forecasts project when and how much revenue the project will generate (for client-funded, revenue-sharing, or SaaS projects). Cost forecasts project the expected final cost (EAC) and expected cost underrun or overrun (VAC). Together, these forecasts enable the organization to make informed financial decisions about the project’s value delivery and continued investment.

Funding proposals: Formal requests for additional funding triggered by cost overruns that are projected to exceed available budget, or by approved scope changes that increase the project’s authorized cost. Funding proposals must be supported by the financial performance data (CPI, EAC, TCPI) and root cause analysis that justifies the additional funding request. A funding proposal without this supporting analysis is unlikely to receive organizational approval.

Work performance information: Analyzed and structured financial performance data: CPI, CV, TCPI, EAC, VAC, trend analysis results, reserve status, and corrective action recommendations. Work performance information is the input to financial performance communications and change control processes.

4. How to Apply the Process Step by Step

Step 1 — Collect actual cost data from financial systems

At each monitoring cycle, collect actual cost data from the organization’s financial systems — not from team estimates or project management tool self-reports. Actual costs must align with organizational accounting records to ensure that financial performance reports are auditable and consistent with the organization’s financial statements. Collect: invoices paid; costs committed (POs issued but not yet invoiced); labor costs charged to the project; overhead allocations; and any revenue received or recognized.

Step 2 — Calculate earned value metrics

For each WBS work package, determine the earned value (EV): the budgeted cost of work performed, calculated by multiplying the budget at completion for the work package by its percent complete. Aggregate EV, PV, and AC to the project level. Calculate CV, CPI, SV, SPI, EAC, ETC, VAC, and TCPI. Document all calculations for audit purposes.

Step 3 — Compare against financial management plan thresholds

Compare the calculated CPI and CV values against the control thresholds defined in the financial management plan. For CPI values below the lower threshold, initiate a root cause analysis and corrective action planning process. For CPI values below the escalation threshold, prepare a financial performance briefing for the sponsor.

Step 4 — Perform root cause analysis for cost variances

For any cost variance exceeding defined thresholds, determine the root cause: Is it a scope addition that was not processed through change control? A work package that took more effort than estimated due to technical complexity? A vendor invoice that was higher than the contract value? A resource rate change that was not reflected in the budget? Root cause determines corrective action: scope additions require change requests; estimation errors may require re-baselining; contract discrepancies require vendor management actions.

Step 5 — Update revenue and cost forecasts

Update the project’s financial forecasts based on current performance data: EAC (expected final cost); ETC (cost to complete remaining work); VAC (projected final variance); and, for revenue-generating projects, updated revenue projections based on current delivery trajectory and customer billing milestones. Present forecasts as ranges reflecting estimation uncertainty.

Step 6 — Produce financial performance reports

Compile work performance information, financial forecasts, reserve status, and corrective action plans into the financial performance report in the format and frequency defined in the financial management plan. Deliver on the agreed schedule. For threshold-triggering variances, produce a supplemental escalation report in the format the sponsor agreed to in the financial management plan.

5. When to Apply Monitor and Control Finances

• Every financial reporting cycle without exception: Financial monitoring is a continuous process executed at every reporting cycle regardless of perceived project health.
• When actual costs are received from organizational financial systems: In organizations with monthly accounting cycles, financial monitoring is performed monthly at minimum. In projects with weekly invoicing, weekly monitoring is appropriate.
• When an approved scope change affects the cost baseline: Approved scope changes with financial implications require cost baseline updates and revised financial forecasts.
• When the CPI falls below defined thresholds: Threshold-triggering cost performance triggers immediate corrective action analysis and sponsor communication.
• At phase gates: Comprehensive financial performance reviews at phase gate decisions assess whether the project’s financial performance supports proceeding to the next phase and whether the business case financial projections remain valid.

6. Two Real-World Examples

Project Phoenix — TechCorp Website Relaunch

Alex Morgan tracked Project Phoenix financial performance using earned value analysis, synchronized with the weekly WBS completion updates. By month 2 (week 8), the cumulative CPI was 0.93 — above the 0.90 corrective action threshold but trending in a concerning direction (from 0.97 in month 1). Alex performed trend analysis and identified the cause: the external design agency was billing at a higher hourly rate than the contract specified for a specific category of design work. The discrepancy was traced to a contract ambiguity about what constituted “original design work” versus “revision work.”

Root cause analysis led to a contract clarification meeting with the agency, which resolved the billing discrepancy and produced a credit for the overcharges in the previous two invoices. The CPI recovered to 0.97 in month 3. Without earned value monitoring, the discrepancy would have continued for the project’s full 16-week duration, consuming $4,200 of contingency reserve unnecessarily. The financial performance report Alex sent Sarah Chen after month 2 included the discrepancy finding, the corrective action, and the updated EAC — demonstrating exactly the kind of proactive financial management that builds sponsor confidence.

Project ProjectAdm — SaaS Project Management Platform

Eduardo monitored ProjectAdm finances using a burn rate model rather than traditional EVM, reflecting the agile context. Monthly metrics: actual burn rate (actual monthly expenditure); planned burn rate (quarterly budget divided by 3); burn rate variance; runway projection (months of funding remaining at current burn rate); and cost per story point (actual monthly cost divided by actual story points delivered). The cost per story point metric was Eduardo’s primary value efficiency indicator: it measured whether the team was delivering more or less value per dollar invested over time.

In month 5, the cost per story point increased from $380 (months 1–4 average) to $510 — a 34% efficiency decline. Root cause analysis in the sprint retrospective identified a specific technical factor: the team was spending disproportionate effort on infrastructure refactoring work that was not producing story point value. The backlog was restructured to separate infrastructure work (tracked as a maintenance budget) from feature development (tracked against the value delivery budget), restoring visibility into the true cost efficiency of feature development. By month 7, the cost per story point had returned to $395.

7. Templates & Downloads

• Financial Management Plan Template: Download — includes financial performance measurement rules and reporting format.
• Cost Baseline Template: Download — time-phased cost baseline with EVM S-curve and variance tracking columns.
• Basis of Estimates Template: Download — for documenting the assumptions and confidence levels supporting cost estimates and EAC revisions.

8. Five Common Errors

Error 1 — Tracking spending without tracking performance

The most common financial monitoring error is reporting actual costs as a percentage of total budget without referencing what value those costs produced. “We have spent 65% of the budget” is only meaningful in context: if the project is 75% complete, cost performance is excellent (CPI = 1.15); if the project is 50% complete, cost performance is poor (CPI = 0.77). Always report cost performance in the context of value delivered, not just money spent.

Error 2 — Not distinguishing between committed costs and actual costs

Committed costs (purchase orders issued, contracts executed, expenses approved but not yet invoiced) represent financial obligations that should be included in financial monitoring even before they appear in the accounting system. Monitoring only actual (invoiced and paid) costs systematically understates financial exposure and produces optimistic CPI values that will deteriorate when commitments are converted to actuals.

Error 3 — Ignoring the TCPI signal

When the TCPI required to complete within the original budget exceeds 1.1, completing within budget is statistically improbable based on project management research. When TCPI exceeds 1.2, it is effectively impossible. Yet many PMs continue to report the original budget as the target long after TCPI signals make this impossible, avoiding a difficult conversation with the sponsor. When TCPI exceeds 1.1, present the sponsor with an honest EAC and a range of options: scope reduction, cost optimization measures, or a revised budget request. The conversation is difficult; the alternative is worse.

Error 4 — Not tracking revenues for revenue-generating projects

PMBOK 8’s explicit inclusion of revenue and cost forecasts in the Monitor and Control Finances outputs reflects the Finance Domain’s value-oriented perspective. For projects that generate revenues (client-facing projects with milestone payments, SaaS platforms with subscription revenue, internal projects with measurable cost savings), financial monitoring that tracks only expenditures is monitoring half the financial picture. Track actual revenues and projected revenue realization against the business case projections.

Error 5 — Allowing the cost baseline to drift without formal change control

When scope additions are informally absorbed without cost baseline updates, the baseline ceases to be a reliable performance measurement reference. CPI calculations based on a baseline that does not reflect the current approved scope produce misleading performance signals. Every approved change that affects the cost baseline requires a formal baseline update through the change control process documented in the financial management plan.

9. Tailoring Considerations

10. Process Interactions

Inputs from: Develop Budget (cost baseline, project funding requirements); Plan Financial Management (financial management plan with performance measurement rules); Monitor and Control Schedule (SPI data for integrated cost-schedule analysis); project execution (work performance data from financial systems).

Feeds into: Governance Domain’s Assess and Implement Changes (change requests for cost baseline adjustments); organizational financial reporting (work performance information and revenue forecasts feed into organizational financial projections); risk register updates (cost variances may represent realized risks or trigger new risk assessments).

Interactions with other domains: Schedule Domain (CPI and SPI are analyzed together in integrated performance monitoring; schedule variances have cost implications); Scope Domain (scope changes trigger cost impact assessments; Monitor and Control Scope produces change requests that feed into financial impact analysis); Risk Domain (cost risk realizations trigger reserve consumption; reserve analysis in this process updates risk management information); Governance Domain (cost overruns triggering escalation engage the governance structure for financial decisions).

11. Quick-Application Checklist

• Actual cost data collected from organizational financial systems (not project estimates)?
• Committed costs included in financial exposure calculation?
• EV, PV, AC calculated for each WBS work package?
• CPI, CV, SPI, SV, EAC, ETC, VAC, and TCPI calculated at project level?
• Current CPI compared to financial management plan control thresholds?
• Trend analysis performed across multiple reporting periods?
• Root cause analysis completed for variances exceeding thresholds?
• TCPI calculated and compared to current CPI for feasibility assessment?
• Revenue and cost savings tracked against business case projections (where applicable)?
• Financial performance report produced and distributed in agreed format and on agreed schedule?

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.