The schedule narrative: what each agency requires it to contain
Almost every scheduling specification read for this site requires a written narrative with the schedule, and the requirement is usually an enumerated list rather than a general instruction to explain yourself. Caltrans names twelve headings in a fixed sequence. SCDOT names nineteen items. CDOT names seven for a baseline and thirteen for an update. UFGS names eight as a minimum. PennDOT itemises seven.
These lists are the least compared part of a scheduling specification and the most consequential for a reviewer, because the narrative is where every requirement that a schedule file cannot answer is supposed to land. A duration cap is decidable from the export; why this duration is not. A constraint type is in the file; the reason for the constraint is in the narrative or nowhere.
This page sets the narrative clauses of sixteen public-agency documents side by side. The comparison hub carries each agency's whole requirement, and each agency page cites the clause.
Part one: is a narrative required, and how is its content specified
| Agency | Required | How the content is specified | Clause |
|---|---|---|---|
| Caltrans | Yes, one PDF with every submittal | Twelve headings in a stated sequence | §8-1.02C(4) |
| NYSDOT | Yes, with each Progress Schedule | Failure to attach it is one of nine grounds for immediate rejection | Item 639 paragraph I.1 |
| VDOT | Yes, with the preliminary, the baseline, each update and each revised baseline | Seven headings for the baseline, eleven for an update | II.2.B, II.3.B, II.4.B |
| WisDOT | Yes, monthly | A stated content list — see below | §108.4.4.4 |
| WVDOH | Yes, with the monthly update | A stated content list built around critical-path position | §108.3.4 |
| ADOT | Not stated in this provision. No narrative accompanies the schedule under the clauses read | — | §108.03, §108.04 |
| MnDOT | Yes, with every submittal | Two lists — one for Baseline, Revised and Impact schedules, one for Updates | §1803.3C.1 |
| NJDOT | Yes, with each update | A stated content list | 153.03.02 |
| SCDOT | Yes, with the baseline and every update | Nineteen numbered contents | Schedule Narrative |
| MDOT SHA | Yes, with the initial schedule, every update and every revision, each unique to its own submittal | A stated content list per submittal type | §109.03.01.02(g), §109.03.02.02(b), §109.03.03.02(b) |
| TxDOT | Yes | A brief bulleted statement; a Department form may take its place | 5.5.2.3, 5.5.2.3.1 |
| WSDOT | In two named places rather than generally — see below | Per-calendar purpose; per-constraint reason on Type C | 1-08.3(2)B, (2)C |
| PennDOT | Yes, with each update | Seven itemised parts | 689.3(c) |
| CDOT | Yes, with every submittal | Seven items for baseline, preliminary and revised; thirteen for updates | 108.03(c) |
| UFGS 01 32 01.00 10 | Yes, a stand-alone document with each submission | Eight items as a minimum | §3.5.2 |
| NAVFAC 01 32 17.00 20 | Yes, monthly | Each entry cites the activity it concerns | Monthly update narrative |
Part two: the common core
Set the lists beside each other and a recurring spine appears. These are the subjects most of the documents ask about, with examples of who asks:
| Subject | Agencies whose narrative clause names it |
|---|---|
| The current critical path, and how it has moved since the last submittal | Caltrans, VDOT, SCDOT, WVDOH, NJDOT, MDOT SHA, PennDOT, CDOT, UFGS, TxDOT |
| Delays and their cause, with the effect on other activities and milestones | Caltrans, NJDOT, CDOT, WVDOH, UFGS, MDOT SHA |
| Corrective or mitigating action | Caltrans, WVDOH, UFGS, VDOT |
| Every logic change made since the previous submission, with its reason | Caltrans, VDOT, SCDOT, NJDOT, PennDOT, CDOT, UFGS, TxDOT, MnDOT |
| Duration changes | SCDOT, PennDOT, CDOT, UFGS |
| Calendar changes, naming the activities and workdays affected | PennDOT, UFGS |
| Work completed in the period | Caltrans, VDOT, NJDOT, WisDOT |
| Work planned for the next period | VDOT, WisDOT, UFGS |
| Constraints, with a reason for each | VDOT, SCDOT, MnDOT, WSDOT (Type C) |
| Lags or leads, with a reason for each | VDOT, MnDOT |
| Out-of-sequence work | SCDOT, UFGS, MDOT SHA |
| A response to the agency's comments on the previous submittal | Caltrans, UFGS |
The last row is the one most often missed and the easiest to check: two of these documents require the narrative to answer the reviewer's previous comments in writing, which turns the narrative into a correspondence thread rather than a monthly report.
Caltrans: a fixed sequence, not just a list
§8-1.02C(4) is distinctive in requiring the narrative to be organised in a stated order, not merely to contain stated things. In this project's own words, the twelve run: a transmittal letter; work completed in the period; unusual conditions or restrictions on labour, equipment or material, including multiple shifts, seven-day weeks, overtime or work outside regular hours; a description of the current critical path; current and anticipated delays, each with its cause, its impact on other activities, milestones and completion dates, and the corrective action proposed; reasons for any proposed change to the planned work; the status of pending permits, change orders, time adjustments and noncompliance notices; changes to the critical path and to the scheduled completion date since the last submittal; reasons for an early or late scheduled completion date against the work completion date; the status of early completion time and Department-owned float where applicable; a written response to the Engineer's comments on the previous month's submittal; and, where the schedule carries resource allocations, the differences between actual allocations and those in the baseline.
Item ten is the one no other agency has, and it is the reporting half of Caltrans' float rule. §8-1.02C(8)(c) assigns Department-owned float to the Department and early completion time to the Contractor, and the narrative is where the ledger of both is kept. See the Caltrans page and float ownership.
VDOT: two lists, and three things a report cannot substitute for
The baseline narrative at II.2.B asks for seven: milestone status; work to be performed by the Department and others, with when it must happen to avoid impacts; the overall sequence of work, including where it begins and how crews flow through the project; the project critical path; scheduling assumptions including anticipated daily production rates for the major driving operations; every relationship carrying a lag, with the reason for each; and every constraint, with the reason for each.
The update narrative at II.3.B runs to eleven, adding progress against earnings, work performed last period, changes in the work plan, non-progress changes to the schedule, days lost in the period with the activities affected, DBE participation activities with their dates and durations, pending contract issues, issues and concerns, and work planned next period.
Three of those items say, in the clause itself, that a generated report will not be accepted as a substitute: a listing of critical path activities does not describe the critical path, a listing of activities does not describe the work performed, and a schedule comparison report does not describe the changes made. That is unusual and worth reading carefully, because each of those three is exactly the artefact a scheduling tool can produce automatically.
This project produces comparisons of that kind — see what the engine does. VDOT's clause is a statement that the comparison is an input to the narrative rather than the narrative, and that is the right way round.
The outliers
WSDOT requires no general narrative at all. 1-08.3 asks for writing in exactly two places: a written narrative describing the purpose of each calendar where multiple calendars are applied, and — on Type C only — a written explanation of why each fixed constraint exists, with the constraints identified on the activity listing. Both are attached to a specific file feature rather than to the submission, so the set of things needing explanation is enumerable from the export.
ADOT requires none in the clauses read. §108.03 and §108.04 carry no narrative obligation. The duration justification §108.03 allows the Engineer to request — estimated manpower, equipment, unit quantities and production rates — is a document request answered on demand, not a narrative accompanying the schedule. Absent is not the same as decided against; a special provision on a particular Arizona contract may add one.
SCDOT makes the narrative carry the performance measurement. Its nineteen numbered contents include the Schedule Variance Index with planned and earned value, the current critical path and its lowest total float, each logic and duration change with its reason, an explanation of each constraint, and out-of-sequence work and failed starts explained individually. It also carries a recovery plan whenever the project is behind the accepted baseline — so in South Carolina the recovery obligation lives inside the narrative rather than in a separate clause. See recovery schedules.
MDOT SHA requires each narrative to be unique to its submittal. §109.03 says so three times, once for each submittal type. It is the only one of the sixteen that legislates against the copied narrative directly.
CDOT asks the update narrative to name activity IDs. Delays are identified by activity ID with their effect on other activities and milestones, and logic and duration changes are reported for critical or near-critical activities specifically. That makes the narrative machine-joinable to the file: a reader can take an ID out of the narrative and find it in the export.
The federal list, quotable in full
UFGS 01 32 01.00 10 is a United States Government work, so §3.5.2 can be read directly rather than characterised. It requires a stand-alone PDF or Word document titled "Schedule Narrative Report" with eight items as a minimum: work scheduled to start next period; activities on the critical path "in addition to activities on the next float path after the critical path"; current and anticipated problem areas, delaying factors and corrective action, identifying the party responsible for delay if applicable; activities that should have started or finished by their late dates and did not; every schedule change by activity ID and name — new and deleted activities, logic, duration, calendar, lag, resource and actual date changes; out-of-sequence work; an explanation of the factors driving any change in the longest path from one monthly update to the next; and responses to schedule review comments from previous updates.
Two of those eight are unusual enough to point at. The second asks for the next float path after the critical path, not merely the critical path — a near-critical requirement stated as a reporting obligation rather than as a threshold. And the seventh asks for the factors driving a change in the longest path, which is a causal statement about a comparison the file can produce but cannot explain.
What a file can and cannot supply
Every narrative clause on this page mixes two kinds of content, and the distinction is the useful one for anyone assembling a submission.
Enumerable from the export: which activities changed logic, duration, calendar or actual dates since the previous submission; which carry lags; which carry constraints and of what type; which started or finished out of sequence; which ran past their late dates; how the longest path moved. This project computes these and reports them — see reading a report and how it works.
Not in any file: the reason for each of those changes, the cause of a delay, the party responsible, the corrective action proposed, and whether an explanation is adequate. Those are the narrative's actual subject, and they are written by the people who made the decisions.
Nothing on this page states what a narrative ought to contain, ranks these lists, or treats a shorter one as a lesser requirement. Which clauses govern a particular project is a fact about its incorporated contract documents.
Related pages
- How the sixteen specifications compare.
- Baseline schedule submission · recovery schedules · time impact analysis requirements.
- Activity durations and logic restrictions.
- Agency detail: Caltrans · CDOT · MDOT SHA · MnDOT · SCDOT · UFGS · VDOT · WSDOT · WVDOH.
- Schedule constraints · lags and leads · float ownership · glossary.
- What the engine does · limitations.
Source: web/pages/schedule-narrative.md. Source commit date: 2026-09-11.