Schedule Narrative
Last reviewed 9 September 20261,940 words9 min read
The report that goes with the programme; what reviewers look for
🟩 In one line: The narrative is the written explanation of what the programme shows and why — for a baseline, the method and basis in summary; for an update, what moved, what caused it, what the critical path is now, and what you're doing about it. Reviewers read it before opening the XER; a good one answers their questions before they're asked.
👤 Who this is for: Juniors writing their first one; mid-level planners who write one every month and want it to land; seniors reviewing a contractor's narrative for what it avoids saying. You should know statusing-a-schedule and monthly-update-checklist.
First, let's be honest about why this page exists
Most narratives are either two paragraphs saying "progress is ongoing, the programme is updated" or thirty pages of copied progress percentages with no sentence about the critical path. Both get rejected or, worse, accepted and ignored.
The narrative is where the programme becomes an argument. A reviewer who understands your critical path from page 2 will trust your XER. One who has to find it themselves will find something else too.
🟨 The standard — what "good" looks like
| Source | What it requires (paraphrased) |
|---|---|
| FIDIC 1999 Cl 8.3 | Supporting report with the programme: general description of methods, stages, and estimate of Contractor's personnel and equipment |
| FIDIC 2017 Cl 8.3 (check the edition in your contract) | Supporting report expanded: methods, resources, and — for revisions — a description of changes since the previous programme |
| FIDIC 1999 Cl 4.21 / 2017 Cl 4.20 | Monthly progress report: progress, comparison with programme, delays, remedial measures |
| NEC3/NEC4 Cl 32.1 | Revised programme shows actual progress and its effect, effects of implemented compensation events, how the Contractor plans to deal with delays and correct defects, and other changes |
| SCL Protocol 2nd ed., Part B Guidance, updating and record-keeping | Updates accompanied by an explanation of changes to logic, durations and calendars, and of the current critical path |
| Typical Gulf client specifications | Fixed narrative structure; critical path description; change log; look-ahead; often a signed declaration that logic changes are listed |
| AACE RP 29R-03 | Contemporaneous narratives are primary evidence of what the parties understood at the time |
🟢 Rule to remember: every narrative states the data date, the forecast completion, the variance, the critical path, and every logic change — in that order, on the first two pages. Everything else is supporting detail.
How it actually works
Two narratives, two jobs.
| Baseline narrative | Update narrative | |
|---|---|---|
| Issued | Once per baseline revision | Every update (monthly, sometimes fortnightly) |
| Purpose | Explain method, sequence, basis; summarise SBM | Explain what changed and why; forecast; actions |
| Length | 15–30 pages | 6–15 pages plus appendices |
| Centre of gravity | Critical path and method | Variance, causes, critical path, changes |
Update narrative — the structure that works.
| Section | What goes in | Length |
|---|---|---|
| 1. Summary | Data date; contract completion; forecast completion; variance in days vs baseline and vs last update; overall % planned vs actual; one sentence on the driver | Half a page — the only page most people read |
| 2. Key dates table | Every contractual milestone: baseline, last forecast, current forecast, variance, trend | Table |
| 3. Progress | Planned vs actual by area/discipline; S-curve reference; manpower planned vs actual | 1–2 pages + tables |
| 4. Critical path | Describe the driving path in words from data date to completion; total float on it; what changed since last month; near-critical paths within 10–20 days | 1–2 pages — the heart of the report |
| 5. Delays and causes | Each delay event: what, when, cause, responsibility (factually), notice reference, impact on the path | Table |
| 6. Changes to the programme | Every logic change, duration change, calendar change, added/deleted activity, constraint added/removed — with reason. Schedule Comparison output in appendix | Table; never omitted |
| 7. Mitigation and recovery actions | What's being done; expected effect in days; who owns each action | Table |
| 8. Look-ahead | Next 4–6 weeks: key starts, finishes, dependencies on the Employer | Table |
| 9. Risks and concerns | Upcoming issues: access, drawings, approvals, materials; date required | Table |
| 10. Appendices | XER reference; Gantt (critical and near-critical filter, plus full); S-curves; histograms; Schedule Comparison report; Schedule Log | — |
Writing the critical path section. Say it as a sequence of activities and dates, not as a list of areas. "The critical path runs from data date through completion of Level 14 slab (forecast 12-Jun, ID ST-1400, -6 d), through structural topping-out (ST-1600), façade closure Zones A–C (FC-0300 to FC-0500), MEP second fix Level 12 upward, testing and commissioning of the chilled water system (CM-0200), to Taking Over. Total float on the path is -6 days, from -2 last month; the 4-day slip came from the Level 13 pour being delayed by rebar delivery (see 5.2)."
The change table. This is what reviewers check against Schedule Comparison. Don't make them find a discrepancy.
| Activity | Change | From | To | Reason |
|---|---|---|---|---|
| FC-0310 | Predecessor added | — | ST-1400 FS | Façade brackets require slab edge complete; missing in baseline |
| MEP-2210 | Duration | 15 d | 20 d | Subcontractor revised quantity; basis note updated |
| ST-1350 | Constraint removed | SOoA 10-May | — | Access granted early |
| CM-0200 | Calendar | 6-day 10 h | 7-day 10 h | Commissioning on continuous shift per method statement Rev 2 |
Tone. Facts, causes, actions. Past tense for what happened, future tense for what will. No adjectives, no blame language; responsibility stated by reference to notices, not opinion. "Rebar delivery for Level 13 arrived 22-May against required-on-site 15-May; see notice CON/N/041" — not "the supplier let us down badly".
📜 Contract points the narrative carries
| Point | Why it matters |
|---|---|
| Recording delay events with notice references | Supports the 28-day / 8-week clocks; a delay first mentioned in a narrative without a notice is a weak position |
| Stating "work proceeds against Rev 1 pending acceptance" | Prevents the "no programme" argument later |
| Declaring logic changes | An undeclared change discovered by the Engineer looks like manipulation even when it isn't |
| Forecast completion vs contract completion | Under NEC the programme must show planned Completion; under FIDIC a forecast beyond the Time for Completion is a notice trigger in itself (Cl 8.3 obligation to notify probable future events) |
🟥 Where people go wrong
- Not stating the critical path in words. "See attached Gantt" is not a critical path description. If you can't write it as a sequence, you don't understand it, and the reviewer will assume so.
- Omitting the change log. The reviewer runs Schedule Comparison, finds 40 logic changes you didn't mention, and every future narrative is read as concealment. List everything; include the boring ones.
- Reporting progress without variance. "Structure 62% complete" means nothing. "Structure 62% against 71% planned, -9%, driven by Level 12–13 pour cycle at 8.5 days against 7 planned" is a narrative.
- Forecasting by hope. Completion is 30 days late in the XER; the narrative says "the contractor is confident of recovering the delay". Either show the recovery actions with day values or report the date the schedule shows (forecasting-honestly).
- Copying last month. Reviewers notice the same paragraph three months running. Every section should be rewritten from the current data.
- Adjectives and blame. "Severe delays caused by the consultant's negligent review" — now it's a letter, not a report, and the facts get lost. State the dates and the notice reference; let them speak.
- Burying the summary on page 9. Data date, forecast completion, variance, driver — first half-page. Directors and Engineers read that and decide whether to read on.
⚖️ When you're challenged
"Your narrative says 'minor slippage' but the XER shows -22 days." "You're right, and the wording was wrong. The forecast is 22 days late against the contract date, 6 days worse than last month, driven by the Level 13 pour. Section 7 shows 14 days of recovery actions; the remaining 8 is the subject of notice CON/N/041."
"You changed logic on 30 activities and mentioned six." "The six in the table are the changes that affect the critical or near-critical paths. The full Schedule Comparison output is Appendix E with all 30. From next month every change goes in the table regardless."
"Why is the critical path different from last month?" "Last month it ran through structure. The Level 13 pour caught up and façade procurement slipped 9 days, so the path now runs through façade to MEP second fix. Section 4 describes both paths; the previous one is near-critical at 4 days."
"This reads like a claim document." "It reads like a record. Each delay is stated with dates and the notice reference. If we're responsible for a delay it says so — item 5.3 is our rebar procurement."
📄 Related pages
- Schedule Basis Memorandum — the baseline-stage document the narrative summarises
- Baseline Approval and Control — the third element of the submission
- Monthly update checklist — what to finish before writing the narrative
- Writing a progress narrative — the sentence-level craft
- Monthly Progress Report — where the narrative sits in the wider report
- Forecasting honestly — the forecast section without wishful thinking
- P6 Schedule Comparison — generating the change appendix
- Notice Requirements and Records — why every delay line needs a notice reference
✏️ Worked example
Summary page from Update 09, a commercial tower in Riyadh (anonymised, figures illustrative):
| Item | Value |
|---|---|
| Data date | 30-Sep-25 |
| Contract Time for Completion | 15-Aug-26 |
| Forecast completion (this update) | 06-Sep-26 |
| Variance vs contract | -22 days |
| Variance vs Update 08 (14-Aug-26 forecast → 06-Sep-26) | -6 days this period |
| Overall progress | 48.3% actual vs 54.1% planned (-5.8%) |
| Critical path total float | -22 days (from -16) |
| Driver this period | Level 13 slab pour 22-May → 30-May; rebar delivery late 7 days (notice CON/N/041) |
| Mitigation identified | 14 days: second formwork set Levels 15–20 (-9 d), façade Zone B resequenced (-5 d) — Section 7 |
| Employer dependencies due next period | IFC lift shaft drawings required 12-Oct-25 (ENG-3100); authority NOC for tower crane climb required 20-Oct-25 |
| Logic changes this period | 30 (6 on critical/near-critical paths, Section 6; all in Appendix E) |
The Engineer's review closed in one cycle with two comments, both on the change table. The previous month's narrative, which said "minor slippage, recovery in progress", had taken three cycles and produced a formal notice of concern.
📖 References
- FIDIC 1999 Cl 8.3, 4.21; FIDIC 2017 Cl 8.3, 4.20 (check the edition in your contract)
- NEC3 / NEC4 ECC Cl 32.1 (check the edition in your contract)
- SCL Delay and Disruption Protocol, 2nd ed. (2017), Part B Guidance — programme updating and records
- AACE RP 29R-03, Forensic Schedule Analysis — contemporaneous documentation
- Oracle, P6 Professional User Guide — Schedule Comparison; Schedule Log
From the field
Experience from working planners. Unreviewed — read it as experience, not guidance.
Add what you know about schedule narrative. What worked, what the consultant pushed back on, what you would do differently next time. A paragraph is plenty.
Contributors get their name and one link on the site — your own templates, course or consultancy. We take nothing and hold nothing.
Add your experience