Critical path in a construction schedule

A construction schedule is a network of work activities, durations, and dependencies. The critical path is the chain that controls the earliest possible completion date. It tells the contractor where a delay matters to the project finish, not simply which activity is most expensive or difficult.

Activities and dependencies

Break the work into activities with estimated durations, then show the logical relationships between them. For example, a foundation normally cannot begin until required site preparation is complete. Framing may depend on the foundation and on materials arriving. Mechanical, electrical, and plumbing rough-ins may depend on the frame being ready. These predecessor-successor links determine which activities can happen in parallel and which must wait.

A critical path method (CPM) schedule represents those relationships and calculates early and late dates for activities. A forward pass finds earliest starts and finishes. A backward pass works from the required completion date to find latest starts and finishes that do not delay the project. The difference between the relevant early and late dates is float.

A small worked network

Suppose site preparation takes 2 days. After it finishes, the contractor can build a foundation in 4 days and wait 6 days for a long-lead delivery at the same time. Framing takes 5 days but cannot start until both the foundation and delivery are ready. Mechanical and electrical rough-in then take 3 days, followed by a 1-day inspection milestone.

Adding the shared site-preparation activity gives an overall scheduled duration of 17 days. In this simplified network, the path through the long-lead delivery is critical. The foundation branch has 2 days of total float: it may slip by that amount without delaying the planned framing start, assuming no other constraint or calendar rule changes the network.

What float means

Total float is the amount an activity can be delayed before it delays the relevant project completion or milestone in the schedule. An activity with zero total float is critical in that schedule calculation. Free float is narrower: it is the delay available before the activity delays the early start of its immediate successor. Contract documents may specify how project float is treated; do not assume a universal ownership rule.

Float is not a permanent cushion attached to one trade. If an activity uses part of its float, less may remain for later delays. If durations, logic, calendars, or progress change, the critical path may move to another sequence. Two or more paths may have the same longest duration, creating multiple critical paths.

How to read a delay question

1. Identify the delayed activity and its successors.
2. Check whether the activity lies on a critical path or has positive total float.
3. Compare the delay with the float available in the relevant schedule, taking account of any concurrent delay or changed logic stated in the facts.
4. Determine whether a contractual milestone or completion date moves; a delay to a noncritical task does not automatically extend the contract time.
5. Use the contract's notice, update, and time-extension provisions rather than inferring entitlement from the diagram alone.

Critical path and contract administration

Owners and contractors use schedule updates to compare actual progress with planned dates, identify changed durations, and forecast completion. Federal construction clauses commonly require a realistic project schedule and use it to evaluate progress and potential time extensions; the contract controls the procedure. A schedule is evidence of planned logic and timing, not a substitute for written notice, supporting records, or the contract's rules for excusable and compensable delay.

When a critical activity slips, the project team may consider resequencing work, adding resources, changing methods, or recovering time on a later activity. Those are possible schedule responses, not automatic permissions to alter the scope or disregard safety, quality, submittal, or inspection requirements.

Common exam errors

• Choosing the activity with the longest individual duration instead of the longest linked sequence.
• Assuming every delayed activity delays completion, even when the activity has float.
• Assuming a zero-float task can slip without effect because the contractor can simply work faster later.
• Forgetting shared predecessor work when adding up total project duration.
• Treating float or a missed date as automatic proof that a time extension is owed.
• Assuming the critical path cannot change as the schedule is updated.

Follow the dependency chain, add durations along each path, and find the longest one. Then check float and contract terms before drawing a conclusion about delay or time extension.