9.1 Project Scheduling Methods

Project Scheduling Methods

Quick Summary: In commercial construction, effective scheduling is the operational backbone of project delivery. While Gantt bar charts provide an accessible visual timeline for field crews and owners, complex commercial projects require the Critical Path Method (CPM). CPM establishes mathematical network logic using Activity-on-Node (AON) or Activity-on-Arrow (AOA) diagrams, executing forward pass (Early Start/Early Finish) and backward pass (Late Start/Late Finish) calculations to determine Total Float, Free Float, and the Critical Path—the sequence of zero-float activities dictating the minimum project completion duration.

---

1. Evolution & Taxonomy of Construction Schedules

Every construction project requires a temporal plan to coordinate labor, equipment, subcontractors, and material deliveries. The construction industry utilizes several scheduling formats, ranging from simple linear representations to sophisticated mathematical networks.

Bar Charts (Gantt Charts)

Developed by industrial engineer Henry Gantt in the 1910s, the bar chart (Gantt chart) remains the most widely recognized visual scheduling tool in commercial contracting.

Traditional Gantt Chart Layout:
Activities (Y-Axis)    │ Weeks:  1   2   3   4   5   6   7   8
───────────────────────┼──────────────────────────────────────
1. Site Grading        │ [██████████] 
2. Foundation Footings │         [██████████]
3. Slab Placement      │                  [█████]
4. Structural Steel    │                       [█████████████]

• Structure: Construction activities or work breakdown structure (WBS) elements are listed down the vertical Y-axis, while calendar time (days, weeks, or months) is scaled across the horizontal X-axis. Each activity is depicted as a horizontal bar whose length represents its estimated calendar duration.
• Benefits:
  1. Visual Simplicity: Extremely easy to read and understand for trade foremen, jobsite crews, subcontractors, and building owners who lack formal scheduling training.
  2. Executive Communication: Excellent for high-level owner progress meetings, loan disbursement reviews, and monthly stakeholder reports.
  3. Baseline Comparison: Clearly displays planned baseline progress versus actual percentage completion bars in the field.
• Limitations:
  1. Lack of Mathematical Interdependency: Traditional bar charts do not explicitly indicate dependency logic. If Activity B follows Activity A, a simple bar chart does not show whether Activity B is strictly dependent on Activity A finishing, or whether they simply coincide on the calendar.
  2. Inability to Identify the Critical Path: Bar charts do not indicate which activities directly dictate the final project completion date.
  3. Masking Float: Bar charts cannot show how much an activity can be delayed before it delays other tasks or the overall project. A three-week delay on an interior finish item may visually alarm an owner even though that item has eight weeks of available float.

Milestone Schedules

A milestone schedule is an executive-level summary schedule tracking only major project events with zero duration (e.g., "Building Permit Issued," "Slab Complete," "Structure Dried-In," "Substantial Completion"). It provides overall project tracking without detailing trade-level operational sequencing.

---

2. Critical Path Method (CPM) & Network Logic Models

Developed in the late 1950s by the DuPont Corporation and the Remington Rand Corporation for industrial maintenance and development, the Critical Path Method (CPM) revolutionized commercial project management. CPM treats a project as a dynamic mathematical network where every activity possesses a quantified duration, specific logical predecessors, and specific successors.

Activity-on-Node (AON) vs. Activity-on-Arrow (AOA)

Licensing examinations test candidates on the fundamental architectural differences between the two primary network modeling formats:

Activity-on-Node (AON / PDM):        Activity-on-Arrow (AOA / ADM):
┌─────────┐        ┌─────────┐             [Node 1] ──── Activity A ────> [Node 2]
│ Task A  │───────>│ Task B  │                 │                             │
└─────────┘        └─────────┘                 └─── Dummy Arrow (0 days) ───┘
(Node = Activity; Arrow = Logic)        (Arrow = Activity; Node = Event/Milestone)

1. Activity-on-Node (AON) / Precedence Diagramming Method (PDM):

   • In AON networks, the nodes (boxes) represent the activities themselves, containing task descriptions, durations, early/late dates, and float values.
   • The arrows connecting nodes represent strictly the logical dependencies between tasks.
   • AON is the universal computational standard utilized by all modern construction scheduling software platforms (e.g., Oracle Primavera P6, Microsoft Project, Procore, ASTA Powerproject).
   • AON easily accommodates complex relationship types (SS, FF, SF) and lead/lag times without requiring artificial modeling constructs.

