On this page
The schedule file contains the model. The narrative explains how the model changed and what the team needs to do next. A good narrative lets someone who missed the update meeting distinguish actual progress, revised assumptions and unresolved decisions.
Begin with the data date, reporting period, current schedule identifier and comparison version. Keep those identifiers aligned with the file and transmittal. Then lead with the milestone movements that matter.
- 01Inspect the fileDates, logic, calendars
- 02Read the contractEdition, clause, exceptions
- 03Check the fieldSequence, access, resources
- 04Record the decisionOwner, evidence, next action
Use a repeatable structure
| Section | Answer this question |
|---|---|
| Status summary | What work actually started or finished during the period? |
| Milestone comparison | Which forecast dates moved, by how much and in what units? |
| Driving work | Which remaining sequence currently controls each key milestone? |
| Model changes | Which relationships, durations, calendars or settings changed? |
| Risks and decisions | What information or action is needed, by whom and when? |
| Recovery actions | What proposed or approved measures could improve the forecast? |
Use the project’s specified headings where required. This structure is an editorial starting point, not a substitute for the contract’s narrative requirements.
Replace vague explanations with traceable ones
Consider this fictional update: energization moves from June 10 to June 14. “Procurement delays continue” leaves the reviewer guessing. A better explanation identifies the equipment package, the revised delivery commitment, the affected activity IDs and the remaining installation and testing sequence.
It should also identify uncertainty. If the supplier has not confirmed shipment, write that explicitly and assign the next confirmation date. Do not present an unconfirmed promise as a verified actual event.
Separate movement from attribution
A milestone comparison shows what changed. It does not, by itself, allocate responsibility. If several changes occurred in the same update, explain them individually. An access change, corrected actual date and new calendar may all contribute to a different forecast.
Avoid arithmetic that adds every local activity delay into a project-delay total. Some work runs in parallel, some consumes float and some changes which path controls completion. Use the recalculated network and describe the assumptions behind the comparison.
Make the next meeting actionable
Close with a short decision register: decision needed, responsible party, required date, affected activity and consequence if unresolved. Reference the actual RFI, submittal, delivery or meeting record. A narrative becomes more useful when the reader can follow the evidence without searching separate folders.
Retain source records and prior narratives with the update series. The Society of Construction Law’s Delay and Disruption Protocol is a further reference on records and delay-management practice; it is not a universal replacement for project terms.
Use the baseline package guide for initial setup and recovery planning when the forecast needs intervention. Explore the Schedule Forensics library for the complete learning path.
Share this article