Quantify the full financial cost of a project delay. Model daily team cost, delayed revenue, contractual penalties and opportunity cost to understand the real price of being late — and whether a rush to avoid it is justified.
Project delays have four cost components that are rarely all accounted for simultaneously: extended team cost (salaries continuing without corresponding revenue), delayed or lost revenue, contractual penalties, and opportunity cost (what the team could have been doing instead). Most delay conversations focus only on the first — missing 50-80% of the true cost.
The rush cost calculation is simple: if rush cost < delay cost, rushing is financially justified. But the calculation must be honest. Rush costs: overtime premiums (typically 1.5× hourly rate), contractor day rates (often 2–3× employee cost), rework from speed-induced errors (add 20–40% to rush labour cost), team burnout impact on subsequent productivity. A rushed delivery that ships with significant bugs may cost more in post-launch remediation than the delay would have cost.
Total delay cost = (Team daily cost × delay days) + (Daily revenue delayed × delay days) + contractual penalties (if any) + opportunity cost (other work team cannot start). Compare this against the cost to rush (overtime, contractors, expediting). If delay cost > rush cost: rushing is financially justified. If rush cost > delay cost: accept the delay and manage stakeholders. Always include opportunity cost — the work your team cannot do while extended on the delayed project.