How is schedule variance calculated in project management

TL;DR: Most articles on schedule variance hand you the formula and move on. This one shows IT company owners how to read the number in context, trace negative variance back to its actual cause, and choose a corrective action that fits the situation. You'll leave with a diagnostic approach you can apply to your next project review.

What is schedule variance in project management?

Schedule variance (SV) is the difference between the work your project has actually completed and the work you planned to complete by a given date, expressed in dollar terms.

The formula is simple: SV = Earned Value (EV) minus Planned Value (PV). A positive result means you're ahead of schedule. A negative result means you're behind. Zero means you're exactly on track. The number comes from earned value management (EVM), a project control framework that ties schedule performance directly to budget, so you're measuring progress in terms of work completed, not just time elapsed.

That distinction matters. A project can burn through 60% of its timeline and still only have 40% of deliverables done. Without EVM, that gap stays invisible until it's too late to recover. With SV, the shortfall shows up in the numbers before it shows up in a missed deadline.

SV sits inside a broader set of earned value management formulas that together give you a full picture of cost and schedule health. On its own, SV tells you the magnitude of a schedule problem. Paired with the Schedule Performance Index (SPI = EV / PV), it tells you the efficiency rate behind that problem.

The next section walks through the SV calculation using real IT project numbers.

How is schedule variance calculated?

The schedule variance formula comes from earned value management (EVM): SV = EV − PV, where EV is earned value (the budgeted cost of work actually completed) and PV is planned value (the budgeted cost of work scheduled by today).

Here is how to calculate it step by step.

1. Set your total budget and timeline: Your IT infrastructure migration has a total budget of $200,000 over 10 weeks.

2. Calculate planned value (PV): At the end of week 5, you planned to complete 50% of the work, so PV = $100,000.

3. Calculate earned value (EV): Your team has only finished 40% of the work by week 5, so EV = $80,000 (40% of $200,000).

4. Apply the schedule variance formula: SV = EV − PV = $80,000 − $100,000 = −$20,000.

That negative number means your project has completed $20,000 less work than planned at this point in the schedule. In project schedule tracking terms, you are two weeks of budgeted work behind.

One additional calculation worth running alongside SV is the Schedule Performance Index (SPI = EV / PV). In this example, SPI = 0.80, meaning the team is delivering 80 cents of planned work for every dollar of scheduled effort. SPI gives you a ratio; SV gives you a dollar amount. Both come from the same EVM inputs, so running them together takes seconds and gives you more context than either number alone. For a parallel calculation on the cost side, the same EVM logic applies to cost variance in project management.

The formula itself is straightforward. The harder part is knowing what the output means for your specific project, which depends on phase, buffer, and team velocity.

How to interpret your schedule variance number

A schedule variance number only tells you something useful once you know which direction it points and what's happening around it.

Positive SV (EV > PV) means your team has completed more work than planned for this period. That sounds good, but check whether the team pulled forward low-complexity tasks to hit milestones while harder work sits untouched. A positive number in week two of a twelve-week engagement can mask a rough final sprint.

Zero SV means planned and actual progress align exactly. In practice, this is rare enough that a perfect zero often signals estimation problems rather than perfect execution.

Negative SV means the project has delivered less value than planned. A small negative schedule variance, say within 5% of planned value, is usually recoverable with a schedule review. Once it crosses roughly -10% of planned value, most project governance frameworks treat that as a trigger for a formal corrective action plan.

Three context factors change how you read any SV figure:

• Project phase: Negative SV in the first 20% of a project is more alarming than the same number at 80% completion, where remaining scope is small.

• Buffer consumed: If your schedule reserve is already gone, even a small negative reading is urgent.

• Team velocity trend: A single bad sprint differs from three consecutive ones. For a deeper look at how earned value analysis fits into broader project control, the relationship between SV and velocity becomes clearer there.

Schedule variance vs schedule performance index

Both metrics come from earned value management, but they answer different questions.

Schedule variance tells you the dollar-denominated gap between work completed and work planned: SV = EV - PV. Schedule performance index (SPI) tells you your efficiency ratio: SPI = EV / PV. Same inputs, different outputs.

Use SV when you need to report the concrete cost of a delay to a stakeholder. Use SPI when you need to forecast completion dates or compare efficiency across projects of different sizes.

