Estimate at Completion Explained for Project Managers
It's Friday afternoon, the steering meeting is over, and the project looked fine an hour ago. Then the delivery lead checks the latest actuals and realises the budget story is no longer comfortable, especially before the next client billing cycle. That's exactly the kind of moment when Estimate at Completion, or EAC, earns its place in the weekly review, because it turns “how much have we spent?” and “how much is left?” into one forward-looking cost forecast.
EAC is not a slogan and it's not a single magic formula. It's a recurring decision under uncertainty, updated as new performance data arrives, so the number can move as the project moves. If you manage delivery, that's the point, you're not trying to admire a spreadsheet total, you're trying to spot whether the final cost is still likely to land near the baseline or has started to drift in a way that needs action.
Table of Contents
- Why Estimate at Completion Matters in Delivery
- How Estimate at Completion Fits in Earned Value Management
- The Core EAC Formulas You Will Actually Use
- Reading the Gap Between EAC and Original Budget
- When EAC Becomes Reliable Enough to Trust
- Common Misinterpretations That Distort Decisions
- Turning EAC Movement Into Delivery Action
Why Estimate at Completion Matters in Delivery
A delivery lead usually doesn't discover budget trouble in a finance report first. It shows up in small ways, a time sheet that looks heavier than expected, a workstream that needs more rework than planned, or a client request that got handled informally and never made it into the change log. By the time the steering deck is updated, the project can already be exposed.
Estimate at Completion exists to surface that exposure early. The basic logic is simple, it blends what you've already spent with what you still expect to spend, so you're not only looking backwards at actual cost, you're also looking forwards at the likely final cost. The U.S. Department of Energy's EVM tutorial describes EAC as the actual cost to date plus an objective estimate of the remaining authorised work, and PMI treats it as the expected total cost when the defined scope is complete project office overview.
Why delivery heads should care before the month ends
A project can look healthy in execution terms and still be drifting financially. That's the part many teams miss, because delivery status and cost status are not always aligned. A workstream can be on time but inefficient, or the team can be busy while still consuming budget faster than the work is being earned.
Practical rule: if the latest cost forecast can't be explained in plain language to a client, it probably isn't being used as a real control signal yet.
For a delivery head, EAC belongs in the weekly review because it helps answer a question steering committees ask all the time, even when they don't phrase it that way, “What will this project cost when it's finished?” That's different from asking what has already been spent. It's also different from asking whether the team is busy.
A strong EAC discussion gives you three things at once. It tells you what has happened, what remains, and whether the original budget still looks credible. That makes it a management forecast, not an accounting label.
The rest of the challenge is learning how to read the variables behind it, when to trust the number, and what to do when it starts moving in the wrong direction.
How Estimate at Completion Fits in Earned Value Management
EAC sits inside earned value management, where the point is to compare planned value, earned value, and actual cost in a way that supports forecasting. The common variables are AC for actual cost, EV for earned value, BAC for budget at completion, and CPI for cost performance index. Together they explain why EAC is a forecast of the finish, not just a sum of invoices.
A simple project example
Take a project with a 100,000 USD budget at completion. If the team has earned 40% EV complete, then the value of work accomplished is 40,000 USD by value, not by spend. If the actual cost is 55,000 USD, then the team has spent more than the value earned so far, which is the first clue that the final cost forecast needs attention.
That's the key distinction many readers get tangled up on. EV tells you the value of work achieved. AC tells you what you've really spent. BAC is the approved total budget. CPI compares earned value against actual cost, so it helps explain whether you're getting cost efficiency or losing it.
A useful way to think about EAC is like a road trip estimate. The fuel already used matters, but so does the distance still ahead and the current rate of consumption. If the car is burning fuel faster than expected, the arrival cost changes even if the destination stays the same.
Plain-English takeaway: EAC is what you get when finance and delivery stop talking in separate rooms and start using the same forecast.
The reason this matters in a PMO dashboard is that each variable contributes a different piece of the story. AC tells you what's gone out the door. EV tells you what that spend has produced. BAC anchors the original commitment. CPI gives you a signal about efficiency. EAC pulls them together into one number a delivery head can manage against.
Choosing Between Common EAC Formulas
| Formula | Best Used When | Example Result |
|---|---|---|
| EAC = AC + ETC | The remaining work has a fresh, credible estimate | If AC is 55,000 USD and ETC is 35,000 USD, EAC is 90,000 USD |
| EAC = AC + CPI(BAC - EV) | Past cost performance is expected to continue | If AC is 55,000 USD, BAC is 100,000 USD, EV is 40,000 USD, and CPI is 0.8, EAC is 130,000 USD |
The table shows an important point. EAC is not a single number produced the same way every time. It's a forecast built from the way you believe the rest of the project will behave.
The Core EAC Formulas You Will Actually Use
The two formulas most delivery teams rely on answer two different questions. One asks, “If I re-estimate the remaining work cleanly, what does the finish look like?” The other asks, “If current performance continues, what's the likely total?” They are different lenses on the same project.
Fresh estimate for the remaining work
Use EAC = AC + ETC when the work left to do has been reassessed properly. ETC means estimate to complete, the remaining cost forecast from this point onward. This works best when the team has a new, realistic view of what's still ahead, maybe because scope has changed, assumptions have been clarified, or the original plan was too crude.
Say you've spent 55,000 USD so far. The team reviews the remaining tasks and believes the rest will cost 35,000 USD. In that case, EAC = 90,000 USD. The value is useful because it reflects current thinking about the unfinished work, not just a mechanical extension of old performance.
Performance-based forecast
Use EAC = AC + (BAC - EV) / CPI when you expect current efficiency to continue. This is the formula many managers reach for when they believe the work ahead will behave much like the work behind. It's especially useful when the team's cost performance is stable enough to extrapolate.
If AC = 55,000 USD, BAC = 100,000 USD, EV = 40,000 USD, and CPI = 0.8, then the remaining budgeted work is 60,000 USD, but adjusted for efficiency it becomes 75,000 USD. Add that to actual cost, and the EAC becomes 130,000 USD. That's a very different management conversation from the fresh-estimate scenario.
Decision habit: use the formula that matches the story you can defend in front of a sponsor, not the one that gives the most comfortable number.
The mistake many teams make is choosing a formula because it looks simpler. The better question is whether the remaining work is reset and re-estimated, or whether yesterday's efficiency is still the best guide. If the answer is unclear, the forecast itself needs discussion, not just the math.
Reading the Gap Between EAC and Original Budget
The easiest way to read EAC is to compare it with BAC. If the two numbers are close, the project still looks aligned with the original plan. If EAC rises above BAC, the team has a cost overrun developing. If EAC falls below BAC, the project may be tracking under budget, or the scope may be shrinking in practice.
That sounds obvious, but the value is in the size of the gap and what it means over time. A small variance can be manageable on a single project. Across a portfolio, though, a gap that looks modest on one programme can force awkward conversations about margin, resourcing, or client billing.
What the gap usually says
If EAC is roughly equal to BAC, the original budget still has credibility. If EAC is above BAC, the delivery head should ask whether the cause is efficiency, rework, scope drift, or a combination. If EAC is below BAC, that isn't automatically good news either, because the forecast might be hiding under-scoped work or unrecorded change.
That's why a gap should never be read alone. Compare it against scope notes, recent changes, and the assumptions behind the remaining estimate. The internal delivery visibility check is only useful when it helps you separate a real delivery issue from a reporting issue.
A practical executive response usually starts when the forecast shift is no longer explainable as noise. If the number has moved and the explanation is vague, the project isn't ready for passive monitoring. It's ready for a review of scope, estimate basis, and whether the current staffing model still matches the work.
The portfolio effect is where leaders feel the pain. A gap that seems tolerable in isolation can create pressure across multiple client accounts, because each project competes for the same delivery capacity and cash flow discipline. That's why EAC should be used as a decision input, not just a project accounting metric.
When EAC Becomes Reliable Enough to Trust
EAC is useful long before a project is finished, but it isn't equally trustworthy at every stage. The DoD contract analysis found that EACCPI and EACSCI both reached the 5% accuracy band at approximately 70% completion, with EACSCI getting there slightly earlier DoD contract analysis. That's a strong reminder that early forecasts can be directionally useful without being tightly dependable.
What that means in practice
Before a project is well underway, the estimate is being built on thinner evidence. That's normal, but it means false precision is dangerous. A forecast made too early can look polished while still being unstable, because there isn't enough execution history to anchor the remaining work.
Once a project moves beyond the midpoint and the team has real delivery data, EAC starts acting more like a control metric. The forecast is still changing, but the movement is better informed by actual performance rather than assumption alone. That is when leaders can start using EAC to decide whether the project is converging or slipping.
EAC is a directional signal early, a control signal later.
The useful rule of thumb is simple. Treat EAC as a conversation starter when the project is still young, and as a management lever once there's enough execution history behind it. If a leader asks for high confidence too early, the right answer is not a prettier number, it's a clearer explanation of the assumptions.
For teams that run manual status reporting, that threshold matters even more. The manual status reporting audit is usually where the hidden weakness shows up, because the more manual the process, the easier it is to overstate certainty.
The practical lesson is not to wait until the end before caring about EAC. It's to change how much weight you give it as the project matures. Early on, use it to spot direction. Later, use it to steer.
Common Misinterpretations That Distort Decisions
The biggest EAC mistakes usually come from treating a forecast like a fixed truth. Teams calculate it once, paste it into a deck, and then act as if the number should stay still even though delivery reality keeps moving. That defeats the point of a forecast.
The four mistakes that cause the most damage
- Treating EAC as a one-time calculation: The forecast should be updated as actual cost and remaining work change. If it sits unchanged for weeks, it stops reflecting delivery reality.
- Confusing EAC with the original budget: BAC is the approved starting budget, EAC is the expected finish. Mixing them up makes a gap look either better or worse than it really is.
- Ignoring scope change: If the scope expanded, a higher EAC may not mean poor performance. It may mean the project has more work than the original budget covered.
- Reporting the number without assumptions: A bare EAC tells you very little. Leaders need to know whether the forecast is based on fresh remaining work, continuing CPI, or some other logic.
The corrective habit is simple, but many teams skip it. Every forecast cycle should include the basis of estimate, the main assumptions, and the trigger that would make the number change again. Without that, EAC turns into a decorative metric instead of a management tool.
In PMO settings, the quality of the conversation matters as much as the arithmetic. If the sponsor only sees the number and not the reasoning, they'll either overreact or underreact. Neither helps the delivery team.
Turning EAC Movement Into Delivery Action
The next useful question is not “What is the EAC?” It's “What do I do when it moves?” The answer should be a short playbook the delivery lead can run every cycle, not a debate that starts from scratch each time.
A simple action sequence
- Define triggers. Decide what level of forecast movement deserves attention, and make the trigger visible in the weekly review. If the movement is material, don't wait for the monthly report.
- Verify inputs. Check the source data behind AC, EV, CPI, and the current remaining estimate. Bad input gives you a confident wrong answer.
- Initiate conversation. Bring the sponsor, finance lead, or workstream owner into the discussion early, then agree whether the right response is scope rebaselining, resourcing adjustment, or a revised ETC.
That playbook is especially useful when delivery teams are spread across tools and conversations. The internal workflows capability is the kind of place where teams can keep the review rhythm visible without turning EAC into a one-person spreadsheet exercise. Deliverhub AI is one option that brings project signals, status context, and forecast movement into a single view for software agencies.
The Friday-afternoon problem doesn't go away on its own. What changes is whether the delivery head sees the drift early enough to act before the client does.
If you want a cleaner way to surface forecast drift before it turns into a client escalation, visit Deliverhub AI and see how it brings project signals, delivery context, and recurring risk review into one workflow. It's a practical fit when you need EAC to live inside the management rhythm, not in a separate spreadsheet that gets opened after the damage is already visible.