CU-TOOL-001 / Contracts & Claims / Beta
EOT / Delay Event Analyser
Structure an event record, check its gross duration and review the information still needed.
Version 0.1.1 · Last reviewed
Calculations run in your browser. Inputs are not uploaded or saved; refreshing clears them.
01 / YOUR INPUTS
02 / MATHEMATICAL RESULT
Your result will appear here.
Enter your inputs and calculate. Changing a value clears the previous result so it cannot be mistaken for an updated calculation.
Calculation methodology
- Gross event days = end date − start date + 1 (both dates included). This is the event span, not assessed critical delay.
- Notice elapsed days = notice date − event start. A notice is within this modelled period if elapsed days ≤ the entered period.
- The responsibility label repeats your selection. Critical-path impact and evidence are recorded as inputs; neither is established by the tool.
Assumptions
- Event start is used only as a proxy for the notice trigger. The actual contractual trigger may differ.
- Notice counting excludes event start and includes every calendar day, without weekend adjustments.
- Same-day events count as one gross day. Notices issued on the trigger date have zero elapsed days.
- Evidence is self-reported. No documents are uploaded or checked.
Worked example
Inputs: Event: 1–5 September 2026; notice: 4 September; notice period: 7 calendar days.
Result: Gross span = 5 days. Notice elapsed = 3 days. Within the modelled 7-day period; no EOT entitlement or critical delay is determined.
Contractual interpretation
Questions about this tool
Are gross event days the EOT to request?
No. The span does not measure critical-path impact, causation, mitigation or overlapping events. Project-specific programme and contractual review are still needed.
Does selecting Employer prove responsibility?
No. The classification is explicitly user-reported and needs supporting records and review.