Skip to content

Claim

James YoungMember for 18 years 4 months
Created
3
1
0
Hello all,

I am asking for some advice really, i am trying to get some experience in delay/claims programmes,

I am currently putting together a as-built programme to prove that the contractor was in delay, i have been reading through the site diaries & emails to see what activities happend when.

Is there anything else i should be doing to help with this claim, any tips or advice would be great.

Many thanks

J

3 replies

Oldest first
  1. 0
    Samer Zawaydeh ·
    Dear James,

    You can start with following these basic requirements that were handed over to me during on seminar:

    1. Must be Based on Contract Clauses.
    2. Timely Notice Required.
    3. Proof of Entitlement
    4. Proog of Damages
    5. Cause and Effect Relationship Required
    6. Burden of Proof
    7. Mitigation Requirements.

    Follow these steps for each event that you have. Compile the supporting documents and then you start considering them in your As Built Program.

    We will make sure that you get the best advice. The more you ask the better information you have.

    With kind regards,

    Samer
  2. 0
    Mike Testro ·
    Hi James

    Not heard from you for a while.

    Samer’s advice is correct for the contractual veiwpoint but you need some more nitty gritty advice.

    An As Built Programme is only the Start.

    To set this up start with a Spreadsheet - I know you only have excell but Lotus 123 will do it much more elegantly (£86.00 worth the investment for the download)

    Set Down in columns.

    Doc Ref - Where the data is from
    Description - what work is described
    Activity - Cross reference to the programme activity.

    From this starting point you can establish the days when work on any activity is being done.

    This data can be transferred to the barchart to compare the As Planned v The As Built (don’t ask me how - I have been doing this for years and i am not about to pass the secret on)

    Now the real task begins:

    Set up a detailed Events Schedule on a spreadsheet -
    Set down a number of column headings:

    Date
    Doc ref
    Sent From
    Sent To
    Desription What is said in the document
    Start Date When the event started - not the same as the Doc date - an AI could be retrospective.
    Lead Time How long before the changed work can be started
    Task Imopacted A description of the activity likely to be delayed.

    Now you have the starting point for a delay analysis which - following Samer’s points may lead you to a succesful outcome.

    Best regards

    Mike Testro
  3. 0
    A D ·
    You may please go through book by Roger Gibson on "Extension of Time and Prolongation Cost".

    Its cheap compared to other books on contract.

Log in or join to reply

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

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