2. Activity-on-Arrow (AOA) / Arrow Diagramming Method (ADM):

   • In AOA networks, the arrows represent the activities requiring time and resources.
   • The nodes (circles) represent "events" or milestones indicating the start or completion of activities (possessing zero duration).
   • The Dummy Activity Rule: In AOA networks, two activities cannot share identical starting and ending nodes. Furthermore, when an activity depends on only one of two concurrent predecessors, AOA requires the insertion of a dummy activity—represented as a dashed arrow with zero duration and zero resource cost—solely to maintain unique numbering and correct logical dependency.
   • AOA is largely obsolete in field operations but remains a frequent conceptual test item on contractor licensing examinations.

---

3. Dependency Logic (Relationships), Leads, and Lags

In CPM scheduling, activities are linked by four logical relationship types that govern how successor activities react to predecessor progress:

1. Finish-to-Start (FS):  [Predecessor] ────────> [Successor]
2. Start-to-Start (SS):   [Predecessor] ─┐
                                         └──────> [Successor]
3. Finish-to-Finish (FF): [Predecessor] ────────┐
                          [Successor]   ────────┴─>
4. Start-to-Finish (SF):  [Predecessor] ─┐
                          [Successor]   <┘ (Rare)

The Four Dependency Types

• Finish-to-Start (FS): The most common construction logic. The predecessor activity must completely finish before the successor activity can start. Example: Concrete foundation footings must be placed and stripped (Finish) before masonry block foundation walls can commence (Start).
• Start-to-Start (SS): The successor activity cannot start until the predecessor activity starts. This relationship allows sequential activities to run concurrently with a staggered offset. Example: Pouring asphalt parking lot paving can start, and 2 days later striping operations can begin (Start-to-Start with a 2-day lag).
• Finish-to-Finish (FF): The successor activity cannot finish until the predecessor activity finishes. Example: HVAC air duct insulation cannot fully finish until air duct testing and balancing finishes.
• Start-to-Finish (SF): The successor activity cannot finish until the predecessor starts. This relationship is exceptionally rare in physical construction operations. Example: A temporary diesel jobsite generator cannot be decommissioned (Finish) until the permanent utility electrical transformer is fully energized (Start).

Lead and Lag Time

• Lag Time (+): A mandatory waiting duration imposed on a relationship that requires calendar time but consumes no direct labor or equipment resources. Example: A Finish-to-Start relationship with a +7-day lag (FS + 7) between pouring an elevated concrete slab and erecting structural steel to allow proper concrete hydration and compressive curing.
• Lead Time (-): A negative lag that allows an activity to accelerate and begin prior to the completion of its predecessor. Example: An interior metal stud framing activity linked to drywall hanging with a -3-day lead (FS - 3 days), allowing drywallers to start hanging sheetrock on completed sections before framing is 100% finished across the entire floor.

---

4. Mathematical Mechanics: Forward and Backward Pass Calculations

The mathematical core of CPM involves two computational passes through the network: the forward pass to determine the earliest possible project completion date, and the backward pass to establish the latest allowable dates that avoid project delay.

Standard AON Activity Node Layout:
┌──────────────────────┬──────────────────────┬──────────────────────┐
│  Early Start (ES)    │       Duration       │   Early Finish (EF)  │
├──────────────────────┼──────────────────────┼──────────────────────┤
│                 Activity Name / WBS Code                   │
├──────────────────────┼──────────────────────┼──────────────────────┤
│   Late Start (LS)    │     Total Float      │   Late Finish (LF)   │
└──────────────────────┴──────────────────────┴──────────────────────┘

The Forward Pass (Early Dates & Project Duration)

The forward pass moves chronologically from project inception to project completion. It establishes the Early Start (ES) and Early Finish (EF) for each activity.

• Early Start (ES): The earliest possible calendar point an activity can commence, provided all predecessor relationships are satisfied.
  • For the initial project activity: $ES = 0$ (or Day 1 when using calendar indexing; standard NASCLA licensing mathematical convention starts at Day 0).
  • For subsequent activities with a single predecessor: $ES = EF_{\text{predecessor}} + \text{Lag}$.
  • The Maximum Rule for Multiple Predecessors: When an activity has two or more immediate predecessors entering its node, its Early Start is dictated by the largest (maximum) Early Finish among all incoming paths: $ES_{\text{successor}} = \max(EF_{\text{predecessor 1}}, EF_{\text{predecessor 2}}, \dots, EF_{\text{predecessor } n})$
• Early Finish (EF): The earliest possible point an activity can complete. $EF = ES + \text{Duration}$
• The total project duration is equal to the largest Early Finish date among all terminal activities.

The Backward Pass (Late Dates & Schedule Deadlines)

Once the total project duration is established, the backward pass moves in reverse from project completion back to project inception. It determines the Late Finish (LF) and Late Start (LS) for each activity without extending the project end date.

