# Monthly schedule narrative worksheet
Prepared for: [project]
Period / data date: [date]
Native schedule filename and revision: [filename]
Prepared by / reviewed by: [names and dates]
Governing submission requirements: [document, edition, clause]

Use this worksheet with the native schedule, prior accepted or agreed comparison schedule, status records, and applicable contract requirements. Replace every bracket. Add or remove sections to match the project. Illustrative examples below are prompts, not project findings.

## 1. Executive decision
- Current completion forecast: [date and milestone ID]
- Prior comparison forecast: [date and schedule reference]
- Movement: [explain date difference and calendar basis]
- Decision needed this period: [owner, decision, due date]
- Confidence limitations: [missing evidence or unresolved settings]

## 2. Status cut-off and evidence
State the data date and when field records were collected. Identify who confirmed actual starts, actual finishes, remaining durations, and quantities. Explain late corrections. Attach a status evidence index.

| Activity ID | Status change | Record supporting change | Confirmed by | Unresolved issue |
| --- | --- | --- | --- | --- |
| [ID] | [actual start / finish / remaining duration] | [daily report or delivery record] | [name] | [question] |

## 3. Milestone comparison
| Milestone / ID | Baseline date | Prior forecast | Current forecast | Explanation / evidence |
| --- | --- | --- | --- | --- |
| [milestone] | [date] | [date] | [date] | [specific cause to investigate] |

Do not describe every forecast movement as a compensable delay. Explain what changed before making any responsibility or entitlement assessment.

## 4. Driving and near-driving work
Describe the current sequence to completion, the affected work fronts, and the constraint that controls each. Define the near-critical criterion used for this review. Explain changes in the driving path from the prior update.

Illustrative prompt: "The delivery-to-installation sequence now controls the forecast. Confirm shipment evidence and remaining installation durations before relying on this result."

## 5. Changes to the model
List added/deleted activities, revised relationships, changed durations, calendars, constraints, external dependencies, and scheduling options. Link each significant change to a reason and approval record. Preserve an unchanged copy of the previous file.

## 6. Out-of-sequence work
Identify actual work that diverges from planned logic. Describe field conditions and how remaining work is modeled. Record the scheduling option used and any required review.

## 7. Risks, mitigation, and recovery
| Risk / event ID | Affected work | Evidence | Proposed action | Owner / due date | Approval required |
| --- | --- | --- | --- | --- | --- |
| [ID] | [activity IDs] | [record] | [action] | [owner / date] | [route] |

State assumptions for crews, work hours, access, materials, inspections, and productivity. Separate an evaluated option from an approved plan.

## 8. Next-period commitments
List work planned for the next reporting period and its prerequisites. Identify required design decisions, submittals, deliveries, permits, inspections, and access releases. Assign owners to unresolved prerequisites.

## 9. Open review items
Reference the review register. State what was corrected, what remains unanswered, and what cannot be concluded from the available records.

## 10. Submission index
- [ ] Native schedule and revision
- [ ] Schedule log and relevant settings
- [ ] Calendar and constraint inventories
- [ ] Comparison report with activity IDs
- [ ] Supporting status records
- [ ] Narrative and review register
- [ ] Contract-specific deliverables
- [ ] Reviewer and transmittal record

Source: Original os.construction worksheet adapted from the Schedule Forensics educational library.
Guide: https://os.construction/blog/schedule-forensics-monthly-narrative
Toolkit: https://os.construction/resources/schedule-forensics/toolkit
