Baseline and schedule variance

A baseline is the copy of a schedule's dates, work and cost saved when the plan is agreed, and schedule variance is how far the work has drifted from it, measured in days as finish variance or in earned value as earned value minus planned value.

Updated .

The rule

Save the baseline once the plan is agreed, before work starts. From then on the current dates move with progress and the baseline stays put, so the gap between them is the slip.

Finish variance counts that gap in working days: the current finish minus the baseline finish. A positive number is late.

Earned value counts it in money. Planned value (PV) is the budget of the work the baseline said would be done by the status date; earned value (EV) is the budget of the work actually done. Schedule variance (SV) is EV minus PV, and a negative number is behind. Divide by PV for a percentage.

Finish variance = current finish - baseline finish. SV = EV - PV. SV% = SV / PV.

Worked example

One task, "Fit out the second floor", baselined to run on days 11 to 30 (20 working days) with a budget of $40,000 spread evenly, $2,000 a day. The status date is the end of day 20, and the task is 40% complete.

The fit-out at the end of day 20, against its baseline
MeasureWorked outValue
Planned value (PV)10 baselined days to the status date x $2,000$20,000
Earned value (EV)40% of the $40,000 budget$16,000
Schedule variance (SV)EV - PV-$4,000
SV%SV / PV-20%
Forecast finishThe remaining 60% (12 days) at the planned rate, from day 21Day 32
Finish varianceDay 32 - day 30+2 days

Both measures say the same thing in different units: the task is two days of work behind its baseline. $4,000 of earned value at $2,000 a day is the two days the finish has moved.

What goes wrong in practice

  • No baseline saved, so there is nothing to measure the slip against, and checks such as DCMA's missed tasks and BEI cannot run.
  • Rebaselining every time the plan slips, so the variance is always zero and the slip disappears from the record.
  • Saving the baseline before the plan is finished, so tasks added later have no baselined dates.
  • Reading SV in money at the end of a late project: when the work is done, EV equals PV equals the budget, so SV is zero however late it finished. Finish variance still shows it.
  • Treating every variance alike: a late task with float does not move the finish, a late task on the critical path does.

See this in your own file

Open an .mpp or Project XML file with a baseline in the free viewer, tick View > Baseline to draw the baselined bars, and add Finish Variance from View > Columns and fields.

See the variance in your own file

Longer read: Schedule Variance: The EVM Formula and the Baseline Version

Questions

Why is schedule variance zero on a project that finished late?

Because SV is measured in money. When every task is done, earned value equals the full budget, and so does planned value, so SV is zero. Finish variance, measured in days, still shows how late it finished.

When should a plan be rebaselined?

When the scope or the agreed dates change through an approved change, not when the work runs late. Keep the old baseline as well, so the record shows both.