Schedule Variance Calculator

Schedule Variance (SV) is a fundamental earned value management metric that tells you whether your project is ahead of, on, or behind schedule at any given point in time. It is one of the first indicators a project manager should check during performance monitoring, and it forms the backbone of schedule performance reporting in the PMBOK Guide's Monitor and Control Project Work process.

What makes SV so valuable is that it measures schedule performance in monetary terms rather than time units. This can feel counterintuitive at first. After all, how can a dollar amount tell you whether you are behind schedule? The answer lies in how Earned Value (EV) and Planned Value (PV) are calculated. PV represents the budgeted cost of work scheduled to be completed by now. EV represents the budgeted cost of work actually completed by now. If EV is less than PV, it means you have completed less work than planned, which translates directly into a schedule shortfall measured in budget dollars.

Schedule Variance should always be interpreted alongside the Schedule Performance Index (SPI). While SV gives you the absolute difference in dollar terms, SPI gives you the relative efficiency as a ratio. An SPI of 0.85 means you are progressing at 85% of the planned rate, regardless of the project size. Together, SV and SPI provide a complete picture of schedule health that is comparable across projects of different sizes and budgets.

EV (Earned Value) is the budgeted cost of work actually performed. It represents the value of the work you have completed, expressed in the same budget terms as your project baseline. If you planned to spend $100,000 on a deliverable and you have finished 60% of it, your EV is $60,000.

PV (Planned Value) is the budgeted cost of work scheduled. It represents the value of the work you should have completed by this point according to your project plan. If your project baseline allocates $80,000 of work to be completed by the end of month 3, then your PV at month 3 is $80,000.

Interpreting SV: A positive SV means the project is ahead of schedule (you have earned more value than planned). A negative SV means the project is behind schedule. An SV of zero means the project is exactly on schedule. The magnitude tells you how far ahead or behind in dollar terms.

Interpreting SPI: An SPI greater than 1.0 indicates ahead of schedule performance. An SPI equal to 1.0 is on schedule. An SPI less than 1.0 indicates behind schedule performance. For example, an SPI of 1.15 means you are completing work 15% faster than planned, while an SPI of 0.80 means you are progressing at only 80% of the planned rate.

1. Establish your Performance Measurement Baseline (PMB). Before you can measure variance, you need a baseline. Your PMB defines the planned value for each period of the project. Without a properly structured baseline with time-phased budget allocation, SV calculations are meaningless.

2. Measure work completed at each reporting period. Determine the percentage of work actually completed for each work package or activity. Use objective measures wherever possible, such as milestones reached, units produced, or deliverables accepted. Multiply the completion percentage by the budget to get EV.

3. Determine Planned Value for the reporting period. Look at your baseline to see how much budgeted work should have been completed by now. This is your PV. It comes directly from your schedule and cost baseline and does not change based on actual performance.

4. Calculate SV and SPI. Subtract PV from EV to get SV. Divide EV by PV to get SPI. These two numbers together tell you the complete story of your schedule performance.

5. Take corrective action if needed. If SPI falls below your organization's threshold (commonly 0.95), initiate corrective action. This may include schedule compression techniques like crashing or fast-tracking, resource reallocation, scope adjustment, or stakeholder communication about revised timelines.

• Confusing SV with a time-based measure: SV is expressed in the same units as your budget (dollars), not in days or weeks. A negative SV of -$50,000 does not mean the project is $50,000 worth of time behind. It means the work you have completed is worth $50,000 less than what you planned to complete.
• Ignoring critical path context: A positive SV does not necessarily mean everything is fine if the work completed is on non-critical activities while critical path work is delayed. Always cross-reference SV with critical path analysis.
• Not updating the baseline: If approved changes have modified the project scope or schedule, your PV calculations must reflect the updated baseline. Using an outdated baseline will produce misleading variance figures.
• Over-relying on SPI alone: SPI approaches 1.0 as the project nears completion regardless of actual performance, because all remaining EV is eventually earned. This creates a misleading impression of improvement. Track SV alongside SPI for a more accurate picture.
• Calculating SV at too high a level: Aggregated project-level SV can mask significant variances at the work package level. Always drill down into individual activities and work packages to identify the specific sources of schedule deviation.

Schedule Variance is a heavily tested topic on the PMP exam. According to the PMBOK Guide, SV and SPI are outputs of the Monitor Project Work process and inputs to the Control Schedule process. You must know the formulas cold: SV = EV - PV and SPI = EV / PV. The exam will present scenarios where you need to calculate these values from given EV and PV data.

Know the critical difference between SV and CV (Cost Variance). SV measures schedule performance while CV measures cost performance. A project can have a positive SV (ahead of schedule) but a negative CV (over budget), or vice versa. The exam frequently tests your ability to distinguish between these two metrics and interpret their combined meaning.

Also understand the forecasting formulas: Estimate at Completion (EAC), Estimate to Complete (ETC), and Variance at Completion (VAC). When SPI is below 1.0, the EAC formula EAC = BAC / SPI adjusts the completion estimate to reflect the current schedule efficiency. Be prepared to calculate and interpret these values in exam questions.