Esc

↑↓ move↵ openIndex · Pagefind

THE SCHEDULE REVIEW TOOLKIT

Better questions.
A stronger project record.

Eight practical worksheets for the work between receiving a schedule and making a decision. Take them to your next review meeting, adapt them to the project, and keep the evidence attached.

Free downloads. No email gate. Editable files and printable checklists.

USE THE WHOLE LOOP

A finding is the start of a conversation.

A register becomes useful when it connects an observation to evidence, a decision owner, and a documented response. Use this sequence with any of the templates below.

  1. 01

    Record

    Name the file, activity, and observation.

  2. 02

    Ask

    State the question and the evidence needed.

  3. 03

    Resolve

    Assign a decision owner and record the response.

  4. 04

    Preserve

    Keep the revision, reason, and closure evidence.

PICK THE NEXT JOB TO DO

Ready for your project folder.

Start with the review register. Add the supporting worksheet that answers your next question.

01Review / CSV

Schedule review register

Turn a finding into an answerable question, an owner, and a closure record.

Activity IDs · evidence · question · owner · disposition

How to use this template

Filter by category or disposition during the review meeting. Keep observations separate from interpretations and record the evidence that closes each comment.

02Prepare / Print / PDF

Baseline submission checklist

Check the submission basis, the network, and the field assumptions behind the plan.

Review basis · logic · buildability · transmittal

How to use this template

Open the worksheet, check completed review actions, and print or save as PDF. Add the governing project requirements and record exceptions instead of forcing a pass.

03Explain / Markdown

Monthly schedule narrative

Explain what moved, why it moved, and which decision the project needs next.

Milestones · driving work · model changes · commitments

How to use this template

Open in a text editor or copy into your document template. Replace the bracketed prompts and attach an evidence index. Retain the native schedule alongside the narrative.

04Document / CSV

Change and delay evidence log

Connect events to contemporaneous records, affected activities, and open questions.

Event ID · source record · schedule revision · evidence gaps

How to use this template

Create an event ID when the issue becomes known. Link original records and note alternative explanations. Keep notice requirements in a separate, contract-specific review.

05Decide / CSV

Recovery options comparison

Evaluate changes to crews, sequence, and calendars with their costs and constraints visible.

Intervention · assumptions · cost basis · risk · approval

How to use this template

Use one row per option. Fill in the model references, resource assumptions, estimate basis, and approval route before comparing outcomes. An option remains unapproved until a decision is recorded.

06Communicate / Print / PDF

Schedule handoff checklist

Give the next reviewer enough context to understand and reproduce the forecast.

File package · forecast explanation · actions · receipt

How to use this template

Use at a handoff meeting or with a transmittal. Check the package with the recipient, capture unresolved questions, and print the completed worksheet for the project record.

07Compare / CSV

Schedule settings comparison

Make calculation and calendar changes visible before interpreting date movement.

Data date · logic options · float · lag basis · calendars

How to use this template

Complete a previous-versus-current comparison from native application settings and available exports. Mark unavailable information explicitly. Never assume a missing setting is unchanged.

08Verify / CSV

Governing specification matrix

Trace every review requirement to the actual document, edition, and amendment.

Document · edition · clause · units · exception · evidence

How to use this template

Read the incorporated project documents and fill in exact clause locations, units, populations, exceptions, and approval routes. Agency guidance alone does not identify the terms of your project.

A FIVE-MINUTE SETUP

Make the template yours.

  1. Create a working copy. Name it with the project, data date, and revision. Preserve the original schedule file.
  2. Replace the examples. CSV examples are labeled “ILLUSTRATIVE EXAMPLE ONLY.” Delete them before recording project information. Use the blank row as a starting point.
  3. Set the review basis. Record the incorporated specification and edition. Confirm units, populations, and exceptions before adding a threshold.
  4. Assign the next action. Every open question needs an owner, a date, and a clear description of what would resolve it.
  5. Keep the result. Save the completed file in your project record. Printable checkboxes are not saved between visits; use Print / Save as PDF before closing.

CSV files open in spreadsheet software; Markdown opens in a text editor. These are reusable review aids, not automated compliance checks. Match them to your project requirements and review process.

FROM LEARNING TO YOUR DAILY WORK

Keep the schedule conversation connected.

A late answer, a changed detail, and a delivery record belong in the same project conversation. Explore how os.construction organizes project workflows, then bring us the handoff you want to improve.

Original os.construction resources adapted from the Schedule Forensics educational library. Return to the guides, visual lessons, and references.

Open file