The Critical Path Trap: Beyond the PDF
In high-stakes delay claims, the “As-Planned” vs. “As-Built” PDF comparison is insufficient evidence. Savvy schedulers often manipulate the native data to hide their own inefficiencies. We utilize the AACE International Recommended Practice 29R-03 for Forensic Schedule Analysis to deconstruct the “black box” of Primavera P6.
Forensic Investigation of the Native .XER
We do not rely on the printed Gantt chart. We audit the logic tables in the native file to identify manipulation tactics that artificially drive the critical path:
- Float Sequestration: Identifying where constraints (e.g., “Must Finish By”) were applied to non-critical tasks to consume Total Float and create an artificial sense of urgency.
- Preferential Logic: Differentiating between “Hard Logic” (physical dependencies) and “Soft Logic” (resource leveling) used to hide periods of inactivity.
- Calendar Manipulation: Detecting retroactive changes to the global calendar (e.g., switching a 5-day work week to a 7-day work week) to mask lost time.
The “Concurrent Delay” Defense
Our primary objective is often establishing Concurrent Delay. If we can prove that an owner-caused delay occurred within the same window as a contractor-caused delay, the financial damages may offset or be eliminated entirely. This requires a granular “Time Impact Analysis” (TIA) that generalist e-discovery firms cannot provide.
“We don’t just tell you the project was late. We tell you who owns the float.”