Preconstruction — Scheduling & Phasing

Schedule Compression

Shortening a project's duration without reducing scope, by crashing or fast-tracking the work.

Quick Answer

Schedule compression is shortening a project's duration without cutting scope. It uses two main techniques: crashing, which adds resources such as labor or overtime to critical activities to shorten them, and fast-tracking, which overlaps activities that would normally run in sequence. Both target the critical path, and both add cost or risk to buy back time.

The Full Picture

Schedule compression exists for the moment a project must finish sooner than the plan allows, an owner moves a deadline, permits eat the schedule, or early delays have to be recovered, and cutting scope isn't acceptable. The team has to find time inside the same work, which always comes at a price in cost, risk, or both.

Crashing adds resources to critical activities to shorten their durations: more crews, overtime, extra shifts, or additional equipment. It works only on the critical path (accelerating non-critical work buys nothing) and it hits diminishing returns as crowding and overtime erode productivity. The scheduler looks for the cheapest critical activities to crash first to buy time at the lowest cost.

Fast-tracking overlaps activities that would normally be sequential, starting foundations before all the design is complete, or beginning one floor's finishes while the next is still framing. It can save significant time but raises the risk of rework if the overlapped upstream work changes, because downstream activities committed on assumptions that later shift.

For preconstruction, compression decisions are shaped by what precon set up: how much design is complete, how procurement is sequenced, and where float exists. The key discipline is compressing the critical path specifically, and re-checking it after each move, since compressing one chain can make another chain critical. Blindly throwing resources at visible work wastes money without recovering the schedule.

Real Examples

Crashing: To recover two weeks lost to weather, the GC adds a second concrete crew and Saturday shifts on the critical foundation work, accepting the overtime premium.
Fast-tracking: Rather than wait for 100% design, the team releases the foundation package early so excavation starts while the superstructure design is still finishing.
Diminishing returns: A third framing crew is added but the floor is too congested to gain much, showing crashing hit the point where extra labor stops buying proportional time.

Common Misconceptions

People assume: Schedule compression means cutting scope to finish faster.

Actually: Compression keeps the full scope and shortens the timeline through crashing or fast-tracking. Reducing scope is a different lever entirely. The point of compression is delivering the same project sooner, not a smaller one.

People assume: Adding more workers always shortens the schedule.

Actually: Only crashing critical-path activities shortens the project, and even then crowding and overtime cause diminishing returns. Adding labor to non-critical work, or overcrowding a critical task, spends money without recovering time.

Does MeltPlan Solve This?

Not directly

Not directly. Compressing a schedule by crashing or fast-tracking is a CPM scheduling exercise outside MeltPlan's scope. MeltPlan focuses on preconstruction document and estimating work such as drawing review, takeoff, and bid leveling. To model crashing and fast-tracking against the critical path you'll want a dedicated CPM tool like Primavera P6 or Microsoft Project.

Frequently Asked Questions

What is the difference between crashing and fast-tracking?

Crashing adds resources (labor, overtime, shifts, equipment) to critical activities to shorten them, which raises cost. Fast-tracking overlaps activities that would normally be sequential, which raises the risk of rework. Both shorten the project but through different tradeoffs.

When is schedule compression used?

When a project must finish sooner than the plan allows, such as an accelerated owner deadline, or to recover time lost to earlier delays, and reducing scope isn't an option. The team buys back time with added cost or risk.

Does schedule compression reduce project scope?

No. Compression keeps the full scope and shortens the duration. Cutting scope is a separate strategy. Compression delivers the same project faster by crashing or fast-tracking the work.

What are the risks of schedule compression?

Crashing raises cost and hits diminishing returns from crowding and overtime. Fast-tracking raises the risk of rework if overlapped upstream work changes. Both must target the critical path, which can shift after each move.

Related Terms

More Preconstruction — Scheduling & Phasing Terms

Sources

  1. Project Management Institute (PMI) — Practice Standard for Scheduling
  2. AACE International — Planning & Scheduling Recommended Practices
MELTPLAN