How schedule delays support change orders
Use your project schedule as evidence for time-related change orders when a scope change pushes back the timeline.
Schedule as evidence
When out-of-scope work adds time to a project, your schedule is one of the clearest pieces of evidence you can attach to a change order. A dated, dependency-driven schedule shows exactly how much delay a change caused and why.
How to use it
- 1Add the delaying event as a task or note it against the relevant task in the schedule.
- 2Add or confirm the dependency that links the delay to downstream tasks.
- 3Recalculate the schedule so the delay is reflected in task dates.
- 4Export the schedule as a PDF or CSV and attach it to the related change order's schedule impact section.
Tip
Pairing a schedule export with daily field report entries from the same period gives a client a hard-to-dispute picture of why the timeline shifted.
Related articles
How to document labor, material, and schedule impacts
What belongs in the labor, material, and schedule impact sections of a change order, with examples.
How to recalculate a schedule
When and why to use the Recalculate Schedule option after changing dates, dependencies, or work calendar settings.
How Daily Field Reports support change order documentation
Daily Field Reports are some of the strongest evidence you can attach to a change order — here's how to use them that way.
How to use the project schedule
An overview of the Gantt-style schedule page: tasks, milestones, dates, and dependencies.