EVM Isn’t Just a DCMA Checkbox: How CPI/SPI Actually Predict Program Health
Original article published on LinkedIn(opens in new tab).
If you have worked in government contracting long enough, you'll hear Earned Value Management (EVM) described the same way almost everywhere: a compliance requirement. Something the Defense Contract Management Agency (DCMA) wants to see. A box to check before a program review. A report that gets generated, reviewed, filed, and forgotten until the next reporting cycle.
That framing is understandable, Earned Value Management System surveillance, ANSI/EIA-748 compliance, and DCMA validation reviews are real and often burdensome. But it also causes a lot of programs to miss the actual point of EVM. It is one of the few tools that tells you, in hard numbers, whether a program is actually in trouble before the trouble becomes visible everywhere else.
Ravi Chitrabhanu
COO
The Two Numbers That Matter Most
Buried in every EVM report are two key metrics: Cost Performance Index (CPI) and Schedule Performance Index (SPI).
CPI = Earned Value (EV) / Actual Cost (AC)
This tells you how much value you're getting for every dollar spent. A CPI of 0.85 means that for every dollar spent, you're only getting 85 cents of planned work done. That's not a rounding error, that's a program burning cash faster than it's making progress.
SPI = Earned Value (EV) / Planned Value (PV)
This tells you how much of the planned work is actually getting done, regardless of cost. An SPI of 0.90 means you're 10% behind where the schedule said you'd be.
One caveat worth knowing, because SPI is calculated in dollar terms rather than calendar days, it mathematically converges to 1.0 as a project nears completion. Regardless of whether the work actually finished on time. That makes SPI most useful early and mid-contract, not as a late-stage indicator of schedule health.
Individually, each metric is useful. Together, they tell a story that neither one tells alone.
Why the Combination Is the Real Signal
A program with a healthy CPI but a poor SPI is often understaffed or facing schedule risk unrelated to spending discipline. It implies work isn't getting done, but what does get done is efficient. That's a resourcing and schedule conversation.
A program with a healthy SPI but a poor CPI is a different animal entirely. Work is getting done on schedule, but it's costing more than planned. That's often a sign of scope creep, underestimated complexity, or inefficient execution and if left unaddressed, it eats margin fast.
A program with both indices trending below 1.0 is the pattern every PM dreads, because it tends to compound. The reason comes from actual DoD research, not folklore. In a series of studies dating back to the early 1990s, Christensen and colleagues analyzed over 150 completed Air Force and defense acquisition contracts and found that the cumulative CPI typically does not move more than about 0.10 from the value it holds once a contract passes the 20% completion mark. When it does move, it usually gets worse, not better. A follow-on study examining 209 DoD contracts spanning 1987-2012 reaffirmed the pattern, though not every researcher agrees it generalizes cleanly outside large defense programs. The practical translation: if your CPI is sitting at 0.85 a fifth of the way through a contract, plan your forecast and, also your conversation with the customer around something close to 0.85, not a hoped-for recovery to 1.0. That's not a compliance footnote. That's a statistically grounded early warning sign that should be changing how a program is managed months before the end-of-contract numbers confirm what CPI already predicted.
The Trap of Treating EVM as a Reporting Exercise
Where a lot of PMOs go wrong is treating EVM as something that happens after the work such as a monthly export, a report format, a set of numbers assembled to satisfy a customer's EVMS surveillance requirement. When that's the mental model, CPI and SPI become backward-looking artifacts instead of forward-looking instruments.
The programs that get real value out of EVM treat it differently. They:
- Review trends, not snapshots. A single month's CPI dip might be noise. Three consecutive months of decline is a pattern worth acting on.
- Tie variance analysis to real corrective action, not just a narrative paragraph in a report that explains away the number.
- Push EVM data down to the control account level, so a declining index at the program level can actually be traced to the work package or cost account driving it.
- Use Estimate at Completion (EAC) calculations derived from CPI, not just budget-based guesses, to get a realistic picture of where the contract is headed financially.
Where This Breaks Down for GovCon Contractors
For many contractors, the real obstacle isn't understanding what CPI and SPI mean. It's that the underlying data pipeline makes trustworthy, timely EVM difficult. Control accounts often don't map cleanly to the WBS. Timesheet data lags actual cost postings. Planned value baselines sometimes live in a spreadsheet instead of the system of record. When the data isn't structured well, your EVM numbers will always be a step behind reality, no matter how well your PMO understands the theory.
This is where the compliance mindset and the management mindset actually reconnect. Getting EVM right as a predictive tool requires getting the system architecture right first. A well-configured project cost accounting environment produces clean, timely, control-account-level cost and schedule data. That doesn't just make it easier to pass a DCMA review. It's the difference between a PM finding out about a cost overrun in month four versus month ten.
The Takeaway
CPI and SPI are not just artifacts of a compliance regime. Read together, and read as trends rather than snapshots, they are one of the earliest and most reliable predictors of program health available to a PM. They often flag problems months before those problems show up in a status meeting or a customer escalation.
The programs that treat EVM as a management discipline instead of a reporting obligation tend to catch problems while they're still cheap to fix. The ones that don't usually find out the hard way, at exactly the point in the contract when options are most limited.
About Iuvo Systems:
Iuvo Systems provides outsourced accounting, financial operations, reporting, data analytics, enterprise system solutions, project management, and staffing support to organizations across government, nonprofit, and commercial sectors. Our team helps clients streamline financial processes, improve visibility, and scale operations through a combination of experienced professionals and proven technology solutions, including Deltek®, Workday®, SAP®, Oracle®, Microsoft®, QuickBooks®, and Xero® platforms.
Founded in 2009, Iuvo Systems is an SBA-certified 8(a) small business dedicated to helping organizations operate more efficiently and achieve their goals.
Iuvo means "to help and to support" in Latin, reflecting our commitment to being a trusted partner in our clients' success.