Baseline development, monthly updates, logic and duration review, DCMA-aligned QC.
Fragnet-based TIAs isolating delay cause and effect, tied cleanly to a single basis of claim.
Schedule recovery strategy and re-sequencing when a project has fallen behind milestone dates.
Schedule-basis support for REAs, separated from weather or other concurrent delay claims.
Reviewing contractor submittals, narrative reporting, and schedule governance on behalf of the owner.
IMS development and maintenance across P6 and Microsoft Project, including hammock and logic-driven structures.
Scheduling logic and narrative are my domain. Field determinations and contractual claims strategy belong to the contractor or owner counsel. I don't make unilateral calls on claim strategy.
Submittals stay factual. Narrative language is written to hold up under later scrutiny, not to argue a position it isn't the schedule's job to argue.
A weather-only TIA stays weather-only. Differing site conditions get their own REA. Commingling bases is where claims lose credibility.