What is earned value management in simple terms?

Earned value management, or EVM, is a way to measure how a project is really performing by combining scope, schedule, and cost into one picture. Instead of only asking how much has been spent, EVM asks how much of the planned work has actually been completed, valued at its budget, and compares that to both the plan and the money spent. It uses three numbers: planned value (the budget for the work that should be done by now), earned value (the budget for the work actually done), and actual cost (what that work cost). From those, EVM produces variances and efficiency ratios that flag a cost overrun or schedule slip early, while there is still time to act. It is widely used on large government and defense programs, where an integrated cost-and-schedule view is a contractual requirement.

What are CPI and SPI in earned value management?

CPI and SPI are the two core efficiency ratios in EVM. The cost performance index (CPI) equals earned value divided by actual cost (EV / AC): it measures how much budgeted value you are getting for each dollar actually spent. A CPI of 1.0 is on budget, below 1.0 is an overrun, and above 1.0 is an underrun. The schedule performance index (SPI) equals earned value divided by planned value (EV / PV): it measures how much of the scheduled work has been earned. An SPI of 1.0 is on schedule, below 1.0 is behind. Because both are ratios around 1.0, they let a program office compare very different projects on the same scale and forecast the final cost, for example by dividing the budget at completion by the CPI.

What is an EVMS and what is ANSI/EIA-748?

An earned value management system (EVMS) is the integrated set of processes, tools, and procedures an organization uses to plan, measure, and report earned value consistently across a program. In the United States, the standard that defines what an EVMS must do is ANSI/EIA-748, first issued in 1998 and adopted by the Department of Defense the same year. For most of its history the standard set out 32 guidelines grouped into five areas: organization; planning, scheduling, and budgeting; accounting considerations; analysis and management reports; and revisions and data maintenance. A later revision (Revision E, published in 2026) reorganized these into a smaller set of guidelines. The guidelines are intentionally outcome-based: they say what a compliant system must achieve, not which software to use. Confirm the current revision and guideline count against the standard itself.

What role does the DCMA play in earned value management?

For United States Department of Defense contracts, the Defense Contract Management Agency (DCMA) is the government authority that reviews and accepts a contractor's earned value management system. When a contract requires EVM, DCMA assesses whether the contractor's EVMS conforms to the ANSI/EIA-748 guidelines, conducts compliance reviews, and can issue findings the contractor must correct. The requirement to apply EVM, and the threshold at which a formal system validation is needed, is set by the DFARS, principally the clause at DFARS 252.234-7002, and by Department of Defense policy. Those dollar thresholds have been revised in recent years, so verify the current figures against the DFARS on acquisition.gov rather than relying on a fixed number.

When is earned value management required on a contract?

On United States defense work, EVM is driven by contract type and value, not chosen at will. Cost-reimbursement and incentive contracts above a defined dollar threshold generally require an earned value management system that conforms to ANSI/EIA-748, and contracts above a higher threshold require that the system be formally validated and accepted by the cognizant federal agency, usually DCMA, before performance. Firm-fixed-price contracts are often exempt because the cost risk sits with the contractor. The specific thresholds are set in the DFARS and have been adjusted by Department of Defense policy changes, so the governing question for any given contract is what its clauses require: confirm against DFARS 252.234-7002 and the contract itself.

How does earned value management connect to government contract accounting?

Earned value does not stand alone: it draws directly on the contractor's accounting and project-control systems. Actual cost in EVM comes from the accounting system, so the work breakdown structure, the cost collection by control account, the indirect-rate structure, and the Cost Accounting Standards all have to align with how earned value is reported. A defense contractor that runs clean DCAA-compliant project accounting already has much of the data an EVMS needs. That overlap is why Lightbridge ERP treats earned value as part of the GovCon back office: see the related guides on GovCon project accounting, indirect cost rates, and DCAA-compliant accounting for the accounting foundation EVM relies on.

How does Lightbridge ERP help with earned value management?

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house expertise in government contract accounting. It helps defense contractors build the data foundation an earned value management system depends on: a disciplined work breakdown structure, cost collection by control account, an indirect-rate structure that ties to the general ledger, and the timekeeping and accounting controls DCAA expects. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its platform advice, whether the EVM engine is in the ERP or a specialized cost-processor, is driven by fit rather than commission. This guide is general information, not accounting, legal, or contracting advice; confirm requirements against the DFARS and your contract.

SK Written by Sarika Krishnan with Robert LabardeeSenior Program Manager and Founder and CEO

Last updated June 2026.

What is earned value management?

Lightbridge ERP defines earned value management (EVM) as a project-controls method that measures cost and schedule performance against a baseline by comparing three values: planned value, earned value, and actual cost. An earned value management system (EVMS) is the integrated set of processes that produces those measures, governed for United States defense programs by the ANSI/EIA-748 guidelines.

GovCon project accounting Talk to an ERP advisor

Earned value management integrates scope, schedule, and cost.

