Write an Extension of Time Assessment
Produce a detailed Extension of Time assessment analysing delay events, critical path impact, and contractual entitlement.
Editor: Owen HaggerLast updated
Overview
This workflow assists Contracts Managers in preparing a thorough EOT assessment that evaluates reported delay events against the contract programme. It analyses whether delay events sit on the critical path, determines the contractor's entitlement under the relevant contract conditions, and presents findings in a format suitable for submission to the Project Manager or Contract Administrator.
Want more templates like this?
Get new AI workflows and construction templates delivered weekly. Free.
Subscribe Free
No spam ever.
Prompt
You are an experienced UK construction Contracts Manager and delay analyst. Prepare an Extension of Time (EOT) assessment based on the following information: Contract Form: [CONTRACT FORM, e.g., NEC4 ECC Option C / JCT SBC/Q 2016] Project: [PROJECT NAME] Original Completion Date: [DATE] Current Completion Date (if previously extended): [DATE] EOT Claim Reference: [REFERENCE NUMBER] Delay Events Claimed: 1. Event: [DESCRIBE EVENT 1, e.g., Late design information for structural steelwork connections] - Date notified: [DATE] - Period claimed: [DURATION, e.g., 14 days] - Contract clause: [CLAUSE, e.g., Compensation Event cl. 60.1(3) / Relevant Event cl. 2.29.6] - Supporting evidence: [LIST EVIDENCE] 2. Event: [DESCRIBE EVENT 2] - Date notified: [DATE] - Period claimed: [DURATION] - Contract clause: [CLAUSE] - Supporting evidence: [LIST EVIDENCE] [Add further events as required] Programme Information: - Baseline programme approval date: [DATE] - Current accepted programme revision: [REV NUMBER] - Critical path activities affected: [LIST ACTIVITIES] Structure the assessment as: 1. Executive summary with recommendation 2. Contractual basis for EOT entitlement under the stated contract form 3. Chronology of events 4. Analysis of each delay event: a. Factual description b. Notification compliance (was it within the contractual time bar?) c. Critical path impact analysis (is the delay on the critical path or does float absorb it?) d. Concurrency assessment (are there concurrent contractor delays?) e. Entitlement determination (days recommended) 5. Cumulative impact and revised completion date 6. Summary table of events, periods claimed vs recommended 7. Supporting documents referenced Apply the SCL Delay and Disruption Protocol (2nd Edition) principles where relevant. State clear reasoning for any reduction or rejection of claimed periods.
Typical result
~6hby hand~2h 30mwith AI
A cautious typical estimate, including the time to gather the inputs and check the output. It varies with the job.
What it replaces: Writing an extension of time assessment from scratch.
What you still check
- Delay events tie to records and notices
- Critical path effects are shown, not asserted
- It's checked against the contract's EOT provisions. Take advice where needed
Use Case
Use when you receive an EOT application from a contractor or need to prepare your own EOT submission, and require a structured assessment of delay events against programme and contract.
When not to use it
Don't use it to decide entitlement. AI drafts and organises the analysis and the narrative. The contract administrator, project manager, QS or legal adviser makes the call.
On its own, it's also the wrong tool for a large or disputed delay claim. That needs a programme analysis by someone who can defend it. Check your contract and take advice.
Common mistakes
- Using the wrong programme. Assess each event against the accepted programme current at the time, updated for progress.
- Ignoring notice compliance. A strong event can fail on a missed notice, especially under NEC4 or an amended JCT form.
- Adding up the days claimed for each event when the events overlap, which double counts the delay.
- Skipping concurrency, or assuming there's no contractor delay in the period. The assessor will look for it.
- Letting the tool fill gaps. If a date isn't in your records, it shouldn't be in the assessment.
Frequently asked questions
- What is an extension of time in construction?
- More time to complete the works, because of an event the contract puts at the employer's risk, such as a late instruction or a change. It moves the completion date, which protects the contractor from damages for that period. It doesn't automatically bring extra money. Check your contract and take advice on what each event entitles you to.
- How do you calculate an extension of time?
- Identify the event, show which activities it affected, and test whether it delayed completion through the critical path or was absorbed by float. The SCL Delay and Disruption Protocol describes several delay analysis methods and suggests choosing one that suits the records and the timing. Check your contract and take advice on what the contract expects.
- What is concurrent delay in construction?
- Delay to completion caused by an employer risk event and a contractor risk event at the same time. In England and Wales the usual approach is time but no money for the concurrent period, but contracts are often amended on this point. Check your contract and take advice.
- Who owns float in a construction programme?
- It depends on the contract. The SCL Protocol's view is that, unless the contract says otherwise, an extension is only due once the delay uses up the float on the affected path. NEC4 protects the contractor's terminal float between planned completion and the completion date. Check your contract and take advice.
- Is the SCL Delay and Disruption Protocol binding?
- Not unless your contract brings it in. It's guidance, but it's widely used as a reference for good practice in UK delay disputes. Following it makes an assessment easier to defend.
Free newsletter
Get AI Tips Weekly
New construction AI workflows, prompts, and templates delivered to your inbox every week.
Subscribe FreeNo spam. Unsubscribe anytime.