4.4 Schedule Compression (Crashing, Fast-tracking, Leveling)

Schedule Compression and Optimization

Construction projects rarely go perfectly according to the baseline plan. Delays due to weather, supply chain disruptions, or design errors frequently push the projected completion date past the contractual deadline. When this happens—or when an owner demands an accelerated schedule upfront—the Construction Manager must employ schedule compression techniques to shorten the project duration without reducing the project scope or compromising quality.

The two primary methods of schedule compression are crashing and fast-tracking. Both involve significant trade-offs regarding cost, risk, and resource allocation.

Crashing the Schedule

Crashing involves a methodical analysis of cost and schedule trade-offs to obtain the greatest amount of compression for the least incremental cost. Conceptually, it means throwing money at the problem by adding resources to activities on the critical path to complete them faster.

Common methods of crashing include:

• Authorizing overtime, weekend work, or double shifts.
• Hiring additional labor crews or bringing in supplementary subcontractors.
• Expediting the delivery of critical materials (e.g., paying a premium for air freight instead of ocean freight).
• Utilizing more productive, heavier equipment (e.g., renting a larger crane to lift heavier assemblies).

Key Rules of Crashing:

1. Only crash the critical path: Crashing a non-critical activity will only increase its float and waste money; it will not shorten the overall project duration.
2. Crash the cheapest activities first: As critical path activities are shortened, the project cost increases. The CM must calculate the Cost Slope to find the most cost-effective activities to crash.
3. Watch for new critical paths: As you compress the primary critical path, a secondary path may lose all its float and become critical. You must then crash activities on both paths simultaneously to achieve further compression, which dramatically increases costs.
4. Beware of diminishing returns: Adding 20 painters to a small room won't get it painted faster; they will get in each other's way. There is a physical limit (crash limit) to how much an activity can be compressed.

The Cost Slope Calculation

To determine the most efficient crashing strategy, CMs calculate the Cost Slope (the premium cost per unit of time saved) for each critical activity:

Cost Slope = (Crash Cost - Normal Cost) / (Normal Time - Crash Time)

Example: Activity A normally takes 10 days and costs $10,000. By working overtime, it can be "crashed" to 7 days at a total cost of $14,500. Cost Slope = ($14,500 - $10,000) / (10 days - 7 days) = $4,500 / 3 days = $1,500 per day saved.

The CM will calculate this for all critical activities and choose to crash the one with the lowest cost slope first.

Fast-Tracking the Schedule

Fast-tracking involves fundamentally altering the network logic by performing activities or project phases in parallel that would normally be performed sequentially. It overlaps activities to compress the overall duration.

Examples of fast-tracking:

• Design-Build: Starting construction of the foundation and structural frame before the interior architectural design is fully finalized.
• Trade Overlap: Beginning electrical rough-in in the eastern wing of a floor while framing is still ongoing in the western wing, rather than waiting for the entire floor to be framed.

Key Considerations for Fast-Tracking:

• Increased Risk: Fast-tracking significantly increases project risk. If an upstream activity changes (e.g., the architect moves a wall design after framing has started), the downstream work that was performed concurrently must be demolished and reworked.
• Cost Implications: Unlike crashing, fast-tracking does not always result in a direct premium cost (like overtime pay). However, the high probability of rework often leads to substantial indirect cost increases.
• Coordination: Fast-tracking requires intense, daily coordination and communication among all project team members to manage the overlapping work safely and efficiently.

Resource Leveling vs. Resource Smoothing

While crashing and fast-tracking focus on time, CMs must also optimize resources. If a schedule requires 10 carpenters on Monday, 50 on Tuesday, and 5 on Wednesday, it is unmanageable.

• Resource Leveling: This technique resolves severe resource constraints (e.g., you only have 20 carpenters maximum). It shifts activities within their available float to reduce resource spikes. If float is exhausted, Resource Leveling will delay critical activities and extend the project duration to ensure resource limits are not exceeded.
• Resource Smoothing: This technique aims to create a steady, level profile of resource usage without extending the project end date. It only utilizes available float. Because it cannot delay the project, it may not be able to eliminate all resource peaks, but it optimizes the profile as much as possible.