shell, house, framework, to build, construction site, work, construction work, housebuilding, unshrouded, building, completion, scaffolding, support, strive, bridge house project, bridge house, new-ulm, crane, construction crane, construction site, construction site, construction site, scaffolding, scaffolding, scaffolding, scaffolding, scaffolding
Photo by Hans on Pixabay

Budgets & Time

Part of Project reporting and delivery metrics

Comparing planned and actual delivery dates

Compare baseline, forecast and actual delivery dates using the same completion rule, and identify which baseline a variance uses.

Compare an actual finish against the agreed baseline for the same deliverable and completion rule. For unfinished work, compare the current forecast against that baseline and label the difference forecast variance. A forecast is not an actual delivery date.

Keep each date's purpose clear

Record the deliverable, its baseline finish, current forecast, actual finish and reporting date. State what counts as delivered. If acceptance is required, an uploaded file is not the actual finish unless the agreed rule says that upload completes delivery.

Date / Purpose

Baseline finish
Agreed reference for comparison
Current forecast
Latest expected finish while work is open
Actual finish
Date the agreed completion condition was met
Reporting date
Point at which the information was checked

Keep the original baseline identifiable. If an authorised change sets a revised baseline, label both versions and state which one the reported variance uses. A moved target should not erase the earlier comparison.

Calculate the variance

For completed work, subtract the chosen baseline finish from the actual finish. For open work, subtract it from the forecast finish. A positive number means later than that baseline; a negative number means earlier. State whether the calculation uses calendar or working days and which project calendar applies.

A deliverable with a baseline finish of 6 October and an accepted finish of 9 October in the same year finished three calendar days after that baseline. If acceptance was still pending on 9 October, that date could be a forecast or reporting date, but not an actual accepted finish.

Add the cause and consequence beside the number. An intermediate item can finish late without moving the final milestone. An item can appear on time because its scope changed. The variance alone does not explain either case.

Check the baseline used by the tool

In Microsoft Project, the Variance field compares planned and scheduled work using the Baseline and Work fields. It does not compare other baseline fields such as Baseline1 or Baseline2. This is a work variance, not a finish-date variance. Check which date field and baseline version your report uses.

Before distribution, compare a completed item, an open item and a changed item with their source records. Confirm their finish rules, dates and baseline versions.

Key Project Delivery Metrics in Australia

Project Calendar Used
Standard Australian Working Days (Mon–Fri, excluding public holidays)
Variance Type
Finish-date variance (not work variance)
Reporting Authority
Australian Project Management Institute (APM) guidelines

More from Budgets & Time