What's the difference between forward pass and backward pass?

The forward pass walks from start to finish to compute Early Start and Early Finish (the earliest each activity can happen). The backward pass walks from finish to start to compute Late Start and Late Finish (the latest each activity can happen without delaying the project). The difference between Early and Late dates is total float.

Do I really need to know this if P6 calculates it automatically?

Yes. The tool calculates whatever you give it. Bad logic, wrong calendars, or hidden constraints produce a confident but wrong forward pass. Understanding the calculation is what lets you spot when the schedule is lying to you.

How do constraints affect the forward pass?

Hard constraints (must finish on, mandatory start) override the calculated dates. They can mask negative float and hide real delays. Best practice is to limit hard constraints to genuine contractual dates and use soft constraints (start no earlier than) sparingly.

What is an 'open end' and why is it bad?

An open end is an activity with no successor (or no predecessor at the start). It breaks the forward-pass chain and creates phantom float. DCMA-14 fails any schedule with more than 5% open ends.

How does the calendar affect the forward pass?

Durations are interpreted through the assigned calendar. A 10-day activity on a 5-day calendar with a holiday week takes 17 calendar days to finish. Mismatched calendars between predecessor and successor produce ES/EF jumps that confuse stakeholders unless explained.

Should I include weather days in the forward pass?

Yes — either via the calendar (preferred for known seasonal patterns) or as discrete weather contingency activities. Hiding weather in unrealistic durations destroys the forward pass's predictive value.

How often should we run the forward pass on a live project?

Every schedule update — typically weekly on construction, every sprint or PI on agile programmes. After each run, compare with the previous update to spot unexplained drift.

What's the most common error in forward-pass calculation?

Wrong relationship type. Schedulers default to Finish-to-Start when the physical reality is Start-to-Start with lag, or Finish-to-Finish. The forward pass faithfully calculates whatever you tell it, which is why logic discipline matters more than the math.

Which calculators on PMMilestone.org apply to Forward Pass Scheduling?

For Forward Pass Scheduling, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Forward Pass Scheduling?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Forward Pass Scheduling?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Forward Pass Scheduling?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Forward Pass Scheduling is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Forward Pass Scheduling defined on PMMilestone Research & Insights?

The CPM calculation that walks the network from project start to finish to determine the Early Start and Early Finish of every activity, establishing the earliest the project can possibly complete. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

What's the difference between forward pass and backward pass?

The forward pass walks from start to finish to compute Early Start and Early Finish (the earliest each activity can happen). The backward pass walks from finish to start to compute Late Start and Late Finish (the latest each activity can happen without delaying the project). The difference between Early and Late dates is total float.

Do I really need to know this if P6 calculates it automatically?

Yes. The tool calculates whatever you give it. Bad logic, wrong calendars, or hidden constraints produce a confident but wrong forward pass. Understanding the calculation is what lets you spot when the schedule is lying to you.

How do constraints affect the forward pass?

Hard constraints (must finish on, mandatory start) override the calculated dates. They can mask negative float and hide real delays. Best practice is to limit hard constraints to genuine contractual dates and use soft constraints (start no earlier than) sparingly.

What is an 'open end' and why is it bad?

An open end is an activity with no successor (or no predecessor at the start). It breaks the forward-pass chain and creates phantom float. DCMA-14 fails any schedule with more than 5% open ends.

How does the calendar affect the forward pass?

Durations are interpreted through the assigned calendar. A 10-day activity on a 5-day calendar with a holiday week takes 17 calendar days to finish. Mismatched calendars between predecessor and successor produce ES/EF jumps that confuse stakeholders unless explained.

Should I include weather days in the forward pass?

Yes — either via the calendar (preferred for known seasonal patterns) or as discrete weather contingency activities. Hiding weather in unrealistic durations destroys the forward pass's predictive value.

How often should we run the forward pass on a live project?

Every schedule update — typically weekly on construction, every sprint or PI on agile programmes. After each run, compare with the previous update to spot unexplained drift.

