Separate schedule impact from entitlement
Nexora includes delay-analysis workflows alongside updates and recovery planning. The engineering task is to assess an event against a defined programme and explain any movement in the forecast.
A calculated impact does not by itself establish contractual entitlement to an extension of time or compensation. Notice provisions, responsibility, concurrency, mitigation and the applicable contract need their own assessment.
Prepare the evidence before choosing the method
- The accepted baseline and relevant contemporaneous updates
- The agreed data date and scheduling settings
- Event start, finish, affected activities and supporting records
- Actual progress and other events in the same period
- Mitigation or recovery actions and their assumptions
When a time impact analysis (TIA) is appropriate, the event representation and the reference update must reflect the project circumstances. For windows analysis or other retrospective methods, programme history and the contract may require a different workflow. Do not choose a method solely because a tool can produce a diagram.
Worked example: a two-day event on a single chain
Illustrative calculation only; not a claim assessment or proof of EOT entitlement.
Assume one critical chain: excavation takes three working days, reinforcement three, and concrete two. A two-working-day access event prevents reinforcement from starting after excavation. With no float, parallel path, mitigation or other event, the chain moves from eight to ten working days.
| Scenario | Chain duration | Technical movement |
|---|---|---|
| Reference programme | 8 working days | — |
| Programme with the access event | 10 working days | +2 working days |
A real network can give a different result because of float, calendars, parallel critical paths, changed progress or concurrent events. Review the actual programme before drawing a conclusion.
Build a technical analysis that can be checked
- Identify the reference programme, revision and data date.
- State the event facts and the assumptions used to represent it.
- Compare the affected path and completion forecast before and after the event.
- Consider other events, actual progress and mitigation.
- Present the schedule result separately from the contract assessment.
Use contemporaneous updates to maintain the programme history, and recovery scenarios to document proposed mitigation. Keep copies of inputs and reviewed outputs with the project records.
Common questions
Does a two-day activity delay always mean two days of EOT?
No. Float, critical paths, concurrent events, mitigation and contract requirements can change the assessment.
Is TIA the right method for every project?
No. Select the method using the contract, available records and project circumstances. A prospective TIA and a retrospective assessment answer different questions.
Does Nexora determine contractual entitlement?
Schedule results provide technical support. Entitlement remains a contract assessment supported by the relevant facts and records.
Explore the workflow in Nexora
Bring a representative work package and review the assumptions with your project team.