What an EVM engagement looks like — methodology walkthrough

How this piece is framed

This is not a write-up of a specific past project. EVM engagements typically sit inside contracts where the cost performance position is commercially sensitive — acquisition programmes, regulated capital schemes, prime-and-sub arrangements with EVM flowed down through the supply chain. Rather than anonymise to the point of meaninglessness, we have written this as a methodology walkthrough: what an EVM engagement looks like in shape, what we do at each stage, what the evidence has to survive, and what we explicitly do not do.

For the underlying technique — PV / EV / AC, CPI / SPI behaviour, why a Cost Performance Index can be lying, and what a recoverable EAC actually looks like — see our guide to when CPI is lying, which sits inside the wider infrastructure topic hub. This piece is the operational counterpart: what an engagement actually involves week-by-week, not what the formulae are.

Engagement shape

A typical EVM engagement falls into one of four scopes, often in combination. EVMS readiness review — ahead of a contract that requires Earned Value Management, an assessment of whether the project organisation, system and people can actually run EVM to the required standard. Performance Measurement Baseline (PMB) validation — once the WBS, OBS, control accounts, work packages and earning rules have been set, an independent check that the PMB is internally consistent, contract-compliant, and capable of producing signals an SRO can act on. Monthly EVM reporting audit — a recurring assurance pass on the live monthly reporting cycle, focused on whether the CPI and SPI numbers in the report genuinely reflect what is happening in delivery. EAC challenge — a structured interrogation of the Estimate-at-Completion, separating trend-based extrapolation from genuine bottom-up re-estimation, and testing whether the EAC is recoverable in the form the project team is presenting it.

Most engagements blend two or three of these. A pre-contract EVMS readiness review will typically lead into a PMB validation once the baseline is built; an audit engagement on a live programme will almost always surface EAC issues that need their own structured challenge.

What we do at each stage

An EVM engagement runs in five recognisable stages. Each one has its own deliverable and its own failure mode — skipping a stage is how an EVM review ends up producing CPI / SPI numbers that nobody trusts.

• Kickoff and scoping — short workshop with the project director, the cost / planning lead and the EVM analyst to confirm scope, the contractual EVM requirement (ANSI/EIA-748 directly, MoD EVM guidance, NEC4 Option C with target cost mechanics, FAR Part 34), the system in use (Cobra, Deltek, SAP, EcoSys, bespoke), the reporting cadence, and the decisions being supported. The output is a one-page EVM brief. Most arguments later in the engagement trace back to a missing line in this brief.
• Data gathering — WBS, OBS, control account plans, work package definitions, earning rules, baseline budget, contract data items list, monthly EVM reports for the prior three cycles, variance analysis narratives, and the change log. We read the EVM reports before we open the tool — the variance narratives tell you whether the EVM is functioning as a management discipline or as a compliance artefact.
• Diagnostic — the formal benchmark against ANSI/EIA-748’s 32 guidelines (organisation, planning and budgeting, accounting considerations, analysis and management reports, and revisions and data maintenance), plus the qualitative checks the guidelines do not fully capture: whether earning rules are deliverable-based rather than judgement-based, whether the PMB is bottoms-up consistent, whether management reserve is held at the right tier, and whether the variance analyses written into the report would convince an independent reader who had not been at the project review.
• Reporting — a written assessment with each finding ranked by impact on the credibility of the cost performance position. Findings are separated into compliance issues (the EVMS is not meeting the 32 guidelines), signal-quality issues (the EVMS is compliant but the CPI / SPI numbers do not reflect delivery reality), and EAC issues (the forecast is not recoverable in the form presented). The recommendations are sized to the gap and tied to the next reporting cycle.
• EAC challenge session — where the engagement extends to the EAC, a structured working session with the cost lead and the planning lead to interrogate the forecast: separating committed cost, in-flight commitment, and to-go forecast; separating trend-based EAC (BAC / CPI) from genuine bottom-up re-estimation; testing whether the EAC assumes performance reverts to baseline (and on what evidence) or whether it assumes current trend continues. The output is a defensible EAC narrative that survives independent challenge — not just a number.