Earned value management, abbreviated EVM, is a project-management discipline that measures performance by integrating three dimensions that are usually tracked separately: how much work was planned, how much was actually done, and how much it cost. Its central insight is to value completed work at its budget, the earned value, so progress and spending can be compared on the same scale. That makes it possible to see a cost overrun or a schedule slip in numbers, early, rather than discovering it when the budget runs out.

EVM is used most heavily on large, long-duration programs where cost and schedule risk are high and a customer needs objective performance data, which is why it is central to United States government and defense contracting. This guide is general information for finance and program leaders, not accounting, legal, or contracting advice. Confirm any regulatory requirement against the official source.

Earned value rests on three measured values and a baseline budget.

Every EVM calculation is built from a few primary values, captured at a point in time against the performance measurement baseline. Get these right and the variances and indices follow directly.

Planned value (PV)

The budgeted cost of the work scheduled to be done by a point in time, also called the budgeted cost of work scheduled (BCWS). It is the baseline plan.

Earned value (EV)

The budgeted cost of the work actually completed by that point, also called the budgeted cost of work performed (BCWP). It is progress measured in budget terms.

Actual cost (AC)

The cost actually incurred for the work completed, also called the actual cost of work performed (ACWP). It is what the completed work really cost.

Budget at completion (BAC)

The total budget for the project baseline. Forecasts of the final cost are compared back to it to show whether the project will overrun or underrun.

Variances and indices turn three values into project health.

From planned value, earned value, and actual cost, EVM derives two variances and two efficiency indices that summarize whether a project is on cost and on schedule. They are simple arithmetic, but together they are a powerful early-warning system.

Cost variance (CV = EV minus AC)

Whether work is costing more or less than budgeted. A negative cost variance means the work done has cost more than its budget: an overrun.

Schedule variance (SV = EV minus PV)

Whether work is ahead of or behind the plan, in budget terms. A negative schedule variance means less work has been earned than was scheduled: behind schedule.

Cost performance index (CPI = EV / AC)

Cost efficiency. A CPI below 1.0 means the project is getting less than a dollar of value for every dollar spent. CPI is the most watched EVM number.

Schedule performance index (SPI = EV / PV)

Schedule efficiency. An SPI below 1.0 means work is being earned more slowly than planned. CPI and SPI together summarize project health in two ratios.

EVM also forecasts the finish. The estimate at completion (EAC) projects the final cost, often by dividing the budget at completion by the CPI when current efficiency is expected to continue. The variance at completion (VAC = BAC minus EAC) shows the expected overrun or underrun, and the estimate to complete (ETC) is the forecast cost of the remaining work. These forecasts are what turn EVM from a status report into a decision tool.

An EVMS is governed by the ANSI/EIA-748 guidelines.

Earned value management on a major program is run through an earned value management system (EVMS): the integrated processes, schedule, accounting, and reporting that produce consistent earned value data. In the United States, the standard that defines a compliant EVMS is ANSI/EIA-748, first issued in 1998 and adopted by the Department of Defense that year. It is maintained with the National Defense Industrial Association, whose Integrated Program Management Division publishes the intent guidance that explains how to apply it.

For most of its history ANSI/EIA-748 set out 32 guidelines across five categories: organization; planning, scheduling, and budgeting; accounting considerations; analysis and management reports; and revisions and data maintenance. A later revision, Revision E published in 2026, reorganized these into a smaller, streamlined set of guidelines. The guidelines are deliberately outcome-based: they state what a compliant system must achieve, not which product to buy, which is why a vendor-neutral approach to the underlying ERP and cost tools fits the standard well. Confirm the current revision and guideline set against the standard itself.

DCMA oversees earned value management systems for defense contracts.

On Department of Defense contracts, the Defense Contract Management Agency (DCMA) is the government authority that reviews and accepts a contractor's EVMS against the ANSI/EIA-748 guidelines. The requirement to apply earned value, and the contract value at which a formal system validation is needed, is set in the DFARS, principally the clause at DFARS 252.234-7002, together with Department of Defense policy. The structure is tiered by contract value: above one threshold a contractor must run a compliant EVMS, and above a higher threshold the system must be formally validated before performance.

Those dollar thresholds have been revised in recent years through Department of Defense policy changes, so any specific figure dates quickly. Treat the contract clauses as authoritative for a given program and verify current thresholds against the DFARS on acquisition.gov. For the wider compliance picture, the cross-entity aerospace and defense hub maps how earned value sits alongside accounting, security, and export-control obligations.

Earned value depends on a contractor's accounting foundation.

Earned value is not a standalone tool bolted onto a program: its actual-cost data comes straight from the accounting and project-control systems. The work breakdown structure, cost collection by control account, the indirect-rate structure, and the Cost Accounting Standards all have to line up with how earned value is reported, or the numbers will not reconcile. A contractor that already runs clean, audit-ready project accounting holds most of what an EVMS needs.

That is why Lightbridge ERP treats earned value as part of the GovCon back office. See the related guides on GovCon project accounting, indirect cost rates, cost-plus contract accounting, and DCAA-compliant accounting for the accounting foundation that earned value reporting relies on.

