Professional Documents
Culture Documents
PROJECTS
Conclusions
Delay Claims
• Contractors frequently assert that they have been delayed due to reasons beyond their control.
• Owners often remain unconvinced that the Contractor is legitimately entitled for time extension or
delay, acceleration and loss of productivity damages.
• Large sums of money may hinge upon the outcome of the dispute over project delays.
• Consequently, a thorough schedule analysis of all project delays is essential for the equitable
resolution of delay and impact related disputes.
• Most construction contracts allow Owner to recover either liquidated damages or actual damages due
to delays caused by the Contractor.
Excusable Non-compensable
Delays that allow extention of time to the Contractor with out Liquidated Damages but no
additional cost for extention
Generally due to concurrent delays of Owner and Contractor, Force Majeure
Concurrent Delays
Delays attributable to both Contractor and Owner and taking place concurrently
Inexcusable Delays
Contractor to be penalised
Are primarily Contractor caused delays
12
APPROACH
Conclusions
APPROACH – DELAY ANALYSIS METHODOLOGIES
Retrospective Analyses Prospective Analyses
TWO
Types
FOUR
Categories*
APPROACH – AS‐PLANNED VS AS‐BUILT (APAB)
• is the most basic method of analysis
• is observational – no changes are made to the programme
• straightforward comparison between the planned vs the actual performance of the
work
• can only be carried out retrospectively (requires as‐built programme/or at least
the overall as‐built completion date)
STRENGTHS WEAKNESS
• is a prospective methodology
• delay effect is measured by imposing events on a model of the original programme
(Baseline)
• does not rely on any actual progress that has been made
• requires a robust and reliable original programme that reflects the indented sequence
and the Scope of Work
STRENGTHS WEAKNESS
• relatively simple to carry out and • cannot be used for complex projects
to understand. • used to quantify potential delays rather and actual
• No as‐built required (likely choice • concurrent delays easily overlooked
when planned programme is available, • assumes that the baseline was achievable
no significant changes in the sequence • does not take actual progress/ resources into
during the project execution, few account
delaying events, and when there is • not reliable in dispute resolution
little or no progress records)
APPROACH – IMPACTED AS‐PLANNED (IAP)
APPROACH – TIME IMPACT ANALYSIS (TIA)
• prospective and dynamic method – but can be applied retrospectively
• takes account of progress and timing of delay events on the Works
• requires reliable as‐built data to update the programme (hence, if detailed and
regular progress data is not available then this method cannot be used)
• a reliable baseline programme is essential (ideally reflects the execution of the planned
project using sound construction logic)
• often undertaken in time slices (windows)
STRENGTHS WEAKNESS
• has a proven track‐record in • time consuming (to determine the factual
forensic application background and correct logic associated
with progress records and delay events)
• preferred method of the SCL
Protocol • requires considerable degree of
expertise and technical knowledge
• based on a dynamic and changing
critical path • hence, difficult to communicate, highly
complex
• demonstrates cause and effect
APPROACH – TIME IMPACT ANALYSIS (TIA)
APPROACH – AS‐BUILT BUT FOR (ABBF)
• retrospective method also known as Collapsed As‐built (CAB)
• relies on a detailed reconstruction of the as‐built programme
• normally restricted to after‐the‐event analyses in forensic work
• does have a limited prospective capability (can be used to demonstrate the effect of a delay on the completed
part of an incomplete project)
• has been proven to be reliable in dispute resolution/ claims
• If done properly can demonstrates effect and cause/ takes account of concurrence
STRENGTHS WEAKNESS
• greatest strength for forensic work • complicated method hence, difficult to
execute and to explain
is that it is fact based (based on asbuild)
• not reliant upon an as‐planned • difficult to establish a dynamic as‐built
programme schedule (as complicated to determine and
model logic)
Conclusions
FINDINGS – CHOOSING A METHODOLOGY
Which Method is appropriate, correct, sustainable?
Legal/Contractual
• What does the jurisdiction/ contract require? (e.g. Concurrency? Likely or Actual delay to
completion? Delay Analysis Method Specified?)
Other issues:
• Proportionality, Type of project, Which party, at what stage is the dispute?
FINDINGS – FACT IS KING
Key Facts:
At least after an event delay becomes a fact and the Other Party/ the Courts are interested in
what actually happened rather than in what could have happened.
For an event to affect the completion date it must fall on the critical path of the project.
must consider all relevant facts and evidence regardless of a positive or negative impact in
relation to the issues in question
Are there facts/ evidence available and accessible to verify the cause
CONCLUSIONS
Conclusions
CONCLUSIONS
Conclusions:
Delay Analysis comes in many guises all with their advantages and
disadvantages