How to Build an Earned Value Management Framework That Survives Board-Level Scrutiny

Earned Value Management (EVM) is intended to give senior decision-makers an integrated view of scope, cost and schedule performance. On complex infrastructure and defence programmes, however, the credibility of the output depends less on the sophistication of the reporting pack than on the discipline of the framework beneath it.

A credible earned value management framework establishes a controlled baseline, captures reliable actual costs, measures physical progress objectively, explains variance and produces a forecast that can withstand challenge. It must support decisions, not simply demonstrate reporting compliance.

Why EVM credibility is under pressure

EVM is widely mandated across major capital, defence and government programmes. Yet it is often implemented as a monthly reporting exercise, separated from the commercial, scheduling, risk and change-control processes that determine whether the forecast is reliable.

That creates familiar weaknesses:

• Earned value is claimed against activity completion rather than objective physical progress.
• Cost and schedule data use different coding structures.
• Estimates to complete are adjusted to preserve an approved narrative.
• Baseline changes are recorded late or outside formal governance.
• Board reports show CPI and SPI without explaining the forecast, confidence range or underlying drivers.

The publication of EIA-748 Revision E in February 2026 provides a useful point of reference. The standard consolidates the previous 32 guidelines into 27 guidelines, aligning them more closely with the full project life cycle and current practice without reducing the underlying rigour.

The NDIA IPMD EIA-748-E Intent Guide, published in May 2026, is the primary practical reference for mapping an organisation’s internal processes to the revised guidelines. Compliance is normally demonstrated through a documented process map, supported by objective evidence, and then verified through certification, acceptance or surveillance reviews.

The important distinction is that compliance is not the same as usefulness. A system may produce compliant reports and still fail to provide dependable management insight if the underlying data, ownership and governance are weak.

The five disciplines of a credible EVM framework

The 27 EIA-748-E guidelines are organised into five connected process categories. Each addresses a different part of the control chain.

Discipline	What it means in practice	Why it matters
1. Organising work	Establish the WBS, OBS, control accounts and accountable managers.	Creates clear ownership for scope, budget, schedule and performance.
2. Planning and budgeting	Build an integrated, time-phased Performance Measurement Baseline (PMB).	Defines the approved plan against which progress is measured.
3. Accounting and data collection	Capture actual costs, commitments and progress consistently by control account and element of cost.	Ensures earned value is compared with the correct cost data.
4. Analysis and reporting	Assess variances, CPI, SPI, ETC and EAC, then explain causes and actions.	Converts data into management information and forecast insight.
5. Change control	Authorise, record and reconcile changes to scope, schedule and budget.	Protects baseline integrity and preserves trend credibility.

1. Organising work

The WBS should represent the complete authorised scope. The OBS should identify the organisations responsible for delivering it. Their intersection creates the control account: the point at which a defined scope of work, an accountable manager, a schedule and a budget come together.

A control account should be sufficiently detailed to support management action, but not so detailed that the system becomes administratively unmanageable. Subcontractor and supply-chain scope must also be visible within the structure.

If ownership is unclear, variance analysis becomes descriptive rather than corrective. A report may identify a problem, but no accountable manager has the authority or responsibility to resolve it.

2. Planning and budgeting

The PMB is the time-phased plan for delivering authorised scope within the agreed schedule and budget. It should integrate:

• Scope and WBS structure.
• Logic-linked schedule activities and milestones.
• Work packages and planning packages.
• Resource and cost budgets.
• Undistributed budget.
• Management reserve.
• Agreed assumptions and risk responses.

The PMB is not simply a cost plan. It establishes when work is expected to occur, what resources are required and how progress will be measured. The baseline must be realistic enough to support management action and stable enough to preserve trend information.

Undistributed budget should remain linked to defined authorised scope until it is allocated. Management reserve should be separately identified and used only in accordance with the approved governance process.

3. Accounting and data collection

Actual costs must be captured consistently with the budgets against which they are compared. This includes labour, material, subcontract, other direct costs and relevant indirect costs.

Defined cost and commitment accounting are particularly important on large programmes. Invoice timing can lag physical progress, while commitments may provide earlier visibility of future exposure. Where actual costs are not yet available, estimated actuals may be required, but the treatment must be controlled, documented and reconciled when the accounting record catches up.

A weak actual-cost feed can make a sound baseline appear unreliable. It can also create false cost variances caused by timing, coding or allocation differences rather than genuine performance.

Using EVM metrics properly

The standard EVM measures remain useful, but only when interpreted within the wider programme context.

• Cost Variance (CV) = EV − AC
  Measures the value of work performed against the actual cost incurred.

• Schedule Variance (SV) = EV − PV
  Measures the budgeted value of work performed against the budgeted value of work scheduled.

• Cost Performance Index (CPI) = EV ÷ AC
  A CPI below 1.0 indicates that work is costing more than its budgeted value.

• Schedule Performance Index (SPI) = EV ÷ PV
  An SPI below 1.0 indicates that less budgeted work has been accomplished than planned.

CV and SV are expressed in value terms, not pounds and calendar days. That distinction matters. A negative schedule variance indicates a difference in planned and earned value; it does not, by itself, state how many days late the programme is.

SPI also requires a critical-path caveat. A favourable SPI can coexist with slippage to a critical activity if non-critical work has been completed early or if the earned value profile is distorted by the measurement method. EVM should therefore be read alongside critical-path analysis, float erosion, milestone movement and, where appropriate, earned schedule or other duration-based measures.

The more useful board-level question is not simply whether CPI is 0.96 or SPI is 0.98. It is:

