Earned value management (EVM) is a program-control method that integrates technical scope, schedule and budget to measure performance objectively. It answers three basic questions: How much work did we plan to complete, how much did we actually complete and what did that completed work cost?
The value of EVM does not come from producing monthly indices. It comes from building a credible baseline, measuring accomplishment consistently and using the results to forecast outcomes. When implemented well, EVM gives control account managers (CAMs) and program leaders early warning of schedule delay, cost growth and unrealistic completion forecasts.
What Is Earned Value Management?
EVM assigns a time-phased budget to planned work. As the team completes that work, it earns the associated budget value. The program then compares earned value with both the planned budget and actual cost.
Therefore, EVM measures physical progress in budget terms rather than relying only on money spent or subjective percent-complete estimates. Spending 60 percent of a budget does not prove that a team completed 60 percent of the work.
An earned value management system (EVMS) is broader than the calculation method. It includes the organization, work breakdown structure, scheduling process, budgeting process, accounting integration, performance measurement techniques, forecasting rules and baseline-change controls used to manage the program. The Defense Contract Management Agency description of an EVMS emphasizes integrated scope, schedule and cost information that supports objective measurement, variance analysis and forecasting.
The Foundation of an Effective EVMS
EVM metrics become trustworthy only after the program establishes an executable management plan. That foundation has four connected elements.
Defined scope
The work breakdown structure (WBS) organizes the complete authorized scope. Each control account sits at an intersection of the WBS and organizational breakdown structure, where responsibility belongs to an accountable manager.
Within control accounts, the team plans near-term scope in work packages. It may hold less-defined future scope in planning packages until enough information exists for detailed planning.
A logic-driven schedule
The integrated master schedule (IMS) places the work on a timeline and connects activities through valid network logic. It identifies when work should occur, which activities drive key milestones and whether the forecast remains achievable.
For more detail on schedule architecture, see the complete guide to the DoD integrated master schedule. Weak schedule logic will undermine EVM because the time-phased budget will no longer reflect a realistic execution plan.
A time-phased budget
The program assigns budget to scheduled work and spreads it across the periods in which the work should occur. The resulting time-phased plan forms the Performance Measurement Baseline (PMB).
The PMB includes control account budgets and applicable undistributed budget or summary-level planning packages. Management reserve sits outside the PMB. It is not budget for unidentified contract scope or a device for hiding overruns. The Department of Energy EVMS Gold Card provides a useful visual summary of these relationships.
Programs establishing this structure should also review how to build a robust Performance Measurement Baseline.
Objective measurement rules
Each work package needs a performance measurement technique that matches the nature of the work. Common methods include weighted milestones, fixed formulas, units complete, apportioned effort and level of effort.
Discrete work should use measurable completion criteria whenever practical. Level of effort is appropriate for support work that produces no measurable product. However, excessive level of effort can mask unfavorable performance because value passes with time rather than demonstrated accomplishment.
Core Earned Value Management Measures
Three data elements form the center of earned value analysis:
- Planned Value (PV): The budgeted value of work scheduled through the status date. The legacy term is Budgeted Cost for Work Scheduled (BCWS).
- Earned Value (EV): The budgeted value of work actually completed through the status date. The legacy term is Budgeted Cost for Work Performed (BCWP).
- Actual Cost (AC): The cost incurred for the completed work. The legacy term is Actual Cost of Work Performed (ACWP).
These values must use the same scope, organizational level and accounting period. Otherwise, the comparisons will produce misleading results.
Variances and performance indices
- Schedule Variance: SV = EV − PV
- Cost Variance: CV = EV − AC
- Schedule Performance Index: SPI = EV ÷ PV
- Cost Performance Index: CPI = EV ÷ AC
A positive variance is favorable, while a negative variance is unfavorable. Likewise, an index above 1.00 is favorable and an index below 1.00 is unfavorable.
However, favorable does not always mean healthy. For example, a favorable cost variance may result from missing actual costs, delayed material invoices or work performed with resources that have not entered the accounting system. Analysts must investigate the cause rather than report the color of an indicator.
For a deeper treatment, see how to calculate and use CPI and SPI.
A Practical EVM Example
Assume the fictional Falcon Ridge program is modernizing a radar signal processor. The authorized work has a Budget at Completion (BAC) of $10 million.
At the end of June, the program reports:
- PV = $4.0 million
- EV = $3.2 million
- AC = $3.6 million
The resulting performance is:
- SV = $3.2 million − $4.0 million = −$0.8 million
- SPI = $3.2 million ÷ $4.0 million = 0.80
- CV = $3.2 million − $3.6 million = −$0.4 million
- CPI = $3.2 million ÷ $3.6 million = 0.89
The team completed only 80 cents of planned work for each dollar of work scheduled. It also earned about 89 cents of budget value for each dollar spent.
Those figures identify a problem but not its cause. The CAM and scheduler should inspect the driving schedule path, incomplete milestones, staffing assumptions, material status and actual-cost timing. If the design release is late and drives fabrication, management needs a recovery plan tied to that schedule logic. A generic instruction to improve SPI will not correct the underlying condition.
How the Monthly EVM Cycle Works
A disciplined monthly process generally follows this sequence:
- Establish the status date. All schedule, cost and accomplishment data must align with the same reporting cutoff.
- Status the IMS. Record actual starts, actual finishes, remaining durations and forecast dates based on current information.
- Measure accomplishment. Apply the approved performance measurement technique and completion criteria to each work package.
- Load actual costs. Reconcile actuals with the accounting system and address material, accrual or estimated-actual timing differences.
- Calculate performance. Generate current and cumulative PV, EV, AC, variances and indices.
- Update the estimate to complete. CAMs reassess remaining labor, material, subcontract and indirect costs.
- Analyze significant variances. Explain the root cause, impact and corrective action rather than restating the metric.
- Process authorized changes. Maintain traceability while protecting historical performance.
The schedule status process deserves particular attention because inaccurate progress dates will distort both planned and earned value. See how to status an integrated master schedule for practical guidance.
What EVM Schedule Variance Does Not Tell You
EVM schedule variance is expressed in budget units, not calendar days. An SV of negative $800,000 does not mean the program is a specific number of weeks late. In addition, SPI trends toward 1.00 when all planned value has been earned, even if the program finishes late.
Therefore, program teams must analyze EVM schedule indicators together with the IMS. They should review the critical path, near-critical paths, total float, forecast milestone dates and schedule risk.
The GAO Schedule Assessment Guide also stresses the connection between a reliable integrated schedule and meaningful earned value information. For hands-on schedule analysis, use the NoahsPlan guide to perform critical path analysis in an IMS.
Forecasting Final Cost
EVM supports several independent estimates at completion. Common formulas include:
- EAC = AC + ETC: Actual cost plus a bottom-up estimate to complete.
- EAC = BAC ÷ CPI: Assumes cumulative cost efficiency continues for the remaining work.
- EAC = AC + (BAC − EV) ÷ (CPI × SPI): Applies both cost and schedule efficiency to the remaining work.
- VAC = BAC − EAC: Forecast variance at completion.
These formulas are analytical tools, not automatic contractual forecasts. The analyst should select assumptions that fit the program’s conditions and compare statistical results with the CAMs’ bottom-up forecast.
For Falcon Ridge, continuing at a cumulative CPI of 0.89 produces an EAC of about $11.25 million. That result is not proof that the program will overrun by exactly $1.25 million. However, management should challenge any bottom-up EAC near $10 million unless the team can identify credible changes in remaining performance.
Additional forecasting measures, including the To-Complete Performance Index (TCPI), are covered in advanced EVM forecasting with TCPI, VAC and ETC.
Contractual Requirements Versus Good Practice
A program may use EVM as a management practice without having a contractual requirement for an EIA-748-compliant EVMS. Conversely, a contract clause can require a formal EVMS, specific reports, system surveillance and an Integrated Baseline Review (IBR).
For civilian acquisitions, FAR Subpart 34.2 addresses EVMS policy and IBRs. Agency supplements, procedures and individual contract terms may add or tailor requirements.
Current DoD applicability requires special attention
As of August 20, 2026, DoD contracting officers are directed to follow Class Deviation 2026-O0011, effective February 1, 2026, in place of the codified DFARS Part 234 text. Under that deviation:
- Cost or incentive contracts and subcontracts valued at $50 million or more require an EVMS that complies with EIA-748.
- At $100 million or more, the contractor must use an EVMS that the cognizant federal agency has determined to comply with EIA-748.
- Below $50 million, applying EVM is an optional, risk-based decision.
- Applying EVMS to firm-fixed-price work is discouraged and requires the specified waiver process.
- The deviation exempts contracts primarily for software, including those using the DoD Software Acquisition Pathway, from that subpart.
The deviation also directs use of provisions 252.234-7998 and 252.234-7999. However, existing contracts may contain earlier clauses, thresholds or tailored requirements. Therefore, proposal and execution teams must read the actual solicitation, contract, Contract Data Requirements List, data item descriptions and modifications. A threshold summary does not override contract language.
The Integrated Baseline Review
An IBR is a joint assessment of whether the baseline provides a realistic plan for accomplishing the authorized work. It examines scope coverage, schedule logic, resources, budgets, assumptions and identified risks.
An IBR is not simply a briefing or a schedule-health score. The review should determine whether CAMs understand their scope, can defend their plans and have identified the risks embedded in the PMB.
Under the current DoD deviation clause 252.234-7999, the review process must occur no later than 180 calendar days after contract award, the exercise of significant options or the incorporation of major modifications. That timing applies when the clause is included; teams should not treat it as a universal requirement for every project.
Common EVM Failure Modes
- Using subjective percent complete. Value gets earned without evidence that defined products or milestones are complete.
- Disconnecting the schedule and budget. The IMS shows one execution sequence while the cost system spreads budget against another plan.
- Ignoring accounting timing. Missing actuals or accruals create favorable cost performance that will reverse later.
- Overusing level of effort. Time-based earning hides delays in discrete technical work.
- Changing the baseline to erase variances. Unauthorized retroactive changes destroy trend information and traceability.
- Managing to indices alone. CPI and SPI indicate where to investigate but do not explain technical causes or schedule consequences.
- Confusing budget and funding. BAC, PMB, management reserve, contract price and available funding serve different purposes.
- Accepting an unsupported EAC. A forecast that ignores actual performance, remaining risk or current resource rates provides false confidence.
What Good Earned Value Management Looks Like
A useful EVMS allows managers to trace every significant result back to authorized scope, schedule activities, work packages, budgets and accounting records. It also gives CAMs enough flexibility to manage future work without rewriting history.
Before relying on the monthly report, verify that:
- The WBS covers the complete authorized scope.
- Control account responsibility is clear.
- The IMS uses valid logic and realistic durations.
- Budget is time-phased consistently with the schedule.
- Work packages have objective completion criteria.
- Actual costs align with earned value in the correct period.
- Variance explanations identify causes, impacts and actions.
- The EAC reflects current performance and remaining risk.
- Baseline changes are authorized, documented and traceable.
- Management uses the data to make decisions.
No scheduling or cost-processing application creates a compliant EVMS by itself. Microsoft Project or Deltek Open Plan may calculate the schedule, while Deltek Cobra may integrate budget, earned value and actual costs. However, the management processes, data discipline and system implementation determine whether the resulting information is reliable.
Earned Value Management FAQ
Is EVM the same as project accounting?
No. Accounting records what the program spent. EVM compares that cost with the budgeted value of completed work and the value planned through the status date.
Can a program use EVM without an EIA-748 requirement?
Yes. A program can use scaled EVM techniques for internal management. However, it should not claim formal EIA-748 compliance or government system approval without the required processes and determination.
Does a favorable CPI prove the program will underrun?
No. The favorable result may be temporary or caused by missing actual costs, easier early work or changes in the remaining resource mix. The team must evaluate the estimate to complete and program risk.
Can management reserve eliminate an overrun?
Management reserve can provide budget for authorized, in-scope work that was not planned within control accounts. It does not change actual costs or erase poor historical performance. Its use must follow the program’s approved EVMS procedures.
Use EVM as a Management System, Not a Report
Earned value management works when the program integrates a credible IMS, time-phased budget, objective accomplishment criteria, actual costs and realistic forecasts. The monthly numbers should direct attention to the technical and execution issues that need management action.
When the baseline lacks logic or teams earn value without evidence, sophisticated reports cannot restore credibility. Build the management plan first. Then use EVM to test that plan against actual performance and forecast where the program is heading.