Do You Still Need to Memorise EVM Formulas for PMP?

Ask a PMP candidate about earned value and you will usually get a list. Planned value, earned value, actual cost, two variances, two indices, three routes to an estimate at completion, and a to-complete performance index that almost nobody enjoys. The list is normally accurate. On its own it is also close to useless, because the question a sponsor asks is never "what is the cost performance index". It is whether the money will last, and what you propose to do about it. Reciting a formula and answering that question are different skills, and preparation has traditionally spent far more effort on the first.

The short answer is that a small core is worth holding in memory, and the long formula sheet is not where candidates come unstuck. What separates a confident answer from a guess is knowing what each measure compares, and what it cannot tell you.

Three measurements generate almost all of it

Earned value rests on three numbers: what you planned to have spent by now, what the work you have actually completed was budgeted to cost, and what you have genuinely paid out. Earned value is the pivot between the other two. Compare it against actual cost and you are asking a cost question. Compare it against planned value and you are asking a schedule question, expressed in money.

Once that structure is clear, most of the formula sheet reassembles itself. Subtract and you get a variance, expressed in currency. Divide and you get an index, expressed as a ratio where anything below one is worse than planned. That single pattern regenerates cost variance, schedule variance and both performance indices without any recall at all. Forecasting extends the same comparison forwards, and the different routes to an estimate at completion are not competing formulas so much as competing assumptions about whether the pattern you have seen so far will continue.

This sits inside a wider frame than cost control. Section 2.4 of the PMBOK® Guide Eighth Edition treats earned value within the Finance Performance Domain, alongside financial planning, estimating, budgets, funding, reserves, forecasting and financial decision-making. The grouping is deliberate. Earned value is one source of decision information among several, not the discipline itself, and a project manager who can calculate a variance but cannot say what it means for funding or reserves has learned the smaller half of the subject.

What the current exam asks you to do with the numbers

The 2026 PMP® Examination Content Outline places finance in the Process domain, which accounts for 41% of items on the exam. The relevant task is Plan and manage finance, and the wording of its enablers repays a close reading. Analyse project financial needs. Quantify risk and contingency financial allocations. Plan spend tracking. Plan financial reporting. Anticipate future finance challenges. Monitor financial variations and work with the governance process. Manage financial reserves.

The verbs there are analyse, plan, anticipate, monitor and manage. None of them is calculate. That does not mean arithmetic has disappeared, and nobody outside PMI can say how many items on a given form involve a calculation. It does suggest that the exam is testing what you do with a financial signal rather than whether you can reproduce a ratio from memory.

The current outline also describes question types that reinforce the same point. Graphic-based questions require candidates to interpret visual information such as charts, graphs and diagrams before answering, and case or scenario questions present a detailed situation, sometimes with accompanying charts, and then ask a series of questions against it. Being able to read a performance curve and say what has probably happened is a more directly examinable skill than being able to write out the formula that produced it.

There is a common preparation convention worth naming here rather than inheriting. Candidates are often advised to reproduce a memorised formula sheet in the first few minutes of the exam. Whether that is permitted at all depends on the delivery modality and current test-centre rules, which are worth checking with PMI rather than with a study forum. Setting the rules aside, the tactic solves a problem most candidates do not have. With 180 questions and 240 minutes, minutes spent transcribing relationships you cannot interpret buy very little.

The number tells you where to look, not what you are looking at

A cost performance index of 0.93 is a prompt to investigate. It is not a diagnosis, and treating it as one is the most common failure of financial control on real projects.

Consider a depot upgrade programme in month seven of eleven. The monthly report shows a cost performance index of 0.93 and a schedule performance index of 1.05. Read literally, the project is ahead of schedule and overspending. The steering group draws the obvious conclusion and asks the project manager to release contingency to cover the gap.

The combination is odd, and that is the first thing to notice. Work that is genuinely running ahead of plan does not usually cost more per unit of output unless something specific has been done to make it so. Two things had. Progress was being claimed when ducting arrived on site rather than when it was installed, which inflated earned value against work that had not yet been performed. Separately, the contractor had added a second shift at premium rates to recover an earlier delay, and that decision was showing up honestly in actual cost.

So one index was flattering and the other was accurate but already explained by a decision the project had taken. The correct sequence was to fix the earned value rule first, reforecast on the corrected basis, and only then take a reserve question to the steering group. Releasing contingency against the original figures would have funded a variance that partly did not exist, and would have done it using the mechanism that exists for identified risk rather than for measurement error. This is the kind of sequencing we work through in some depth during PMP® Exam Preparation, because the order in which you check things usually matters more than the calculation itself.

The schedule index carries a structural weakness worth knowing about. It is measured in cost units rather than time, and it drifts towards 1.0 as a project approaches completion, because eventually all the planned work has been earned regardless of how late it was. A late project can show a perfectly respectable schedule performance index in its final months. Experienced project managers therefore treat it as a mid-project trend indicator and go to the schedule network and the milestone dates for anything that matters.

So how much should you actually memorise?

Hold the three measurements and the two comparison structures. Be able to rebuild the variances and the indices from that structure rather than from recall. Understand what each forecasting route assumes about the future, because that assumption is the real content and the letters are only notation. Know what a poor index does not tell you.

That is a much shorter list than most study material implies, and it survives contact with real work in a way the longer list does not. On a live project the arithmetic sits inside a cost tool and nobody calculates it by hand. What no tool will do is tell you whether percentage complete is being reported honestly, whether the earned value rules match how work is genuinely claimed, whether a variance is a pattern or a one-off, or whether a figure has drifted because a supplier changed their invoicing cycle.

The approach also matters. Earned value assumes a reasonably stable baseline against which performance can be measured, which is why it works well across predictive delivery and awkwardly across adaptive work, where scope is expected to change by design. Adaptive teams more often track spend against funded increments, cost per iteration or run rate, and ask value questions at the point of reprioritisation. On hybrid projects, earned value is frequently applied to the predictive workstreams while the adaptive workstreams are governed by funding decisions instead, and confusing the two produces reports that are internally consistent and quietly meaningless.

For a PMP candidate, the useful habit is to read every financial scenario twice: once for the number, and once for what the number is being asked to prove. For a working project manager, the same habit prevents you from taking a well-formatted variance to a steering group before you have established whether it is real.

Andre Malowney

Interested in going further?

Financial questions on real projects rarely arrive as clean arithmetic. They arrive as a figure that looks wrong, a reserve request that may be premature, and a governance meeting already in the diary. Structured preparation gives you the sequence to work through that under pressure, across the wider syllabus rather than in one topic at a time.

If you want to see how earned value sits alongside budgets, funding and reserves rather than standing apart from them, the Finance Performance Domain in the PMBOK® Guide Eighth Edition is the section to read next.

Ad · Amazon affiliate link.

References

A123: The PMBOK 8 Finance Performance Domain: What It Really Covers
A127: CPI and SPI Explained Without Formula Memorisation
A129: Estimate at Completion: What Question Are You Really Answering?
A125: Budget vs Cost Baseline vs Funding
A126: Contingency Reserve vs Management Reserve

PMP and PMBOK are registered marks of the Project Management Institute, Inc.