The Most Important Document in a Schedule Submission

The most important document in a schedule submission isn't the schedule.

It's the contractor's narrative.

When a contractor submits a schedule update, it usually comes with a narrative. Most reviewers read it once, note a few things, and move on to the data.

That's a missed opportunity.

The contractor narrative is one of the most underutilized tools in the schedule review process. Not because it lacks value — but because most teams don't carry it through the full analysis.

Here's how it should work.

When the narrative first comes in, it's telling you what the contractor thinks happened. Delays, impacts, recovery efforts, milestone shifts. Some of it lines up with the data. Some of it doesn't. That gap between what the narrative says and what the schedule shows is where the real review starts.

One of the first things you should do is identify the delay claims and impact statements, then bring them to the project team. Are these delays real? Does the owner see it the same way? The contractor's version of events isn't automatically the truth — it's their perspective. Getting the owner's take early shapes how you interpret everything that follows.

Then take it to the contractor. In the schedule review meeting, go through each point in the narrative. Get their more detailed perspective on each delay, each impact, each recovery claim. Sometimes the narrative just doesn't have enough detail to clarify what's going on. Having face time with the contractor and extracting that information point by point builds a much clearer picture than the written narrative alone.

From there, carry it through the entire review. Progress analysis, schedule changes — if the contractor mentioned a two-week delay to structural steel, you should see it in the data. If the narrative says one thing and the schedule shows something else, that's a finding.

Longest path analysis — if the contractor identified milestone impacts, those should be traceable through the driving paths. Milestone variance — their statements about milestone movements should be validated or challenged by the actual data.

And when it's time to write your deliverable, the contractor narrative is where you started and where you finish. Your analysis should respond to it, incorporate the project team's perspective, and present findings in context.

The contractor narrative isn't a formality. It's the thread that connects every step of the review — from first read to final deliverable. Whether it's detailed, thin, or missing entirely, it's telling you something.

Next time a schedule update lands on your desk, start with the narrative. Carry it through the entire process. You might be surprised how much it changes your analysis.