Project Management KPI

Project Schedule Variance Formula

Learn what Project Schedule Variance means, how to calculate it in Excel, and how to recreate the same KPI as a Power BI DAX measure.

💡 Ideas for You

Resources related to this KPI and spreadsheet reporting.

4 useful links
📚 Step-by-step booksStart with beginner-friendly step-by-step books and learning resources from Create & Learn.📊 KPI dashboard resourcesBooks and templates for building project management KPI dashboards in spreadsheets.📈 Business metrics booksReferences for understanding project management metrics, definitions, and reporting habits.📘 Excel reporting guidesGuides for turning spreadsheet calculations into clear reports and dashboards.

Quick answer

Project Schedule Variance is calculated as:

Earned Value - Planned Value

Use this Excel version when your inputs are on row 2:

=B2 - C2
Example result4,000
FormatNumber
Typical chartKPI card for the latest value, plus a trend line over time.

What is Project Schedule Variance?

Project Schedule Variance is a Project Management KPI used to turn business activity into a clear number. It helps a project manager preparing a status report decide whether the project is on track or needs corrective action.

Project management KPIs compare plan versus actual work, cost, schedule, risks, and resource use.

Beginner tip: A KPI is not just a formula. It is a number used to make a decision. Before adding it to a dashboard, write down the definition, time period, owner, target, and data source.

Real-life example

Imagine a project manager preparing a status report. The team adds the inputs for Project Schedule Variance to a project status dashboard, calculates the KPI for the current month, and compares it with the previous month and target. In the sample below, the result is 4,000. That number becomes useful when everyone uses the same formula each month.

Excel cellInputWhat it meansSample value
B2Earned Valuethe input value used by the KPI formula$84,000
C2Planned Valuethe input value used by the KPI formula$80,000
ResultProject Schedule VarianceOutput of the KPI formula4,000

How to calculate Project Schedule Variance in Excel

  1. Create one row per reporting period, team, product, campaign, location, or customer segment.
  2. Add one input per column. Do not combine inputs in the same cell.
  3. Paste the Excel formula in the KPI result column.
  4. Format the result as Number.
  5. Copy the formula down the table and compare the result against target, previous period, and trend.
Quality check before publishing:
  • Use the same date range for every input.
  • Confirm that the denominator is not blank or zero.
  • Document whether the KPI is calculated before or after discounts, refunds, taxes, returns, or cancellations.
  • Keep the definition stable so reports remain comparable over time.

Power BI DAX measure

If you also report this KPI in Power BI, create a measure instead of hard-coding the calculation in a visual. Replace the measure names below with the names used in your model.

Project Schedule Variance = [Earned Value] - [Planned Value]

For best results, build base measures first, such as revenue, cost, customers, orders, or tickets, and then build the KPI measure from those base measures.

How to read the result

Higher is usually better, because this KPI normally represents revenue, efficiency, quality, retention, productivity, or successful outcomes.

Do not read the KPI alone. A single value can be misleading without a target, trend, segment, and business context. For example, the same result may be good for one product line but poor for another.

Useful comparisons

  • Current month versus previous month.
  • Actual result versus target or budget.
  • By channel, product, customer segment, team, or location.
  • Rolling average over several periods to smooth one-off spikes.

Common mistakes

  • Mixing time periods, such as monthly cost with quarterly revenue.
  • Using a total when the KPI should be segmented.
  • Changing the formula definition after the dashboard is already in use.
  • Comparing two teams that collect the inputs differently.
  • Ignoring blanks, zeros, refunds, cancellations, or duplicate records.