Schedule Variance Formula & Examples: Calculate SV in Project Management

Project managers juggle many responsibilities—from scheduling and budgeting to managing people and technology. One of their core duties is ensuring work is completed on time and within budget. But how can you tell if a project is tracking as expected? A simple calculation, schedule variance (SV), shows whether actual progress matches your plan.

Schedule variance measures the difference between the earned value of completed work and the planned value of work that should have been completed at a given point in time.

In earned value management, these values are expressed in monetary units rather than hours, making them easier to compare. A positive SV means you’re ahead of schedule; a negative SV means you’re behind. This objective metric enables project managers to identify issues early, communicate clearly with stakeholders, and make informed decisions.

Why Schedule Variance Matters

Schedule variance shows how far a project drifts from its planned timeline. It gives the project team early warning before delays worsen. Falling behind schedule does more than delay a project. It can erode trust, raise costs, and derail business goals. When deadlines slip, clients worry, and teams rush, which leads to more errors.

Data proves how serious this is. A recent study reviewed 321,042 construction activities. It found that schedule variances tied to poor handoffs caused the most delays. These issues led to 168,000 reported problems. Staffing gaps added another 65,000 variances. Material and equipment issues created 44,000 more delays. Minor problems, such as poor communication or late deliveries, accumulated over time.

As projects grow larger and spread across countries, schedule control matters more than ever. Tracking schedule variance helps managers act early, fix root causes, and keep projects aligned with business goals.

Key Terms: BCWS and BCWP

Two earned value metrics form the foundation for schedule variance:

• Budgeted Cost of Work Scheduled (BCWS) – often called planned value. This is the monetary value of work that should have been completed by a specific date per the project schedule. To calculate BCWS:
• Define the budget at completion (BAC)—the total budget for the entire project.
• Break down the project scope into tasks using a work breakdown structure.
• Estimate the cost and duration of each task.
• Sum the planned costs of tasks expected to be completed by the reporting date.
• Budgeted Cost of Work Performed (BCWP) – also known as earned value. This represents the monetary value of work completed as of the reporting date. To calculate BCWP, you assess the percentage of each task that is finished and multiply it by the task’s budgeted cost.

These two metrics allow you to quantify progress in dollars, which simplifies comparisons and decision-making.

How to Calculate Schedule Variance

Schedule variance is found by subtracting the planned value (BCWS) from the earned value (BCWP):

SV=BCWP-BCWS

SV=EV-PV

The result is expressed in the same monetary units used for BCWP and BCWS. A positive SV means the project is ahead of schedule because more value has been earned than planned. A negative SV means the project is behind schedule because less value has been earned than planned. A zero value indicates that the project is exactly on schedule.

Below is a visual summary of the formula:

Schedule Variance Examples

Let’s see two examples of schedule variance.

Example #1

For a project, the earned value is 40,000, and the planned value is 45,000 USD. Calculate the schedule variance.

SV = EV – PV

= 40,000 – 45,000

= –5,000 USD

Since the SV is negative, the project is behind schedule.

Example #2

For a project, the earned value is 45,000, and the planned value is 40,000 USD. Calculate the schedule variance.

SV = EV – AC

= 45,000 – 40,000

= 5,000 USD

Since the SV is positive, the project is ahead of schedule.

Interpreting Schedule Variance

Schedule variance helps you measure project performance, but it’s not the only measure you should consider. A negative SV doesn’t automatically mean failure—it signals that corrective action may be needed. You might re-allocate resources, adjust the scope, or identify and remove roadblocks. Conversely, a positive SV could mean tasks are being completed faster than planned, but it might also indicate under-estimated workloads or scope creep. 

Pairing schedule variance with other EVM metrics, such as the schedule performance index (SPI) or cost variance (CV), provides a more complete picture.

Schedule Variance Vs Project Variance and SPI

• Project variance refers to the gap between planned and actual performance across multiple dimensions: schedule, cost, scope, and quality. Schedule variance is one component of this broader concept.
• Schedule performance index (SPI) is a ratio that complements schedule variance. It is calculated by dividing earned value by planned value: SPI = BCWP / BCWS. An SPI greater than 1 indicates you’re ahead of schedule; less than 1 indicates you’re behind.

Both metrics belong to the family of earned value indicators. While SV provides a dollar figure, SPI offers a relative rate, making it easier to compare projects of different sizes.

Common Causes of Schedule Variance

Why do projects fall behind despite careful planning? The construction study mentioned earlier reveals some of the most frequent culprits:

• Handoffs: Poorly executed handoffs between teams or disciplines were the number one cause of delays, resulting in numerousissues. When one trade finishes late, the next cannot start on time.
• Staffing problems: Labour shortages and crew misalignment caused schedule variances. When the right people aren’t available, tasks slip.
• Material and equipment issues: Late deliveries or equipment unavailability also cause delays. Long lead times for specialized components can stall progress.
• Design changes: Modifications during execution require rework, which ripples through the schedule.
• Weather: Unexpected storms or extreme temperatures can halt work on site, especially in construction and infrastructure projects.

Understanding these causes helps managers implement preventive measures—such as improving handoff processes, securing resources early, and building contingency time into the schedule.

Tips for Reducing Schedule Variance

While variances will always occur, proactive steps can minimize their impact:

• Plan Thoroughly: Develop a detailed work breakdown structure, assign realistic durations and budgets, and account for dependencies.
• Involve Stakeholders Early: Clear requirements and communication reduce the likelihood of design changes late in the lifecycle.
• Build Buffers: Include contingency time and budget for high-risk activities; these buffers absorb unavoidable delays, such as weather.
• Monitor Frequently: Use software to track progress daily or weekly so you can respond to emerging issues quickly.
• Manage Resources Carefully: Ensure that skilled personnel, materials, and equipment are available when needed; adjust resource allocations as the project evolves.
• Learn from Past Projects: Conduct post-mortems to identify recurring sources of variance and implement process improvements.

FAQs

Q1. What is schedule variance in project management?

Schedule variance is the difference between the earned value of completed work and the planned value of work that should have been completed at a given point in time.

Q2. How do you quickly calculate schedule variance?

Subtract the budgeted cost of work scheduled (BCWS) from the budgeted cost of work performed (BCWP). A positive result means you’re ahead of schedule; a negative result means you’re behind.

Q3. Why is schedule variance important?

It provides an objective measure of schedule performance, allowing managers to detect delays early and take corrective action before they snowball into bigger problems.

Q4. How is schedule variance different from cost variance?

Schedule variance compares planned and earned value over time; cost variance compares budgeted and actual costs. Both are essential earned value metrics.

Q5. When should I use the schedule performance index instead?

Use the SPI when you need a relative measure of schedule efficiency. SPI divides earned value by planned value, making it easier to compare across projects of different sizes.

Q6. Can schedule variance be positive?

Yes. A positive SV indicates work is completed ahead of schedule. Ensure the speed doesn’t compromise quality or lead to cost overruns.

Summary

Schedule variance helps you determine whether your project is ahead, on track, or behind schedule. By comparing planned work with completed work, you can identify issues early and respond quickly. When you review schedule variance often, you gain better control over time, costs, and team effort. This simple metric supports smarter decisions and more transparent communication with stakeholders. When used alongside other earned value measures, schedule variance becomes a powerful tool for keeping projects predictable, focused, and successful.

Further Reading:

• What is Earned Value Management?
• What are EV, PV, and AC?
• What is Cost Variance?
• What is SPI?
• What is CPI?

References:

• The Practical Calculation of Schedule Variance in Terms of Schedule
• The Limits of the Linear Approach to Schedule Variance

This topic is important from a PMP exam point of view.