Every project manager has been there. You’re tracking progress, reviewing reports, and something feels off. The schedule says you’re on time, but the budget is bleeding. Or costs look fine, but deliverables are slipping. Without a structured way to measure these gaps, you’re flying blind.
That’s where variance analysis comes in. In earned value management, schedule variance (SV) and cost variance (CV) give you precise, data-driven insights into how your project is actually performing against the plan. They turn vague concerns into measurable deviations you can act on.
TL;DR
Variance analysis shows how far a project’s actual progress and costs differ from planned values. It enables data-driven corrective action before small issues escalate into major overruns or delays, giving you control when it matters most.
What Is Variance Analysis in Earned Value Management?
Variance analysis is the process of measuring and interpreting deviations from your project’s baseline across scope, schedule, and budget using earned value metrics.
Definition and Purpose of Variance Analysis
Earned value management relies on three core data points: what you planned to spend (Planned Value), what you’ve actually accomplished (Earned Value), and what you’ve actually spent (Actual Cost). Variance analysis takes these numbers and calculates the gap between plan and reality.
It answers two critical questions: Are we behind or ahead of schedule? Are we over or under budget?
These aren’t subjective assessments. They’re quantified using formulas that produce clear, comparable metrics you can track over time and present to stakeholders with confidence.
Why is Variance Analysis Important in Project Management
Variance analysis supports better decision-making in several ways:
- Forecasting accuracy: Early variance trends help you predict final costs and completion dates with greater precision.
- Stakeholder confidence: Clear, fact-based reporting replaces guesswork and builds trust in your project controls.
- Timely corrective action: Catching variances early means you can adjust resources, scope, or timelines before problems compound and recovery becomes expensive or impossible.
Key Variance Metrics in Earned Value Management
Two primary variance metrics reveal your project’s health: cost variance shows budget performance, and schedule variance shows timeline performance.
Cost Variance (CV)
Formula: CV = EV – AC
Cost variance tells you whether you’re spending more or less than the value you’ve earned. If CV is positive, you’re under budget. If it’s negative, you’re over budget.
Example: Your project has earned $80,000 worth of work (EV) but has actually spent $90,000 (AC). CV = $80,000 – $90,000 = –$10,000. You’re $10,000 over budget for the work completed so far.
Schedule Variance (SV)
Formula: SV = EV – PV
Schedule variance compares what you’ve earned against what you planned to earn by now. Positive SV means you’re ahead of schedule. Negative SV means you’re behind.
Example: You planned to complete $85,000 worth of work by today (PV), but you’ve only earned $70,000 (EV).
SV = $70,000 – $85,000 = –$15,000. Hence, you’re $15,000 worth of work behind schedule.
Cost Variance and Schedule Variance Combined Insight
CV and SV together provide early indicators of delivery and cost performance trends, helping you spot problems before they derail the project.
How to Calculate and Interpret Project Variances
Calculating variances is straightforward, but interpreting them requires context. Follow this step-by-step process to turn raw numbers into actionable project intelligence.
1. Gather the data
Start with three baseline metrics from your earned value system: Planned Value (PV), Earned Value (EV), and Actual Cost (AC). These should come from your project management software, timesheets, and financial tracking systems.
2. Compute CV and SV
Apply the formulas: CV = EV – AC and SV = EV – PV.
Use consistent units (dollars, hours, or story points) across all calculations.
3. Determine whether variances are favourable or unfavourable
Positive variances indicate better-than-planned performance. Negative variances signal trouble. Zero variance means you’re exactly on track, though this is rare in practice.
4. Analyse root causes
Don’t stop at the number. Ask why the variance exists. Common culprits include scope changes, productivity issues, inaccurate estimation, resource constraints, or external dependencies that shifted.
5. Calculate trend impact using CPI and SPI
Cost Performance Index (CPI) and Schedule Performance Index (SPI) convert variances into ratios, making it easier to confirm trends and compare performance across different project phases or workstreams.
Learn more about how SPI and CPI work together to provide complete performance visibility.
6. Present findings via variance charts or dashboards
Visualize CV and SV over time using line charts or cumulative variance graphs. Dashboards improve visibility for stakeholders and make variance trends easier to spot at a glance. Clear presentation drives faster, more informed decisions.
Understanding Positive vs Negative Project Variances
Variance signs tell you which direction performance is heading. Knowing how to respond to positive, negative, or neutral variances keeps your project adaptable and realistic.
Positive Variance
Indicates favourable performance. You’re either ahead of schedule or under budget. This doesn’t mean you relax. Investigate what’s driving the efficiency so you can sustain or replicate it across other work packages.
Negative Variance
Signals overruns or delays. Dig into the causes immediately. Look for scope creep, resource inefficiency, estimation errors, or external risks that weren’t accounted for in the baseline.
Zero Variance
Means you’re tracking exactly to plan. While this sounds ideal, it’s uncommon in real projects. If you see consistent zero variance, double-check your data collection methods. Perfect alignment often indicates measurement lag or reporting inaccuracy.
Variance trends matter more than single data points. A small negative variance in one reporting period might be normal noise. But three consecutive periods of worsening CV or SV? That’s a pattern requiring corrective action and stakeholder communication.
Integrating Variance Analysis with Performance Indices in Project Management
Variances reveal the size of the problem. Performance indices reveal the efficiency behind it. Used together, they paint a complete picture of project health.
Variance Analysis and SPI
Schedule Performance Index (SPI) uses the same data as schedule variance: SPI = EV / PV.
While SV tells you the dollar value of schedule deviation, SPI converts it into a ratio. An SPI of 0.85 means you’re earning 85 cents of planned value for every dollar scheduled.
This ratio format makes it easier to compare schedule efficiency across different projects or phases.
Variance Analysis and CPI
Cost Performance Index (CPI) measures cost efficiency: CPI = EV / AC.
If your CPI is 0.90, you’re getting 90 cents of value for every dollar spent. Combine CPI with CV for deeper insight.
CV shows the absolute cost overrun, while CPI shows whether your spending efficiency is improving or declining over time.
Interpretation
Use variance and index data together to trigger early risk discussions or re-forecast conversations. If CV is negative and CPI is trending down, you’re not just over budget, you’re becoming less efficient.
That’s a signal to reassess resourcing, scope, or timelines before costs spiral further.
For a detailed comparison of these metrics, see our guide on SPI vs CPI in earned value management.
Variance at Completion (VAC) and Forecasting
Variance at Completion extends current performance trends to predict final project outcomes, helping you communicate budget expectations and make proactive adjustments.
VAC Formula and Interpretation
Formula: VAC = BAC – EAC
Budget at Completion (BAC) is your original total budget. Estimate at Completion (EAC) is your revised forecast based on current performance. VAC shows the expected budget variance when the project finishes.
If VAC is positive, you expect to finish under budget. If VAC is negative, you’re forecasting an overrun.
VAC Example
Your project’s original budget (BAC) was $200,000. Based on current cost performance, you’ve recalculated your Estimate at Completion (EAC) to $220,000.
VAC = $200,000 – $220,000 = –$20,000
This means you expect a $20,000 overrun by project close. VAC gives stakeholders early visibility into final costs, letting them plan for additional funding, scope reduction, or acceptance of the variance based on business priorities and risk tolerance.
Understanding the relationship between BAC and EAC is critical for accurate variance forecasting.
Common Causes of Variance in Projects
Understanding why variances occur helps you prevent them in future projects and respond appropriately when they appear.
- Scope creep: Uncontrolled changes or additions to deliverables increase work without adjusting the baseline, creating negative cost and schedule variances.
- Resource inefficiency: Team members lacking skills, experience, or availability take longer and cost more than planned. Productivity assumptions that don’t match reality drive variances quickly.
- Incorrect estimation: Overly optimistic timelines or budgets set you up for negative variances from day one. Poor historical data or pressure to lowball estimates compounds the problem.
- Schedule compression: Fast-tracking or crashing the schedule often increases costs through overtime, expedited procurement, or rework from rushed decisions.
- External risks: Vendor delays, regulatory changes, or supply chain disruptions create variances outside your direct control but still impact performance metrics.
- Change management gaps: Approved changes that aren’t reflected in the baseline make variances look worse than reality. Always rebaseline after formal change approval to maintain measurement integrity.
Corrective Actions Based on Variance Insights
When variances signal trouble, respond with targeted corrective actions rather than hoping performance improves on its own.
- Re-baseline affected work packages after approved scope or schedule changes to restore measurement accuracy and stakeholder alignment.
- Reallocate resources from lower-priority tasks or bring in additional capacity to address schedule slippage or productivity gaps.
- Adjust scope or schedule buffers by negotiating reduced deliverables, extended timelines, or phased releases that protect critical path items.
- Conduct root-cause workshops with the team to identify systemic issues driving variances, such as unclear requirements or technical blockers.
- Communicate forecast changes transparently to sponsors and stakeholders early, presenting updated EAC, VAC, and recovery options with clear trade-offs and recommendations.
FAQs
What is the main goal of variance analysis in EVM?
The main goal is to quantify deviations from your project baseline so you can take corrective action early.
Variance analysis transforms vague concerns into measurable gaps in cost and schedule performance, enabling data-driven decisions before small issues become major problems.
How do CV and SV differ from CPI and SPI?
CV and SV measure absolute variance in dollar terms. CPI and SPI convert those variances into efficiency ratios. Variances show the size of the problem. Indices show the trend and allow easier comparison across projects or phases.
What indicates a healthy project variance?
Small variances close to zero with stable or improving trends indicate healthy performance. Consistent negative variances or worsening CPI/SPI ratios signal control issues requiring investigation and corrective action.
Can variances be positive but still risky?
Yes. Positive variances might indicate overly conservative estimates, underutilized resources, or scope cuts that weren’t communicated. Always investigate why performance exceeds expectations.
Key Takeaways
Cost variance (CV) shows whether you’re over or under budget. Schedule variance (SV) reveals if you’re ahead or behind timeline. Both rely on earned value data for precision and objectivity.
Combine variances with CPI and SPI for full visibility into project performance trends and efficiency patterns.
Regular variance analysis prevents budget overruns and schedule drift by catching problems early when corrective actions are still affordable and feasible.
Use VAC to forecast final outcomes and communicate expected variances to stakeholders with enough lead time for informed decision-making.
Earned Value Management Glossary
CV (Cost Variance): The difference between earned value and actual cost, indicating budget performance.
SV (Schedule Variance): The difference between earned value and planned value, indicating schedule performance.
VAC (Variance at Completion): The projected budget variance at project completion, calculated as BAC minus EAC.
EVM (Earned Value Management): A project management methodology that integrates scope, schedule, and cost to measure performance.
BAC (Budget at Completion): The total planned budget for the project.
EAC (Estimate at Completion): The revised forecast of total project cost based on current performance.
Track Your Project Performance in Real-Time
Calculate CV, SV, CPI, SPI, and VAC instantly with our interactive dashboard. Enter your task data and get automated variance analysis with visual performance charts.
For project managers preparing for PMP certification or looking to deepen their earned value expertise, the PMI Practice Standard for Earned Value Management provides comprehensive guidance on variance analysis and forecasting techniques.
![Tuyota Manuwa [SAFe, CSM, PSM, Agile PM, PRINCE2]](https://secure.gravatar.com/avatar/db5d7f9dcb30834fa1a2233afd2599baed692852fbfb7acddda0272c1a52bb7c?s=120&d=mm&r=g)
