Esc

↑↓ move↵ openIndex · Pagefind

A weekly schedule review checklist for the project team

Confirm the selected schedule, review the next three weeks, check calculated coverage and assign follow-up before changing field dates.

Charley Forey3 min readScheduleChecklistProject management
On this page
  1. Before the meeting: name the schedule
  2. Review the work that needs a decision
  3. Check what criticality actually tells you
  4. When changing an eligible adopted plan
  5. Close the loop with connected work

Use this checklist to run a meeting around the schedule the field team actually sees. Record decisions and owners in your meeting notes. A discussion about a saved plan is useful, but it does not itself change task dates.

Before the meeting: name the schedule

  • Record the project, meeting date and selected schedule context. Current schedule, a specific imported revision and Manual tasks only are different selections. An older import is useful for comparison; do not present it as the current field schedule.
  • Check the data date when one is available. The 3-Week Lookahead starts at that date and spans 21 days, so confirm that everyone understands the period being discussed.
  • Keep the retained source file available. Download Original XML/XER returns that source, not an export of your edited Planner version.
  • If discussing Planner, record its saved version separately. Saving and calculating a plan does not automatically apply dates to field tasks.

Review the work that needs a decision

  • Open the Lookahead and discuss overdue open work first. Record a recovery action, responsible person and follow-up date for each item needing attention.
  • Review At Risk work: tasks finishing inside the lookahead window that have not started. Confirm the next handoff, materials and access with the responsible people.
  • Open an activity when you need its progress, actual dates, notes or dependencies. Keep the selected revision in mind as you move between views.
  • Separate a percent-complete update from a date change. A change in duration can alter duration-weighted project progress even when individual percentages stay the same.

Check what criticality actually tells you

  • Read the source of the displayed result. A verified applied Planner result and the legacy calendar-day calculation use different scheduling semantics.
  • Distinguish critical, known noncritical, and unavailable. A task outside an applied result’s calculated coverage can still be visible in the field schedule. Missing a critical badge is not proof that it has float.
  • If publication evidence is stale or unavailable, record the unresolved review instead of substituting an older stored flag. Analytics counts of stored critical flags do not validate their freshness.

When changing an eligible adopted plan

This part requires Schedule, Submittals and CRM admin permissions, with those tools enabled. It applies to existing tasks linked through reviewed retained-source adoption. For native plans, use the separate Planner publication walkthrough: review creation policies, exact bindings and retain/retire/restore decisions before applying. Its flat, unstarted mapping and 64-version editor-history limits still apply. Integrations can use the native publication API.

  • Check working calendars, activity durations, dependency direction, relationship type, lag and constraints. Save and calculate before reviewing task changes.
  • Open Review task date changes. Compare current and calculated start, finish and critical flags. Check Derived summary rows against their mapped descendants.
  • Resolve blockers before applying. If another change makes the review stale, obtain a fresh review; do not repeatedly submit an old result.
  • Choose Apply reviewed task dates only after the team has reviewed the proposed changes. Record the decision, then confirm the resulting task dates in the field views.

Close the loop with connected work

  • Check linked submittal activity displays after applying dates. Independent due, procurement and required-on-site dates do not move automatically; assign any necessary follow-up.
  • Review CRM milestone snapshots that may now be stale. Updating schedule dates does not rewrite a reviewed snapshot or publish a customer update.
  • Record unresolved mappings, manual edits and unknown calculated coverage as follow-up items with owners. Do not delete records merely to clear a blocker.
  • At the next meeting, check the previous decisions before reviewing another proposed plan.

A useful closing note is concrete: “We reviewed this schedule selection and saved version, applied these task-date changes, and assigned these remaining follow-ups.” If no changes were applied, say that explicitly so a planning discussion is not mistaken for a field update.

See the Schedule guide for controls and current limits, the date-review tutorial for the full workflow, and the Schedule API workflow for integration semantics.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file