Delays

Many contracts give a short window, often counted in business days, to notify a delay after you become aware of it. Astruct reads the project mail for the moment that happens.

What counts as a potential delay

• Plant or equipment unavailable, such as a tower crane out of service during your allocated time.
• Late access to the work area, such as a slab edge handed over later than programmed.
• Late information, such as an RFI response or a revised drawing that holds up work.
• A direction or variation that adds work or changes the sequence.
• A programme update that moves your activities.

What Astruct records

• The cause and the evidence for it, quoted from the source.
• The date you became aware, with the email or document that shows it. This is usually the date the clock starts.
• Updates that change the likely delay, such as a second revised handover date.

Checking the effect

Astruct flags a potential delay. Whether it actually delays completion depends on your programme and what else is happening. Ask in a chat, for example does the L6 handover delay us to practical completion?, and Astruct will reason it through from the programme it has. Your team decides whether to notify.

For the notice itself, see Notices of delay and EOT claims.