Earned value analysis report: what to include

An earned value analysis report turns work-package performance into a review of cost exposure, delivery risk and the remaining estimate. Show planned value, earned value and actual cost together, then explain the exceptions and forecast assumptions. The report is useful only when the completed work and incurred costs can be supported at the same cutoff.

Define the question for the review

The sponsor needs to know whether accepted work is keeping pace with the baseline, whether that work is costing more than expected, and whether the proposed completion estimate is credible. A page of indices without those answers leaves the decision unfinished.

The Department of Energy describes earned value management as integrating cost, schedule and technical accomplishments. Keep that connection visible: the report's dollar-valued progress measures should sit beside delivery evidence and forecast milestones.

Use the existing CPI, SPI and estimate-at-completion guide for the full formula reference. This report focuses on presenting a reconciled position and deciding what to do about it. For iteration-based delivery, the neighboring earned value analysis in agile projects addresses the progress basis separately.

Assemble the report from controlled exports

Bring the time-phased baseline, accepted-progress export, project ledger and the delivery owner's remaining-cost estimate. Keep project ID, work-package ID, reporting date, baseline version and currency on the inputs. Document how progress earns its budgeted value before interpreting a variance.

Use the approved budget for the measured scope as budget at completion, or BAC. Planned value, PV, is the budgeted value scheduled through the cutoff. Earned value, EV, is the budgeted value of accepted work. Actual cost, AC, is incurred cost for the same scope, including the finance team's required accruals.

Do not infer EV from invoices or cash paid. A supplier payment can precede acceptance, and completed work can require an accrual before an invoice arrives. The project management report covers the wider package of spending, commitments and milestones.

Build the work-package table

Consider a US equipment replacement project at September 30, 2026. Engineering uses accepted drawings, assembly uses accepted production milestones, and commissioning uses accepted test stages. The progress export supplies their budgeted values; the ledger supplies incurred costs.

The delivery owners provide estimate-to-complete amounts, or ETC, for remaining scope. These are current estimates, not amounts calculated by subtracting actual cost from the original budget.

Place the following fields in spreadsheet columns A through F, with data in rows 2 through 4. All monetary columns are USD.

Add columns G through J for cost variance, schedule variance, forecast total cost and variance at completion. In G2 through J2, use these formulas respectively, then fill down:

=D2-E2
=D2-C2
=E2+F2
=B2-I2

Negative variances are unfavorable under these definitions. Schedule variance is the dollar-valued gap in budgeted work, not calendar days late. Commissioning's delivery forecast still needs its own schedule assessment.

For a compact headline, calculate cumulative CPI and SPI from the totals:

=SUM(D2:D4)/SUM(E2:E4)
=SUM(D2:D4)/SUM(C2:C4)

CPI is 268,000 / 315,000 = 0.851, and SPI is 268,000 / 308,000 = 0.870, rounded to three decimals. Keep the source amounts beside these indices so stakeholders can see their scale.

Explain the forecast and prove the totals

The estimate at completion is $315,000 incurred cost + $275,000 remaining cost = $590,000. Against the $500,000 approved budget, the forecast overrun is $90,000. Engineering is complete; its overrun remains in the forecast even though its remaining estimate is zero.

Assembly's owner must support the $155,000 remaining estimate with unfinished milestones, expected labor and outstanding purchases. Commissioning's owner must support $120,000 for remaining test work. State whether those estimates include expected rework, whether quoted purchases remain valid and which schedule assumptions require confirmation.

This is a bottom-up completion estimate. It does not assume that historical cost efficiency automatically continues. Present an index-based challenge separately if the reviewer needs one, rather than silently substituting it for the owner's estimate.

Before writing the summary, check that:

• The work-package BAC totals tie to the approved $500,000 baseline.
• The $315,000 actual cost ties to the ledger and documented cutoff adjustments.
• Cost variance sums to $268,000 EV minus $315,000 AC, or -$47,000.
• Schedule variance sums to $268,000 EV minus $308,000 PV, or -$40,000.
• The sum of forecast costs equals $590,000, and budget minus forecast equals -$90,000.

The DOE implementation guidance describes a review sequence covering data validity, schedule health, variances, trends and forecasting. Follow that order when judging whether the headline is ready to circulate.

Write exceptions as decisions

Assembly is the largest forecast exposure in the example. Its exception should identify the unfinished scope, the evidence behind the revised estimate, the practical recovery choices and the person who must decide. Distinguish a proposed action from an approved change to the baseline.

For each material exception, record the accountable owner, required decision, due date and evidence that will close it. Show prior-report movement only when both report versions are available. Place the resulting headline in the broader management reporting package.

Where the report goes wrong

• Unsupported completion estimates. Progress needs accepted work under an agreed measurement rule, not a manager's impression.
• Costs arriving after the progress snapshot. Missing accruals can temporarily make cost performance look favorable.
• Reading schedule variance as days. Budgeted-work variance does not establish the critical path or completion date.
• Hiding forecast assumptions. A calculated total can reconcile perfectly while omitting remaining rework or expected supplier costs.

Review your own earned value files in Covirage

Bring your baseline, accepted-progress, incurred-cost and remaining-estimate files. Covirage maps the columns, its tools compute and check the work-package comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own project data.

See project cost control for the supporting business context.