Build the factual sequence first
Identify what happened, when the team knew about it and which records establish those dates. Distinguish requested information dates from agreed commitments. Keep correspondence, drawing registers and field records connected to the event. At this stage, record uncertainty rather than writing a conclusion the available evidence has not yet supported.
Find the affected work
Examine the relevant schedule status and the conditions at the workface. Was predecessor work complete? Were materials and access available? Could unaffected work continue? These questions help establish whether an event changed a particular activity, its sequence or its resource needs. They also prevent the event duration from being automatically treated as movement in the project finish.
Explain the analysis within its limits
Preserve the relevant schedule versions and document the method, assumptions and modeled connections used in the assessment. Separate modeled impact from subsequent field history. The appropriate method depends on the assignment and available records. Technical schedule analysis does not by itself establish contractual entitlement or liability; those questions need the applicable contract and appropriate professional review.
Bring it to the next conversation.
- Preserve the relevant records and programme.
- Trace the event to specific work.
- Separate technical effects from contractual conclusions.
From the Hexifyer team. Examples are illustrative and do not identify client projects. Project requirements and professional responsibilities are agreed for each engagement.