What's the most common error in forward-pass calculation?

Wrong relationship type. Schedulers default to Finish-to-Start when the physical reality is Start-to-Start with lag, or Finish-to-Finish. The forward pass faithfully calculates whatever you tell it, which is why logic discipline matters more than the math.

Which calculators on PMMilestone.org apply to Forward Pass Scheduling?

For Forward Pass Scheduling, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Forward Pass Scheduling?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Forward Pass Scheduling?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Forward Pass Scheduling?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Forward Pass Scheduling is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Forward Pass Scheduling defined on PMMilestone Research & Insights?

The CPM calculation that walks the network from project start to finish to determine the Early Start and Early Finish of every activity, establishing the earliest the project can possibly complete. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Schedule · Letter F

Forward Pass Scheduling

The CPM calculation that walks the network from project start to finish to determine the Early Start and Early Finish of every activity, establishing the earliest the project can possibly complete.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-23

Definition

The forward pass is the half of the Critical Path Method calculation that walks the schedule network from the project's start date through to its finish, deriving the Early Start (ES) and Early Finish (EF) of every activity. Combined with the backward pass (which produces Late Start and Late Finish), it determines total float and identifies the critical path. If the forward pass is wrong — bad logic, missed lag, sloppy calendar — every downstream number, including the contractual completion date, is wrong.

The Calculation in Plain English

You start at the project's data date. For each activity, ES = the latest EF of all its predecessors (respecting lags and relationship type), and EF = ES + duration. You repeat across the network until every activity has been visited. The largest EF in the network is the project's earliest possible completion. It sounds trivial; in a 12,000-activity refinery turnaround with hundreds of constraints, it is anything but.

Why Schedulers Still Need to Understand It

Primavera P6 and Microsoft Project run the forward pass for you in milliseconds. The reason competent schedulers still learn to do it by hand on a 15-activity network is that the tool will calculate whatever you give it. If your relationship is wrong, the EF is wrong. If the calendar is wrong, the EF is wrong. The forward pass discipline trains your eye to spot logic that doesn't make physical sense — and that judgement is the difference between a schedule and a wishlist.

Real-World Construction Example

On a 22-storey tower I audited, the contractor's forward pass showed structural topping-out on week 41. Walking the logic by hand exposed three issues: a missing FS lag between core slip-form pour and post-tension stressing, a calendar that ignored monsoon shutdowns, and a redundant SS relationship that compressed the slab cycle artificially. Once corrected, the forward pass produced week 47 — six weeks later — which matched what the site team had been quietly telling everyone for two months. The numbers had been lying because the inputs were lying.

Real-World IT / Agile Example

Agile teams rarely "do" a forward pass on a sprint, but they do it constantly at the release-train level. On a banking platform migration with 14 squads, the release plan was effectively a network: data-model freeze → API contracts → squad implementation → integration → UAT → cutover. We modelled it as a CPM network and ran the forward pass. It surfaced that the API-contract activity was a bottleneck no one was tracking; pulling it forward by two weeks shortened the whole programme by ten. PI planning boards rarely surface this; a forward pass does.

Project Controls Perspective

Controls teams treat the forward pass as the integrity test of a schedule submission. We re-run it after every update with the relationships and calendars frozen, and compare ES/EF deltas activity-by-activity. Unexplained deltas usually mean either a hidden logic change or a constraint that was added without a change request. The DCMA-14 schedule health checks (which most defence and infrastructure clients require) are essentially a structured audit of forward-pass integrity.

Common Mistakes

Constraints masking logic. Hard "must finish on" dates override the forward pass and hide real float problems.
Calendar mismatches. An activity on a 5-day calendar feeding one on a 7-day calendar produces ES/EF jumps that aren't intuitive.
Open ends. Activities with no successor short-circuit the forward pass — DCMA flags more than 5% open ends as a failure.
Lag abuse. Long FS lags used as substitutes for real activities; the forward pass treats them as free time, but the site team can't.
Ignoring resource calendars. Especially for shutdowns, holidays and shift patterns — the forward pass uses whatever calendar you assign.