Lightbridge ERP builds the data foundation earned value runs on.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house expertise in government contract accounting. It helps defense contractors put in place the disciplined work breakdown structure, control-account cost collection, indirect-rate structure, and timekeeping controls that an earned value management system depends on, so the actual-cost data feeding EVM is accurate and DCAA-ready.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its advice on whether earned value is best processed inside the ERP or in a specialized cost engine is driven by fit rather than commission. When the underlying system still needs to be chosen, ERP consulting and a structured selection are the right place to start.

Earned value management: frequently asked questions

What is earned value management in simple terms?: Earned value management, or EVM, is a way to measure how a project is really performing by combining scope, schedule, and cost into one picture. Instead of only asking how much has been spent, EVM asks how much of the planned work has actually been completed, valued at its budget, and compares that to both the plan and the money spent. It uses three numbers: planned value (the budget for the work that should be done by now), earned value (the budget for the work actually done), and actual cost (what that work cost). From those, EVM produces variances and efficiency ratios that flag a cost overrun or schedule slip early, while there is still time to act. It is widely used on large government and defense programs, where an integrated cost-and-schedule view is a contractual requirement.
What are CPI and SPI in earned value management?: CPI and SPI are the two core efficiency ratios in EVM. The cost performance index (CPI) equals earned value divided by actual cost (EV / AC): it measures how much budgeted value you are getting for each dollar actually spent. A CPI of 1.0 is on budget, below 1.0 is an overrun, and above 1.0 is an underrun. The schedule performance index (SPI) equals earned value divided by planned value (EV / PV): it measures how much of the scheduled work has been earned. An SPI of 1.0 is on schedule, below 1.0 is behind. Because both are ratios around 1.0, they let a program office compare very different projects on the same scale and forecast the final cost, for example by dividing the budget at completion by the CPI.
What is an EVMS and what is ANSI/EIA-748?: An earned value management system (EVMS) is the integrated set of processes, tools, and procedures an organization uses to plan, measure, and report earned value consistently across a program. In the United States, the standard that defines what an EVMS must do is ANSI/EIA-748, first issued in 1998 and adopted by the Department of Defense the same year. For most of its history the standard set out 32 guidelines grouped into five areas: organization; planning, scheduling, and budgeting; accounting considerations; analysis and management reports; and revisions and data maintenance. A later revision (Revision E, published in 2026) reorganized these into a smaller set of guidelines. The guidelines are intentionally outcome-based: they say what a compliant system must achieve, not which software to use. Confirm the current revision and guideline count against the standard itself.
What role does the DCMA play in earned value management?: For United States Department of Defense contracts, the Defense Contract Management Agency (DCMA) is the government authority that reviews and accepts a contractor's earned value management system. When a contract requires EVM, DCMA assesses whether the contractor's EVMS conforms to the ANSI/EIA-748 guidelines, conducts compliance reviews, and can issue findings the contractor must correct. The requirement to apply EVM, and the threshold at which a formal system validation is needed, is set by the DFARS, principally the clause at DFARS 252.234-7002, and by Department of Defense policy. Those dollar thresholds have been revised in recent years, so verify the current figures against the DFARS on acquisition.gov rather than relying on a fixed number.
When is earned value management required on a contract?: On United States defense work, EVM is driven by contract type and value, not chosen at will. Cost-reimbursement and incentive contracts above a defined dollar threshold generally require an earned value management system that conforms to ANSI/EIA-748, and contracts above a higher threshold require that the system be formally validated and accepted by the cognizant federal agency, usually DCMA, before performance. Firm-fixed-price contracts are often exempt because the cost risk sits with the contractor. The specific thresholds are set in the DFARS and have been adjusted by Department of Defense policy changes, so the governing question for any given contract is what its clauses require: confirm against DFARS 252.234-7002 and the contract itself.
How does earned value management connect to government contract accounting?: Earned value does not stand alone: it draws directly on the contractor's accounting and project-control systems. Actual cost in EVM comes from the accounting system, so the work breakdown structure, the cost collection by control account, the indirect-rate structure, and the Cost Accounting Standards all have to align with how earned value is reported. A defense contractor that runs clean DCAA-compliant project accounting already has much of the data an EVMS needs. That overlap is why Lightbridge ERP treats earned value as part of the GovCon back office: see the related guides on GovCon project accounting, indirect cost rates, and DCAA-compliant accounting for the accounting foundation EVM relies on.
How does Lightbridge ERP help with earned value management?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house expertise in government contract accounting. It helps defense contractors build the data foundation an earned value management system depends on: a disciplined work breakdown structure, cost collection by control account, an indirect-rate structure that ties to the general ledger, and the timekeeping and accounting controls DCAA expects. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its platform advice, whether the EVM engine is in the ERP or a specialized cost-processor, is driven by fit rather than commission. This guide is general information, not accounting, legal, or contracting advice; confirm requirements against the DFARS and your contract.

From earned value theory to an audit-ready EVMS foundation.

When the question shifts from what earned value means to how your ERP and accounting should feed a compliant EVMS, Lightbridge ERP designs the work breakdown, cost structure, and controls that make the data hold up.

Talk to an ERP advisor GovCon project accounting