Construction Schedule Updates: A Practical Review Checklist

Start with the record behind the dates

A construction schedule update should explain what happened in the field and what the team now expects to happen next. A new finish date is useful only when the records and assumptions behind it are clear.

This checklist from Ryan Lippmann turns that review into a repeatable conversation between the scheduler, field team, and project manager. Use it alongside the weekly project controls review when a schedule update needs closer attention.

Agree on the cutoff before comparing progress

Identify the schedule's status date: the boundary between recorded progress and forecast work. The file's save date is not a substitute. Use field reports, delivery records, and other project evidence covering the same reporting period.

The U.S. Government Accountability Office's Schedule Assessment Guide, Best Practice 9, explains this distinction and the need to update actual progress and remaining work. Keep the previous update available so changes can be traced.

At the start of the review, write down the current file version, status date, previous update, and approved baseline version. That short record makes it easier to reproduce the comparison later.

Check what started, what finished, and what remains

Review the activities reported as started or finished since the previous update. Identify the supporting record and confirm what each activity's completion actually means. Installation, inspection, and acceptance can be separate steps.

For work still in progress, ask the field lead to describe the remaining quantity, access needed, material availability, and crew assumptions. A percentage alone cannot explain whether the next activity can begin.

For example, an equipment installation may be almost complete while its controls connection remains unresolved. Record the remaining connection work and its dependency explicitly. This is an illustrative situation, not a report from a client project.

Review the relationships that drive the forecast

Check changes to dependencies, activity durations, work calendars, and imposed dates. Ask why each material change was made and whether it reflects the planned construction sequence. When work happens out of sequence, document how the update represents the remaining dependency.

Trace the activities driving the affected milestone. A delayed delivery does not automatically move the project finish by the same number of days; available float, other work paths, calendars, and the proposed response matter. The guide's Best Practice 6 explains why the critical path must be checked after an update.

Explain movement against both reference points

Compare important milestones with the previous update and with the approved baseline. The first comparison shows what changed this period. The second shows the accumulated difference from the agreed plan.

Keep those comparisons separate. A milestone can improve since last week and still remain later than the baseline. A routine progress update should preserve the baseline reference; if a new baseline is approved through the project's change process, retain the earlier version and the approval record.

The arithmetic describes date movement. The schedule narrative still needs to explain which activities and assumptions produced it. See Best Practice 10 for the guide's treatment of baseline and current schedules.

Give each unresolved issue an owner and a required date

Turn the review into a short action record. For each material issue, capture the activity identifier, affected milestone, evidence, unresolved question, person responsible for the response, and date the response is needed.

A useful entry might read: “Equipment delivery remains unconfirmed. Procurement lead to obtain a written shipping commitment before the next schedule update. Scheduler to assess the effect on installation once the delivery date is confirmed.” That keeps an unverified date visible without presenting it as a commitment.

Record a proposed recovery measure separately from an agreed change. Name the resources, access, or approvals it depends on before treating the resulting date as the working forecast.

Use this checklist before issuing the update

1. Confirm the status date and the versions being compared.
2. Check reported starts and finishes against the field record.
3. Confirm the remaining work and the assumptions behind its duration.
4. Review changed dependencies, calendars, and imposed dates.
5. Trace the work driving each important milestone.
6. Explain movement since the previous update and against the approved baseline.
7. Record open decisions, owners, required dates, and supporting evidence.
8. Issue the schedule with its narrative and retain the review record.

The guide calls for a narrative explaining significant schedule changes and their effects in Best Practice 9, Schedule Narrative. The checklist above is a practical review format, not a claim that an individual project has passed a formal assessment.

Sources and related work

Technical reference: U.S. Government Accountability Office, Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G), December 2015. The examples on this page are illustrative; they do not describe client schedules or former employers' internal procedures.

For the wider reporting routine, read A Weekly Project Controls Review for Small Construction Teams. When responsibility passes between teams, use the construction handoff checklist. The construction portfolio and career record provide background on Ryan's work.