What is the difference between crashing and fast-tracking?

What each one spends. Crashing keeps the sequence the same but throws more resources at critical activities, extra crews, a second shift, or overtime, to finish them in less calendar time. It costs money, and it has diminishing returns: past a point, adding people to the same work makes it slower, not faster. Fast-tracking changes the sequence instead, overlapping activities that were planned one after another so a successor begins before its predecessor is fully complete. It costs little cash up front but adds risk: if the earlier activity changes, the overlapped work may have to be redone. Crashing buys time with dollars; fast-tracking buys time with risk.

When should you crash versus fast-track?

It depends on whether you have more tolerance for cost or for risk, and on what is actually driving the delay. Crashing is the safer choice when the work is well-defined and the budget can absorb the premium, because it does not change the logic of the plan. Fast-tracking is used when the schedule pressure is severe and the cash is tight, or when activities genuinely can proceed in parallel with manageable risk, but it demands tight coordination and a clear view of what might have to be reworked. Both only help if they are applied to the critical path; adding crews or overlapping work on activities that already have float shortens nothing and just spends money or adds risk for no schedule gain.

Is compression the same as acceleration?

They are closely related but not identical, and the distinction matters commercially. Compression is the technique, crashing or fast-tracking to shorten the schedule. Acceleration is the situation that often calls for it: being required to finish sooner than the current plan allows. When an owner directs acceleration, or refuses a time extension the contractor was entitled to and thereby forces the contractor to compress to avoid being late, that can become constructive acceleration, a basis for recovering the added cost. So compression is how you shorten the job; whether the cost of doing so is recoverable depends on why you had to, which is a matter of entitlement and the contract.

Construction Glossary · Scheduling

ScheduleCompression

You can pull a finish date in two ways: spend money to go faster, or take risk to go in parallel. Neither is free, and both only work on the critical path.

Definition

Schedule compression is shortening the project duration without reducing scope, by two main techniques. Crashing adds resources, crews, shifts, or overtime, to critical activities so they finish faster, which costs more money. Fast-tracking overlaps activities that were planned in sequence, which adds risk because the later activity starts before the earlier one is finalized. Both recover delay or hit an accelerated date; both carry a cost, in money or in rework risk.

Two ways to pull the finish in

Crashing shortens the same activity by adding resources, at a cost. Fast-tracking slides a successor back to overlap its predecessor, at a risk. Both move the finish left; neither is free.

Crashing vs fast-tracking

Same goal, opposite currencies. One spends dollars without touching the plan’s logic; the other spends risk by changing it.

	Crashing	Fast-tracking
Method	Add resources to critical work	Overlap activities planned in sequence
Primary cost	Money (premium time, lower efficiency)	Risk (possible rework)
Changes the logic?	No	Yes — successors start early
Best when	Budget can absorb it, work is defined	Cash is tight, work can run in parallel

Both act on the critical path; when an owner forces it, the cost may be recoverable as compensable.

How POD informs a recovery

Compression only helps on the critical path, and POD reads the critical path and each activity’s float from the imported schedule, so the activities actually worth crashing or fast-tracking are the ones in view, not activities that already have slack. The overtime and extra crews a crash consumes show up in the labor and cost record, where the premium is visible rather than lost. POD does not model the compressed schedule or run the Critical Path Method, that is done in the scheduling tool; it surfaces which work is critical and what acceleration is costing, so the recovery is aimed where it moves the finish.

Construction scheduling software guide

Frequently asked questions

It all lives on one chart

Critical path, float, milestones, and the compressed sequence all show up in the same place: the Gantt chart the whole schedule is read from.

Gantt Chart Back to the Glossary