Chennai HQ · serving India, UAE, Saudi Arabia and Omaninfo@projectassure.inCall us 24/7 +91 94895 88922
Project Assure
Schedule Quality

Schedule compression: crashing vs fast-tracking, and when it becomes an acceleration claim

Crashing buys time with resources and fast-tracking buys it with overlap. Both work only on the critical path, and both can become an acceleration claim when the employer drives them.

In short

Crashing shortens critical path activities by adding resources, at a cost measured by the cost slope, while fast-tracking overlaps activities planned in sequence, at the risk of rework. Compression only brings the finish forward when it acts on the critical path. When the employer instructs acceleration, or insists on the original date after refusing a valid extension of time, the cost may be recoverable, but only with contemporaneous records of the trigger, the cause, the measures, the cost and the time saved.

Crashing and fast-tracking are the two schedule compression techniques for shortening a programme without cutting scope. Crashing adds resources to critical path activities so they finish sooner, which costs more money. Fast-tracking overlaps critical path activities that were planned in sequence, which costs little up front but adds the risk of rework.

Both only help if they act on the critical path, and both have a contractual side. Once a contractor is told, or pressed, to finish earlier than its entitlement allows, compression becomes acceleration, and the cost of it is recoverable only if the instruction, the cause and the cost were recorded at the time.

What is schedule compression?

Schedule compression is any technique that shortens the remaining duration of a project while keeping the same scope. It is used when a project has fallen behind its baseline, when a delay event has pushed the forecast finish beyond a contractual date, or when the client wants an earlier completion. The two primary methods are crashing and fast-tracking. They differ in cost, risk and how predictable the time saving is.

Compression works on the critical path, the longest path of logically linked activities to the finish. In Primavera P6 this is usually the chain with the lowest total float, and where a contractual date cannot be met, negative total float shows how many working days the path must recover. See total float and negative float explained for how P6 calculates it.

What is crashing in project management?

Crashing shortens critical path activities by adding resources: more labour, overtime, extra shifts, additional plant or equipment, or a second work front. The work content stays the same, but more of it is done per day.

How does crashing work?

  1. Identify the critical path and the number of working days you need to recover.
  2. For each critical activity, estimate a normal duration and cost, and a crash duration (the shortest practical duration) and crash cost.
  3. Calculate the cost slope: (crash cost minus normal cost) divided by (normal duration minus crash duration). This is the cost of each day saved.
  4. Crash the critical activity with the lowest cost slope first, by one increment.
  5. Reschedule. A near-critical path may now become critical, so check the critical path again before the next step.
  6. Repeat until you have recovered the time you need, or until the extra cost of the next day saved is more than it is worth.

Example: an activity normally takes 10 days at a cost of 20,000. With an extra crew it can be done in 7 days at a cost of 26,000. The cost slope is 6,000 divided by 3, or 2,000 per day saved. If another critical activity can be shortened for 1,500 per day, crash that one first.

Once parallel paths become critical together, each further day saved means crashing activities on every one of those paths, so the cost per day rises quickly.

What are the risks of crashing?

  • Higher cost: overtime premiums, extra labour and plant, plus diminishing returns when too many people work in the same area.
  • Quality: rushed work can produce defects and rework.
  • Safety: long hours and congested workfaces raise the risk of accidents.
  • Availability: skilled labour, specialist plant or materials may simply not be available.

What is fast-tracking?

Fast-tracking runs critical path activities in parallel that were planned in sequence, by starting a successor before its predecessor is complete. For example, foundations can start before the superstructure design is fully complete, or long-lead equipment can be ordered before the design is frozen.

How does fast-tracking work in a P6 schedule?

Find Finish-to-Start relationships on the critical path where the successor could start on part of the predecessor's output. Model the overlap by converting the link to a Start-to-Start relationship with a lag, or better, by splitting the predecessor into stages so the successor can follow the first stage with a normal Finish-to-Start link. Splitting keeps the logic transparent and avoids leads (negative lags), which the DCMA 14-point assessment expects to be zero. The amount of overlap is limited by the work itself: the successor can only start once the predecessor has produced enough to start on.

What are the risks of fast-tracking?

  • Rework: if the predecessor's output changes, the overlapped work may have to be redone, which can cost more time than it saved.
  • Coordination: more interfaces between teams working at the same time need more management.
  • Less buffer: overlapping removes the float between activities, so a slip in one is felt sooner by the next.
  • Uncontrolled change: work started on incomplete information invites informal changes that bypass change control.

Crashing vs fast-tracking: what is the difference?

AspectCrashingFast-tracking
How it saves timeMore resources on critical activitiesOverlapping critical activities planned in sequence
Main costDirect cost of extra resourcesPotential cost of rework
Main risksCost, quality, safety, resource availabilityRework, coordination, loss of buffer
Time savingFairly predictableVariable, and can be lost to rework
Change in P6Shorter durations, more resourcesChanged relationships or split activities
PrerequisiteBudget and available resourcesWork that can safely start on partial information

When should you crash and when should you fast-track?

