Once the activities and relationships in a construction schedule have been established, the next step is to calculate when the work can actually occur. In Critical Path Method scheduling, this analysis begins with the forward pass.

The forward pass moves through the network from left to right, calculating the earliest start (ES) and earliest finish (EF) for each activity. The basic formula is:

Early Finish = Early Start + Duration − 1

The subtraction of one matters. If an activity starts on Day 1 and lasts three working days, the crew works on Days 1, 2, and 3. The activity finishes on Day 3—not Day 4. Failing to account for inclusive working days can create small errors that compound across a complex schedule.

A Simple Generator-Yard Example

Consider the following sequence for a data-center generator yard:
| Activity | Early Start | Duration | Early Finish |
| — | — | — | — |
| Excavate generator yard | Day 1 | 4 days | Day 4 |
| Install underground duct banks | Day 5 | 6 days | Day 10 |
| Form and pour slab | Day 11 | 5 days | Day 15 |
| Deliver generators | Day 1 | 12 days | Day 12 |
| Set generators | Day 16 | 2 days | Day 17 |

The first three activities form one continuous path. Generator delivery follows a separate, parallel path and finishes on Day 12. The final activity—setting the generators—requires both paths to be complete. The slab is not ready until Day 15, so the generators cannot be set until Day 16, even though they arrived earlier.

This illustrates an essential forward-pass rule: when multiple paths merge, the successor’s early start is driven by the highest predecessor early finish.

The logic reflects physical reality. Equipment can arrive at the site, but it cannot be installed on an unfinished slab. The later prerequisite controls the start of the next activity.

Why Manual Understanding Still Matters

Scheduling software can perform these calculations across thousands of activities, but it does not understand what the numbers represent. Behind every duration is a crew, a piece of equipment, a delivery, a work area, or a physical constraint. The software calculates the network; the project team must validate whether the network represents the way the work will be performed.

A manual forward pass is therefore more than a classroom exercise. It helps schedulers understand how dates are generated, how parallel paths merge, and why one delayed prerequisite can control an entire sequence. It also makes the schedule easier to explain in the field. The superintendent should be able to see when the duct-bank crew is required, when the concrete must be ready, and when the crane needs to be mobilized.

The forward pass identifies the earliest possible dates for project activities. It shows how quickly the work could progress if the planned logic and durations hold. But it does not yet reveal how much flexibility each activity has or which sequence controls the project completion date.

For that, the analysis must move in the opposite direction.

The backward pass starts with the required project completion date and calculates the latest allowable start and finish dates for each activity. Comparing those dates with the forward-pass results reveals float—and ultimately identifies the activities that form the project’s critical path.

The forward pass tells us how early the project can finish. The backward pass tells us how late each activity can occur without affecting that finish date. Together, they turn a network of activities into a schedule the project team can manage.