What good evidence looks like

A defensible EVM product satisfies three audiences. The project director needs to know whether the cost performance position in this month’s report is real — and if not, where the gap is. The independent reviewer (IPA gateway team, NAO, internal audit, an SRO with a sceptical eye) needs structured evidence that the EVMS meets ANSI/EIA-748 and that the CPI / SPI signals are doing real work, not just passing an audit. The cost / planning team that runs the system needs to recognise the assessment as fair — an EVM review that the in-house team rejects stops being useful as a governance tool.

In practice that means benchmarking the EVMS against ANSI/EIA-748’s 32 guidelines explicitly — not the high-level five categories, but the underlying guidelines that govern WBS structure, OBS integration, control account discipline, earning rule appropriateness, accounting accruals, variance analysis triggers, EAC re-estimation frequency, and baseline change control. Each guideline reported as compliant / partially compliant / non-compliant, with the evidence behind the call, and with the implication for the credibility of the cost performance signal.

Where the work supports an investment decision or a gateway review, the report is structured so that the headline finding, the EVMS compliance summary, the signal-quality assessment, and the EAC narrative are each self-contained and traceable. That way an investment-committee or gateway reader can audit the chain from CPI / SPI back to specific control accounts and work packages without taking a guided tour. On NEC4 Option C contracts the same logic applies, but the chain runs through the contractor’s defined cost build-up and the pain / gain share mechanism rather than through a pure EVMS structure.

What we don’t do

It is worth being explicit about scope limits. We do not run the EVMS on behalf of the client — we review, audit, validate and challenge; the operational discipline stays with the in-house cost and planning team or with the contracted EVM service provider. We do not authorise baseline changes — a baseline change request might be informed by our review, but the authorisation sits with the appropriate change control board, not with the independent reviewer. We do not sign off the EAC as recoverable when our diagnostic shows it is not — we describe what would have to change, but the EAC sign-off remains with the accountable party. And we do not perform formal EVMS certification audits as a certifying authority — our assurance work prepares an organisation for, and validates against, ANSI/EIA-748, but the certification itself is a separate regulated activity.

This matters because the failure mode in independent EVM assurance is drift. A reviewer who starts adjusting the EAC themselves, or whose ANSI/EIA-748 commentary turns into a critique of the contractor’s commercial strategy, has stopped being independent — and the assessment stops being usable at gateway or investment-committee challenge. Staying inside the EVM remit is what makes the independence credible.

How engagements typically run

An EVM engagement runs in one of three sizes. A four-week engagement — single readiness review or PMB validation, written report, working-session debrief. Right-sized for a focused decision point: a pre-contract EVMS readiness check, a one-off PMB validation ahead of a gate, or a structured EAC challenge at a quarter-end. A four-week run is enough to deliver a credible independent product on a single programme where the EVMS is in reasonable shape; it is not enough to remediate a system that is non-compliant against ANSI/EIA-748.

An eight-week engagement — the typical shape for a more substantial piece of work. Readiness review or PMB validation, plus a benchmarked audit of two consecutive monthly reporting cycles, plus an EAC challenge session, plus a coaching pass with the in-house EVM analyst. This is the shape that suits programmes preparing for a major gateway, or contractors preparing an EVM compliance submission they need to defend.

Ongoing retainer — monthly or quarterly EVM reviews against a live programme, with the EVM analyst supported through reporting cycles, EAC cycles and baseline change cycles. The assurance stops being a one-off document and becomes a maintained discipline that tracks signal quality as the programme moves. This is where EVM assurance earns its keep on a multi-year programme — a frozen PMB validation from sanction loses value within two reporting cycles; a maintained discipline continues to inform governance throughout delivery.

Most EVM engagements that produce real change are a defined Phase 1 (four or eight weeks) plus a Phase 2 retainer at a lower cadence. Engagements that stop at the report typically see the discipline drift within two quarters, because the operating model after the report is unchanged — the same earning-rule habits, the same EAC trend method, the same variance narrative shape, all of which the original report flagged.