Closing a 30-Month Fit-Out With Live Claims
Your 30-month hospital fit-out has reached substantial completion 5 weeks late. The as-built record shows 214 change orders, 19 approved time extensions totalling 41 calendar days, and 6 unresolved delay claims in which 12 days of float are contested between the contractor and the client. The client wants all schedule records archived and the project team released within two weeks. The construction manager wants to keep the working schedule 'open and updatable' in case the claims go to arbitration. Your scheduler has already been reassigned to a new pursuit starting Monday.
1. Define what schedule closeout actually requires here, and specify what must be preserved.
Read the worked answer
Closeout content
- A final as-built schedule with actual start and finish dates on every activity, logic retained (not stripped), and all approved changes incorporated, reconciled line-by-line against the baseline.
- A reconciliation statement: baseline finish vs approved-extension finish vs as-built finish, with the 41 approved days shown separately from the 12 contested days.
- The full version history: every update with its data date and the baseline(s), not just the last file.
- Formal sign-off from client and contractor that the schedule record is accepted as the record of performance.
- Confirmation that no activities remain open or unstatused, and that all milestones are marked complete or formally cancelled.
What must not happen
- No deletion of activities, logic or lags to 'tidy up' the file - those elements are the evidence.
- No overwriting of the baseline, and no retro-editing of past data dates. Archive as immutable copies with read-only permissions and a version index.
- Handover of the archive to a named custodian, with the index and access route documented - the departing scheduler cannot be the only person who knows where it lives.
2. The construction manager wants to keep the schedule open for arbitration. How do you respond?
Read the worked answer
Why 'keeping it open' is the wrong instinct
- A schedule that continues to be updated after completion loses its standing as a contemporaneous record. Each subsequent edit creates a question about who changed what, when, and why - which is exactly the argument you do not want to have in arbitration.
- It also blurs the data date. A live file has a moving data date; a forensic record needs a fixed one tied to a known update cycle.
What to do instead
- Close the working schedule. Freeze a verified copy as the record, with its version history and data dates.
- If claims proceed, the vehicle is a separate time-impact analysis or forensic schedule built from the frozen record, clearly labelled as an analysis rather than a project update.
- Preserve the contemporaneous evidence that supports the analysis: the sequence of updates, the correspondence around each extension, the change order register, the daily reports.
- Cost of freezing: negligible. Cost of a record that looks manipulated: the claim.
Judgment point
- Closing the schedule does not close the dispute. Conflating the two is what creates risk.
3. The scheduler leaves in two weeks. What must be captured for the organization, and how do you manage the handover?
Read the worked answer
Capture before release
- Schedule-specific lessons: estimate versus actual duration by discipline, how much float was consumed and where, lag and constraint usage, number of baseline revisions, volume of change orders and the schedule impact each actually caused, calendar and logic errors found in peer review.
- Benchmarks that feed the organization's estimating and scheduling standards - e.g., realistic duration ranges for fit-out packages, typical extension rates.
- A short closeout report that separates 'what happened' from 'what we would do differently,' with the evidence referenced rather than restated.
Handover discipline
- A written handover: archive location, index, naming convention, custodian, access rights, and open claim items with their status and next action.
- A named successor custodian who has actually opened the archive and verified it, not just been told about it.
- Formal release of the scheduler recorded against the project, with the handover as the exit criterion.
Judgment point
- Resource release is a project decision that carries a records risk. Releasing early without a verified archive and a custodian converts a routine closeout into an avoidable discovery problem.