How to Document Schedule Impacts from a Change

Start with the current approved schedule and identify the activity, area, predecessor, successor, and planned dates related to the change. Note which schedule version is being used and when it was current.

Describe the event and its timing: when the condition or direction arose, when the team learned of it, and when the work could proceed. Separate actual observations from forecast effects.

• Schedule version and affected activity identifiers
• Event dates, notice dates, and relevant dependencies
• Work sequence or access condition that changed
• Available mitigation, resequencing, or recovery steps

Describe how the change interacts with the planned sequence, lead times, inspections, crew availability, and other trades. Identify what evidence supports the relationship and what information remains uncertain.

Avoid converting a calendar interval directly into project delay without checking the activity logic, float, concurrent work, and contract method for evaluating time. Where a proper analysis is pending, label the effect as preliminary.

Attach schedule updates, meeting notes, submittals, delivery information, notices, and daily reports that explain the event. Preserve the original baseline and each update so reviewers can compare what changed.

Coordinate the time record with the change-order scope and cost record. Schedule days, labor hours, and added cost are related but separate impacts; explain each using its own basis.

State the requested adjustment or explain that the analysis is still being developed. Follow the notice, update, and approval process in the contract, and keep the dated response or decision with the project record.

Schedule guidance here is general documentation information, not a determination of delay responsibility or entitlement. Have the appropriate project or scheduling professional review disputed impacts.