Earned value management compares the budgeted value of work completed with both the work planned and the cost incurred at a common cutoff. Its core inputs are planned value, earned value, and actual cost. You need a current approved baseline and a defensible rule for earning progress before the resulting variances can explain project performance.
A project that has spent less than its planned budget may have completed even less work than planned. Comparing actual spend with planned spend alone misses that difference. Establish the completed scope first, value it at the approved budget, and then compare it with actual costs for the same work and date.
Establish planned value, earned value, and actual cost
Planned value (PV) is the budgeted cost of work scheduled through the cutoff. Earned value (EV) is the budgeted value of work performed. Actual cost (AC) is the cost incurred for that work. PMI’s earned value management explanation defines these inputs and the performance calculations that follow from them.
Keep the work package and baseline revision attached to each measure. A revised package budget and an old progress percentage do not describe a consistent comparison. Record approved changes with their effective dates so a report can show performance under the current baseline while retaining the version used for an earlier decision.
Actual cost needs a declared cutoff and scope. If progress includes installed work through Friday but the cost extract excludes invoices or accrued costs for that work, the apparent cost efficiency can be overstated. Have the project accountant identify the coverage (including approved accruals) before accepting the cost population. Missing costs should remain a qualified input rather than be assumed to be zero.
Choose how a package earns its budget
Use a progress rule that the work can support. Installed quantities, accepted milestones, and completed deliverables create different evidence. For quantity-based work, retain the total scope, measured completed quantity, unit, and acceptance status. The person reporting progress should identify what was counted and what remains, including any rework that invalidates an earlier completion claim.
PMI’s worked earned-value example values progress by multiplying a completed proportion by its budget. That requires the proportion to represent the budgeted work. Spending half the cash does not establish that half the scope is complete, and a material delivery does not necessarily earn the value assigned to its installation.
Agree on the rule before the reporting period. If a package earns value only on accepted completion, keep unfinished work unearned under that rule. If progress is measured by quantities, specify how inspection, rejected work, and changes affect the completed quantity. Apply the same method across periods or label the effect of a method change.
Calculate variances and performance indices
Assume a hypothetical project with a $200,000 budget at completion. At the review cutoff, $100,000 of budgeted work was scheduled, $80,000 of budgeted work has been completed under the approved earning rule, and actual cost is $90,000. All amounts are USD, the baseline is unchanged, and actual cost includes the completed work through the same cutoff.
| Measure | Calculation | Hypothetical result |
|---|---|---|
| Schedule variance | EV - PV | $80,000 - $100,000 = -$20,000 |
| Cost variance | EV - AC | $80,000 - $90,000 = -$10,000 |
| Schedule performance index | EV / PV | $80,000 / $100,000 = 0.80 |
| Cost performance index | EV / AC | $80,000 / $90,000 = 0.889 |
Actual spending is $10,000 below planned value, but the project has earned $20,000 less work than planned and spent $10,000 more than the budgeted value of that completed work. The indices describe value against planned value and cost. They do not establish the cause, which still needs investigation of quantities, productivity, rates, and cost timing.
Schedule variance is expressed in budget value, not elapsed days. A negative result does not say which milestone is late or how many days the finish will move. PMI’s analysis of earned value systems identifies the limits of interpreting schedule variance without work sequence and critical-path context. Review the statused schedule before accepting a recovery date.
Check one package’s progress and cost evidence
Start with an approved budget, accepted progress record, and cost extract for the same cutoff.
Separate the performance signal from the forecast
One conditional estimate at completion is budget at completion divided by cost performance index. In the example, $200,000 / ($80,000 / $90,000) = $225,000. That assumes the remaining work continues at the same cost efficiency. It is a calculation under a stated assumption, not a forecast established by the index alone.
A package with a one-time mobilization cost can behave differently from one with a continuing productivity problem. Record a bottom-up remaining-work estimate when the team has better evidence, and keep its assumptions beside it. The construction cost-to-complete article explains the separate estimate of remaining exposure and the need to avoid counting commitments twice.
Use the construction job cost report to reconcile costs and commitments, and project controls to route decisions about baseline changes and recovery. An earned-value calculation should contribute evidence to those decisions without treating a favorable index as authority to accept scope or revise a contract.
When evaluating construction cost management software, ask whether the progress rule, cost cutoff, and baseline revision can be inspected together. A dashboard that calculates an index without those inputs leaves the reviewer unable to explain the result. Keep your existing tool when it can preserve that evidence and the decisions made from it.
Where Permute connects the measurement records
Permute sells connected business data and custom applications. We can combine permitted cost records, supplied schedule exports, and progress registers using agreed project and work package identities. That lets a review retain the budget revision and source cutoff behind each comparison.
We can apply your declared earning rules and variance formulas in reusable transformations. A controls manager could inspect a package whose cost performance changed and open the progress and cost evidence within their permissions. Confirm source fields, history, and refresh timing before relying on a recurring review; missing acceptance evidence cannot be repaired by a formula.
Keep progress acceptance and forecasts with the project team
We are not a forecasting engine and do not certify physical progress, choose an earning method, or approve a recovery plan. This analytical workflow reads the supporting records rather than changing the project baseline or source system. The project team remains responsible for acceptance, cost estimates, schedule dependencies, and the applicable change approvals.
Calculate earned value management measures only after aligning the baseline, accepted progress, and actual cost at a common cutoff. Read cost variance against the value of work completed, and read schedule variance alongside the schedule’s dependencies. Keep any estimate at completion attached to its assumption. Investigate the supporting package records before deciding how the project should respond.
Review a project performance discrepancy
Bring a package where spending and reported progress disagree to assess the evidence behind the calculation.
Questions about earned value calculations
What if planned value or actual cost is zero?
Do not calculate an index with a zero denominator. Show it as undefined and inspect whether the package has started, whether cost posting is incomplete, or whether the scope is wrong. Keep the underlying amounts visible so the exception can be resolved.
Can billing progress stand in for physical progress?
Only if the agreed measurement method establishes that relationship and the evidence supports it. Payment milestones can reflect commercial terms rather than completed scope. Preserve the approved progress basis separately from the pay application.
Does an SPI of 0.80 mean the finish will be 20% late?
No. SPI compares earned value with planned value in budget terms. Work sequencing, remaining scope, and the critical path determine the schedule implications, so the index cannot supply a finish date by itself.