Project budgets rarely collapse in a single moment. They erode hour by hour — until the end of the project reveals a shortfall that could have been spotted weeks earlier. The Forecast (EAC) Hours KPI makes exactly that possible: a reliable projection of total hours based on real project data, not gut feeling.
What Are Forecast (EAC) Hours?
EAC stands for Estimate at Completion. The KPI answers the central question: How many hours will this project consume in total if it continues at its current efficiency level?
What makes EAC different from a simple extrapolation is that it accounts for how productively your team has actually been working — measured by the Cost Performance Index (CPI). Teams that have been more efficient than planned get a favorable forecast. Teams running behind plan see that honestly in the number — and still have time to act.
How Are EAC Hours Calculated?
The formula is:
EAC = AC + (BAC − EV) ÷ CPI
Breaking down each component:
- AC (Actual Cost in hours): all project hours worked to date — what has already happened cannot be changed.
- BAC (Budget at Completion): the sum of all planned task budgets, i.e., the project’s total planned hours.
- EV (Earned Value in hours): the hours already “earned” through completed or in-progress work — the share of budget that has actually been delivered.
- CPI (Cost Performance Index): the ratio of earned value to actual hours consumed. A CPI of 0.95 means the team is spending 1.05 hours for every planned hour.
Step-by-Step Example from the Dashboard
Assume the project has the following figures:
| Metric | Value |
|---|---|
| BAC (planned budget) | 168 hours |
| AC (hours worked so far) | 78 hours |
| EV (earned value) | 74 hours |
| CPI | 0.95 |
Calculation:
- Remaining work: 168 h − 74 h = 94 h not yet delivered
- Efficiency adjustment: 94 h ÷ 0.95 = 98.9 h — because the team is slightly below plan, a few more hours will be needed
- Total forecast: 78 h + 98.9 h = 176.9 h ≈ 177 h
Result: The project is projected to consume 177 hours against a planned 168 — an overrun of 9 hours, or +5.4%.
What Does This Mean in Practice?
Reading EAC follows a straightforward logic:
- EAC = BAC: The project is exactly on plan. No overrun or underrun expected.
- EAC < BAC: The project will finish more efficiently than planned — a positive signal for capacity planning and future project estimates.
- EAC slightly > BAC (up to ~10%): A minor overrun within normal variation. Monitor the trend, but no immediate action required.
- EAC significantly > BAC (>10%): A significant overrun — analyze the root cause now: Was the estimate wrong? Has complexity increased? Are there resource bottlenecks?
In the example above, +5.4% is a yellow flag, not a crisis. The project is running slightly over budget, but the CPI of 0.95 shows the deviation is moderate and stable.
Three Perspectives on EAC Hours
What the Project Manager Sees
The PM immediately knows whether the hour budget is still sufficient or whether capacity needs to be reallocated. EAC enables early stakeholder communication — before the budget is actually breached, not after the fact.
What C-Level Sees
Executives can assess across a portfolio which projects are on track and which are consuming reserve capacity. A consistently high EAC across multiple projects signals that the estimation and scoping process deserves a review.
What the Team Lead Sees
The team lead understands how their team’s efficiency affects the overall outcome. A CPI below 1.0 is not a judgment — it is useful information that invites an honest conversation about task distribution, complexity, or capacity constraints.
Common Mistakes and Pitfalls
Many project teams make the same error: they look only at hours worked so far (AC) and extrapolate linearly. This produces inaccurate forecasts because it ignores the team’s actual efficiency.
A second classic mistake: time reports are updated too infrequently. If team members log hours only at the end of the month, the EAC is effectively blind for three to four weeks at a time. Up-to-date time tracking is a prerequisite for a meaningful forecast.
A third pitfall: vacation and sick leave hours are included in project hours. This inflates AC and distorts the CPI. Only genuine project hours — no absences — should feed into the calculation.
How zistemo Delivers EAC Hours
1. Earned Value Analysis Out of the Box
zistemo calculates EV, CPI, and EAC automatically — no manual Excel formulas, no configuration overhead. As soon as time entries are recorded, the forecast updates in real time. The project dashboard displays EAC alongside all other KPIs in a single, clearly structured cockpit.
2. Time Tracking with Automatic Categorization
The integrated time tracking distinguishes automatically between project hours, vacation, and sick days. Only project hours feed into the EAC — absences do not distort the forecast. Team members can log time via timer, manual entry, or the mobile app; data is immediately visible in the dashboard.
3. Approval Workflows for Reliable Data
Weekly reports go through a structured approval process in zistemo: team member submits, manager approves. This ensures that only validated hours enter the EAC — no estimated figures, no retroactively corrected values.
zistemo USPs: Why EAC Works Especially Well Here
More Clarity — Now, Not at Month-End
In many organizations, the project status is current only once a month — when the reporting backlog is finally cleared. zistemo updates EAC and all other KPIs continuously. You see the forecast today, not three weeks from now.
All-in-One Instead of Tool Chaos
Time tracking, earned value analysis, and project controlling in a single platform — no data transfer between Excel and project management tools, no manual merging of hour lists. All the data EAC requires is generated in the same place where work is recorded.
Out-of-the-Box Earned Value and EAC
EAC calculation following PMI methodology is not an add-on or a consulting engagement. It is included in zistemo as standard — for every project, from day one.
Related KPIs
- Forecast (EAC) Cost — the cost equivalent of EAC Hours
- Budget Usage (Hours) — current hour consumption baseline
Conclusion
Forecast (EAC) Hours is not an academic concept from a project management textbook. It is the earliest reliable warning signal a project team can have: based on actual efficiency, it shows whether the hour budget will hold — or whether action is needed before an overrun becomes a fait accompli.
The prerequisite is that the underlying data is current and accurate. With an integrated platform like zistemo, that is not extra work — it is the natural result of a consistent time-tracking habit.
Start Using zistemo for Free
Get full earned value analysis, EAC forecasting, and a real-time dashboard — no setup overhead, no Excel formulas required.
FAQ
What is the difference between EAC and BAC?
BAC (Budget at Completion) is the originally planned hour budget — a fixed value from the project estimate. EAC (Estimate at Completion) is the current, data-driven projection of how many hours the project will actually consume. EAC changes with every new time entry; BAC stays constant unless a scope change is formally agreed.
How often should EAC be updated?
Ideally daily, with every new time entry. In zistemo, this happens automatically. Projects updated only monthly have an EAC that lags reality by up to four weeks — making early corrective action impossible.
What should I do if EAC is significantly above BAC?
Start with root-cause analysis: Is the CPI consistently below 1.0, or was it a one-off event? Then evaluate your options: reduce scope, add resources, inform the client about additional effort, or formally adjust the budget. zistemo gives you the data foundation — the decision is yours.
