AI for Programme Narrative Writing

A programme narrative is the prose that explains the programme. Not the bar chart, the words: what moved, why, what it means for completion, and what you are doing about it. It is a separate discipline from building the programme itself, and it is the one planners tend to like least. It is also, when a job goes wrong, the document that gets read most closely, because the monthly narratives are a contemporaneous record of what everybody knew and when. That is worth sitting with. A narrative written to sound reassuring in month seven is evidence in month nineteen. WORKED EXAMPLE: THE SAME MONTH, WRITTEN TWICE Month 7 of 14 on a distribution centre. Frame complete. Envelope two weeks behind. One compensation event notified and not yet assessed. Completion still shown as programmed. Here is the narrative most people write: "Good progress has been made during the period. The steel frame is now complete and the envelope package is progressing well. Some minor delays have been experienced due to adverse weather and material deliveries. The team continues to work hard to mitigate these issues and completion remains as programmed. The compensation event notified last month is being progressed with the Project Manager." Read it as an auditor would. It says nothing. Which envelope activity, behind by how much, against what float? Was the weather exceptional or just weather? What does "mitigate" mean in practice? If completion remains as programmed, what absorbed the two weeks? And if the compensation event is not assessed, what happens to the date if it is refused? Every one of those questions gets asked eventually. The narrative that dodged them looks, in hindsight, like it was written to avoid them. Here is the same month written properly: "Steelwork completed 3 July, two days ahead of the Accepted Programme. Cladding installation to the north and east elevations is 14 days behind the Accepted Programme. The cause is the late release of the revised parapet detail (RFI-0112, issued 26 June against a requested date of 12 June). Cladding was the driving activity on the critical path from week 24. The 14 days have been absorbed by resequencing: internal blockwork has been brought forward from week 32 to week 28, using the float previously held on that activity. Completion is therefore unchanged at 19 December. That resequencing consumes the whole of the blockwork float, so the path through blockwork is now critical and any further delay to either activity will move Completion day for day. Compensation event CE-014 (parapet detail delay) was notified 27 June and remains unassessed. Our quotation of 4 July sought no extension of time on the basis of the resequencing above, but did seek the associated cost. If the resequencing does not hold, a time quotation will follow. Action required: the Project Manager's assessment of CE-014 is now 11 days beyond the period in clause 62.3. We have written separately on 14 July." Same facts. The second one names the activity, quantifies the delay, identifies the cause with a document reference, explains what absorbed it and what that cost in float, states the contractual position honestly, and ends with a specific ask. It is also longer, more uncomfortable to write, and much harder to argue with in eighteen months. WHAT MAKES A NARRATIVE HOLD UP Name the activity, not the package. "Cladding to north and east elevations" beats "the envelope". Quantify against the Accepted Programme, not against last month's feeling. Give the cause a document reference. An RFI number, a date, an instruction. Assertions without references are opinions. Say what happened to the float. This is the one people omit and it is the one that matters. Absorbing a delay is not the same as not having a delay, and a narrative that reports an unchanged completion date without saying what it cost is misleading by omission. End with the ask. What do you need, from whom, by when. WHERE AI HELPS, AND WHERE IT WILL BURY YOU It helps with the writing. Give it the facts above as bullets and it will produce clean, structured prose in the right register. That is genuinely useful, particularly for planners who find the writing a chore. It will also, left alone, produce the first version. Vague, positive, reassuring, and hedged. That register is what most training text sounds like, so it is the default it reverts to. If you paste in thin facts you will get comfortable prose, and comfortable prose is precisely the failure mode this document has. And it cannot do the analysis. Whether cladding is genuinely critical, how much float blockwork actually had, whether the delay is concurrent with something of your own making, all of that comes from the programme and from someone who can read it. AI writing a narrative that asserts a delay was critical, with no analysis behind it, is writing a claim you cannot support. WHEN NOT TO USE AI HERE Where the narrative is going into a claim or a dispute. At that point the words are evidence and they should be yours, or your advisers'. Where you do not yet know what happened. A narrative written from incomplete facts reads as confident and commits you to a version of events you may have to retract. FREQUENTLY ASKED QUESTIONS What is the difference between a programme narrative and a progress report? The narrative is about time: the programme, the critical path, float, and the causes of movement. The progress report is the broader monthly document covering progress, commercial position, safety, quality and risk, and it usually contains the narrative as one section. Different audiences too. The narrative is read by planners, contract administrators and, later, by anyone analysing delay. Confusing the two produces a narrative padded with information nobody reads it for. Should the narrative admit our own delays? Yes, and this is the hardest discipline in the job. A narrative that only ever reports employer-caused delay is not credible and it destroys your position when a genuine claim comes along, because the pattern is visible across twelve months of reports. Recording your own delays accurately costs you nothing you were going to keep, and it makes every other statement in the document believable. Concurrency is a complicated area and how it affects entitlement is a technical and legal question, so record the facts accurately and take advice on what they mean. How long should a monthly narrative be? As long as the movement requires. A quiet month where everything tracked the programme is three or four honest paragraphs. A month where the critical path changed needs the full treatment, because the reader has to be able to reconstruct what happened without you in the room. Length is not the measure. Whether a stranger could follow the logic in a year is the measure. Can AI identify the critical path from a description? No. The critical path comes from the programme logic, through a forward and backward pass, not from a description of what feels important. AI given a written summary will produce a confident statement about what is critical and it will frequently be wrong, because activities that look important often carry float and unglamorous ones often do not. Get the critical path from the programme, then use AI to write about it. What if the client disputes the narrative? Get the disagreement recorded in writing at the time. Unchallenged narratives tend to be treated later as an agreed account, which cuts both ways: it is exactly why you should object promptly to someone else's narrative that misstates the position, and why your own should be defensible when it is written rather than when it is challenged.