CPM Network Logic and Relationships

Why This Topic Matters on the CCM Exam

Time Management is one of the core domains of the CMAA Certified Construction Manager (CCM) examination, and Critical Path Method (CPM) network logic sits at the heart of that domain. A Construction Manager is expected to review the contractor's baseline schedule, evaluate monthly updates, assess time extension requests, and defend or challenge delay claims. Every one of those tasks depends on understanding how activities are linked together and how those links drive the calculated dates, float values, and the critical path.

In practice, a schedule with poor logic produces misleading dates, hides risk, and becomes useless as a management tool. The CM who cannot read a network diagram cannot tell whether a contractor's schedule is realistic, whether a claimed delay is truly critical, or whether a recovery plan actually recovers anything. On the exam, this translates into scenario questions asking you to identify relationship types, compute early and late dates, determine float, recognize logic errors, and judge the effect of a change on project completion. Mastering this material is therefore both a professional necessity and a direct path to exam points.

What CPM Network Logic Is

A CPM network is a graphical and mathematical model of a project. It consists of activities (discrete work items with a defined duration) connected by logic ties or relationships that express the sequence in which work must occur. The network is the logic; the calendar dates are merely the output produced when durations and logic are processed through a scheduling calculation.

Two diagramming conventions exist:

1. Arrow Diagramming Method (ADM), also called activity-on-arrow. Activities are represented by arrows and connected at nodes (events). ADM supports only finish-to-start logic and requires dummy activities to show certain dependencies. It is largely historical but still appears on exams as a point of contrast.

2. Precedence Diagramming Method (PDM), also called activity-on-node. Activities are boxes (nodes) and relationships are arrows between them. PDM is the industry standard used by Primavera P6, Microsoft Project, and virtually all modern scheduling software. It supports four relationship types and allows lags and leads.

The Four PDM Relationship Types

Every relationship has a predecessor (the activity that comes first in logic) and a successor (the activity that depends on it). The relationship type defines which end of the predecessor controls which end of the successor.

Finish-to-Start (FS): The successor cannot start until the predecessor finishes. This is the most common and most conservative relationship. Example: Formwork must finish before concrete placement starts. Roughly 80 to 90 percent of ties in a well-built schedule are FS.

Start-to-Start (SS): The successor cannot start until the predecessor starts. Used to model overlapping or parallel work that begins together. Example: Drywall hanging can start once framing has started (often with a lag). Note that SS controls only the start; it says nothing about when the successor must finish.

Finish-to-Finish (FF): The successor cannot finish until the predecessor finishes. Example: Painting cannot finish until drywall finishing is complete. FF controls only the finish end.

Start-to-Finish (SF): The successor cannot finish until the predecessor starts. This is rare, counterintuitive, and generally discouraged. The classic example is a shift handover or a temporary system that cannot be removed until the permanent system is started. Many specifications prohibit or restrict SF ties.

A best practice, and a common exam point, is that SS and FF relationships are often used together on the same pair of activities so that both the start and the finish of the successor are controlled. An SS tie alone can leave the successor's finish uncontrolled, creating a dangling activity.

Lags and Leads

A lag is a mandatory waiting period added to a relationship, expressed as a positive number of time units. Example: Concrete placement FS+7 to form stripping represents a seven-day cure period. A lead is a negative lag (FS-3), allowing the successor to begin before the predecessor completes. Leads are often discouraged because they obscure the actual logic; many specifications prefer that overlaps be shown with SS relationships and positive lags instead. Lags are not activities, they consume no resources, cannot be statused with percent complete, and are frequently criticized when used to hide duration or avoid proper detail. Expect exam questions testing whether you understand that excessive lags and negative lags are red flags in a schedule review.

Hard Logic versus Soft Logic

Hard logic (mandatory or physical logic) reflects dependencies that cannot be violated: you cannot pour the slab before the footings exist. Soft logic (preferential or discretionary logic) reflects a chosen sequence driven by crew flow, resources, or preference: painting Room A before Room B. Resource logic is a form of soft logic used to prevent two activities from demanding the same crew or crane at the same time. External dependencies link to events outside the contractor's control, such as owner-furnished equipment or utility company connections. The distinction matters in delay analysis because soft logic can legitimately be resequenced to mitigate a delay, while hard logic cannot.

Constraints

Constraints are date restrictions imposed on activities independent of logic, such as Start No Earlier Than, Finish No Later Than, Must Start On, or Must Finish On. Constraints override or compete with logic and can produce negative float. Good scheduling practice limits constraints to the project start, contractual milestones, and genuine external dates. Heavy use of constraints is a sign the schedule is being forced to show desired dates rather than calculated ones. Exam questions frequently ask you to identify constraints as a cause of negative float or as a scheduling deficiency.

