Schedule Variance (SV) Calculator
Calculate Schedule Variance (SV) to quantify how far ahead or behind schedule your project is in monetary terms.
SV = EV − PVInterpretation Guide
- SV > 0Ahead of schedule.
- SV = 0On schedule.
- SV < 0Behind schedule.
Example
EV $80,000 and PV $100,000 → SV = −$20,000 (behind schedule by 20% of planned value).
Real-world use cases
- Weekly status reporting
- EVM dashboards
- Recovery planning
Common mistakes
- Confusing SV (in $) with schedule slip in days
- Ignoring critical-path while celebrating positive SV
Professional tips
- Pair SV with SPI for ratio context
- Always trend SV over time, not just absolute value
Frequently asked questions
Why is SV in dollars?
EVM measures schedule performance in budgeted cost of work, so SV is expressed in currency, not time.
What this tool does
Calculate Schedule Variance (SV) to quantify how far ahead or behind schedule your project is in monetary terms.
It applies the standard formula SV = EV − PV so planners, schedulers and PMOs get a defensible number they can put in front of a steering committee.
Looking for the underlying terminology? Open the PM Glossary or the PM Cheat Sheet for quick references on EVM, scheduling and risk terms.
When to use it
- Weekly status reporting
- EVM dashboards
- Recovery planning
Typical owners: project managers, planning engineers, project controls leads and PMO analysts running weekly or monthly performance reviews on EPC, infrastructure, IT and construction projects.
How to interpret the result
Treat the number as a signal, not a verdict. Read it together with the trend over the last 3–6 reporting periods, the critical-path status, and the risk register before you change the plan.
- Compare against the baseline, not against another project.
- Investigate the drivers behind the value before reporting it up.
- Pair it with at least one complementary KPI (cost, schedule, risk or quality).
Worked example
EV $80,000 and PV $100,000 → SV = −$20,000 (behind schedule by 20% of planned value).
In a real project review, document the inputs, the resulting value, the interpretation, and the corrective action you committed to. That audit trail is what turns a calculator output into a controls decision.
In-depth guide: Schedule Variance (SV) Calculator
Schedule Variance (SV) is the absolute, dollar-denominated companion to SPI. Where SPI is a ratio, SV is a magnitude: SV = EV − PV tells you how much budgeted work, in currency terms, your project is ahead or behind. The two metrics are mathematically linked — SPI = (EV/PV) and SV = EV − PV — but they answer different questions. SPI tells you the rate of slip; SV tells you the size of the gap.
On large programmes, SV is the number sponsors react to. A −$2M SV on a $50M project triggers a different conversation than a −$200k SV on a $5M project, even though both correspond to SPI = 0.96. That is why most enterprise PMO dashboards lead with SV in dollars and use SPI as the supporting ratio.
SV is also the basis for time-translation rules of thumb. Dividing SV by the average burn rate gives an approximate days-behind figure — useful for non-technical audiences, but not a substitute for Earned Schedule when accuracy matters.
When to use it (and when not to)
Use SV in dollar-sensitive contexts: change-control submissions, sponsor briefings, contract-claim notifications, and quarterly earnings reviews. It is also the right metric for trend charts because the absolute value makes the rate of change visible.
Avoid SV as the headline metric for projects with large planned-value front-loading or back-loading, because SV in those cases can be misleading without the underlying PV curve in view.
Related KPIs to read alongside
Pair SV with SPI (the ratio form), SV(t) from Earned Schedule (the time-based form), CV (the cost equivalent), and the float profile from the schedule. For programme-level reporting, also track the count of WBS elements with SV worse than −10% of their PV as a quality indicator.
Worked example — fibre-optic rollout programme
A fibre-optic rollout has BAC = $30M over 18 months. At the end of month 8, PV = $14.0M (47% of baseline), EV = $12.6M (42% earned).
SV = 12.6 − 14.0 = −$1.4M. That is roughly 5% of the project value behind plan — large enough to matter, not large enough to panic. SPI for the same period is 0.90, exactly on the warning threshold.
The PMO converts SV to time using the rolling 3-month burn: $1.4M ÷ $1.75M per month ≈ 0.8 months behind. The recovery plan adds one extra crew for two months at a cost of $480k drawn from contingency, with a target of returning SV to ±$300k by month 11.
Decision table
| Signal | What it means | Recommended action |
|---|---|---|
| SV ≥ 0 | On or ahead of plan in budgeted work. | Hold — audit EV to ensure no over-claiming. |
| −5% of PV ≤ SV < 0 | Mild slip, within normal variance. | Note in PMO log; monitor next period. |
| −10% of PV ≤ SV < −5% | Material slip. | Root-cause analysis; brief sponsor at next review. |
| SV < −10% of PV | Significant slip. | Formal recovery plan; consider rebaseline. |
Common pitfalls in the field
- Treating SV as days-behind. SV is in dollars, not days, and the conversion depends on the burn rate at the data date, not the project average. For accurate time-impact, use Earned Schedule SV(t).
- Reading SV without the underlying PV curve. A heavily front-loaded baseline can show large negative SV in early months that disappears naturally as the curve flattens — not a real performance issue.
- Reporting a positive SV as 'on track' without checking critical-path status. A project can be ahead in dollars and still slipping its end date if the work being accelerated is off the critical path.
Featured in Academy articles
This calculator is referenced in the FAQs of these Academy articles — read them to understand the theory behind the numbers.
Learn more on PMMilestone
Continue exploring
Upgrade to Enterprise-Level Project Intelligence
Discover the Elite Project Controls System — a professional intelligence framework for modern project controls, forecasting, executive reporting, AI PM workflows and risk management.
- ★Executive-grade KPI frameworks
- ★AI-powered project workflows
- ★Forecasting & risk intelligence
- ★PMO-ready reporting templates