Expert Tips

Do one by hand each quarter. Pick a 20-activity slice of your live schedule and walk the forward pass on paper. It will keep your judgement sharp and routinely surface logic flaws the tool accepted.
Lock the data date. Forward pass results change with the data date; comparing two updates means freezing it consistently.
Audit lags ruthlessly. Any FS lag over 5 days deserves a note in the basis-of-schedule explaining the physical reason.
Inspect successors of milestones. Project finish milestones with multiple driving predecessors are where forward-pass surprises hide.
Re-run after every constraint change. Constraints distort the pass; treat each one as a small contractual decision.

Key Takeaways

The forward pass produces Early Start and Early Finish; together with the backward pass it produces float and the critical path.
Tools run it instantly; the discipline is in the inputs — logic, lags, calendars, constraints.
Most "schedule slips" are forward-pass surprises caused by bad logic discovered late.
DCMA-14 health checks are largely a structured audit of forward-pass integrity.
Doing one by hand each quarter is the best investment a scheduler can make in their judgement.

Related Encyclopedia Entries

Critical Path Method — companion entry on a directly related concept.
Float Management — companion entry on a directly related concept.
Network Diagram — companion entry on a directly related concept.
Baseline Schedule — companion entry on a directly related concept.
Time Impact Analysis — companion entry on a directly related concept.
Integrated Master Schedule — companion entry on a directly related concept.

Frequently Asked Questions

What's the difference between forward pass and backward pass?
The forward pass walks from start to finish to compute Early Start and Early Finish (the earliest each activity can happen). The backward pass walks from finish to start to compute Late Start and Late Finish (the latest each activity can happen without delaying the project). The difference between Early and Late dates is total float.
Do I really need to know this if P6 calculates it automatically?
Yes. The tool calculates whatever you give it. Bad logic, wrong calendars, or hidden constraints produce a confident but wrong forward pass. Understanding the calculation is what lets you spot when the schedule is lying to you.
How do constraints affect the forward pass?
Hard constraints (must finish on, mandatory start) override the calculated dates. They can mask negative float and hide real delays. Best practice is to limit hard constraints to genuine contractual dates and use soft constraints (start no earlier than) sparingly.
What is an 'open end' and why is it bad?
An open end is an activity with no successor (or no predecessor at the start). It breaks the forward-pass chain and creates phantom float. DCMA-14 fails any schedule with more than 5% open ends.
How does the calendar affect the forward pass?
Durations are interpreted through the assigned calendar. A 10-day activity on a 5-day calendar with a holiday week takes 17 calendar days to finish. Mismatched calendars between predecessor and successor produce ES/EF jumps that confuse stakeholders unless explained.
Should I include weather days in the forward pass?
Yes — either via the calendar (preferred for known seasonal patterns) or as discrete weather contingency activities. Hiding weather in unrealistic durations destroys the forward pass's predictive value.
How often should we run the forward pass on a live project?
Every schedule update — typically weekly on construction, every sprint or PI on agile programmes. After each run, compare with the previous update to spot unexplained drift.
What's the most common error in forward-pass calculation?
Wrong relationship type. Schedulers default to Finish-to-Start when the physical reality is Start-to-Start with lag, or Finish-to-Finish. The forward pass faithfully calculates whatever you tell it, which is why logic discipline matters more than the math.
Which calculators on PMMilestone.org apply to Forward Pass Scheduling?
For Forward Pass Scheduling, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Forward Pass Scheduling?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Forward Pass Scheduling?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Forward Pass Scheduling?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Forward Pass Scheduling is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Forward Pass Scheduling defined on PMMilestone Research & Insights?
The CPM calculation that walks the network from project start to finish to determine the Early Start and Early Finish of every activity, establishing the earliest the project can possibly complete. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Forward Pass Scheduling →