When a California project encounters delay, the schedule record is part of the evidence. HADVEN analyzes the project chronology, logic and available records so the time impact can be explained in a way project teams can review.
Use the guide below to understand the discipline, then move directly to a service, project case study or schedule review.
A delay analysis should begin with what the project record can establish: baseline logic, update status, actual work, critical path, milestone changes and contemporaneous documentation. The methodology should fit the record.
A TIA can quantify the schedule effect of a defined change event when the schedule model and project records support the analysis. EOT documentation then needs a clear link between event, schedule effect and requested time.
Forensic work looks backward through the record to identify how project events changed the schedule. The output depends on the available record and can include windows-style analysis, as-built reconstruction or another appropriate methodology.
