Explore how to calculate the Estimate at Completion when future work mirrors current performance. With EAC = AC + (BAC − EV), you sum what’s spent to date and the remaining budget to finish. This practical explanation ties together EV, AC, BAC, CPI, and cost forecasting concepts in PMI project management.

Multiple Choice

How is the Estimate at Completion (EAC) computed when future work is expected to proceed at the same rate as current performance?

When future work is expected to proceed at the same rate as what has been achieved so far, the forecast for the total cost is the money already spent plus the cost needed to finish the remaining work. The remaining work in budget terms is the total budget minus the earned value to date (BAC − EV). So the estimate at completion is the actual costs to date plus that remaining amount: EAC = AC + (BAC − EV). This uses the idea that you’ll carry on with the same cost performance, adding what's left to finish to what you've already spent.

Ever wonder how project financials project out when things are cruising along at the same pace they’ve been? In project management speak, that’s the moment to think about the Estimate at Completion (EAC) under a simple, steady-state assumption. If the project’s future work is expected to run at the same rate as the work that’s already been done, what does the cost picture look like when you pull the curtain on the last mile?

Let’s unpack it in plain terms and with a little practical intuition. You’ve got a budget at completion (BAC), you’ve spent some money so far (AC, actual cost), and you’ve earned some value from the work completed (EV, earned value). The key is to connect what you’ve spent, what you’ve earned, and what remains to be done, under the premise that the cost performance from here on out mirrors what you’ve already achieved.

The core idea: what’s left to do, in budget terms, is BAC minus EV. If future work proceeds at the same pace as current performance, the cost to finish that remaining work should resemble that remaining budget. Add that to what you’ve already spent, and you’ve got your EAC.

Want to see it in a compact form? The expression is:

EAC = AC + (BAC − EV)

Now, let me explain what each piece means and why this works so well in steady-state scenarios.

Breaking down the components

  • BAC (Budget at Completion): This is the total budget for the project. Think of it as the ceiling you’ve promised to stay under, the grand sum you planned to invest to deliver everything.

  • EV (Earned Value): This is the value of the work actually completed, expressed in terms of the budget. If you’ve completed 40% of the scope and the total budget is $100,000, your EV would be $40,000.

  • AC (Actual Cost): This is the money you’ve spent up to now, regardless of what you’ve earned. It’s the real cash outflow that has happened.

  • BAC − EV: This tells you how much value (in budget terms) is left to earn. It’s not just dollars left to spend; it’s the remaining portion of the planned value that must be delivered to reach completion.

Putting it together

  • If the future pace keeps matching the past pace, you’ll continue to burn money to deliver the remaining value at roughly the same cost rate you’ve seen so far.

  • The remaining work, in budget terms, is BAC − EV.

  • Add that to AC, and you’ve projected the total expenditure when all is said and done: EAC.

A concrete example helps it click

Imagine a project with:

  • BAC = $1,000,000

  • EV to date = $420,000

  • AC to date = $480,000

That means you’ve spent $480k and earned $420k in value so far, so there’s $580,000 worth of planned value left to capture (BAC − EV = 580,000). If the trend continues—same cost performance as today—the forecasted total cost to complete the job is:

EAC = AC + (BAC − EV) = $480,000 + $580,000 = $1,060,000

So, under the steady-state assumption, you’d expect to end up around $1.06 million, a bit above the original budget. The idea is simple, but the implications are practical: you can flag that overrun early and consider corrective actions that could tighten the remaining cost curve.

Contrast with other scenarios (worth knowing what’s not implied)

It’s helpful to see what this approach does and doesn’t assume, especially when you’re juggling multiple project conditions. The EAC formula above rests on a particular premise: the rate of spending and the rate of earning will continue as they have been. In other words, the cost performance index (CPI) is expected to stay stable.

  • If CPI is high and healthy (costs are efficient), that steady-state assumption might hold longer, and EAC will hover closer to BAC.

  • If CPI has fallen off a cliff (costs creeping up, or earned value lagging), sticking with the same rate would be optimistic. In those cases, you might use more complex EAC calculations that factor in CPI trends or forecasted changes in productivity.

That’s the beauty of the EAC under this specific assumption: it’s a clean, intuitive forecast based on what’s already happened, projected forward with the same rhythm.

Some practical takeaways you can keep in mind

  • It’s a forward-looking yardstick under a simple rule: continue the current pace. If you’re delivering more slowly or spending less efficiently, this method will still show the continuing path, but you’ll want to compare it against other indicators to see if realism is slipping in.

  • It highlights the “gap” between what was planned and what’s been delivered so far. If that gap grows, the EAC climbs, signaling a potential overruns if trends don’t shift.

  • It’s particularly useful in steady, mature projects where performance doesn’t swing wildly from week to week. Think of ongoing manufacturing lines, maintenance programs, or software habitats with stable cost drivers.

