5.2 Construction Schedules, Critical Path Method (CPM) & Delay Analysis

5.2 Construction Schedules, Critical Path Method (CPM) & Delay Analysis

Time is money in commercial construction, and project scheduling is among the most contentious areas of construction administration. Under AIA Document A201-2017 Section 3.10, the general contractor carries the exclusive legal and operational responsibility to plan, schedule, sequence, and execute the work to achieve Substantial Completion within the Contract Time.

For the project architect, understanding schedule mechanics is essential not because the architect directs the work, but because the architect must evaluate contractor payment applications, review submittal workflows, determine the validity of delay claims under Article 15, and guard the owner against unwarranted financial liability. Mastering the Critical Path Method (CPM) and the legal taxonomy of delays is critical for the ARE 5.0 CE exam.

---

Contractor Construction Schedules under AIA A201 § 3.10

Under AIA Document A201 Section 3.10.1, the contractor must, promptly after being awarded the contract, prepare and submit for the owner's and architect's information a contractor's construction schedule for the Work. This schedule must satisfy three strict requirements:

1. Contain the date of commencement, interim milestone dates, and the date of Substantial Completion.
2. Be apportioned by construction activity across trades and specification divisions.
3. Provide for the orderly, expeditious, and practicable execution of the Work.

The contractor must monitor progress and submit schedule updates at intervals appropriate to the project's conditions (typically monthly, submitted concurrently with each Application for Payment under Division 01 32 16). The contractor is legally bound to perform the work in general accordance with the most recently submitted schedule.

The Submittal Schedule (§ 3.10.2)

In addition to the overall construction schedule, Section 3.10.2 mandates that the contractor prepare and promptly update a submittal schedule. This submittal schedule must:

• Be coordinated with the contractor's construction progress schedule.
• Allow the architect reasonable time to review submittals (typically 14 calendar days per Division 01).
• Establish specific submittal packages, submission dates, and required return dates.

The Architect's Review Scope: Informational vs. Approval

A vital legal distinction frequently tested on the ARE is the nature of the architect's review of the construction schedule:

• The architect reviews the schedule to verify that it meets the contractual completion deadline, respects project phasing, accommodates owner-occupied spaces, and provides realistic windows for submittal reviews and inspections.
• The architect does NOT approve the construction schedule. Approving a construction schedule would pierce the legal firewall established in A201 § 3.3.1 and B101 § 3.6.1.2, potentially making the architect liable for the contractor's means, methods, sequences, or scheduling logic flaws. The architect stamps or returns the schedule as "Reviewed," "Received for Information," or "Approved for Conformance with Contract Milestones Only."

---

Critical Path Method (CPM) Mechanics

The Critical Path Method (CPM) is a mathematical network analysis technique that models project activities, durations, and logical dependencies. It determines the minimum total calendar time required to complete the project.

Network Activities and Dependency Types

In a CPM network, an activity is an individual task consuming time and resources. Activities are connected by four types of logical dependencies:

1. Finish-to-Start (FS): The successor activity cannot begin until the predecessor activity finishes (e.g., finish concrete curing before starting structural steel erection). It is a common relationship; other link types require their own logic.
2. Start-to-Start (SS): The successor activity cannot begin until the predecessor activity starts (e.g., pipe insulation can start 2 days after pipe rough-in begins).
3. Finish-to-Finish (FF): The successor activity cannot finish until the predecessor activity finishes (e.g., exterior joint sealant cannot finish until exterior stone cladding finishes).
4. Start-to-Finish (SF): The successor activity cannot finish until the predecessor starts (rare in construction practice).

Activities can also carry Lags (mandatory waiting periods, such as a 7-day cure lag following a concrete pour) or Leads (accelerations allowing negative lag, where an activity begins prior to predecessor completion).

Mathematical Calculations: Forward and Backward Passes

Use elapsed working-time boundaries starting at time 0, finish-to-start links and no lags for these formulas. A task starting at 40 with duration 12 finishes at 52. Inclusive calendar-day labeling uses different plus/minus-one rules; do not mix conventions. CPM calculates the early and late boundaries of every activity through two sequential mathematical sweeps:

1. The Forward Pass (Calculates Early Dates):

   • Moves left-to-right through the network from project commencement.
   • Early Start (ES): The earliest calendar date an activity can possibly begin once all predecessor activities are complete.
   • Early Finish (EF): The earliest calendar date an activity can finish: $\text{EF} = \text{ES} + \text{Duration}$.
   • When an activity has multiple predecessors, its Early Start is the maximum of the Early Finishes of all immediate predecessors: $\text{ES} = \max(\text{Preceding EFs})$.

2. The Backward Pass (Calculates Late Dates):

   • Moves right-to-left through the network from the project completion milestone.
   • Late Finish (LF): The latest calendar date an activity can finish without delaying the overall project Substantial Completion date.
   • Late Start (LS): The latest calendar date an activity can begin without delaying the overall project Substantial Completion date: $\text{LS} = \text{LF} - \text{Duration}$.
   • When an activity has multiple successors, its Late Finish is the minimum of the Late Starts of all immediate successors: $\text{LF} = \min(\text{Succeeding LSs})$.

---

Float Mechanics: Total Float vs. Free Float

