Forward and Backward Pass Calculations

Why Forward and Backward Pass Calculations Matter

Forward and backward pass calculations are the mathematical engine behind the Critical Path Method (CPM), which is the dominant scheduling technique in construction. Every CPM schedule you will ever review as a Construction Manager, whether a baseline, a monthly update, or a time impact analysis supporting a delay claim, is built on these two passes. If you cannot perform them by hand, you cannot independently verify a contractor's schedule, challenge a float calculation, or confirm that a claimed delay actually sits on the critical path.

For the CCM exam, this topic lives in the Time Management domain and is one of the most predictable sources of calculation questions. Examiners like it because it has a single correct answer, it tests understanding of logic rather than memorization, and it reveals whether a candidate truly understands float, criticality, and schedule sequencing. In practice, a CM who understands the passes can explain to an owner why a two-week delay to one activity did not move the completion date, or why a three-day delay to another activity did.

What the Forward and Backward Passes Are

A CPM network is a set of activities, each with a duration, connected by logic relationships that define which activities must precede others. The forward and backward passes are the two sequential calculations that turn that network into a schedule with dates and float.

The Forward Pass works from the start of the project to the end. It calculates, for every activity:
• Early Start (ES): the earliest an activity can begin, given that all of its predecessors have finished as early as possible.
• Early Finish (EF): the earliest an activity can finish, which is simply its Early Start plus its duration.
The forward pass answers the question: How soon can everything happen? The largest Early Finish in the network is the earliest possible project completion date.

The Backward Pass works from the end of the project back to the start. It calculates, for every activity:
• Late Finish (LF): the latest an activity can finish without delaying the project completion date.
• Late Start (LS): the latest an activity can start without delaying the project, which is its Late Finish minus its duration.
The backward pass answers the question: How late can everything happen without hurting the finish date?

Once both passes are complete, the difference between the early and late dates for each activity is its Total Float. Activities with zero total float are critical, and the continuous chain of these activities from start to finish is the critical path.

How the Calculations Work: Step by Step

Step 1: Understand the Two Date Conventions. Before computing anything, identify which convention the question uses, because it changes every number.
• Zero-based (end-of-day or elapsed time) convention: The project starts at time 0. EF = ES + Duration. ES of a successor = EF of its predecessor. This is the convention most commonly used in CCM study materials and hand calculations.
• One-based (calendar day or start-of-day) convention: The project starts on Day 1. EF = ES + Duration − 1. ES of a successor = EF of its predecessor + 1. Scheduling software typically displays dates this way.
If the question does not state a convention, look at the answer choices and the given data; a project that starts at Day 0 is a strong signal of the zero-based method.

Step 2: Perform the Forward Pass.
• Set the ES of the first activity (or activities) to 0.
• EF = ES + Duration.
• For any activity with more than one predecessor, its ES is the maximum (latest) EF of all its predecessors. This is the single most important rule of the forward pass: an activity cannot start until all of its predecessors are finished.
• Continue until every activity has an ES and EF. The highest EF is the project duration.

Step 3: Perform the Backward Pass.
• Set the LF of the final activity (or activities) equal to the project completion date found in the forward pass (unless the question imposes a different contractual completion date, which is discussed below).
• LS = LF − Duration.
• For any activity with more than one successor, its LF is the minimum (earliest) LS of all its successors. This is the mirror-image rule of the backward pass: an activity must finish early enough to allow every one of its successors to start on time.
• Continue until every activity has an LS and LF.

Step 4: Calculate Float.
• Total Float (TF) = LS − ES, which is identical to LF − EF. Total float is the amount of time an activity can be delayed without delaying the project completion date. It is shared along a path; if one activity uses it, downstream activities on the same path lose it.
• Free Float (FF) = (earliest ES of all immediate successors) − EF of the activity. Free float is the amount an activity can be delayed without delaying the early start of any successor. Free float is never greater than total float.
• Activities with TF = 0 are critical. The critical path is the longest path through the network and has the least float.

Step 5: Identify the Critical Path. Trace the continuous chain of zero-float activities from project start to project finish. There can be more than one critical path, and the critical path can change as the project progresses.

A Fully Worked Example

Consider a six-activity network using the zero-based convention and finish-to-start logic:
• Activity A, 3 days, no predecessors
• Activity B, 4 days, predecessor A
• Activity C, 2 days, predecessor A
• Activity D, 5 days, predecessor B
• Activity E, 3 days, predecessor C
• Activity F, 2 days, predecessors D and E

Forward Pass:
• A: ES = 0, EF = 0 + 3 = 3
• B: ES = 3 (EF of A), EF = 3 + 4 = 7
• C: ES = 3 (EF of A), EF = 3 + 2 = 5
• D: ES = 7 (EF of B), EF = 7 + 5 = 12
• E: ES = 5 (EF of C), EF = 5 + 3 = 8
• F: ES = max(12, 8) = 12, EF = 12 + 2 = 14
Project duration = 14 days.

Backward Pass:
• F: LF = 14, LS = 14 − 2 = 12
• D: LF = 12 (LS of F), LS = 12 − 5 = 7
• E: LF = 12 (LS of F), LS = 12 − 3 = 9
• B: LF = 7 (LS of D), LS = 7 − 4 = 3
• C: LF = 9 (LS of E), LS = 9 − 2 = 7
• A: LF = min(3, 7) = 3, LS = 3 − 3 = 0

Total Float (LS − ES):
• A: 0 − 0 = 0 (critical)
• B: 3 − 3 = 0 (critical)
• C: 7 − 3 = 4
• D: 7 − 7 = 0 (critical)
• E: 9 − 5 = 4
• F: 12 − 12 = 0 (critical)

