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
Member for
17 years 3 months
Member for17 years3 months
Submitted by Samer Zawaydeh on Wed, 2009-07-22 14:52
Member for
18 years 5 monthsRE: Claim
You may please go through book by Roger Gibson on "Extension of Time and Prolongation Cost".
Its cheap compared to other books on contract.
Member for
19 years 10 monthsRE: Claim
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
Member for
17 years 3 monthsRE: Claim
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