Skip to main content

Earned value management software for project control

Use EVM metrics to compare planned progress, earned progress, and actual cost so project health is visible before status meetings.

Topics this page coversearned value management softwareCPI SPI project managementEVM tracking toolearned value management calculatorCPI SPI calculatorEVM formulas

What earned value management actually measures

Earned value management answers one question with numbers instead of adjectives: for the money spent so far, how much project did you actually get? It does that by putting three quantities on the same scale. Planned value (PV) is what the schedule said you should have delivered by today, priced at budget. Earned value (EV) is what you have delivered, priced the same way. Actual cost (AC) is what that delivery has cost so far. Compare any two of the three and a specific performance question gets a specific answer.

That shared scale is the whole trick. Percent complete on its own cannot tell you whether you are doing well, because a percentage carries no price tag and no deadline. A project reporting "about 60% done" in week six of ten could be on track or quietly bleeding money, and the report cannot tell you which. EVM turns the same progress report into earned value, sets it beside what the plan expected and what the work cost, and the ambiguity disappears into arithmetic.

The method has a reputation for bureaucracy because full-scale implementations on government programs earned it. The working core, though, is three inputs and two ratios. Pocket PMO implements that core: you set a budget and a schedule, record milestones with values and costs, and the tool computes everything else continuously from the live project record.

The three inputs: PV, EV, and AC

Everything starts from the project budget, which becomes BAC, the budget at completion. Pocket PMO treats the budget set on the EVM tracker as that baseline. From there each input has a precise derivation:

  • Planned value: BAC multiplied by planned percent complete, which Pocket PMO derives from the schedule as the share of project days elapsed between the start date and the status date. Once the planned finish date passes, PV stops growing at BAC, matching the PMI convention that all work is planned to be earned by then.
  • Earned value: BAC multiplied by the weighted progress of your milestones. Each milestone carries a value (its percentage of the budget) and a progress status. Completed milestones earn their full value; in-progress milestones earn a fraction you control, the in-progress value, which defaults to 50 percent.
  • Actual cost: the recorded cost against your milestones. In-progress milestones count a proportional share of their cost using the same fraction, so the EV and AC sides of every ratio stay comparable.

CPI and SPI: the two numbers that run the review

CPI, the cost performance index, is earned value divided by actual cost. It reads as value delivered per unit of money spent: 1.00 means every dollar is buying exactly a dollar of planned work, 0.85 means you are paying about 1.18 dollars for every dollar of value, and 1.10 means each dollar is earning a 10 percent premium over plan. SPI, the schedule performance index, is earned value divided by planned value and reads the same way against time: below 1.0 means the work performed so far is worth less than what the schedule said should be done by now.

Pocket PMO shows both on the Project Health Summary card with the BAC share of EV and PV beside them, so the index never floats free of the amounts behind it. The observations engine applies PMI-style bands automatically: below 0.9 is flagged as critical, between 0.9 and 1.0 as a watch item, and above 1.1 as genuinely strong performance rather than noise.

The discipline that makes these numbers useful is refusing to argue about them. A CPI of 0.92 is a fact with a formula behind it, and so is its trend. When the indexes sit in the same screen as the milestones and costs that produced them, a status review spends its time on causes instead of calculations.

Pocket PMO EVM health summary showing earned value, planned value, CPI, and SPI against the project budget at completion
The Project Health Summary card showing EV and PV as shares of budget beside the CPI and SPI indexes.

Setting up EVM in Pocket PMO

Setup is deliberately short. You set the project budget (which becomes BAC), set a start date and a planned finish date, and the tracker derives the project duration and elapsed time from them. Then you define milestones, each with a value expressed as a percentage of the budget, a cost, and a progress status of Not Started, In Progress, or Complete.

The Project Configuration card carries the one judgment call: the in-progress value. This is your rule of credit for work that has started but not finished, selectable as 0, 20, 50, or 80 percent, defaulting to 50. Pick the number your organization can defend; a milestone that is genuinely all-or-nothing deserves 0, and one where the bulk of effort lands early can justify 80. The card also carries a toggle controlling whether completing a milestone automatically creates a matching expense entry, which keeps the cost ledger and the milestone records in step without a manual re-entry pass.

