Start with a chronology, not a conclusion
Record what information was required, when it was expected, when it arrived and what work depended on it. Distinguish a requested date from an agreed commitment. Keep drawing registers, correspondence and contemporaneous site records linked to the event. The aim at this stage is a factual sequence, including uncertainties, rather than a statement that every day of late information caused a day of late completion.
Find the work that was actually affected
Suppose a drawing for one equipment base is issued late. Was the workface otherwise ready? Were access, materials and preceding activities available? Could unaffected work continue? Examine the relevant schedule status and site evidence around the event. These questions help identify the affected activity and whether the event changed its timing, its sequence or the resources needed to execute it.
An event date is the beginning of the explanation, not the whole explanation.
Preserve the schedule basis
Retain the relevant schedule versions and document the assumptions used to examine the event. Where a modeled sequence is introduced, explain how it connects to existing work and how its durations were established. Distinguish the modeled effect from what later occurred in the field. The suitable analysis method depends on the assignment, available records and applicable project requirements; one approach should not be treated as universal.
Explain the result within its limits
Separate the event’s timing, its effect on affected work and any movement in the relevant completion milestone. State missing records and material assumptions. A clear technical explanation helps the team understand what the evidence supports and what remains unresolved. Schedule analysis alone does not determine contractual entitlement, liability or a right to payment; those questions require the relevant contract and appropriate professional review.
- Preserve the contemporaneous schedule and records.
- Trace the event to specific affected work.
- Separate modeled impact from contractual conclusions.
This article is general planning commentary. Project requirements and engagement methods are defined for each assignment.
