Published and reviewed 22 August 2026 · By Syed Ali Hasan
Start with reliable records
A useful analysis begins by establishing what records exist, how they were maintained, and what each record can support. The baseline programme, update files, calendars, logic links, progress evidence, change records, correspondence, and meeting records often form the working evidence set.
The first question is not “which method should be used?” It is whether the available data can support a transparent explanation. Gaps, assumptions, and inconsistencies should be stated rather than hidden.
Choose a method that fits the question
Time-impact, windows, and retrospective approaches answer different questions and rely on different records. The appropriate approach depends on the contract, the timing of the decision, the quality of updates, and whether the purpose is management, entitlement assessment, or dispute support.
The analysis should identify the method, key assumptions, treatment of concurrency, and tests performed. A conclusion that cannot be reproduced or challenged constructively is difficult for a project team to use.
Make the explanation decision-ready
A decision-ready output combines a plain-language narrative with programme evidence, a dated chronology, and visuals that show the relevant path and movement. It separates fact, assumption, and opinion so decision-makers can see what is established and what requires confirmation.
Related resources
How to organise claims evidence →
Forensic schedule analysis service →