Most construction projects report cost and schedule progress separately — and that’s exactly why project managers routinely get blindsided. A project can be precisely on budget while running 15% behind schedule, and the traditional cost report will show nothing wrong. Earned Value Management fixes this by integrating scope, schedule, and cost into a single, objective reporting system. This guide explains every formula, shows a worked example on a real construction scenario, and tells you exactly how to implement EVM starting next week.
What Is Earned Value Management?
Earned Value Management (EVM) is a project performance measurement technique that integrates three data streams — planned scope (schedule), earned scope (physical completion), and actual cost — into a single framework. Rather than asking “How much money did we spend?” and “How many days behind are we?” as separate questions, EVM asks a single integrated question: “For the money we’ve spent so far, how much work have we actually completed — and what does that tell us about where we’ll end up?”
EVM originated in the US Department of Defense in the 1960s under the name “Cost/Schedule Control Systems Criteria” (C/SCSC). It was standardized as ANSI/EIA-748 in 1998 and updated in 2019. It is now used on major construction, aerospace, defense, and IT projects globally — and is legally required on large US federal government contracts under FAR Part 34 and DFARS 252.234-7002.
The Three Core Data Points
Planned Value (PV)
Earned Value (EV)
Actual Cost (AC)
Performance Indices and Variance Formulas
| Metric | Formula | Meaning | Good / Bad |
|---|---|---|---|
| Schedule Variance (SV) | EV − PV | Dollar value of schedule difference. Negative = behind schedule. | SV > 0 = ahead SV < 0 = behind |
| Cost Variance (CV) | EV − AC | Dollar value of cost difference. Negative = over budget. | CV > 0 = under budget CV < 0 = over budget |
| Schedule Performance Index (SPI) | EV ÷ PV | How efficiently you’re accomplishing scheduled work. 0.90 = earning 90 cents of work for every $1 of planned schedule. | SPI > 1.0 = ahead SPI = 1.0 = on track SPI < 1.0 = behind |
| Cost Performance Index (CPI) | EV ÷ AC | How efficiently you’re spending money. 0.85 = earning 85 cents of work for every $1 spent. | CPI > 1.0 = under budget CPI = 1.0 = on budget CPI < 1.0 = over budget |
| Estimate at Completion (EAC) | BAC ÷ CPI | Forecast of total project cost at completion, assuming past cost performance continues. Most common EAC formula. | EAC > BAC = cost overrun projected |
| Estimate to Complete (ETC) | EAC − AC | How much money you expect to spend from today to project completion. | ETC = remaining budget needed |
| Variance at Completion (VAC) | BAC − EAC | Projected cost overrun or underrun at project end. Negative = projected overrun. | VAC > 0 = projected under budget |
| To-Complete Performance Index (TCPI) | (BAC − EV) ÷ (BAC − AC) | The CPI you must achieve from today forward to finish within the original budget. A TCPI above 1.10 is generally considered unrealistic. | TCPI ≤ 1.10 = achievable |
Worked Example: Highway Bridge Deck Project
Project Scenario
A highway bridge deck replacement contract has:
- Budget at Completion (BAC): $4,000,000
- Planned Duration: 12 months
- Reporting Date: End of Month 6 (50% of the schedule elapsed)
Reported data at Month 6:
- Planned Value (PV): $2,200,000 (per baseline schedule, 55% of work should be complete by now)
- Earned Value (EV): $1,800,000 (actual physical completion of work = 45%)
- Actual Cost (AC): $2,100,000 (money actually spent through Month 6)
| Metric | Calculation | Result | Interpretation |
|---|---|---|---|
| Schedule Variance (SV) | $1,800,000 − $2,200,000 | −$400,000 | $400K behind schedule in earned value terms |
| Cost Variance (CV) | $1,800,000 − $2,100,000 | −$300,000 | $300K over budget for work accomplished |
| Schedule Performance Index (SPI) | $1,800,000 ÷ $2,200,000 | 0.82 | Earning 82¢ of schedule for every $1 planned Behind Schedule |
| Cost Performance Index (CPI) | $1,800,000 ÷ $2,100,000 | 0.857 | Earning 85.7¢ of work for every $1 spent Over Budget |
| Estimate at Completion (EAC) | $4,000,000 ÷ 0.857 | $4,668,612 | Projected final cost if performance continues |
| Variance at Completion (VAC) | $4,000,000 − $4,668,612 | −$668,612 | Projected cost overrun of ~$669K (16.7% of BAC) |
| To-Complete Perf. Index (TCPI) | ($4,000,000 − $1,800,000) ÷ ($4,000,000 − $2,100,000) | 1.158 | Must earn $1.16 of work for every $1 spent from here on — very difficult to sustain Unlikely |
Conclusion for the owner: At Month 6, this project is both behind schedule and over budget. The EAC of $4.67M represents a $669K projected overrun. The TCPI of 1.16 means the contractor would need to perform at a level of efficiency never demonstrated on this project to stay within the original budget. The recommendation at this point is to reassess scope, staffing, and productivity rates — and prepare a revised contract completion date and cost.
EVM Status Thresholds (Practical Rules of Thumb)
| CPI Value | SPI Value | Status | Recommended Action |
|---|---|---|---|
| ≥ 1.05 | ≥ 1.05 | Excellent | Document lessons learned. Verify data quality — values this high can indicate inaccurate percent-complete reporting. |
| 0.95 – 1.05 | 0.95 – 1.05 | On Track | Continue monitoring. No corrective action required. |
| 0.90 – 0.95 | 0.90 – 0.95 | Watch | Investigate root cause. Monitor weekly. Prepare recovery plan if trend continues. |
| 0.85 – 0.90 | 0.85 – 0.90 | Caution | Issue formal warning. Require recovery schedule. Review subcontractor performance. |
| < 0.85 | < 0.85 | Critical | Escalate to senior management or owner. Forensic review of cost and schedule data. Consider contract action. |
EVM in Construction vs. Government/Defense
EVM was born in defense procurement but has been widely adopted in heavy civil and infrastructure construction — particularly on large federal, state, and transportation authority contracts. The requirements differ by contract type:
| Contract Type | EVM Requirement | Governing Standard |
|---|---|---|
| US DOD contracts > $20M | Full EVMS compliance required | DFARS 252.234-7002; ANSI/EIA-748 |
| US federal civilian agency contracts > $20M | EVMS compliance per OMB Circular A-11 | FAR Part 34; ANSI/EIA-748 |
| USACE construction contracts (major programs) | Monthly CPR or CSSR reporting | USACE ECB guidance; EM 1110-2-1302 |
| State DOT design-build contracts | Varies by state; many require EVM on contracts > $50M | State DOT specifications |
| Private commercial construction | No regulatory requirement; often used voluntarily on projects > $50M | AACEI RP 11R-88 (recommended) |
| Owner-developer projects | No requirement; S-curve and milestone reporting often substituted | Internal owner standards |
Percent Complete Methods in Construction
The accuracy of any EVM report depends entirely on the quality of the percent-complete estimates. In construction, the most common methods are:
- Units completed: Best for repetitive work (rebar tons placed, concrete CY poured, piles driven). Earned Value = (units complete ÷ total units) × activity budget. Highly objective and auditable.
- Milestone weights: Budget is allocated to pre-defined milestones within each activity (mobilization, form, rebar, pour, cure, strip). EV is earned when each milestone is achieved. Reduces subjectivity on non-repetitive work.
- Weighted steps: Similar to milestone weights but with finer-grained step definitions. Used for engineering and design activities.
- 50/50 rule: 50% EV is earned when an activity starts; the remaining 50% is earned when it finishes. Simple to administer; best for short-duration activities (under 2 reporting periods).
- 20/80 rule: 20% earned at start, 80% at finish. More conservative than 50/50; discourages early over-reporting.
- Supervisor estimate (Level of Effort): PM or superintendent estimates percent complete subjectively. Lowest objectivity — avoid on activities where units-completed or milestone methods are feasible.
EVM Software in Construction
EVM reporting can be done at different levels of sophistication depending on project size:
- Oracle Primavera P6: The most capable tool for integrated cost and schedule EVM. P6 has native support for resource-loaded schedules, earned value calculation (PV, EV, AC, CPI, SPI, EAC, VAC), and can generate Contract Performance Reports (CPR) in the formats required by US federal contracts. Required on most large government construction programs.
- Microsoft Project Plan 3 and 5: Supports basic EVM metrics for projects where P6 is not required. Integration with Power BI allows dashboard reporting. Not ANSI/EIA-748 compliant for formal government reporting.
- Procore (with ERP integration): Procore’s project financials module provides real-time cost-to-date data that can feed into EVM calculations when connected to accounting systems. Widely used by general contractors.
- Excel-based EVM: Acceptable for projects under $10M or where formal EVM software is not contractually required. AACEI (Association for the Advancement of Cost Engineering) provides EVM calculation templates. Simple, auditable, and sufficient for straightforward project structures.
- Deltek Cobra: Specialized EVM software used in defense and aerospace programs. Integrates with P6 for schedule data and supports the full range of ANSI/EIA-748 data item descriptions (DIDs) required on major government contracts.
How to Implement EVM on Your Next Project: Step-by-Step
- Define the Work Breakdown Structure (WBS). Decompose the project scope into work packages — manageable units of work with a single responsible manager, a defined scope, measurable deliverables, and a budget. Work packages should be 1–3 months in duration for most construction work.
- Establish the Performance Measurement Baseline (PMB). Resource-load the schedule so that each work package has a time-phased budget (the BAC spread across the planned duration). The PMB is your planned value (PV) curve — the S-curve of cumulative budget over time.
- Choose percent-complete measurement methods per work package. Select units-completed, milestone weights, or 50/50 rules as appropriate for each work package. Document the method in the EVM plan.
- Collect actual cost data at the same WBS level. Your cost accounting system must allocate actual expenditures to the same work packages used in the schedule. If payroll, subcontracts, and materials are tracked to different cost codes than the schedule WBS, you cannot compute meaningful CV or CPI.
- Calculate EVM metrics monthly. At each reporting period: record PV from the baseline, collect EV (% complete × BAC per work package), collect AC from cost accounting, calculate SV, CV, SPI, CPI, EAC, VAC, and TCPI.
- Analyze and report. Present the EVM data with the S-curve (PV vs. EV vs. AC over time), a CPI and SPI trend chart, and the EAC vs. BAC comparison. The trend direction matters as much as the current value.
- Take corrective action. EVM is only valuable if it drives decisions. When CPI or SPI falls below 0.90, require a written recovery plan from the responsible manager: specific actions, quantified expected impact, and target recovery date.
Common EVM Mistakes to Avoid
- Retroactively adjusting percent complete to match budget. If a supervisor changes a percent-complete estimate to make CPI look better, the entire EVM system becomes meaningless. Require independent verification of percent-complete on high-value work packages.
- Not resource-loading the schedule. Without time-phased budgets in the baseline, you cannot calculate PV per period — and therefore cannot calculate SPI or SV. A bar chart schedule without resource loading cannot support EVM.
- Tracking cost but not earned value. This produces traditional cost reporting — not EVM. The EV step is what differentiates EVM from budget tracking.
- Reporting only at project level. Project-level CPI masks problems in specific work packages. A project with an overall CPI of 0.95 could have one work package at 0.70 and another at 1.20 — the averaging hides the real problem. Report EVM at the work-package level and roll up to project level.
- Ignoring EVM data in decision-making. EVM reports that get filed and forgotten are a waste of effort. The value is in the monthly review meeting where CPI trends drive staffing, procurement, and scope decisions.
Frequently Asked Questions
What is Earned Value Management (EVM) in construction?
EVM is a project performance measurement technique that integrates scope, schedule, and cost into a single framework. It compares planned value (budget for scheduled work), earned value (budget for completed work), and actual cost (money actually spent) to objectively measure project performance and forecast final cost and completion date.
What is the formula for Earned Value in construction?
EV = % Complete × Budget at Completion (BAC). For example, a $2M concrete package that is 45% complete has an EV of $900,000. The key performance indices derived from EV are CPI (EV ÷ AC) and SPI (EV ÷ PV).
What is a good CPI in construction?
CPI of 1.0 is on budget. Above 1.0 is under budget; below 1.0 is over budget. Research on US government programs shows that a CPI established by the 20% completion point tends to remain stable. A CPI below 0.90 at the 20% mark is a strong predictor of final cost overrun.
What is EAC in project management?
EAC (Estimate at Completion) is the forecast of total project cost at completion. The most common formula is EAC = BAC ÷ CPI, which assumes past cost performance continues to the end of the project.
Is EVM required on government construction contracts?
Yes — for large US federal contracts, EVM is required under FAR Part 34 and DFARS 252.234-7002 (DOD contracts over $20M). USACE requires monthly EVM reporting on major construction programs. Private construction has no regulatory requirement, but EVM is widely used on projects above $50M.
What is the difference between EVM and traditional project reporting?
Traditional reporting compares actual cost to planned cost — missing the critical question of how much work was actually done for the money spent. EVM adds earned value (the budget equivalent of work completed), allowing you to measure both cost efficiency (CPI) and schedule efficiency (SPI) from the same dataset.
Key References and Resources
- ANSI/EIA-748 Earned Value Management System Standard — NDIA Intent Guide
- Federal Acquisition Regulation (FAR) Part 34 — Major System Acquisition (acquisition.gov)
- AACEI Recommended Practice 11R-88: Required Skills and Knowledge of Cost Engineering — AACEI
- Practical Guide to Earned Value Management — PMI Learning Library
- GAO Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G) — US Government Accountability Office
EVM thresholds and performance rules cited in this article reflect widely adopted industry practice and published government guidance. Contract-specific EVMS requirements vary — always refer to your contract documents and the applicable FAR/DFARS clauses. CivInnovate is not a licensed engineering firm; this content is educational.
