On this page
A useful schedule audit ends with a decision: fix a record, explain an assumption, obtain missing evidence or accept a documented exception. A red score without activity IDs and follow-up actions creates another meeting, not a better forecast.
Start by preserving the original file and recording the project, data date, software version and calculation settings. Review a copy. Keep the submitted schedule and the recalculated schedule distinguishable throughout the review.
- 01Inspect the fileDates, logic, calendars
- 02Read the contractEdition, clause, exceptions
- 03Check the fieldSequence, access, resources
- 04Record the decisionOwner, evidence, next action
Run three different reviews
| Review | Questions to answer | Evidence to retain |
|---|---|---|
| File integrity | Do relationships resolve? Are there open ends, future actuals or missing calendars? | Activity IDs, dates, relationships, import warnings |
| Contract requirements | Which submission rules, duration limits and calendar requirements apply? | Incorporated clause, edition, amendment and any approved exception |
| Construction credibility | Can the crews perform this sequence with available access, labor and materials? | Superintendent review, procurement records, production assumptions |
The GAO Schedule Assessment Guide provides a broader framework for evaluating schedule reliability. Use it as a reference alongside the actual project requirements; a generic checklist does not establish which terms govern your contract.
Work through the network
Check incomplete activities for missing predecessors or successors. Then examine dangling logic: an activity can have links on both sides while its finish still fails to drive any later work. Trace the completion milestone backward rather than relying only on red bars.
Review negative float with its constraints and calendars visible. Inventory long durations, leads, lags and nonstandard relationship types. Compare the current update with the prior update for added links, deleted links, changed durations and changed calendar assignments. Separate status changes from changes to the plan.
Do not delete an exception simply to improve a score. Ask whether it is deliberate, permitted and understood. A procurement activity may need a longer duration than a field installation; an external interface may explain an apparent open end.
Turn one finding into a useful comment
Consider this fictional review result: activity M-240, “Install switchgear,” starts before its delivery predecessor finishes. A weak comment is “Fix logic.” A useful comment says:
“M-240 carries an actual start before P-180 delivery is complete. Confirm whether partial delivery allowed work to start. Provide the delivery record, describe the remaining work and explain the calculation setting used for out-of-sequence progress.”
That comment names the observation, offers a plausible question and requests evidence. It does not invent misconduct or assume the entire installation is complete.
Close the loop
Maintain a review register with finding ID, activity ID, observation, governing requirement if any, requested action, owner, response date and disposition. Mark an item resolved only when the revised file or supporting evidence answers the question. Retain earlier responses so the next reviewer can understand the decision.
For your next review, read P6 settings that change the forecast, then use the Schedule Forensics resource library. When the team is ready to connect reviewed dates with daily work, explore the os.construction Schedule guide.
Share this article