Risk & Delay Claims
Filing a delay event and requesting an extension of time
Video walkthrough for this article has not been recorded yet — the written steps above are the full guide in the meantime.
The Delay events tab is where you document something that actually happened and track it through to an extension of time (EOT), the way a real claims process expects.
Steps
- Log the delay event — who's responsible for it (owner-side, neutral like weather, or contractor-side), when it happened, when notice was given, and what it's linked to (a change order or RFI, if any).
- Jig calculates your notice deadline and flags late notice automatically — it won't bar the claim for you, it just makes sure you see it.
- Attach a Time Impact Analysis if you need to show the schedule effect — a TIA projects the impact without touching your live, working schedule; running a new one never overwrites the last.
- Move the event through its stages: identified → notified → assessed → EOT determined → closed. Days granted only go up on their own — if you ever need to walk a number back, there's a separate, clearly labeled override action that requires an explanation.
This tab is also office-only.
Was this helpful?
Thanks — that helps us fix it.