Crash when:

  • There is budget or contingency to pay for the extra resources.
  • Labour, plant and materials are available, and the workface can take them.
  • Critical activities respond to more resources rather than being fixed in duration (curing, testing, regulatory periods and long-lead deliveries usually are not).
  • Quality and safety can be maintained with additional supervision.

Fast-track when:

  • Budget is tight and extra resources cannot be funded.
  • The dependencies allow a safe overlap, as is common in design and build.
  • Change control is strong enough to manage the rework risk.
  • The design or predecessor output is stable enough to build on.

Many recovery plans combine the two: fast-track where the overlap is safe, and crash the critical activities that cannot be overlapped. The combined risk should be assessed, because both techniques reduce the margin for error.

What is an acceleration claim?

When compression is driven by the employer rather than the contractor's own lateness, it becomes acceleration in the contractual sense, and the contractor may be able to recover its cost. There are two broad forms.

  • Instructed acceleration: the employer or its engineer formally instructs the contractor to finish earlier than its entitlement allows, or to recover time lost to an employer risk event. Under most standard forms this is treated as a variation or a separately agreed acceleration, and the cost is valued and paid under the contract. If the contractor is late through its own fault, an instruction to improve progress is usually at the contractor's cost.
  • Constructive acceleration: there is no formal instruction, but the contractor is entitled to an extension of time that is refused or not decided, and the employer still insists on the original completion date, for example by threatening liquidated damages. The contractor accelerates to protect itself and then claims the cost. Recognition of constructive acceleration varies by jurisdiction and contract, so the contract terms and the governing law decide whether, and how, the cost can be recovered.

The SCL Delay and Disruption Protocol recommends agreeing the basis of payment before acceleration starts, and dealing with extensions of time promptly so that contractors are not left to accelerate on the strength of a disputed entitlement.

Why must the cost and cause of acceleration be recorded?

An acceleration claim succeeds or fails on its records. A tribunal or adjudicator will ask what was instructed or what pressure was applied, which delay the acceleration was meant to overcome, what was actually done, what it cost, and what time it saved. Without contemporaneous records, the cost tends to be treated as the contractor's own recovery of its own delay, or as disruption that cannot be separated from other causes. Keep:

  • The trigger: the instruction, or the correspondence showing the extension of time request, its refusal or non-response, and the insistence on the original date.
  • The cause: the delay event being overcome, with the programme showing its effect on the critical path before acceleration.
  • The measures: what was added and when: extra gangs, overtime hours, additional shifts, plant and supervision, linked to the activities they were applied to.
  • The cost: the extra cost of each measure, recorded separately from normal working cost and from costs caused by other events.
  • The effect: programme updates before and after, showing the time actually recovered on the critical path.

The same records protect the employer: they show whether the acceleration was needed, whether it was effective, and whether the cost claimed matches the measures taken. Where acceleration is in dispute, a forensic planning review links the delay events, the programme updates and the cost records into one evidenced account.

Best practices for schedule compression

  • Compress the critical path only. Shortening non-critical activities does not bring the finish forward.
  • Re-check the critical path after each step. Compression changes which paths drive the finish.
  • Model options in a copy of the schedule. Compare each what-if against the current update before committing to it.
  • Record assumptions and risks. Both techniques add risks that belong in the risk register.
  • Watch for rework loops. Fast-tracking needs a process for absorbing design changes without derailing the work already started.
  • Settle the contractual position first. Before accelerating, know whether you are recovering your own delay or responding to an employer risk event, and record it.

Crashing buys predictable time at a price. Fast-tracking can save money but carries rework risk. Whichever is used, analyse the schedule before compressing, because compressing the wrong path wastes money, and record why you are compressing, because that decides who pays.

FAQ

Common questions

What is the difference between crashing and fast-tracking?
Crashing adds resources to critical path activities to shorten them, which increases direct cost. Fast-tracking overlaps critical activities that were planned in sequence, which adds little direct cost but raises the risk of rework.
How do I calculate the cost slope for crashing?
Cost slope equals crash cost minus normal cost, divided by normal duration minus crash duration. Crash the critical activity with the lowest cost slope first, then recheck the critical path before the next step.
Can crashing and fast-tracking be used together?
Yes. Many recovery plans fast-track where the overlap is safe and crash critical activities that cannot be overlapped. Both reduce the margin for error, so their combined risk should be assessed.
What is constructive acceleration?
Constructive acceleration arises when a contractor entitled to an extension of time is refused it, or receives no decision, and the employer still insists on the original completion date, so the contractor accelerates and claims the cost. Whether it is recoverable depends on the contract and the governing law.
What records support an acceleration claim?
The instruction or the correspondence showing the refused extension of time, the delay event being overcome, the measures taken and when, their extra cost kept separate from other costs, and programme updates showing the time recovered. Without these, the cost is hard to distinguish from the contractor's own recovery of its own delay.
Chennai city skyline at dusk under a vivid pink and violet sky

Bring this discipline onto your programme.

Every insight comes from live mandates. A principal replies within one working day.