Float (or slack) is the measure of scheduling flexibility associated with an activity.

Total Float (TF)

Total Float is the total amount of time an activity can be delayed from its Early Start date without delaying the project's overall contract completion date (Substantial Completion):

$$\text{Total Float} = \text{LS} - \text{ES} = \text{LF} - \text{EF}$$

• If an activity has a Total Float of 10 days, that activity can slip by up to 10 days before the project's final completion date is pushed back.
• Crucial Rule: Total Float belongs to the path, not to a single activity. If Activity A and Activity B are in series and share 10 days of Total Float, if Activity A consumes 6 days of float, only 4 days of Total Float remain for Activity B.

Free Float (FF)

Free Float is the amount of time an activity can be delayed from its Early Start date without delaying the Early Start of any immediately succeeding activity:

$$\text{Free Float} = \min(\text{Successors' ES}) - \text{EF}$$

• Free Float represents localized slack that can be consumed without causing a ripple effect on downstream trade subcontractors.
• Free Float can never exceed Total Float ($FF \le TF$).

The Critical Path

The Critical Path is the continuous sequence of interdependent activities from project start to finish that has zero Total Float ($TF = 0$).

• It is the longest path through the network in terms of total duration.
• Any delay to any activity on the critical path causes an unavoidable, day-for-day delay to the overall project Substantial Completion date.
• A project network may have more than one critical path. If non-critical activities slip and consume all their available Total Float, they become critical, creating multiple parallel critical paths.

Float and contract entitlement

Float allocation depends on contract provisions and applicable law; A201 does not establish a universal first-come-first-served ownership rule. A delay within available float may have no completion-date impact while still causing a substantiated cost or disruption claim. Analyze time and money separately.

A critical-path delay normally affects the forecast finish unless recovery, mitigation or changed logic offsets it. In constrained schedules, critical activities can have negative float; the zero-float description here assumes an unconstrained basic network.

---

The Delay Taxonomy: Evaluating Construction Delays

When a delay occurs on a construction project, the architect (or Initial Decision Maker under A201 § 15.2) must evaluate the claim. Legally, all construction delays fall into a strict three-tier delay taxonomy based on causation and risk allocation:

1. Excusable Compensable Delays

• Causation: Delays caused directly by the Owner, the Architect, or separate contractors employed by the owner (parties for whom the owner is legally responsible).
• Common Triggers: Owner-directed scope changes via Change Orders; owner's failure to grant timely site access or clear easements; concealed or unknown conditions under § 3.7.4; architect's failure to return submittals or answer RFIs within the agreed submittal schedule; design errors and omissions requiring field redesign.
• Contractual Remedy: The contractor is entitled to BOTH an extension of Contract Time AND an increase in Contract Sum to cover extended jobsite overhead (superintendent salary, jobsite trailer, utility costs), equipment standby fees, and extended home office overhead.

2. Excusable Non-Compensable Delays

• Causation: Delays caused by unforeseeable events beyond the control and without the fault or negligence of either the contractor or the owner.
• Common Triggers: Acts of God, war, civil unrest, regional labor strikes, industry-wide material freight embargoes, and abnormally severe weather.
• Contractual Remedy: The contractor is entitled to an extension of Contract Time ONLY. The contractor receives zero monetary compensation for extended overhead. The financial principle is that both parties absorb their own overhead losses resulting from uncontrollable external acts.
• Weather evidence (§ 15.1.6.2) must show abnormal conditions for the period, inability to anticipate them reasonably, and adverse effect on scheduled construction. Compare actual conditions with a suitable local baseline and actual work records. A201 does not mandate a ten-year NOAA period or automatically award actual rainy days minus average rainy days. Check critical-path effect, planned nonworking days, normal-weather allowance, mitigation and overlapping delays.

3. Non-Excusable Delays

• Causation: Delays caused by the fault, neglect, or operational mismanagement of the Contractor, trade subcontractors, or material suppliers.
• Common Triggers: Subcontractor default or abandonment; late placement of equipment orders; inadequate staffing; failure to coordinate trade sequences; correcting defective or rejected work.
• Contractual Remedy: The contractor is entitled to NEITHER an extension of Contract Time NOR an increase in Contract Sum.
• Consequences: The contractor must absorb all extended overhead. Furthermore, if the delay pushes project completion beyond the contractual Substantial Completion date, the owner may assess actual delay damages or contractually stipulated Liquidated Damages (LDs) for every calendar day the project is late.

Concurrent delays

Overlapping owner and contractor delays require analysis of independent causes, actual critical paths, schedule updates, mitigation and contract terms. A time extension without compensable delay damages can be an outcome, but there is no universal rule that overlapping delays automatically cancel each other's monetary consequences. Distinguish true concurrency from two events on the same calendar dates when only one affects completion.

For an exam scenario, use the stated contract and verified net effects. Do not award both time and money simply because an event is labeled owner-caused, or deny costs solely because float remained. Determine causation, notice, entitlement and amount separately.

Source and application

A201-2017 official sample. Checked October 16, 2026. Apply the cited form edition and the actual project amendments, adopted codes and supplied scenario assumptions. Numerical examples are teaching inputs unless expressly attributed to a requirement.