Skip to content
ProjectControls.com
Forensic Claims Analysis

Contents of EOT claim

In the Open Standard
Sree BinduMember for 11 years 11 months
Created
5
2
0

Dear all,

Can some one please help me with the contents for an EOT ? Below is my idea. 

1. Executive Summary

2. Project Details (contracting parties, time, value etc)

3. Contract Representations (clauses etc)

4. Scope of work

5. Baseline Programme/Planned programme/ planned sequence of works

6. Procedure for EOT claim analysis (method etc)

7. Contractor's claims (delay events description)

8. Delay Analysis

9. Costs

10. Conclusion

Save Follow Follow forum Report
Reply New topic

5 replies

Oldest first
  1. 0
    Anoon Iimos ·
    #1

    The reason why you seek for

    The reason why you seek for an EOT is simply because there is a "DELAY". If things only happened exactly as planned, then who needs an EOT? IMO, the most important thing to consider is your Actual Schedule or Performance compared against Planned Data. And where the delays should be attributable to?
    Report
  2. 0
    Mike Testro ·
    #2

    Hi Sree - welcome to planning

    Hi Sree - welcome to planning planet.

    You have presented a text book list but no eot assignment is unique and should not be limited to a text book approoach.

    Anoon has given good advice - I would only add:

    Stick to the FACTS

    Tell each story concisely - supported with charts where necessary 

    Best regards

    Mike Testro

    Report
  3. 0
    Tommy James Nuneza ·
    #3

    Anoon,It will really help if

    Anoon,

    It will really help if you can share information/documents where you sucessfull claim EOT.

     

    Thanks/Tommy

    Report
  4. 0
    Anoon Iimos ·
    #4

    Seriously? Why should I share

    Seriously? Why should I share for free if I had any? Well, honestly I don't have anything. I'm just talking about my personal opinion and I don't even care whether I'm correct or not. Anyway, an "EOT" should always be present in every project, otherwise, a project can never be completed or you'll just scrap it and go bankrupt (I guess nobody wants that). Hence, IMO, it is a process from subjective to objective. EOT or extension of time is always necessary to complete any job. Therefore it is a fact that may occur in every minute of the process of doing any work. Firstly, your Process or Plan of doing the project is subjective. The time you actually start the works, then you become objective. To be continued later...
    Report
  5. 0
    Anoon Iimos ·
    #5

    Oh, by the way, why there is

    Oh, by the way, why there is a need for a claim for an "Extension of Time" when time is continuously running  and no one can prevent it? And besides, everytime there is a delay in a project, consequently, time is literally extended without claiming or granting it. 

    Even if say, you were given or granted with a specific amount of time as extension to your original contracted time, I guess it is still not a guarantee that you will finish the project in the newly desired completion time, if there is no improvement in the actual performance of the works. 

    For me, it is all about budget or money and profits or losses. And of course Time has an equivalent amount of money. 

    So I guess it's about time to forget the term "Claim for EOT" or "Extension of Time" (Scrap it!). As whether you like it or not, time is always extended when you are not able to complete the project as originally promised (given with a contract and a specific amount of time and money). 

    If there is any delay, just determine what or who causes it and let them pay for it. And how do you determine if there is any delay? Well, of course you compare your plan with what's actually happening or facts. 

    Report

Log in or join to reply

ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.

Log inJoin free

Existing members: your original username and password still work. Forgot password?