Fast-Tracking vs. Crashing: Schedule Compression [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on August 30, 2026
9 min read
Your project is running late, the finish date will not move, and cutting scope is off the table, so how do you buy back time? You have exactly two levers, and pulling the wrong one costs you either money you do not have or quality you cannot spare. Fast-tracking versus crashing is that choice, and knowing which to use, and when, is one of the most practical skills in scheduling. This guide explains both schedule compression techniques: what each is, how they differ, when to use which, their risks, and how they are tested on the PMP and CAPM exams.
What is schedule compression?
Schedule compression is shortening a project's schedule without reducing its scope — you still deliver everything, just sooner. There are exactly two techniques for it: crashing and fast-tracking. Everything else about compression is a variation on one of these two.
One rule governs both: they only work on the critical path. The critical path is the longest chain of dependent activities, and it sets the project's finish date, so compressing an activity that is not on it saves nothing — the project still ends when the critical path ends. That is why the first step in any compression effort is to find the critical path, using the project network diagram and its float analysis, and target only the activities on it.
What is crashing?
Crashing shortens the schedule by adding resources to critical-path activities — more people, more hours, more equipment — to complete them faster. It buys time with money: crashing always increases cost, and it does not change the project's logic or the sequence of work, only how fast individual activities get done.
Because it costs money, crashing is done deliberately, not everywhere at once. You compare the crash cost per unit of time saved across the critical activities and start with the cheapest — the activity that buys the most schedule for the least money.
A small worked example shows the discipline. Suppose the project needs 3 weeks back, and the critical path offers three crashable activities:
| Critical activity | Max weeks crashable | Extra cost | Cost per week saved |
|---|---|---|---|
| Design review | 1 | $2,000 | $2,000 |
| Testing | 1 | $3,000 | $3,000 |
| Build | 2 | $9,000 | $4,500 |
Cheapest-first says: crash the design review ($2,000), then testing ($3,000), then just one of Build's two weeks ($4,500) — three weeks recovered for $9,500. The intuitive move of attacking the biggest activity first — both weeks of Build plus the design review — recovers the same three weeks for $11,000. Ranking by cost per week saved, not by activity size, is what the exam's crashing calculations reward, along with rechecking after each step that the critical path has not shifted. Crashing also runs into diminishing returns: the classic example is that nine women cannot deliver a baby in one month. Doubling a team rarely halves the duration, because of coordination overhead, onboarding time, and tasks that simply cannot be parallelized. Crash too hard and each additional week saved costs far more than the last.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
What is fast-tracking?
Fast-tracking shortens the schedule by overlapping activities that were originally planned in sequence — starting the next one before the previous one fully finishes. Unlike crashing, it usually adds no direct cost; instead it buys time with risk. Running work in parallel that was meant to be sequential increases the chance of rework, because the downstream activity may start on assumptions the upstream one later changes.
The critical constraint is the type of dependency between the activities. You can only safely fast-track where the relationship is discretionary — a "we usually do it this way" preference — not mandatory, where one activity physically cannot start until another is done. You cannot pour a foundation and frame the walls at the same time; that dependency is mandatory. But you might start drafting content before the design is fully signed off, accepting that some drafting may need redoing. Fast-tracking is often tried before crashing precisely because it does not add cost, but only where the work genuinely can overlap.
Fast-tracking vs. crashing
Both compress the schedule without cutting scope, and both target the critical path — but they pay for the time in different currencies. Crashing spends money; fast-tracking spends risk. Here is the comparison at a glance:
| Crashing | Fast-tracking | |
|---|---|---|
| How it works | Add resources to critical activities | Overlap activities that were sequential |
| Main cost | Increases cost | Increases risk (rework) |
| Effect on budget | Higher | Usually unchanged |
| Main limit | Diminishing returns; needs budget | Only works on discretionary dependencies |
| Changes the logic? | No — same sequence, done faster | Yes — activities now run in parallel |
When to use crashing vs. fast-tracking
The choice comes down to your binding constraint, and in practice the two techniques are often combined.
A practical decision order:
- Is there budget? No → lean fast-tracking (no added cost). Yes → crashing is available.
- Can the critical activities overlap? Only where the dependency is discretionary; mandatory dependencies rule fast-tracking out.
- How much time do you need back? Small amounts often come cheaply from fast-tracking; large amounts may force crashing despite the cost.
- Which risk can you absorb? A cost overrun, or the rework and quality risk of parallel work?
Many project managers fast-track first because it does not add cost, then crash whatever time remains.
Advantages and risks
Each technique earns its place, and each carries a signature danger:
- Crashing — advantage: predictable and controllable; you can often forecast exactly how much time a given amount of resource will buy, and it does not disturb the project's logic.
- Crashing — risk: it raises cost, hits diminishing returns fast, and adding people can slow a team down through coordination and onboarding before it speeds them up.
- Fast-tracking — advantage: it usually adds no cost, so it is the natural first move when the budget is fixed and the work can genuinely overlap.
- Fast-tracking — risk: parallel work increases the odds of rework and quality problems, and it makes the schedule harder to manage because more is happening at once. Overdo it and the rework can cost more time than you saved.
The shared discipline for both: recalculate the critical path after every compression. Shorten one chain enough and a different one becomes the longest — and the new critical path is what you must target next.
Schedule compression on the PMP® and CAPM® Exams
On the PMP exam, schedule compression shows up as situational judgment. A scenario gives you a late project and a constraint — a fixed budget, a hard deadline, a dependency you cannot change — and asks what the project manager should do. The exam expects you to match the technique to the constraint: crash when you have money and cannot overlap the work; fast-track when you cannot spend more but the dependencies are discretionary. It also tests the traps: compressing a non-critical activity (which saves nothing), fast-tracking a mandatory dependency (which is not possible), and forgetting that crashing adds cost while fast-tracking adds risk.
The CAPM tests the same material a little more directly — often defining each technique or asking which one adds cost versus risk — but the CAPM is scenario-based like the PMP, so expect to apply the distinction, not just recite it. Both exams assume you know compression targets the critical path and never reduces scope. Our PMP Complete Study Guide walks through the decision logic with worked scenarios so the right technique becomes obvious under exam pressure.
PMP Practice Question: Fast-Tracking vs. Crashing
A project must pull its finish date in by four weeks. Two parallel paths lead to the finish milestone. The critical path runs through Activity B and totals 20 weeks. A second, parallel path runs through Activity C and totals 18 weeks. Activity B can be crashed by up to four weeks and Activity C by up to four weeks, each by adding resources; no other activity can be compressed. The project manager needs to recover the full four weeks.
Which action recovers the full four weeks?
a) Crash Activity B by four weeks, since B is on the critical path and four weeks of crashing recovers the four weeks needed.
b) Crash Activity B by four weeks and Activity C by two weeks.
c) Fast-track the critical path by overlapping Activity B with its successor to recover the four weeks at no added cost.
d) Crash Activity C by four weeks, since it sits on the path with the most float and compressing it frees up the schedule.
Correct answer: B.
Rationale: The finish date is set by whichever parallel path is longest, so reaching a 16-week finish means compressing every path that would exceed 16 weeks, not just the path that is critical today. Crashing Activity B by four weeks takes its path from 20 to 16 — but that alone leaves Activity C's path at 18, which quietly becomes the new critical path and caps the real saving at two weeks, so the last two weeks of crashing B buy nothing; that is the central trap. Crashing C by two more weeks brings both paths to 16 and recovers the full four. Fast-tracking only B's path fails the same arithmetic while adding rework risk for a partial result, and crashing C alone compresses a path that was never setting the finish date — its float is the reason compressing it is wasted, not a reason to target it. The discipline being tested: after any compression, recheck which path is now the longest. To drill this kind of multi-path crashing question under exam conditions, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Frequently asked questions
What is the difference between fast-tracking and crashing?
Crashing shortens the schedule by adding resources to critical-path activities, which increases cost. Fast-tracking shortens it by overlapping activities that were planned in sequence, which increases risk of rework but usually adds no cost. Crashing spends money; fast-tracking spends risk. Both compress the schedule without reducing scope, and both apply only to the critical path.
What is schedule compression?
Schedule compression is shortening a project's schedule without reducing its scope — delivering the same work sooner. It has exactly two techniques: crashing (adding resources) and fast-tracking (overlapping activities). Both target the critical path, because compressing an activity that is not on the critical path does not change the project's finish date.
Does crashing or fast-tracking cost more money?
Crashing costs more money, because it works by adding resources — more people, hours, or equipment — to critical activities. Fast-tracking usually adds no direct cost, since it only rearranges activities to run in parallel; its price is paid in increased risk and potential rework rather than in budget.
When should you fast-track instead of crash?
Fast-track when the budget is fixed and the critical activities have discretionary dependencies that can safely overlap. Crash when you have budget to spend but the work cannot be overlapped, for example because the dependency is mandatory. Many projects fast-track first, since it adds no cost, then crash any remaining time.
Why does compression only work on the critical path?
The critical path is the longest chain of dependent activities and it determines the project's finish date. Shortening an activity that is not on the critical path leaves the longest chain unchanged, so the project still ends at the same time. Compression must target critical activities — and be rechecked after each change, since the critical path can shift.
Can you fast-track a mandatory dependency?
No. A mandatory dependency means one activity physically cannot start until another finishes — you cannot frame walls before the foundation is poured. Fast-tracking requires overlapping activities, so it only works on discretionary dependencies, where the sequence is a preference rather than a physical necessity. Attempting to overlap mandatory work leads to failure or rework.
Is schedule compression on the PMP exam?
Yes. Fast-tracking and crashing are core PMP scheduling topics. The exam tests them through situational questions that give you a late project and a constraint, then ask which technique fits — rewarding you for knowing crashing adds cost, fast-tracking adds risk, both target the critical path, and only discretionary dependencies can be fast-tracked.
Is fast-tracking vs. crashing on the CAPM exam?
Yes. The CAPM covers both compression techniques, usually a bit more directly than the PMP — defining each or asking which one adds cost versus risk. Because the CAPM is scenario-based, expect to apply the difference in a short situation, not merely recall the definitions.
Bottom-Up Estimating: Definition, Steps & Example [2026]
Bottom-up estimating sums every work package for the most accurate cost or duration. How it works, a worked example, bottom-up vs top-down, and its limits.
Monte Carlo Simulation in Project Management [2026]
Monte Carlo simulation in project management: how it works, reading the S-curve and P50/P80 values, when to use it, and how it is tested on the PMP exam.
Resource Leveling vs. Smoothing: Guide & Examples [2026]
Resource leveling explained: what it is, how it works, and how it differs from resource smoothing — including the effect on the critical path and the PMP exam.
