Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Concurrent Delay and Dominant Cause

6 replies [Last post]
David Barker
User offline. Last seen 7 years 12 weeks ago. Offline
Joined: 4 Sep 2007
Posts: 27
Groups: None
How does one determine the dominant cause?

Is it simply first event dominates until overtaken and therefore substituted by subsequent events or are their far more complicated iterations to consider?

Replies

Andrew Flowerdew
User offline. Last seen 3 years 34 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
I think Clive has got it it one!!!!!!

Not an uncommon situation unfortunately.
Clive Randall
User offline. Last seen 17 years 29 weeks ago. Offline
Joined: 15 Aug 2005
Posts: 744
Groups: None
probably the same reason as the Engineer is able to have an out of body experience and become impartial when assesing claims.
David Barker
User offline. Last seen 7 years 12 weeks ago. Offline
Joined: 4 Sep 2007
Posts: 27
Groups: None
Gentlemen,

Each month the Contractor applies for payment, within that payment application is usually an amount for Variations, Day works & Claims. This sum is usually backed up by an AI Schedule and a Claim Summary log identifying the value of each event and each event would probably have its breakdown in some cursory format, Day works dockets, vouchers, invoices etc, there may even be an attempt at estimating an amount or attaching some other records, nevertheless some form of detail.

Usually at the same time (or at intervals to suit the Contract notice requirements) a monthly progress report is being submitted. There is usually a section in that report that says matters affecting progress with a no blame narrative of what happened during the month as a record. Furthermore, attached to the report is the updated as built program and various other logs such as Drawing register, AI schedule, RFI schedules (Reqests for Information and Requests for Inspection), Claims log, Labour and Plant logs etc. You want Logs in this report, just ask and they can usually be provided. The record in my experience is maintained. You just have to be willing to roll your sleeves up an dig. Oh and by the way to know what you are looking for helps.

The above information provided, whether believable or not, is/are detailed particulars (bear in mind under professional ethics misrepresentation is abhorred and if criminal or negligent can be prosecuted).

What I want to know is why the Engineer always hides behind a veneer of rhetoric and this above information is never deemed the detailed particulars required by the Contract?
Andrew Flowerdew
User offline. Last seen 3 years 34 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
David,

Your post brought a smile to my face!

You have to read your contract and determine if it is up to the contractor to prove his entitlement to an EoT or, as is usually the case, it is up to the contract administrator (CA) to assess the EoT.

In the latter case it is not up to the contractor to prove his entitlement to an EoT, but only to supply such information that is reasonably requested by the CA in order to allow the CA to properly assess the EoT claim himself.

Unfortunately, many CA’s don’t understand this and mistakenly avoid making any decision by claiming the contractor has not proved his case or similar.

The other mistake often made is that the CA wants "absolute" proof! They forget that the standard of proof is on the balance of probabilities only. Only in a criminal case does the burden of proof rise to “beyond reasonable doubt”. QS’s also frequently make this same mistake when dealing with monetary claims.

As for ‘dominant cause’ – if you’ve just read the recent Mirant Asia v Ove Arup case from the TCC, don’t go running away with the idea that it applies to EoT’s. The case was an assessment of damages, not an EoT case and the ‘dominant cause’ theory has often been used to assess damages – but has not been used as a basis to award an EoT. The wording of that case is very confusing, it can be read as applying to EoT’s, it can be read as not applying!!!! The judge uses the terms ‘critical delay’ and ‘dominant cause of delay’ in nearly the same breath. I only read the judgment twice and wouldn’t like to say either way.
David Barker
User offline. Last seen 7 years 12 weeks ago. Offline
Joined: 4 Sep 2007
Posts: 27
Groups: None
Roger Gibson, you replied that

“The ’Dominant Cause Approach’ as regards Concurrency, is generally expressed by Lawyers as,

"if there are two causes, the effective, dominant cause is to be the deciding factor".

Sounds simple doesn’t it, but as you say ’how Do we determine the dominant cause’.

This is determined by the facts of the concurrent delays in question, and not by a method of Delay Analysis.

Under most forms of contract an Extension of Time, should be awarded when an event occurs which is likely to cause a delay to completion of the project. This means that in the ideal world, a Contractor will be granted an EOT before the delay happens, and therefore concurrent delays and the ’dominant cause’, or any of the other concurrent delay approaches favoured by lawyers, such as ’Devlin approach’, ’Burden of Proof approach’ or ’Malmaison approach’ need to be considered.”

This is important as with most Construction Contracts and delay claims that I have had experience dealing with, the Engineer always maintains an extension of time can only be granted if the Contractor can provide evidence [within certain time limits or in the event of a continuous occurrence at intervals not exceeding a prescribed duration] that disruption occurred. Note the past tense!

I have on many occasions submitted notice of the Engineers delinquency in this regard, but, alas to no avail to date. I shall pursue our rights with more vigour in future.

Thank you DB.

ps Engineers take note? You shall determine, it does not say you may determine.
Roger Gibson
User offline. Last seen 7 years 41 weeks ago. Offline
Joined: 1 Jun 2001
Posts: 71
David,

The ’Dominant Cause Approach’ as regards Concurrency, is generally expressed by Lawyers as,
"if there are two causes, the effective, dominant cause is to be the deciding factor".

Sounds simple doesn’t it, but as you say ’how to we determine the dominant cause’. In my experience, it is determined by the facts of the concurrent delays in question, and not by a method of Delay Analysis.

Please bear in mind that for an Extension of Time, under most forms of contract an extension should be awarded when an event occurs which is likely to cause a delay to completion of the project. This means that in the ideal world, a Contractor will be granted an EOT before the delay happens, and therefore concurrent delays and the ’dominant cause’, or any of the other concurrent delay approaches favoured by lawyers, such as ’Devlin approach’, ’Burden of Proof approach’ or ’Malmaison approach’ need to be considered.

Roger Gibson