A focused review of logic, interfaces, assumptions and the reliability of the forecast.
Does it represent the work?
Check that the work breakdown reflects the contracted scope, physical sequence and responsibility boundaries. Milestones should connect to deliverables and approvals.
Are the interfaces real?
Test links to client information, other contractors, access, procurement and commissioning. Open ends and generous lags often conceal delivery assumptions.
Can the critical path be explained?
The team should be able to describe the controlling sequence, near-critical paths and available float without relying on software output alone.
Is progress changing the forecast?
Actual performance, remaining durations and recovery actions should flow through to the forecast. Repeated date retention without changed logic deserves challenge.