Hi everyone,

My current project is ending on November 09, 2024.

It has 2 Milestones in which Milestone 1 will be completed before the end date.

And Milestone 2 is on hold but out of that around 30% will be released and te remaining 70% from Milestone 2 will be descoped.

What do you think should be the actio plan and how to deal with the EOT?

Please advise.

Regards

Sam

Hi

i just want to ask how to prepare EOT if the approved baseline programme is not logic. i mean there is a high float.

Is there any method to prepare EOT without approved baseline?

Thank You

Mike,

In your post It is very clear you work for the client side.

That is the best thing to do.

In my previous post, I’m referring to work in the contractor side, meaning, contractor claim presentation will not show detrimental concurrent delay, the other way around is the work of an idiotic contractor forensic claim analysis.

Cheers,
Charlie

I also haven’t read the whole thread either… just the last couple of postings.

"Why will a contractor forensic claim specialist show in TIA that the contractor was (in) delay?"

I thought the first step in TIA was to update the programme with achieved progress to the point just prior to the delaying event happening. This means that any default by the contractor, for instance ‘delay in procurement of long lead items, delay in mobilization of essential personnel, delay in submission of shop drawings, etc. etc. etc’ will manifest themselves in the progress reported. Progress data is usually a matter of contemporaneous record so not so easy to fudge. Anyone doing so is very likely to get quickly found out in almost any tribunal and then their expert opinion, whether or not good or bad on the whole, will be questionable.

Whilst I dislike quoting Pickavance, with regard to Time Impact Analysis and concurrency (which I think is where the thread started) at paragraph 14.319 he says:
”This simple contemporaneous approach to delay analysis allows assessment to be made of three important aspects, which tend to be unavailable with other methods:
1. the actual state of progress at the time the event was initiated;
2. the changing nature of the critical path as a result of delays to progress and acceleration; and
3. the concurrency of delays to progress and to completion.

Regards

David

Hi Charleston

You asked "why will a contractor forensic claim specialist show in TIA that the contractor was (in) delay"

Because his duty as an expert is to the tribunal - not the contractor or any other party who is paying him - to assist the court in reaching a just conclusion.

On a more practical level all credibility is lost if I do not include contractor culpable delays in the analysis.

If the Employer knows of contractor culpable delays and I have not accounted for them then my work is worthless.

Best regards

Mike Testro

Hi Charleston

Welcome back to the forum.

As usual you have jumped in without reading the whole thread.

Go back to page one and then if you have anything worthwhile to add on the subject of concurrency I will be pleased to read it.

As will Atem.

Best regards

Mike Testro

Hi Hatem

Who owns the float was the subject of a very lengthy thread earlier this year - it was finally resolved as the float belongs to the project on a first come first served basis.

A delay event has to use up all float before it affects the critical path.

Provided the events are impacted in strict chronological order then the float will be allocated correctly.

Regarding the method of analysis then since the works are complete a Time Impact Analysis is the most suitable provided the As Built Records are up to it.
Impacted As Planned is not suitable at this stage as it will not reflect waht actually happened and - as far as the Employer is concerned - will most likely result in a longer period than required.

Not having an agreed programme as a baseline could be a problem in some forms of contract - in any case it is not too late to agree one now - why not bring in an independant planner to review the original programme and turn it into an agreed baseline BEFORE any form of analysis starts.

Concurrency is a real issue as - in the UK at least - the rules are constantly evolving.
However following the "Dominant Delay" method will keep things more or less on track.

I hope this helps

Best regards

Mike Testro