How to write a construction schedule narrative an owner can use

The first paragraph of the monthly schedule narrative is the one the owner carries into the next meeting. If it opens with an activity count or a list of every bar that moved, the owner either works out the effect on their milestones alone or repeats a guess. That paragraph should name the milestone that moved, the work behind it and the decision the owner has to make, with the activity comparison kept behind it as backup.

Write the rest in a fixed order. Movement comes first and explanation second, only where the records support it, with references close enough that a reviewer can check a statement without redoing the analysis.

State the comparison basis up front

Give the project, report period, previous and current data dates and the revision status of each file. If the current update is still proposed and not yet accepted, put that in the first paragraph.

Someone opening the report after closeout has to be able to find the two files it describes, so use revision references and drop labels like "latest update". Name the milestones in scope using the project's own terms, whether that is phased turnover, commissioning, beneficial occupancy or another handoff the owner tracks separately from overall completion.

Lead with the change that matters

The first paragraph gives the milestone movement, the work driving it and the open decision or question. A hypothetical example, with made-up Activity IDs:

"In the current update, commissioning milestone CX-900 moves from October 20 to October 25. The chiller delivery activity HV-310 and the chiller startup HV-330 that follows it both moved in the same update. The team needs to confirm the revised chiller delivery commitment before deciding whether to resequence startup and testing."

That paragraph reports what the files show and what has to happen next. It does not say the delivery revision caused all five days, assign liability or promise that resequencing recovers the date. If the analysis supports a more specific cause, state it with its basis, and if it does not, leave the question open in the text.

Word observations and explanations differently

Keep four kinds of statement apart throughout the report, and word each so the reader can tell which one they are reading.

An executive summary has to be short, and that pressure tends to turn open questions into confident causes, so check each summary sentence against the table above. When several changes overlap on one path, do not assign the same days to more than one activity, and state the method behind any attribution. If the analysis cannot split the movement cleanly, report the remainder as unattributed rather than spreading it across the parties or adding it to the largest share.

Use references that survive forwarding

Each material finding names the two files, the Activity IDs and where the supporting record is filed. The report should still make sense to someone who was not in the review meeting and receives it as a forwarded PDF.

A screenshot of a Gantt bar without the data date, milestone or layout settings tells that reader very little. For a delivery revision, keep the message with the original commitment and the message with the new date, and for a corrected actual date keep the basis for the correction. The narrative summarizes while the review record holds the detail, inside the project's controlled document system and away from public links.

Make each action finishable

"Monitor the critical path" is a standing duty and resolves nothing. Name the action that would close the question, such as confirming the equipment ship date with the supplier, checking whether a prerequisite approval has been issued, reconciling a duration forecast with the crew plan or modeling a proposed sequence. Give each a named person and a due date.

Mark a proposed recovery as proposed. A modeled improvement still has to be checked against crews, access and the assumptions in the model, and the owner should know that before anyone relies on the earlier date.

Keep the summary short and the backup complete

Not every activity change belongs in the executive paragraph. Group related changes under the milestone or decision they affect and put the detail in a supporting section. A workable reading order runs from the update basis and significant milestone changes, through the main findings with references, to actions and open questions, with the technical detail last. If the contract prescribes a report format, keep its sections and make the same distinctions inside them, and check that every figure in the summary matches the backup.

Check the draft before it goes out

Check names, dates, units, file references and milestone selection. Then read it as someone who does not know the job and ask whether they could separate what the files show from what the team believes and from what is still under investigation.

The scheduler should review every material explanation and look for context that is missing. Generated text reads fluently whether or not the cause is right, so check the claims and ignore how smooth the prose sounds. Keep the issued revision, and if a later review changes a conclusion, send a correction to the people using the report.

Draft next month's narrative in Pathizer

We built Pathizer to draft the executive narrative from each analyzed schedule update, for the scheduler to review before anything reaches the owner. Angel Pans, Pathizer's co-founder, has over a decade in project controls across $2B+: AECOM, a $600M South Florida portfolio, and USACE RMS/SDEF federal work. Start a 60-Day Pilot at pathizer.com/pilot with no card, load an update your team has already reported on, and set Pathizer's draft beside the narrative you issued.