Because every input lives in the project record, the calculation is continuous. Mark a milestone complete, or record a cost, and CPI, SPI, variances, and forecasts all move together. There is no separate modeling step to forget to rerun.

Variances and forecasts: the additional details layer

Beneath the headline indexes, the Additional Details card computes the standard variance and forecast set. Cost variance (CV) is EV minus AC, stated in currency: how far under or over budget you are for the work actually performed. Schedule variance (SV) is EV minus PV, the same comparison against the plan. From those, the tracker derives the completion forecasts: estimate to complete (ETC, the remaining work priced at your demonstrated cost efficiency), estimate at completion (EAC, actual cost plus ETC), and variance at completion (VAC, BAC minus EAC), which tells you where the budget lands if current efficiency holds.

The forecast arithmetic embeds an assumption worth saying out loud: ETC divides remaining work by CPI, so it assumes future efficiency will look like past efficiency. That is the standard EAC formula and a reasonable default, and it is a projection from evidence rather than a promise. When the team knows the expensive part is behind them, say so in the review and treat EAC as the no-change scenario it is.

Money-based schedule measures have a known blind spot, so the tracker also computes earned schedule metrics. SV(t) and SPI(t) restate schedule performance in time rather than currency, and from the earned schedule the tracker projects a completion date. Pocket PMO derives both index families from the same weighted milestone progress and the same elapsed-time percentage, so with milestone values that sum to BAC, SPI and SPI(t) land on the same number; the time-based restatement matters because it turns the index back into days and dates.

Observations: the tracker reads its own numbers

The Observations card is where the arithmetic turns into sentences. It applies a fixed rule set to the live metrics and reports what it finds. When nothing trips, the card says so plainly: all key metrics within acceptable ranges, no significant concerns. That message is a claim you can defend out loud, which is more than most status narratives can manage. The rules it checks:

  • Baseline integrity: a warning fires when milestone values do not sum to the project budget, with the gap stated in currency.
  • Cost and schedule pressure: CPI or SPI below 1.0 raises a warning, below 0.9 raises a critical alert with the efficiency percentage spelled out, and above 1.1 earns the positive counterpart.
  • Material variances: CV or SV beyond 5 percent of budget gets its own callout with the amount and the percentage of BAC.
  • Completion trajectory: the projection observation compares VAC with 10 percent of budget; EAC is displayed alongside it without an independent threshold. Earned-schedule observations use SPI(t) thresholds of 0.9 and 1.1, and SV(t) thresholds of minus 5 and plus 5 percentage points.
  • Progress inventory: how many milestones are complete out of the total, plus a flag when any are running late.
Pocket PMO EVM observations card flagging cost performance index pressure and milestone progress
The Observations card flagging cost performance index pressure and milestone progress.

Milestone progress and the fight against optimistic reporting

The three-state progress model, Not Started, In Progress, Complete, exists because free-form percent complete invites optimism. Ask a team how done a work package is and you will hear 90 percent for six consecutive weeks; the last 10 percent is where overruns hide. Discrete states plus a fixed rule of credit trade a little precision for a lot of honesty: an in-progress milestone earns exactly the configured fraction, and there is nothing to negotiate.

Milestone choice matters more than any setting. Milestones should sit at natural checkpoints where completion is verifiable, a deliverable accepted or a phase exited, rather than at arbitrary month boundaries, and their values should roughly track the effort each chunk represents. When those two conditions hold, EVM numbers track reality closely enough to steer by. When they do not, even correct arithmetic produces confident nonsense.

Pocket PMO EVM milestone list with budget percentage values, recorded costs, and progress status per milestone
The EVM milestone list with budget percentage values, recorded costs, and progress status per milestone.

Reading CPI and SPI together

The two indexes earn their keep in combination. Either deviation alone invites a story; together they constrain the stories to the plausible ones. Each of the four quadrants has a distinct meaning:

  • CPI above 1.0, SPI above 1.0: ahead on both axes. Check whether it is real outperformance or an underestimate hiding in the baseline.
  • CPI below 1.0, SPI below 1.0: the classic troubled project, burning more than planned while delivering less. Escalation conversations write themselves.
  • CPI above 1.0, SPI below 1.0: usually under-spending because work has not started. Before banking the favorable variance, ask what the schedule slip is doing to it.
  • CPI below 1.0, SPI above 1.0: buying schedule with money, crashing or adding resources to hold dates. Legitimate sometimes, and it should be a decision rather than a drift.

