Earned Value Management for Government Contracts
Earned Value Management (EVM) is a project management methodology that integrates scope, schedule, and cost data to provide an objective, quantitative measure of project performance. The Department of Defense and other federal agencies require EVM on major acquisitions as a critical tool for monitoring contractor performance and forecasting cost and schedule outcomes.
This guide covers the core EVM metrics, the 32 ANSI/EIA-748 guidelines, EVMS validation and surveillance, reporting requirements, and the contract thresholds that trigger mandatory EVM implementation.
100M+ government records · 300+ gov/news sources · Updated hourly
What Is EVM and When Is It Required?
EVM provides a disciplined framework for measuring the value of work accomplished against the plan and the actual cost of performing that work. By comparing planned value, earned value, and actual cost at any point during contract execution, project managers and government oversight officials can determine whether a contract is ahead or behind schedule, over or under budget, and forecast the likely cost and completion date.
The ANSI/EIA-748 standard, "Earned Value Management Systems," defines 32 guidelines organized into five categories that an EVMS must satisfy. Federal agencies require compliance with this standard through contract clauses, primarily DFARS 252.234-7001 (for DoD) and FAR 34.2/48 C.F.R. 34.2 (for civilian agencies).
EVM requirements are triggered by contract value and type. For DoD, full EVMS compliance is generally required on cost or incentive contracts valued at $20 million or more. Contracts between $20 million and $50 million may use a simplified EVM approach at the contracting officer's discretion. Contracts above $50 million typically require a validated EVMS. Firm-fixed-price contracts are generally exempt from EVM requirements since the government does not bear cost risk.
Key EVM Metrics
EVM relies on three foundational measurements and a set of derived performance indicators. Understanding these metrics is essential for both contractors implementing EVM and government program managers evaluating contract performance.
Foundation Metrics
The authorized budget assigned to scheduled work. Also known as Budgeted Cost of Work Scheduled (BCWS). PV represents the time-phased budget plan — what you planned to accomplish by a given date.
The measure of work performed expressed in terms of the budget authorized for that work. Also known as Budgeted Cost of Work Performed (BCWP). EV represents the value of the work actually completed.
The realized cost incurred for the work performed. Also known as Actual Cost of Work Performed (ACWP). AC represents what was actually spent to accomplish the earned value.
Variance Metrics
Positive SV means ahead of schedule; negative means behind. SV = 0 means on schedule.
Positive CV means under budget; negative means over budget. CV = 0 means on budget.
Performance Indices
SPI > 1.0 means ahead of schedule, SPI < 1.0 means behind schedule, SPI = 1.0 means on schedule. An SPI of 0.85 means only 85% of planned work has been completed.
CPI > 1.0 means under budget, CPI < 1.0 means over budget, CPI = 1.0 means on budget. A CPI of 0.90 means you are getting only 90 cents of value for every dollar spent.
Forecasting Metrics
The projected total cost of the contract when complete. Multiple EAC formulas exist depending on assumptions: EAC = AC + (BAC - EV) / CPI is the most common, assuming current cost efficiency continues.
The expected cost to finish the remaining work. ETC = EAC - AC. This metric is critical for program managers assessing whether remaining budget is sufficient to complete the work.
The 32 ANSI/EIA-748 Guidelines
The ANSI/EIA-748-D standard organizes the 32 EVM guidelines into five categories that address different aspects of program management. A contractor's EVMS must comply with all 32 guidelines to be considered compliant.
Organization (Guidelines 1-5)
Define the authorized work, identify the organizational structure, assign responsibility for all work, and integrate the work breakdown structure (WBS) with the organizational breakdown structure (OBS) at the control account level.
Planning, Scheduling, and Budgeting (Guidelines 6-15)
Establish a performance measurement baseline (PMB), schedule authorized work, identify products and milestones, establish time-phased budgets for work packages, and ensure the sum of all budgets equals the total contract budget.
Accounting (Guidelines 16-21)
Record direct and indirect costs in a manner consistent with the budgets, accumulate costs at the control account level, summarize costs from the control account to the WBS and OBS, and identify unit costs where applicable.
Analysis and Management Reports (Guidelines 22-27)
Identify significant variances at the control account level, analyze variances and develop corrective actions, prepare estimates at completion based on performance to date, and provide accurate and timely management reports.
Revisions and Data Maintenance (Guidelines 28-32)
Incorporate authorized changes in a timely manner, reconcile internal EVM data to external reports, control retroactive changes to records, prevent unauthorized revisions to the PMB, and document management reserve usage.
EVMS Validation and Surveillance
For major contracts, the government validates the contractor's EVMS through a formal review process conducted by the cognizant federal agency (typically DCMA for DoD contracts). Validation involves a detailed examination of the contractor's EVM policies, procedures, and actual implementation against the 32 ANSI/EIA-748 guidelines.
The validation process typically includes a system description review, a documentation review, data trace exercises (following individual work packages from authorization through planning, scheduling, budgeting, and performance measurement), and interviews with contractor personnel at all levels. The review team produces a report identifying any discrepancies from the guidelines, and the contractor must develop a corrective action plan for any findings.
After initial validation, the government conducts ongoing surveillance to ensure the EVMS continues to operate in compliance. Surveillance reviews are typically conducted annually and focus on previously identified risk areas, data quality, and the contractor's internal self-governance processes. DCMA has shifted toward a risk-based surveillance approach, focusing resources on contractors and programs with higher risk profiles.
Reporting: CPR and IPMR
The primary EVM reporting vehicle is the Integrated Program Management Report (IPMR), which replaced the older Contract Performance Report (CPR) and Integrated Master Schedule (IMS) data item descriptions. The IPMR consists of seven formats:
- Format 1 (WBS): Cost and schedule performance data organized by work breakdown structure element
- Format 2 (OBS): Cost and schedule performance data organized by organizational element
- Format 3 (Baseline): Time-phased budget baseline, including changes and management reserve
- Format 4 (Staffing): Planned and actual staffing by functional category
- Format 5 (Narrative): Explanatory analysis of variances, risks, and corrective actions
- Format 6 (IMS): Integrated master schedule with task relationships, critical path, and status
- Format 7 (History): Contract history and over-target baseline changes
Reports are typically submitted monthly or as specified in the contract data requirements list (CDRL). The data is submitted electronically through the Earned Value Management Central Repository (EVM-CR), which allows government program offices, DCMA, and other oversight organizations to access and analyze EVM data across programs.
Track Contract Performance with Bureauify
Monitor cost-type and incentive contracts, analyze spending trends, and stay ahead of EVM reporting requirements across your federal portfolio.