- Project plans
- Project activities
- Legislation and standards
- Industry context
Last edited 07 Aug 2019
Project crashing can be necessary when:
- The programme planning has been inaccurate.
- When there have been unforeseen events which have caused delays, such as defects being discovered.
- Or if the client has requested that the project, or a section of the project, is completed earlier than previously specified, for example if there has been an extension of time, but the client still wishes to achieve the original completion date (this is generally referred to as acceleration).
- Addressing productivity issues being experienced by the current resources and trying to find ways of increasing their efficiency.
- Increasing the assignment of resources on critical path activities. These could be internal resources or subcontracted recources.
- Adopting different techniques. This might include off-site prefabrication, extra scaffolding, temporary weatherproofing and so on.
- Overlapping activities (fast tracking).
- Working longer hours.
- Additional supervision.
- Changes to design or specification (for example standardisation replacing bespoke solutions)
- Reduction in scope (for example transferring work to a separate post-contract agreement for occupational works).
- Early procurement of items.
Many of these strategies will necessarily lead to some additional costs being incurred, or cost uncertainty. Whilst the same number of tasks need to be performed, they are condensed into a shorter period, and so are likely to require more resources. In addition, purchasing costs may be higher due to time pressures, incomplete information and the complexity of managing the interfaces between elements. A greater number of variations are also likely than on a traditional contract.
There are several risks attached to project crashing. While resources are typically focused on critical path activities, there is the possibility that non-critical paths will also be affected. Quality, safety and compliance should not be affected as a result of the critical path being crashed. Another risk is that new resources may not be as productive as existing resources, because they may be unfamiliar with the project, the programme and the tasks at hand.
This may require that the size of the contingency is increased.
Project crashing should be resisted if:
- It is no longer cost effective to continue.
- It causes another path to become critical.
- Time reduction is no longer realistically achievable.
An alternative to project crashing is fast-track construction, which is a scheduling technique that can be used to compress the overall project schedule. Typically this is decided at the beginning of a project, organising it so that the design and construction phases overlap. This means that that activities normally performed sequential are rescheduled to be performed in parallel or partially in parallel. This will reduce the overall programme, but is likely to increase costs and risks.
 Related articles on Designing Buildings Wiki
- Acceleration of construction works.
- Constructive acceleration.
- Contractor’s master programme.
- Critical path method.
- Fast-track construction.
- Key performance indicators.
- Pareto analysis.
- Programme float.
- Project programme.
- Resource leveling.
- Scheduling construction activities.
Featured articles and news
Securing suitable water systems.
Love them or hate them, they are popping up everywhere.
The initiative to enhance the environment continues.
Could underused community spaces offer an alternative to working from home?
Keeping workers and workplaces safe in the United States.
A history lesson in geographic information systems.
A low tech, easy to use method of extinguishing small fires.
How can these valued spaces be reused?
Partnership avoids the need for listed building consent.
Connecting building design from inception to completion to operations.
Gregor Harvie predicts interoperability will be construction’s Uber moment.
Expert commentary and insight.
Guidance offered for stained glass window maintenance.
Define need before determining viability.