What is the forecast completion position, how confident are we in it, and which cost, schedule, risk or scope drivers could change it?

Trend data is more informative than a single-period figure. A deteriorating three- or six-period trend may require action even where the current period remains within threshold.

Making the forecast defensible

The Estimate at Completion (EAC) should be the result of a controlled forecast process, not a management preference.

A defensible EAC requires:

1. A control-account-level estimate to complete.
2. Reconciliation between the forecast, the cost model and the resource-loaded schedule.
3. Consistent treatment of risk, contingency, management reserve and approved changes.
4. Consideration of commitments, subcontractor forecasts and indirect-rate movements.
5. Documented assumptions, exclusions and dependencies.
6. Independent challenge of the most material forecast components.

Performance-based EAC calculations can provide useful reference cases, but they should not replace informed analysis. A management override may be valid where corrective action is evidenced, but the rationale must be explicit. An unexplained override simply weakens forecast integrity.

A monthly forecast change log should record movement from the previous EAC, including:

• The amount and direction of change.
• The affected control account or cost element.
• The cause of movement.
• The relevant risk, change or schedule driver.
• The owner and supporting evidence.
• Whether the movement is realised, forecast or contingent.

This makes the forecast explainable and provides an audit trail for board and government review.

Governance and reporting design

An effective reporting regime should provide a single source of truth, a defined reporting calendar and clear escalation routes. The monthly cycle should integrate:

1. Schedule status and critical-path review.
2. Physical progress and earned value assessment.
3. Actual cost and commitment reconciliation.
4. Risk, opportunity and contingency review.
5. Change-control and baseline movement.
6. Control-account forecast review.
7. Independent challenge of material variances and EAC movements.

The executive report should fit on one page, but it should not be superficial. It should show:

• Current trajectory.
• Forecast completion position.
• Confidence range.
• Principal cost and schedule drivers.
• Risk exposure and contingency position.
• Milestone and critical-path movement.
• Decisions required from senior leadership.

The detailed evidence should sit behind the executive view. Board-level assurance depends on being able to move from a concise decision statement to the supporting control-account analysis without changing the underlying numbers.

Common failure modes and practical remedies

Failure mode	Practical remedy
Compliance-only implementation	Define how EVM data will drive corrective action, investment decisions and governance reviews before documenting the system.
Disconnected cost and schedule tools	Use common WBS, OBS, control-account and coding structures across scope, schedule, cost, risk and reporting processes.
Over-optimistic ETCs	Require bottom-up estimates, independent challenge and evidence for productivity, rates, commitments and remaining quantities.
Unresolved change outside the baseline	Maintain a formal change log, identify authorised but undefinitised work and establish clear rules for undistributed budget and management reserve.
No clear ownership of the integrated baseline	Assign a named baseline owner with authority to control revisions and require reconciliation between the schedule, cost model and PMB.

On NEC programmes, the EVM framework should complement, not replace, the contract’s early warning, programme and compensation event processes. EVM trends can provide valuable evidence for risk reduction and forecast discussions, while the contractual processes must remain governed by the relevant Scope, Contract Data and accepted programme requirements. Related NEC governance considerations are set out in the guidance on NEC4 early warnings and NEC4 compensation events.

A practical implementation sequence

Framework design should precede tooling. A sensible implementation sequence is:

1. Establish the integrated baseline
   Confirm scope, WBS, OBS, control accounts, schedule logic, budget structure and ownership.

2. Agree the Performance Measurement Baseline
   Time-phase authorised budgets, define earned value techniques and document assumptions, undistributed budget and management reserve.

3. Harden change control
   Set approval thresholds, maintain revision history and reconcile every approved change across scope, schedule and cost.

4. Fix the actual-cost feed
   Align charge codes, accounting treatment, commitments, estimated actuals and subcontractor data with control accounts.

5. Build the analysis and reporting layer
   Define thresholds, variance narratives, CPI/SPI trends, critical-path measures, ETC and EAC requirements.

6. Build assurance and independent review
   Produce the EIA-748-E compliance map, retain objective evidence and arrange independent assessment or surveillance.

The resulting system should be scaled to the programme’s size, complexity and risk. It should be rigorous where scrutiny and uncertainty are highest, while remaining practical enough for delivery teams to use consistently.

Conclusion

An earned value management framework survives board-level scrutiny when it connects five disciplines without breaking the chain: organised scope, integrated planning, reliable accounting, objective analysis and disciplined change control.

The output required by senior stakeholders is not a larger dashboard. It is a defensible view of trajectory, confidence, exposure and decision requirements. That depends on a stable baseline, transparent assumptions, reconciled data and forecasts that can be challenged without losing their evidential foundation.

Sources and references

• SAE International: EIA-748E Earned Value Management Systems
• NDIA IPMD: EIA-748-E Intent Guide, May 2026
• Association for Project Management: Earned Value Management – APM Guidelines
• APM: Interfacing Risk and Earned Value Management
• NEC4 contract family and selection considerations

Social-sharing summary

A credible earned value management framework is more than a compliance report. It links scope, schedule, cost, risk, forecasting and change control into one evidence-led management system capable of supporting board-level and government scrutiny.

---

About the Author

Nick Garvey is a chartered construction professional (MCIOB, FCaSA, FQSi) with more than 25 years of experience in commercial leadership and project controls across defence infrastructure, government estates, highways, facilities management and public-sector programmes. He leads cost, schedule, risk and performance reporting on major defence infrastructure programmes, chairs risk reviews at senior governance level, and writes about earned value management, quantitative risk analysis, NEC4 contracts and forecast integrity.

All views my own, shared in a personal capacity.