Crashing (Schedule Compression)
Crashing buys a shorter duration by adding cost on tasks that actually set the end date.
Crash slope = (crash cost − normal cost) ÷ (normal time − crash time). Crash the cheapest critical task first.
Crash cost slope
Slope = (crash cost − normal cost) ÷ (normal time − crash time).
Crashing is not “work faster and hope”. You pay overtime, extra crew or a faster vendor on a task that has zero float, because only those tasks move the project end. Non-critical tasks can be crashed and the date will not move until their float is gone.
The cost slope tells you the price of one unit of time. A task that costs $1,500 extra to save three days has a slope of $500 per day. Crash the critical task with the smallest slope first, then recompute the path: a new task may become critical.
Crashing is different from fast-tracking (overlap that adds risk, not cash). Walk the arithmetic in the crash time guide before you buy time you cannot actually use.
Formula
cost slope = (Ccrash − Cnormal) ÷ (Tnormal − Tcrash)
Owning tool: How to calculate crash time.
Related terms: Critical path · Slack.
Written by Umesh Manral. Formulas checked against the site's test suite on 11 November 2026. Last updated 10 November 2026. Formulas and tests: methodology. Report a calculation error.