Free Float:
• C: ES of E (5) − EF of C (5) = 0. Notice that C has 4 days of total float but zero free float; any delay to C immediately pushes E, even though it does not push the project.
• E: ES of F (12) − EF of E (8) = 4. E has 4 days of both total and free float because it feeds directly into the merge point.

Critical Path: A → B → D → F, 14 days. The path A → C → E → F takes only 10 days and therefore carries 4 days of float.

Important Variations You Must Be Ready For

1. Precedence Diagramming Method (PDM) relationships. Modern schedules use four relationship types. In the forward pass:
• Finish-to-Start (FS): Successor ES = Predecessor EF + lag
• Start-to-Start (SS): Successor ES = Predecessor ES + lag
• Finish-to-Finish (FF): Successor EF = Predecessor EF + lag (then back-calculate ES)
• Start-to-Finish (SF): Successor EF = Predecessor ES + lag (rare)
In the backward pass, the relationships are reversed. If an exam question gives you SS or FF logic, slow down and apply the correct formula rather than defaulting to FS.

2. Lags and leads. A lag adds time to the relationship (FS with 2-day lag means the successor starts 2 days after the predecessor finishes). A lead is a negative lag (the successor can start before the predecessor finishes). Add lags in the forward pass; subtract them in the backward pass.

3. Negative float. If the backward pass starts from a contractual completion date that is earlier than the forward-pass completion date, activities on the longest path will show negative total float. Negative float means the schedule is behind and the project cannot meet the required date without acceleration or logic changes. Exam questions sometimes test this by giving you a required finish date rather than letting the forward pass define it.

4. Constraints. Hard constraints such as Must-Finish-On or Start-No-Earlier-Than dates override calculated dates and can create or hide float. If a question mentions a constraint, apply it before completing the pass.

5. Multiple start or finish activities. If several activities have no predecessors, each starts at ES = 0. If several activities have no successors, each has LF equal to the project completion date (the maximum EF in the network), unless a specified completion date is given.

6. Float ownership. Although not a calculation issue, the CCM exam frequently connects float to contract administration. Unless the contract states otherwise, float is generally treated as a shared project resource, available to whoever uses it first. Know your contract language.

Exam Tips: Answering Questions on Forward and Backward Pass Calculations

Tip 1: Draw the network every time. Even for a six-activity problem, sketch nodes with a standard box layout: ES and EF on top, LS and LF on the bottom, duration and activity name in the middle. A clean diagram prevents the most common error, which is reading the wrong number into the next calculation.

Tip 2: Confirm the convention before you write a single number. Decide whether the problem is zero-based (EF = ES + D) or one-based (EF = ES + D − 1). If answer choices differ by exactly one day, the convention is the trap.

Tip 3: Maximum on the way forward, minimum on the way back. Burn this into memory. At every merge point in the forward pass, take the largest predecessor EF. At every burst point in the backward pass, take the smallest successor LS. Reversing these is the second most common error.

Tip 4: Verify your critical path with two checks. First, every activity on the path must have zero total float (or equal minimum float). Second, the sum of durations along the path must equal the project duration from the forward pass. If either check fails, recalculate.

Tip 5: Do not confuse total float with free float. If a question asks how long an activity can be delayed without delaying the project, it is asking for total float. If it asks how long an activity can be delayed without delaying the next activity, it is asking for free float. Read the question twice.

Tip 6: Watch for a specified completion date. If the question states the owner requires completion by a date earlier than your forward-pass finish, start the backward pass from the required date and expect negative float. The question is likely testing whether you recognize the schedule is behind.

Tip 7: Treat lags as part of the relationship, not the activity. A 2-day lag is not added to the predecessor's duration; it is added to the link. Add it in the forward pass, subtract it in the backward pass, and remember it does not change the activity's own LS − ES calculation.

Tip 8: Eliminate answers using logic before you finish calculating. The project duration can never be shorter than the longest single chain of durations you can see at a glance. The critical path must run continuously from start to finish. Any answer violating these principles is wrong regardless of your arithmetic.

Tip 9: Manage your time. A full forward and backward pass on an exam-sized network should take three to five minutes. If a scenario question only asks for the project duration, you only need the forward pass; do not waste time on the backward pass. If it asks only for the critical path and durations are simple, you may be able to identify the longest path by inspection and confirm with a quick forward pass.

Tip 10: Connect the numbers to the CM role. Many CCM questions wrap the calculation in a management scenario: a subcontractor delay, a change order, a request for a time extension. After calculating, ask yourself what the result means. Did the delayed activity have float? Was the float consumed? Did the critical path shift? Is the contractor entitled to time? The exam rewards candidates who can both compute the answer and interpret it.

Common Mistakes to Avoid

• Adding the wrong duration to the wrong ES because the diagram was not labeled clearly.
• Taking the minimum instead of the maximum at a forward-pass merge.
• Forgetting to subtract (rather than add) lag in the backward pass.
• Assuming an activity with a long duration is automatically critical; criticality depends on path position, not duration.
• Assuming there is only one critical path.
• Mixing conventions midway through a problem.
• Reporting free float when total float was requested, or vice versa.

Summary

The forward pass establishes the earliest possible dates and the project duration by moving left to right and taking the maximum at merges. The backward pass establishes the latest allowable dates by moving right to left and taking the minimum at bursts. The difference between the two sets of dates is total float, and the chain of zero-float activities is the critical path. Master the mechanics with the worked example above, practice with PDM relationships, lags, and imposed completion dates, and always interpret the result in the context of the Construction Manager's responsibility to protect the project schedule. Do this, and forward and backward pass questions become some of the most reliable points you can earn on the CCM exam.