Estimate at Completion (EAC): PMP Formulas and When to Use Them
Estimate at Completion (EAC) answers a practical project-control question: if the project continues under a particular cost-performance assumption, what is the total cost likely to be when the work is finished? The arithmetic is not difficult. The judgment is choosing the formula that matches what you believe about the remaining work.
EAC belongs to the larger logic of earned value management. Before calculating it, you need to understand the relationship among budget, planned value, earned value, actual cost, and performance indexes. The broader earned value management formulas matter because an EAC result is only as meaningful as the assumptions behind the numbers.
The most common EAC calculations use four inputs:
BAC — Budget at Completion. The approved budget for the work being measured.
EV — Earned Value. The budgeted value of work actually completed.
AC — Actual Cost. What the completed work has actually cost.
CPI — Cost Performance Index. CPI = EV / AC. A CPI below 1.00 indicates that the project is receiving less budgeted value than the money it is spending.
Some forecasts also use the Schedule Performance Index, SPI = EV / PV, when the analyst believes schedule pressure will continue to affect cost. The important point is that the indexes are not decorations. They encode the assumption you are carrying into the forecast.
Use EAC = BAC / CPI when you believe the cost efficiency experienced so far is reasonably representative of the remaining work.
Suppose BAC is $1,000,000. The project has earned $400,000 of value while spending $500,000. CPI is therefore 400,000 / 500,000 = 0.80. If that 0.80 cost efficiency continues, the forecast becomes:
EAC = 1,000,000 / 0.80 = 1,250,000
The calculation says the project is trending toward a $1.25 million total cost, or $250,000 above the original budget.
This method is often the cleanest forecast when the overrun is systemic: productivity is lower than expected, unit costs are consistently higher, rework is recurring, or the estimating assumptions were broadly optimistic.
Use EAC = AC + (BAC - EV) when the cost variance to date is real but you have a credible reason to believe it will not continue.
Using the same project, AC is $500,000, BAC is $1,000,000, and EV is $400,000. The remaining budgeted work is $600,000. If you expect the remaining work to perform according to the original estimate:
EAC = 500,000 + (1,000,000 - 400,000) = 1,100,000
That forecast is much lower than the CPI-based result because it treats the first $100,000 of unfavorable performance as a non-recurring event.
This assumption needs evidence. A one-time supplier penalty, an isolated prototype failure, or a completed piece of expensive rework may justify it. “We will do better from now on” does not.
This form makes the assumption explicit: actual cost already spent cannot be changed, and the remaining budgeted work is adjusted by the current cost-performance index.
EAC = AC + (BAC - EV) / CPI
With AC = $500,000, BAC = $1,000,000, EV = $400,000, and CPI = 0.80:
EAC = 500,000 + 600,000 / 0.80 = 1,250,000
In this simplified example it produces the same result as BAC / CPI. The value of writing the expanded form is that the logic is easier to see: sunk actual cost plus a performance-adjusted estimate for the remaining work.
Some forecasting scenarios assume that poor schedule performance will continue to create cost pressure. In that case, a combined index may be used:
EAC = AC + (BAC - EV) / (CPI × SPI)
If CPI is 0.80 and SPI is 0.90, the denominator becomes 0.72. With the same remaining budgeted work of $600,000:
EAC = 500,000 + 600,000 / 0.72 ≈ 1,333,333
The higher forecast reflects a more pessimistic assumption. It says the remaining work is affected by both the cost inefficiency already observed and schedule conditions that may continue to drive cost.
Do not apply the combined formula automatically whenever SPI is below 1.00. The forecast should reflect the causal reality of the project. A schedule variance does not always translate into additional cost.
Formula-based forecasts are useful when performance history is a reasonable basis for predicting the rest of the project. They are weaker when the future work is materially different from the work already completed.
If the team has re-estimated the remaining scope from the ground up, use:
EAC = AC + bottom-up ETC
ETC is Estimate to Complete: the current forecast of what the remaining work will cost. This can be more defensible after a major scope change, supplier change, architecture redesign, recovery plan, or material shift in resource strategy.
Good forecasting therefore connects EAC with the quality of the estimate itself. The broader set of project estimation techniques matters because a detailed ETC should be built from credible assumptions, quantities, rates, risks, and remaining work—not simply chosen to make the final number look acceptable.
Once you have EAC, calculate Variance at Completion:
VAC = BAC - EAC
If BAC is $1,000,000 and EAC is $1,250,000:
VAC = 1,000,000 - 1,250,000 = -250,000
A negative VAC indicates a forecast overrun. A positive VAC indicates a forecast underrun.
The number becomes useful when it changes a decision. A forecast overrun may require scope review, contingency use, supplier action, funding approval, or a different delivery approach. The project manager should not wait until the money is actually spent before escalating a trend that is already visible.
The To-Complete Performance Index (TCPI) does not predict the final cost. It shows the cost efficiency the remaining work would need in order to achieve a target.
If management still expects the project to meet BAC:
TCPI = (BAC - EV) / (BAC - AC)
Using BAC = $1,000,000, EV = $400,000, and AC = $500,000:
TCPI = 600,000 / 500,000 = 1.20
The team has been performing at a CPI of 0.80 but would need a future efficiency of 1.20 to recover to the original budget. That gap should trigger a management discussion. The number may show that the original target is no longer realistic.
The PMP formula set is easier to learn when each formula answers a management question rather than being treated as a symbol-memorization exercise.
For exam questions and real project work, the most important words are usually the assumptions:
“Current cost performance is expected to continue.” Think CPI-based forecast.
“The variance was atypical and the remaining work will follow the original plan.” Think actual cost plus original remaining budget.
“Both cost and schedule performance are expected to influence the remaining work.” Consider the combined CPI/SPI forecast.
“The remaining work has been re-estimated.” Use actual cost plus a new bottom-up ETC.
This scenario-based reasoning is more useful for the current PMP certification than memorizing formulas without knowing when their assumptions apply. PMI’s current exam places substantial emphasis on project outcomes, value, business impact, and real-world decision making, so calculations should be connected to the management choice they inform.
A strong project status report should not present one EAC number with no context. State which method was used, why it was chosen, what assumptions matter, and which risks could move the forecast.
For example: “Current EAC is $1.25 million based on CPI performance of 0.80. The forecast assumes the productivity trend continues through remaining software integration. If the planned automation reduces rework after the next release, the bottom-up ETC will be refreshed.”
That sentence gives management something to evaluate. It is stronger than a spreadsheet that produces a precise number from an assumption nobody discussed.
Practice EAC inside broader cost-control scenarios rather than in isolation. Use PMP financial planning and cost-control scenarios and performance-measurement scenarios to explain why one forecast is more appropriate than another.
EAC is not a single formula. It is a family of forecasts built around different assumptions about future performance. Identify the reason for the variance, decide whether it is expected to continue, determine whether schedule pressure affects cost, and use a bottom-up estimate when the remaining plan has materially changed. The arithmetic then becomes the easy part.
