Delay and EOT Process¶
Purpose¶
Record a delay event and, where appropriate, claim additional time and cost for it.
Prerequisites¶
None beyond the project and, ideally, evidence of the delay.
Role required¶
Super Admin or Admin.
Steps¶
- Record the delay event — cause, relevant dates, responsibility, evidence.
- If more time is needed, submit an EOT request, linking it to the delay event.
- Track the EOT request through Submitted → Under Assessment → Granted or Refused.
- If there is a cost impact, raise a loss and expense claim linked to the delay event or EOT request.
Expected result¶
A recorded delay event, with a decision recorded on any linked EOT request, and a generated decision notice once decided.
Linked modules¶
- Delay and Extension of Time
- Programme — a granted EOT can move programme dates
- Risks
Common mistakes¶
- Raising an EOT request without linking it to the delay event it stems from — linking keeps the evidence trail clear.
What to do next¶
Update the Programme if the EOT decision changes key dates.