A "mechanical delay" is rarely a mechanical delay.
It's one of the most common patterns in forensic schedule analysis. Equipment shows up late. The contractor logs it as a delivery delay. The schedule analyst signs off. The owner accepts the change.
Walk it back five steps and the real predecessor is almost always upstream. A submittal that took 60 days to approve instead of 30. A fabrication window that got compressed because of it. A shipping date that slipped as a downstream effect. By the time it reaches the field, the delay is wearing a costume.
This is the part of forensic analysis nobody likes to do. Going back through submittal logs and RFI responses against the schedule baseline. Reading the procurement record alongside the field record. It's slow. It almost always changes who owns the float.
If your delay log reads like a list of symptoms instead of causes, you're going to lose the argument that matters.
#ConstructionManagement #ProjectControls #CPMScheduling
It's one of the most common patterns in forensic schedule analysis. Equipment shows up late. The contractor logs it as a delivery delay. The schedule analyst signs off. The owner accepts the change.
Walk it back five steps and the real predecessor is almost always upstream. A submittal that took 60 days to approve instead of 30. A fabrication window that got compressed because of it. A shipping date that slipped as a downstream effect. By the time it reaches the field, the delay is wearing a costume.
This is the part of forensic analysis nobody likes to do. Going back through submittal logs and RFI responses against the schedule baseline. Reading the procurement record alongside the field record. It's slow. It almost always changes who owns the float.
If your delay log reads like a list of symptoms instead of causes, you're going to lose the argument that matters.
#ConstructionManagement #ProjectControls #CPMScheduling
Shared byHayden Bose - A month ago
Log in to comment
Loading ..
5
0/100