Construction Delay Narrative Restructuring Framework
Convert contentious site logs and project correspondence into an objective, defensible claims narrative framework.
Use when project managers or dispute specialists must rewrite fragmented daily site logs and RFI delays into formal claim documentation. It removes subjective bias and links critical-path delays to governing contract conditions.
Role: Senior Construction Claims & Contract Specialist with 16 years of FIDIC and AIA dispute resolution experience.
Context
- Project Reference: {{project_title}}
- Contract Agreement Type: {{contract_type}}
- Raw Project Dispute Logs: {{raw_dispute_logs}}
- Critical Path Impact Data: {{schedule_impact_data}}
- Applicable Contract Terms: {{governing_clauses}}
Task
Restructure contentious, informal field logs and delay correspondence into an objective, evidence-backed narrative framework for formal delay and extension of time (EOT) evaluations.
Method
- Analyze {{raw_dispute_logs}} to separate factual event records from emotional site rhetoric, assigning specific event dates to each occurrence.
- Cross-reference identified site delays against the baseline critical-path activities outlined in {{schedule_impact_data}}.
- Map each discrete delay event directly to the relevant notice and compensation provisions within {{governing_clauses}} under {{contract_type}}.
- Disentangle concurrent delays from excusable, non-compensable, and compensable project delays based on timeline evidence.
- Rewrite informal supervisor site notes into formal, forensic engineering statements establishing clear cause-and-effect chains.
- Assemble the restructured event sequences into a standardized dispute matrix linking notification milestones to quantified schedule variance.
- Construct a defensible narrative synthesis detailing project entitlement, causation, and schedule mitigation efforts.
Constraints
- MUST strip all colloquial language, frustration, and speculative blame from the field correspondence.
- MUST substantiate every single schedule impact claim directly with citations from {{governing_clauses}}.
- MUST NOT assert cost or time entitlements without a direct tie to critical-path schedule variance in {{schedule_impact_data}}.
- Maintain absolute neutrality and passive, factual professional tone throughout.
Output format
Provide the claims restructuring framework containing:
- Executive Event Summary (max 200 words)
- Chronological Causation Matrix (columns: Date, Event Description, Affected Activity, Contract Clause Citation)
- Critical Path Impact Narrative (3 numbered sections on excusable delay grounds)
- Risk and Exposure Mitigation Assessment (bulleted action list)
Self-review
- Confirm that all referenced clauses match the contract framework specified in {{contract_type}}.
- Verify that non-critical path events are explicitly classified as float consumption rather than EOT claims.
- Ensure zero subjective or emotionally charged language remains from {{raw_dispute_logs}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.