How the Calculation Works

Once logic, durations, and a data date are established, the scheduling engine performs two calculations.

Forward Pass: Moving from project start to finish, the engine computes the Early Start (ES) and Early Finish (EF) of every activity. For an FS relationship with no lag, the successor's ES equals the latest EF of all its predecessors (plus one if using the start-of-day convention common in P6, or with no adjustment if using the zero-based academic convention). EF equals ES plus duration (minus one in the day-numbered convention). The project's earliest completion is the largest EF in the network.

Backward Pass: Moving from the project finish back to the start, the engine computes the Late Finish (LF) and Late Start (LS). The LF of the last activity is set equal to its EF (or to a contractual finish constraint). Each predecessor's LF is the earliest LS of its successors (adjusted for the relationship type and lag). LS equals LF minus duration.

Total Float (TF): TF equals LS minus ES, or equivalently LF minus EF. It is the amount of time an activity can slip without delaying the project completion or a constrained milestone. Activities with zero total float (or the lowest total float in the network) are on the critical path, the longest continuous path through the network that determines the minimum project duration.

Free Float (FF): Free float is the amount an activity can slip without delaying the early start of any successor. It is always less than or equal to total float. Do not confuse the abbreviation FF for free float with FF for finish-to-finish; context will tell you which is meant.

Negative Float: Occurs when the calculated early dates are later than a constrained late date. Negative float means the schedule, as logically built, cannot meet the required date, and recovery or a time extension is needed.

Worked Example

Consider four activities: A (5 days) is the start. B (10 days) and C (4 days) both follow A with FS ties. D (3 days) follows both B and C with FS ties. Using zero-based convention: A has ES 0, EF 5. B has ES 5, EF 15. C has ES 5, EF 9. D has ES 15 (the later of B and C), EF 18. Project duration is 18 days. Backward pass: D has LF 18, LS 15. B has LF 15, LS 5. C has LF 15, LS 11. A has LF 5, LS 0. Total float: A, B, and D have zero float and form the critical path A-B-D. C has TF of 6 (LS 11 minus ES 5). Free float of C is also 6, because C could slip to day 15 without delaying D. If C were instead delayed by 8 days, the path through C would become critical and the project would finish on day 20, with the original critical path activities now showing positive float. This illustrates that the critical path can shift as logic and durations change, a concept central to time impact analysis.

Common Logic Deficiencies the CM Must Recognize

Open ends: Activities with no predecessor (other than the project start) or no successor (other than project finish). Open-ended activities produce false float and undermine the critical path. Only the first and last activities should be open.

Dangling activities: Activities with only an SS predecessor and only an FF or no successor controlling the finish, so one end floats freely.

Redundant logic: A tie that is already implied by other ties (A to C when A to B and B to C already exist). Not harmful to dates but clutters the network and complicates revision.

Logic loops: Circular dependencies that make calculation impossible. Software will reject them.

Out-of-sequence progress: When actual progress violates the planned logic (a successor started before its predecessor finished). The CM must understand how the software handles this: retained logic holds the remaining successor work until the predecessor finishes, while progress override ignores the tie and lets the successor continue. The choice affects projected dates and is a frequent dispute point.

Excessive lags, negative lags, SF ties, and constraints: All are indicators that the schedule may be manipulated or poorly built.

Long durations: Activities significantly longer than the update period (commonly more than 20 working days) reduce the schedule's ability to track progress and are often restricted by specification.

Why Logic Matters in Delay Analysis

Time extension entitlement generally requires that a delay affect the critical path, consume all available float, and be excusable. The CM evaluates this through techniques such as Time Impact Analysis, where a fragnet (a small network of delay activities) is inserted into the schedule using proper logic ties, and the effect on the completion date is measured. If the fragnet is tied incorrectly, the analysis is invalid. Understanding float ownership (often addressed in the contract as project float shared by the parties or owned by the project), concurrent delay, and critical path shifts all flow from network logic fundamentals.

How to Approach Exam Questions on This Topic

CCM exam questions in this area generally fall into five categories: definitional (identify the relationship type described), computational (find ES, EF, LS, LF, or float), diagnostic (identify what is wrong with a schedule described in a scenario), consequential (what happens to the completion date or critical path if X changes), and procedural (what should the CM do when reviewing a schedule with certain features). Read each stem carefully to determine which category you are in, then apply the appropriate approach described in the tips below.

Exam Tips: Answering Questions on CPM Network Logic and Relationships

