Schedule Variance vs. Schedule Forecast: What Is the Difference?

October 12, 2026 September 24, 2026

admino

What happened versus what is expected?

A project reports a negative schedule variance.

The sponsor asks:

“Does this mean the project will finish late?”

Not necessarily.

This is where PMP® scenarios often test whether you can distinguish earned-value schedule performance from schedule forecasting.

The key question is:

Is the scenario asking how current performance compares with the plan — or what the remaining work suggests about the future?

A useful Project Reasoning Lab principle is:

Variance tells you where you are relative to plan. Forecasting asks where the remaining work is likely to take you.

1. What Is Schedule Variance?

In earned value management:

SV = EV − PV

Where:

EV = Earned Value
PV = Planned Value

Interpretation:

SV > 0 → more earned value than planned at this point
SV = 0 → earned value equals planned value
SV < 0 → less earned value than planned

Suppose:

EV = $180,000
PV = $200,000

Then:

SV = $180,000 − $200,000 = −$20,000

The project has earned $20,000 less value than planned at the measurement point.

But an important caution follows:

Earned-value schedule variance is expressed in value terms, not calendar time.

An SV of −$20,000 does not mean the project is 20 days late.

Nor does it directly tell you when the project will finish.

2. What Is a Schedule Forecast?

A schedule forecast asks a different question:

Given what we know now, what is likely to happen next?

Forecasting may consider:

current schedule performance,
remaining work,
critical path,
float,
dependencies,
resource availability,
known risks and issues,
corrective actions,
updated duration estimates.

The distinction is:

Variance measures deviation. Forecasting estimates future outcome.

Or more practically:

Earned-value schedule variance shows how earned progress compares with planned progress. Forecasting combines current information with what remains to be done.

3. What Happened vs. What Is Expected?

Question	Schedule Variance	Schedule Forecast
Main question	How does earned progress compare with plan?	What is currently expected to happen?
Orientation	Current/past performance	Future
Based on	EV and PV	Current data + remaining work + schedule conditions
Directly gives final completion date?	No	May estimate future completion
Changes over time?	Yes	Yes

The two are related.

But they answer different questions.

4. Current Performance and Future Outlook Can Diverge

This is where many PMP scenario mistakes happen.

Scenario A: Negative SV, but Forecast Improving

Suppose:

A project has negative SV because an earlier activity finished later than planned. That delay has now been recovered, the remaining critical work is stable, and the current forecast still meets the required completion date.

The project is behind its earned-value plan at the measurement point.

But the future outlook may still support on-time completion.

So:

Behind plan is not automatically the same as forecast to finish late.

Scenario B: Positive SV, but Forecast Deteriorating

Now reverse the situation.

Suppose:

The project currently has positive SV, but a supplier warns that a critical component will arrive three weeks late.

Current performance looks favorable.

The future outlook may not.

So:

Good current performance does not guarantee a good future outcome.

That is why variance and forecast should not be treated as interchangeable.

5. Critical Path Still Matters

Consider:

A delayed activity contributes to negative earned-value schedule performance but has available float and does not affect the critical path.

The project may be behind plan at the measurement point without moving the final completion date.

Now consider:

A smaller delay occurs on a critical-path activity with no float.

That delay may have a much greater effect on project completion.

This is why forecasting should consider:

critical path,
float,
dependencies,
remaining durations,
schedule constraints.

A useful principle is:

Earned-value schedule performance does not replace critical-path analysis.

6. SV vs. SPI: Brief Clarification

Schedule Variance and Schedule Performance Index are closely related.

SV = EV − PV

SPI = EV ÷ PV

The distinction is:

SV gives the value-based difference,
SPI gives the performance ratio.

For example:

SPI > 1 → more earned value than planned
SPI = 1 → earned value matches plan
SPI < 1 → less earned value than planned

But neither metric directly tells you how many calendar days early or late the project will finish.

SV and SPI are earned-value performance indicators, not automatic completion-date forecasts.

7. Variance Is a Signal — Not the Cause

Suppose SV is negative.

What caused it?

The metric alone does not tell you.

Possible causes include:

resource constraints,
productivity problems,
delayed dependencies,
technical issues,
scope changes,
supplier delays,
external events.

This gives us a useful reasoning sequence:

Variance identifies the signal. Analysis identifies the cause. Forecasting considers what the signal and cause mean for the future.

That is more useful than reacting to the number alone.

8. Forecasting Should Reflect the Remaining Work

A weak forecast would say:

“We are behind now, so we will remain equally behind.”

That may be wrong.

Future performance may change because:

recovery actions are implemented,
resources change,
risks occur or are resolved,
the critical path shifts,
remaining work differs from completed work.

A better principle is:

A forecast should reflect what remains — not merely repeat what has already happened.

Ask:

What work remains?
What currently controls completion?
What known risks remain?
What corrective actions are active?
What assumptions have changed?

9. Interpret the Metric Only as Far as It Supports

Suppose the exam says:

“The project has an SPI of 0.92.”

That tells you current earned-value schedule performance is below plan.

It does not, by itself, establish:

the final completion date,
how many days late the project will be,
whether the critical path is delayed,
what caused the performance gap.

A strong PMP reasoning habit is:

Interpret the metric only as far as the metric supports.

Do not turn a measurement into a prediction without additional analysis.

10. Project Reasoning Lab: Four-Question Test

When a PMP scenario presents schedule-performance information, ask:

1. What is being measured?

Current performance or future outcome?

2. What does the metric actually tell me?

Interpret the result without adding assumptions.

3. What is driving the remaining schedule?

Consider:

critical path,
dependencies,
float,
remaining work,
known risks.

4. What does the current evidence suggest about the future?

Only then move from measurement to forecasting.

The reasoning sequence becomes:

Measure → Interpret → Forecast → Decide

11. Four Common PMP Traps

Trap 1: Negative SV = Project Will Finish Late

Not automatically.

Negative SV means earned progress is below planned progress at the measurement point.

Trap 2: Positive SV = Project Will Finish On Time

Not guaranteed.

Future critical work can still create delay.

Trap 3: SV Shows Calendar Days Ahead or Behind

No.

Earned-value SV is expressed in value terms.

Trap 4: Forecast = Current Variance Continued Into the Future

Too simplistic.

Forecasting should consider the remaining work and current schedule conditions.

Final Takeaway

When a PMP scenario gives schedule-performance data, first ask:

What happened relative to the plan?

Then ask:

What does that mean for the work that remains?

Schedule variance and schedule forecasting are related, but they answer different questions.

Earned-value schedule variance tells you how earned progress compares with planned progress at the measurement point. Schedule forecasting asks where the remaining work is likely to take the project.

The broader Project Reasoning Lab principle is: