Date posted: 12 September 2013
ENSURE YOU NOTIFY DELAY STRICTLY IN ACCORDANCE WITH THE CONTRACT MECHANISM
To successfully claim an Extension of Time there are a number of things we would suggest you should do. Some because they make sense practically and some because you are required to do so in order to ensure your claim can succeed.
Most standard and bespoke forms of Main Contract and Sub-Contract which contain Extension of Time provisions comprise the following elements:
The obligation to notify is commonly a condition precedent (or “time bar”) to receiving any Extension of Time.
To be deemed a condition precedent it is often stated that a clause should set out a timescale for action (for example, a notice) and explain what will happen (a Claimant losing a right) should the action be carried out outside the prescribed time frame. However, if the impact of failure can possibly be simply implied from the words, such a condition precedent may still be deemed to have force.
There have been a number of cases which have confirmed the view that if properly drafted, such clauses are enforceable and the failure to comply with the notice provisions in a Contract will result in a Claimant losing its rights under the Contract.
These cases include Multiplex Constructions (UK) Limited v Honeywell Control Systems Limited, Steria Limited v Sigma Wireless Communications Limited, Education 4 Ayrshire Limited v South Ayrshire Council and City Inn Limited v Shepherd Construction Limited.
So, the first piece of advice in our suggested best practice is – Ensure you notify delay strictly in accordance with the Contract mechanism.
PREPARE A FULLY LINKED PROGRAMME AND MONITOR PROGRESS AGAINST IT
Practically speaking, however, you need to be in a position to know when a delay is going to have a critical effect on your ability to complete before any such notice can be issued.
To do this properly you need to have a fully linked construction programme to start with and monitor intended progress against achieved progress.
Modern programming software facilitates the production of such a programme and enables you to impact actual progress onto the programme to see what the impact of achieved progress is on the Completion Date. The updating (re-scheduling) of the programme is fairly straight forward and gives you a good, and importantly, sustainable indication of projected completion.
Our second piece of advice in our suggested best practice is – Prepare a fully linked programme and monitor progress against it.
Whilst this is often viewed as a time consuming task the benefits of having such a programme far outweigh the time and cost expended preparing such a programme at a later stage.
Ramskill Martin has Planning and Programming resources which are able to assist you in preparing these programmes efficiently and effectively in terms of both time and cost.
Whether you follow this advice (regarding the programme) or not, the next piece of advice should most definitely be heeded as it is the most common cause for failing to achieve an acceptable Extension of Time.
RECORD ALL EVENTS AND MATTERS WHICH CAUSE, APPEAR TO CAUSE OR HAVE THE POTENTIAL TO CAUSE DELAY
Quite simply, if you do not record the cause and details of the delay at the time retrospective collation is difficult, time consuming, expensive and often almost impossible to do properly.
Ramskill Martin have prepared a template referred to as a “D” Schedule which we use to assist our clients in recording delay information and any of our Consultants would be happy to discuss this with you.
It may be on final analysis that some recorded events did not cause critical delay but the time taken to record these events, at the time, makes such “unnecessary” effort miniscule compared to the time taken to look for such issues/evidence retrospectively. It really is better to have the information and not need it than to need it and not have it.
Failure to collate information, record progress and have a workable programme will often result in a final claim for time being global in nature with a high chance of failure.
We suggest you should record all events regardless of cause (Employer, Main Contractor, Sub-Contractor, You or whoever).
RECORD ALL COSTS ASSOCIATED WITH EVENTS WHEREVER POSSIBLE
Whilst not necessarily linked to claiming simply time, we would also recommend that when you record the event you record any specific costs associated with the event/matter.
Providing evidence of the direct causal link between a cost and event improves the chance of achieving an acceptable outcome.
So, our next item of advice is – Record all costs associated with events wherever possible.
RECORD WHEN CHANGES/VARIATIONS WERE CARRIED OUT ON SITE
Once your programme is prepared (in whatever detail you have adopted) and the project is progressing we would recommend that when a variation/change occurs you allocate the time effect to the various tasks on your programme and you record the events (on and off site) associated with each change. Record when the change was instructed, why did it arise, what tasks did it effect and why, what resources did it require, when was it carried out and record any other events associated with the change both on and off site.
The impact of change on the progress of the work needs recording at the time as often retrospectively this lack of detail can have a detrimental effect on claim preparation. Whilst it is straightforward to identify when the change was instructed, when it was carried out on site (which is far more important in an Extension of Time claim), it is often far more difficult and with this lack of detail has often caused our clients difficulties in the past.
Our next piece of advice therefore is – Record when changes/variations were carried out on site.
PRESENTING YOUR CASE
Once you have the fundamental information necessary you need to present your case.
In summary, here are our tips for ensuring the best possible outcome:
- Keep the submission clear, concise, factually based and rely as much as possible on contemporaneous records and the recollections of those on site.
- Provide a narrative explaining each of the delay events and sequence of events all of which should be cross referred to contemporaneous records, the recollection of those directly involved on the project and any programmes you have available. Ideally you would have all your progress programmes presented in such a way as to evidence both the cause of the delay and the effect.
If you rely on retrospective delay analysis do not present a claim which is over reliant on such a claim; the courts do not like them so why should the recipient of your claim?
If applying retrospective delay analysis techniques use the right method which will be dictated, to a large extent, by your records.
Focus on the critical delays; there are usually numerous delays on a project but only some cause critical delay. Including non-critical delay into a claim can cause a loss in focus and make the claim appear “flabby” and cause confusion or create the suspicion that there are issues with the claim.
In Summary, with regards to protecting yourself we suggest:
- Understand and comply with the Contract with regard to notices.
- Prepare a programme and keep it updated.
- Record all events and matters which cause, appear to cause or have the potential to cause delay.
- Record when changes/variations were carried out on site.
PRESENTING YOUR CLAIM
When presenting your claim:
- Keep to the facts.
- Explain your case clearly.
- Use all information collated.
- Use retrospective delay analysis with caution and do not be over reliant on it.
Article by: Nick Cheetham
|5/6 Heritage Business Centre
T: 01773 599 299
F: 01773 880 089
M: 07803 628177
|3 Hardman Street
T: 0161 932 1535
F: 0161 932 1401
M: 07753 837149
260 Ecclesall Road South
T: 0114 230 1329
F: 0114 229 5804
M: 07824 690101
|54 Clarendon Road
T: 01923 431600
F: 01923 431700
M: 07753 837148