• Late Finish (LF): The latest possible calendar point an activity can complete without delaying the overall contractual completion date.
  • For the final terminal project activity: $LF = EF_{\text{project}}$.
  • The Minimum Rule for Multiple Successors: When an activity has two or more immediate successors departing from its node, its Late Finish is governed by the smallest (minimum) Late Start among all outgoing paths: $LF_{\text{predecessor}} = \min(LS_{\text{successor 1}}, LS_{\text{successor 2}}, \dots, LS_{\text{successor } n})$
• Late Start (LS): The latest possible point an activity can start without delaying the project completion date. $LS = LF - \text{Duration}$

---

5. Float Calculations & Critical Path Management

Float (also termed "slack") is the measure of scheduling flexibility associated with activities in a network.

Float Comparison:
Total Float (TF) = LS - ES  or  LF - EF    (Shared along the entire path)
Free Float (FF)  = Min(ES of Successors) - EF  (Owned exclusively by the activity)

Total Float (TF)

Total Float is the total amount of time that an activity may be delayed from its Early Start date without delaying the contractual completion date of the project.

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

• Shared Property of Total Float: Total float is a shared commodity across an entire chain of non-critical activities. If an excavation contractor consumes 4 days of a 6-day total float path, the subsequent foundation and backfill contractors on that path only have 2 days of float remaining.
• Zero Float: Activities with zero Total Float ($TF = 0$) have no schedule flexibility whatsoever.
• Negative Float: Occurs when a fixed contractual completion milestone is earlier than the calculated Early Finish date ($LF < EF$). Negative float indicates that the project is currently behind schedule and will miss the contractual deadline unless accelerated.

Free Float (FF)

Free Float is the amount of time an activity can be delayed without delaying the Early Start of any immediate successor activity.

$\text{Free Float (FF)} = \min(ES_{\text{immediate successors}}) - EF_{\text{current activity}}$

• Exclusive Property of Free Float: Unlike total float, free float belongs exclusively to the single activity that possesses it. Consuming free float does not impact the early schedule of any other trade on the jobsite.
• Mathematical Boundary: Free Float can never exceed Total Float ($FF \le TF$). On the critical path, Free Float and Total Float are both zero.

The Critical Path

The Critical Path is defined as the continuous sequence of dependent activities through the network from project start to finish that requires the longest total duration. It establishes the absolute minimum calendar time required to complete the project.

• Key Rules of the Critical Path:
  1. Critical path activities are characterized by zero Total Float ($TF = 0$).
  2. Any delay to any single activity on the critical path results in an immediate, day-for-day delay to the overall project completion date.
  3. A project can possess multiple critical paths simultaneously if two parallel paths share identical maximum durations. Multiple critical paths significantly increase project delivery risk.

Schedule Compression Techniques

When an owner demands an earlier completion date, or when critical path delays threaten liquidated damages, general contractors utilize two primary schedule compression techniques:

---

6. Real-World Arkansas Contractor Scenario

Scenario: The Washington County Medical Clinic

Ozark Commercial Constructors LLC, a licensed Arkansas general contractor based in Fayetteville, was awarded a $6.2 million contract to build a two-story medical clinic in Springdale. The contract incorporates an aggressive 240-calendar-day completion schedule with a $1,500 per day liquidated damages clause for unexcused delays beyond the contractual completion date.

During month three, Ozark's project manager and scheduler evaluated two concurrent jobsite events:

Schedule Analysis for Springdale Medical Clinic:
Path A (Critical Path, TF = 0):
[Structural Steel Erection] (15 days) ──> [Elevated Metal Deck] ──> [Slab Pour]
     * Hydraulic crane breakdown halts steel erection for 3 days.
     * Impact: Zero float exists. Critical path slips 3 days. Project completion extended 3 days.

Path B (Non-Critical Path, TF = 8 days):
[Underground Storm Retention Basin] (10 days) ──> [Parking Lot Paving]
     * Precast pipe delivery delayed by 4 days due to supplier backlog.
     * Impact: Total float was 8 days. Delay consumes 4 days. Remaining TF = 4 days.
     * Project completion date remains 100% unaffected.

• Managerial Decision: Because Path B possessed 8 days of Total Float, the 4-day delivery delay was absorbed without any project delay or financial impact. However, the 3-day crane breakdown on the structural steel path directly threatened $4,500 in liquidated damages (3 days × $1,500/day).
• Schedule Recovery (Crashing): Rather than fast-tracking subsequent deck trades (which would risk safety violations over open steel framing), the project manager crashed the steel erection path by authorizing 10-hour workdays and a Saturday double-crew shift at an overtime labor cost of $2,400. This recovered the 3 lost days on the critical path, avoiding both the project completion delay and liquidated damages.