A project can spend less than planned and still be over budget for its progress

A project report showing $70,000 spent against $80,000 planned can look favorable. That comparison is incomplete if the team has delivered substantially less work than the plan required. The missing question is how much the completed work was expected to cost under the agreed budget.

Earned value introduces that comparison. The National Science Foundation defines earned value as the budgeted cost of work performed, planned value as the budgeted cost of work scheduled, and actual cost as the cost of work performed. These are project-control measures; earned value is not customer revenue or the value of an invoice.

Use the method when progress can be measured against a reasonably defined scope. A spending total alone cannot establish physical completion, and a manager's unsupported percentage cannot make the calculation reliable. The project needs a practical way to show which deliverables have actually been achieved.

Consider an invented project with a total approved work budget of $200,000. At the reporting date, the plan called for work carrying $80,000 of that budget to be complete. The project has actually completed work carrying $50,000 of the original budget and incurred $70,000 of cost.

Planned value is therefore $80,000, earned value is $50,000 and actual cost is $70,000. The project has completed 25% of its budget-weighted work when 40% was scheduled. It has spent 35% of the total work budget.

The apparent $10,000 spending saving disappears when progress is considered. Completing the work delivered so far was budgeted to cost $50,000, but it cost $70,000. This indicates $20,000 of unfavorable cost performance for that completed work, subject to the accuracy of the progress and cost records.

The cost performance index is earned value divided by actual cost: $50,000 divided by $70,000, or approximately 0.714. In this example, each dollar incurred has produced about 71 cents of work measured at its original budgeted cost.

The schedule performance index is earned value divided by planned value: $50,000 divided by $80,000, or 0.625. The project has earned 62.5% of the budgeted progress scheduled by this date. The cost variance is negative $20,000; the schedule variance, earned value minus planned value, is negative $30,000.

That schedule variance is expressed in budget dollars, not days. It does not mean the project is 37.5% late in calendar time. A delayed critical activity and an early noncritical activity can affect the completion date differently, even if their budget values offset in the aggregate index.

One forecast assumes the observed cost efficiency continues across the remaining work. Dividing the $200,000 total budget by the 0.7142857 cost performance index produces an estimated final cost of $280,000. This is a projection of the measured performance, not an independent estimate of every unfinished task.

A different forecast assumes the remaining work can be completed at its original budget. The remaining budgeted work is $200,000 minus $50,000, or $150,000. Adding that amount to the $70,000 already incurred gives a final cost of $220,000.

The $60,000 difference between those forecasts is a question for the delivery team. Did a one-time problem cause the early overrun, or does the same problem affect the unfinished scope? A revised estimate built from the remaining tasks can be more useful than selecting whichever formula gives the preferred answer.

Suppose a work package has a $20,000 budget and a ten-week planned duration. Reaching week five does not by itself earn $10,000. If the acceptance criteria remain unmet, elapsed time may reveal effort without demonstrating equivalent progress.

Choose completion rules that fit the work. A short, indivisible deliverable may be counted only when accepted. A longer package may use documented milestones with budget weights assigned beforehand. The purpose is to prevent progress from rising simply because people have continued charging time.

Avoid repeatedly awarding the same progress after rework. If a previously completed item fails acceptance, explain whether the earned amount needs correction or whether the repair is separately authorized scope. Keeping an optimistic completion percentage while hiding repair effort makes the index harder to interpret.

Match actual costs to the progress period. An unrecorded supplier invoice can make current cost efficiency appear stronger, while a large advance payment can make a cash-spending report appear weaker. Use the cost basis agreed for the project-control system and reconcile the difference from cash paid.

Document approved scope additions before interpreting a changed budget. If management adds a new deliverable, the total work budget and the schedule may legitimately change. Preserve the prior baseline and the authorized adjustment so readers can distinguish scope expansion from an overrun on the original work.

Do not erase historical variances merely by resetting every unfinished package to its latest estimate. A current forecast and a performance baseline serve different purposes. Management needs to see both what the job is now expected to cost and how that expectation differs from the commitment originally approved.

A $280,000 estimated final cost is not a payment schedule. Some incurred costs may remain unpaid, some supplier deposits may already have been paid, and future work may have different billing terms. Build the cash forecast from those dates after reconciling the project estimate.

Likewise, customer billing can depend on contract milestones that differ from internal progress measures. A project can earn budgeted progress without qualifying for an invoice. Check the contractual trigger before treating the next earned-value increase as a near-term receipt.

For the illustrative project, the immediate review should identify why $50,000 of planned work cost $70,000, which unfinished packages face the same condition, and whether the delivery date changes. Those questions determine whether the $220,000 or $280,000 forecast is closer to a defensible operating plan.

Assign corrective actions to the affected work, with an expected effect on remaining cost or timing. The useful outcome is a revised completion estimate supported by the delivery evidence. The indices help reveal the problem; they do not supply the engineering, staffing or commercial decision needed to resolve it.