Tip 1: Translate the scenario into a diagram. For any question involving multiple activities, sketch a quick PDM diagram on your scratch paper. Draw boxes, label durations, and draw arrows with relationship types and lags. Most calculation errors come from trying to hold the network in your head.

Tip 2: Identify predecessor and successor before identifying the relationship type. The question may describe the dependency in reverse order. Ask which activity is controlling and which is being controlled, then determine which ends are linked. Painting cannot finish until drywall finishing is complete is FF with drywall as predecessor.

Tip 3: Remember what each relationship controls. FS controls the successor's start by the predecessor's finish. SS controls start by start. FF controls finish by finish. SF controls finish by start. If an answer choice depends on the uncontrolled end, it is probably a distractor.

Tip 4: Apply lags consistently. A lag is added to the controlling date of the predecessor to determine the earliest allowable date of the successor. For FS+5, successor ES equals predecessor EF plus 5. For SS+3, successor ES equals predecessor ES plus 3. Watch for negative lags (leads) and apply them by subtracting.

Tip 5: Check which date convention the question uses. Some questions treat time as a continuous line where EF equals ES plus duration (Day 0 start convention). Others use calendar day numbering where an activity starting Day 1 with duration 5 finishes Day 5 and the successor starts Day 6. Look at any worked values given in the question to detect the convention, and stay consistent throughout your calculation. Answer choices are usually spaced widely enough that a one-day convention error will still point to the correct answer, but not always.

Tip 6: Total float equals LS minus ES equals LF minus EF. If you compute two different values, you made an error in a pass. Recheck the backward pass first; it is where most mistakes occur because people forget to take the minimum LS of all successors.

Tip 7: The critical path is the longest path, not the path with the most activities. Compare path durations, not activity counts. Also remember that in a constrained schedule the critical path may be defined as the path with the lowest (possibly negative) float rather than exactly zero.

Tip 8: Free float can never exceed total float. If an answer choice shows free float greater than total float, eliminate it immediately. Also remember that free float is measured against the early start of the successor, not the project end.

Tip 9: For change questions, recompute only the affected paths. If the question says activity C is delayed by 8 days, add 8 to C's duration or start, recompute forward from C, and compare the new path length through C to the original critical path. The project is delayed only by the amount the new path exceeds the original longest path.

Tip 10: Recognize red-flag vocabulary. Words such as open-ended, dangling, negative lag, start-to-finish, excessive constraints, logic loop, out-of-sequence, progress override, and durations exceeding the update period all signal a schedule deficiency. When the question asks what the CM should do, the correct answer typically involves requiring correction before acceptance, not approving the schedule or ignoring the issue.

Tip 11: Distinguish hard from soft logic in delay scenarios. If a question asks whether a delay could have been mitigated, consider whether the controlling logic was preferential. Soft logic can be resequenced; hard logic cannot. This distinction also underlies questions about contractor responsibility to mitigate.

Tip 12: Know the CM's role, not the scheduler's. The CCM exam tests the Construction Manager's responsibilities: reviewing and accepting the baseline, verifying logic reasonableness, monitoring updates, evaluating time extension requests, and advising the owner. Answers framed as the CM dictating means and methods or building the contractor's schedule are usually wrong. Answers framed as the CM reviewing for compliance with specification requirements and reasonableness are usually right.

Tip 13: Watch for the word not and for absolute terms. Questions asking which statement is NOT correct or which relationship is LEAST appropriate are common. Underline the qualifier. Also be skeptical of choices containing always or never, since network behavior is situational.

Tip 14: Budget your time. Calculation questions can consume several minutes. If a network has more than six or seven activities, do the forward pass carefully once, record values directly on your diagram, then do the backward pass. Avoid redoing work. If stuck, eliminate impossible answers (negative durations, float greater than project length, free float greater than total float) and move on.

Tip 15: Memorize a compact checklist. Before answering any logic question, run through: Who is predecessor and successor? Which ends are tied? Is there a lag or lead? Are there constraints? What convention is in use? Is the question asking for early dates, late dates, float, or critical path? This thirty-second discipline prevents the most common errors.

Summary

CPM network logic is the framework that turns a list of activities into a predictive model of the project. The four PDM relationship types, together with lags, constraints, and the forward and backward pass calculations, generate early dates, late dates, float, and the critical path. A competent Construction Manager reads this logic fluently, recognizes when it has been built incorrectly or manipulated, and uses it to evaluate progress, recovery, and delay. On the CCM exam, success comes from diagramming scenarios, applying relationship rules precisely, calculating methodically, and always answering from the perspective of the CM's oversight role. Master these fundamentals and the Time Management domain becomes one of the most predictable and highest-scoring areas of the examination.