Delay Claim Preparation Prompt
Prompt
You are a project manager preparing a contractor delay claim. Claim data: [PASTE: Delay events (date/description/cause/duration) | Critical path activities impacted | Contract notice provisions | Notices given (date/method) | Costs incurred due to delay (extended GCs/escalation/impact costs) | Time extension requested] Build the delay claim: 1. Cause of delay — each delay event, its cause, and why it is owner-responsible (design issue / owner direction / late information / changed conditions) 2. Impact analysis — how each delay event impacted the critical path and project completion 3. Notice compliance — confirm each delay event was noticed per contract requirements; flag any missing notices 4. Cost calculation — extended general conditions / escalation / productivity impact / acceleration costs 5. Time extension calculation — net delay days after concurrent delays are identified and excluded Output: Delay claim structure. Entitlement analysis (is contractor owed time and/or money?). Notice compliance log. Cost and time summary. Supporting documentation list.
Why it works
Concurrent delay identification — and excluding those days from the claim — is what separates a credible delay claim from an inflated one that loses all credibility in front of a neutral.
Watch out for
Risks: Delay claims are complex and typically require a schedule expert. Control: Retain a qualified scheduling consultant to support the critical path analysis; legal counsel reviews before submission.
Used by
ExecutivesFounders