A few caveats to keep in mind (and yes, we’ll keep it practical)

  • Not a crystal ball: The method assumes the future resembles the past. If a major scope change is on the horizon, or if the team’s productivity is expected to shift (for better or worse), this EAC won’t catch those shifts on its own. It acts as a baseline, not a prophecy.

  • Data quality matters: You need accurate AC, EV, and BAC. If EV is lagging because of reporting delays, you might misread the pace. Clean, timely data is the secret sauce here.

  • It’s one lens among many: Cast a wider net by looking at schedule performance index (SPI) too, or use forecast methods that incorporate trend lines, risk buffers, or scenario analysis. The goal is a well-rounded picture, not a single number.

Where this fits into the bigger toolkit

If you’re exploring project controls, you’ll encounter a handful of related concepts that feel a bit like siblings. Here’s how this particular EAC fits in and where it connects:

  • CPI (Cost Performance Index): EV divided by AC. It tells you whether you’re getting more value for every dollar spent. If CPI is above 1, you’re earning more value per dollar; below 1, expenses outpace progress. In the steady-state EAC, you’re effectively presuming CPI holds steady.

  • SPI (Schedule Performance Index): EV divided by PV (planned value). It signals whether you’re delivering on time relative to the plan. Even if CPI is steady, if you’re behind schedule, the EAC might look different once you factor in schedule pressure.

  • Variances (CV and SV): Cost variance (CV = EV − AC) and schedule variance (SV = EV − PV) give you a quick pulse on how things are trending. They can cue you to re-run EAC with more nuanced assumptions.

  • EAC variants: There are other formulas that reflect different outlooks. For instance, if you expect the remaining work to be priced at the current CPI, you might see EAC = BAC / CPI. That’s a different flavor for different project realities.

A quick, relatable analogy

Think of a road trip with a fixed budget. You’ve saved a certain amount and spent a chunk to get this far. The road ahead has a known distance left—equal to the portion of the budget you haven’t yet used (BAC − EV). If you keep driving with the same fuel efficiency (the same cost performance) you’ve shown so far, you’ll need the remaining budget to finish the trip. You add that to what you’ve already spent, and you have a realistic estimate of total spending by the time you reach the destination. It’s not magic; it’s a straightforward arithmetic that honors how you’ve actually moved so far.

Common pitfalls to avoid

  • Treating EAC as a guarantee: It’s a forecast, not a promise. Use it as a guide, and test it against alternative scenarios.

  • Forgetting to update inputs: As the project progresses, AC, EV, and BAC can shift. Recalculate as new data rolls in to keep the picture honest.

  • Over-relying on a single metric: The EAC sits within a family of performance measures. Bring in a few more perspectives to ground your decisions.

A call to curiosity

If you’ve ever watched a project’s rhythm—the way teams coordinate, the way vendors bill, the way milestones slip or slide—you know there’s a story behind the numbers. The EAC under a steady-state assumption is a story about consistency. It asks a simple question: given how we’ve done so far, what will it cost to finish if nothing changes in the cost pattern?

That question isn’t about verdicts. It’s about anticipation. It’s a prompt to keep an eye on the horizon without losing sight of the ground you’ve already covered. And truth be told, that balance—staying grounded while forecasting beyond the next bend—is what makes project management both art and science.

If you’re curious to see how this plays out in real-world projects, pull up a case study or two where teams documented their AC, EV, and BAC over several reporting periods. It’s enlightening to watch how, even with a steady rate, small shifts in earned value can nudge the EAC in meaningful ways. You’ll notice patterns—seasonal demand, supplier lead times, or a sudden bump in productivity—that illuminate how the same formula adapts to real life.

Final reflections

The EAC idea we’ve explored is pleasantly straightforward: forecast the finish by taking what you’ve spent and adding the cost needed to finish the remaining work, assuming the future keeps pace with the past. It’s a practical lens for teams that want to keep their eyes on the road, without getting lost in a tangle of complexities. It invites a calm, informed conversation about how to steer a project toward completion with clarity and confidence.

And if you ever find yourself juggling metrics and wondering which one tells the full story, remember this: numbers are powerful not because they shout the truth, but because they help us see patterns, test intuitions, and guide smarter choices. The steady-state EAC is one such compass—simple in its math, meaningful in its implications.