Delay to progress that caused loss and/or expense to be suffered
by contractors or subcontractors; and
• Reduction in productivity (or disruption) that caused loss and/or
expense to be suffered by contractors and/or subcontractors.
Dealing with each of these scenarios or a combination of them
involves the claimant assessing how the delays experienced by various
project activities affect others and the project completion date,
and then determining how much of the overall project delay is
attributable to any party involved. To carry out this undertaking,
employers and contractors often resort to various delay analysis
techniques available in practice. The most common techniques,
as reported in the literature (for example, Finke 1999; Alkass et al.
1996; Zack 2001; SLC 2002; Pickavance 2005) are As-planned
versus As-built, Impacted As-planned, Collapsed As-built, Window
Analysis, and Time Impact Analysis. Not only are each of these
techniques known by different terminologies among practitioners,
they also have their own variant forms of unique application
procedures (Alkass et al. 1996; Pickavance 2005). The various
techniques therefore produce different results at different levels
of accuracies when applied to the same delay claims scenario,
as established in various studies (Alkass et al. 1996; Bubshait
and Cunningham 1998; Stumpf 2000). In addition, disputing
parties tend to employ the techniques in such a way as to satisfy
their individual interest of casting their cases in the best light.
All these characteristics go to compound the problems associated
with delay claims resolutions. As detailed descriptions of the
techniques abound in the literature, only programming requirements
affecting their application will be focused on in the sections
following.