Same record as the budget, risks, and status

EVM in Pocket PMO is an isolated calculator in no sense. The budget tracker and the EVM tracker read the same project record, and their spend figures are built to reconcile, not to be identical: EVM actual cost totals recorded milestone costs, including a proportional share for in-progress milestones, while budget spend counts dated ledger expenses plus completed milestone costs that have no ledger entry. A standalone expense moves the budget view without touching AC, and in-progress credit moves AC before any expense is recorded. The risk matrix, status reporting, and forecasts all read the same project record, so when CPI crosses a threshold, the data that tripped it is on screen during the review. For a project manager running two or more projects, that consistency is the practical benefit: one record per project instead of a spreadsheet model per project, each hoping it was updated after its last status meeting.

A connected workflow, not another isolated file

Pocket PMO keeps project management techniques close to the rest of the project record so decisions can be based on consistent data.

  • Track planned value, earned value, and actual cost
  • Use CPI and SPI to identify cost and schedule pressure
  • Connect project status to objective performance metrics

How teams use it

  1. Step 1

    Define baseline budget and progress expectations.

  2. Step 2

    Update actual cost and earned progress as work completes.

  3. Step 3

    Review CPI, SPI, and variance signals to guide decisions.

Frequently asked questions

What is CPI in project management?

CPI stands for Cost Performance Index: earned value divided by actual cost. It answers how much planned work each unit of money has bought so far. A CPI of 1.00 is exactly on budget, 0.90 means you are receiving 90 cents of planned work per dollar spent, and 1.10 means each dollar is buying 10 percent more value than planned. Pocket PMO shows CPI on the health summary card alongside the earned value and actual cost behind it.

How is planned value calculated?

Planned value is BAC multiplied by planned percent complete at the status date. Pocket PMO derives planned percent complete from the schedule: elapsed days between the start date and the status date as a share of total project duration. Once the planned finish date passes, PV holds at BAC, following the PMI convention that all work is planned to be earned by the finish date. A 120-day project with a 200,000 budget that is 40 days in has a PV of roughly 66,700.

What is the difference between SPI and earned schedule SPI(t)?

SPI compares earned value with planned value, both in currency. SPI(t) expresses earned schedule relative to elapsed time. Pocket PMO derives both from weighted milestone progress and elapsed project time, so with milestone values totaling BAC they produce the same index; front-loaded spending does not make them diverge. The tracker also shows a projected finish date derived from SPI(t).

What in-progress value should I use?

Pocket PMO lets you choose 0, 20, 50, or 80 percent for in-progress milestones, and the default of 50 (the classic fifty-fifty rule) is a sensible starting point. Use 0 for milestones that genuinely deliver all or nothing, and a higher fraction only where most of the effort demonstrably lands early. Whichever you pick, apply it consistently across the project, because a rule of credit only works when it does not change with the mood of the status report.

Why use EVM instead of percent complete alone?

Percent complete has no price and no deadline, so it cannot distinguish a project that is on track from one that is overspending its way to the same percentage. EVM prices the progress (earned value), sets it against the priced plan (planned value) and the money spent (actual cost), and the comparisons produce CPI, SPI, variances, and forecasts. The progress report becomes a set of ratios you can compare across weeks and across projects.

When do EVM numbers stop being trustworthy?

When the inputs stop being honest. The classic failure modes: milestone values that do not reflect real effort, milestones placed where completion cannot be verified, actual costs recorded late or lumped at month end, and an in-progress value chosen to flatter the trend. Pocket PMO checks the baseline (milestone values should sum to the budget) and the observations card surfaces pressure the narrative would rather hide, but the arithmetic is only ever as good as the milestone and cost discipline behind it.

Related planning pages

See it in Pocket PMO

Pocket PMO keeps project management techniques close to the rest of the project record so decisions can be based on consistent data.