The two metrics work together. A project can show a small negative SV but a deteriorating SPI trend, which signals the gap is widening, not stabilizing. Tracking both inside a single earned value management workflow catches that pattern before it compounds.

Common causes of negative schedule variance in IT projects

Negative schedule variance rarely has a single cause. In IT projects, it tends to stack from a few predictable pressure points.

Scope additions mid-sprint are the most common trigger. A stakeholder approves "one small change" on day three of a two-week sprint, and the team absorbs the work without adjusting the baseline. Planned value stays fixed; earned value falls behind.

Blocked dependencies compound the problem fast. When Task B can't start until Task A ships, a one-day slip in Task A can cascade into a week of idle time downstream. Taro maps every task relationship so nothing ships out of order, which makes these bottlenecks visible before they become schedule variance.

Underestimated QA cycles are a quieter culprit. Development estimates rarely account for regression testing, bug triage, and re-deployment time. Teams consistently plan QA as a two-day phase and execute it in five.

Resource reassignment mid-project is the fourth pattern. A senior engineer pulled onto a critical client issue for three days doesn't just lose those three days — the context-switching cost adds another day or two of recovery.

For a deeper look at how these factors interact with earned value calculations, the earned value analysis guide for IT project managers covers the mechanics in full. Accurate project schedule tracking starts with knowing which of these four causes is driving your numbers.

How to use schedule variance to improve your project timeline

Once you have a negative schedule variance reading, the next move is corrective action, not just documentation. Here is a three-step workflow that turns the number into a decision.

Step 1: Quantify the gap using SPI alongside SV: The schedule variance formula (SV = EV - PV) tells you the dollar-denominated gap. The schedule performance index (SPI = EV / PV) tells you your efficiency rate. An SPI of 0.82 means you are completing 82 cents of planned work for every dollar of schedule consumed. Use both together: SV shows magnitude, SPI shows trajectory. If SPI is trending below 0.85 over two consecutive reporting periods, most teams treat that as the threshold for a formal corrective action plan.

Step 2: Trace the variance to a specific task dependency: Generic "we're behind" analysis wastes time. Pull your task dependency chain and find where completion stalled. Taro's dependency mapping surfaces blocked tasks and flags which downstream work is at risk, so you are diagnosing the actual bottleneck rather than the symptom.

Step 3: Reforecast and update your timeline: Adjust planned value for remaining work based on your current SPI. If you need to rebuild your schedule from a clean baseline, how to create a project timeline covers the sequencing logic. Taro's completion analysis then tracks whether the corrected plan is holding, giving you early warning before the next reporting cycle surfaces another negative SV.

Consistent project schedule tracking at this level turns schedule variance from a lagging indicator into a tool you act on weekly.

Frequently asked questions about schedule variance

What is schedule variance in project management? Schedule variance (SV) measures how far ahead or behind a project is relative to its planned timeline. The formula is SV = Earned Value (EV) minus Planned Value (PV). A positive result means you're ahead; a negative schedule variance means work is falling behind plan.

How is schedule variance calculated? Multiply the percentage of work completed by the total budget to get EV. Subtract PV, which is the budgeted cost of work scheduled to date. The difference is your SV. For a deeper walkthrough, earned value management formulas explained for IT project managers covers each variable with worked examples.

What is the difference between SV and the schedule performance index? SV gives you an absolute dollar gap. The schedule performance index (SPI = EV / PV) gives you a ratio. An SPI below 1.0 confirms the same delay SV flags, but as a rate — useful for forecasting how long recovery will take.

When does negative SV require a formal response? Most teams treat an SV below -10% of planned value as the threshold for a corrective action plan.

How does earned value analysis connect to schedule tracking? Earned value analysis in project management ties cost and schedule data into a single performance picture, so SV never sits in isolation.

Closing

Schedule variance only works when the data feeding it is live. A perfectly calculated SV based on last week's task status or estimated hours won't tell you what's actually happening right now—it'll tell you what you thought was happening seven days ago. That's why the diagnostic approach matters: you need current earned value, real-time task progress, and dependency visibility the moment work shifts. Taro keeps that data accurate in real time, so your SV reflects what is actually happening, not what was estimated three weeks ago. Your next project review will be sharper because your numbers will be. Ready to see how real-time data changes your schedule variance reading?

FAQ