# Construction Claim

> The formal assertion of a right to additional compensation or time when a change request has been denied or a dispute cannot be resolved through the ordinary change process — entitlement, causation, and damages, packaged for adjudication.

- Source: https://briq.ai/acu/object/construction-claim
- Department: Change Management (https://briq.ai/acu/department/changes)
- Catalog code: CHG 302 · Level: Advanced · Track: Operations · 13 min read
- Also known as: Contractor Claim, Request for Equitable Adjustment, REA, Delay Claim, Dispute Claim

## Definition

A construction claim is a formal, documented assertion by one party that it is entitled to additional compensation, additional time, or both, arising from an act, omission, or condition for which it contends the other party is contractually responsible. It is what a disputed change becomes when the ordinary change order process fails: the entitlement is contested, the parties cannot agree, and the requesting party must now prove three distinct things — that it has a contractual or legal right to relief (entitlement), that the responsible party's action caused the impact (causation), and that the impact translates into quantifiable cost or time (damages). A claim is not a change order request and not a lawsuit by itself; it is the structured demand that precedes and supports formal dispute resolution, whether that is negotiation, mediation, arbitration, or litigation. Its distinguishing feature is that it must stand on proof, because by definition the other party disputes it.

## Why it matters

The claim is where the contemporaneous record is finally cashed in — or found wanting. Everything upstream in the change process, the dated change events, the notices, the RFI response times, the daily reports, the schedule updates, exists partly so that if a dispute reaches this stage, the requesting party can prove what happened when. A claim is only as strong as the record built long before anyone knew there would be a claim, which is why disciplined change management is really claim preparation done in advance.

It rests on three separable pillars, and weakness in any one defeats it. A contractor can have airtight entitlement and clear damages but lose because it cannot prove causation — that the specific owner action, not the contractor's own inefficiency, caused the impact. Understanding that entitlement, causation, and damages are independent burdens is what separates a serious claim from an expensive complaint, and most failed claims fail on causation or on damages methodology, not on entitlement.

The stakes and the cost of pursuing it are both high. Claims consume management time, expert fees, and relationship capital, and their outcomes are uncertain, so the decision to pursue one is a business decision as much as a legal one. A claim that is meritorious but too small to justify the cost of proving it, or one filed after notice was blown, is a claim not worth pursuing regardless of the underlying injustice — and recognizing that early preserves resources for the claims that can actually be won.

Notice and procedural compliance decide claims that never reach their merits. Contracts impose strict notice requirements, claim-submission deadlines, and continuing-to-work obligations, and courts and arbitrators routinely deny otherwise valid claims for procedural default. The most sophisticated damages model in the world does not survive a missed notice deadline, which is why the humble, contemporaneous act of giving notice at the moment of impact is disproportionately valuable relative to its cost.

## Lifecycle

1. **Triggering event and notice** — An event occurs — a differing site condition, an owner-caused delay, a design defect, cumulative disruption — and the party gives contractual notice within the required window. This step, done contemporaneously, is what makes the eventual claim viable.
2. **Preservation of records** — The party preserves the contemporaneous evidence: daily reports, photos, schedule updates, correspondence, cost records, and the change event and COR history. Records created after the dispute crystallizes are weaker than those created in the ordinary course.
3. **Entitlement analysis** — The party establishes the contractual or legal basis for relief — the clause breached, the condition that qualifies, the representation relied upon. Without a theory of entitlement, there is no claim regardless of impact.
4. **Causation analysis** — The party connects the responsible action to the specific impact, often through schedule analysis for time claims and through cost segregation for cost claims. This is the hardest pillar and where concurrent delay and contractor inefficiency are litigated.
5. **Damages quantification** — The party quantifies the injury using a recognized methodology — actual cost, measured mile, total cost or modified total cost where justified, or a schedule-based time impact analysis for delay. The method must fit the facts, because an unsupportable methodology sinks provable damages.
6. **Claim submission** — The claim is packaged and submitted within the contractual deadline, stating entitlement, causation, and damages with supporting exhibits. It goes through the contract's initial decision process, often an architect or a dispute board, before escalating.
7. **Negotiation and dispute resolution** — The parties negotiate; unresolved claims proceed to mediation, then arbitration or litigation per the contract. Most claims settle, but the settlement value tracks the strength of the record and the causation proof.
8. **Resolution and closeout** — The claim is settled or adjudicated, converted into a change order or an award, and the project record is closed. The outcome, and the lessons about where the record was weak, feed back into how the next project is administered.

## Anatomy

- **Claim number and title** — The identifier and a precise statement of what is claimed. Links to the change events, CORs, and CCDs from which the claim grew.
- **Entitlement basis** — The specific contract clause, legal doctrine, or representation relied on. The theory that establishes a right to relief before any dollars are discussed.
- **Statement of facts** — A chronological, evidence-anchored narrative of what happened, cited to the contemporaneous record. The backbone the causation and damages analyses hang on.
- **Causation analysis** — The linkage between the responsible action and the impact, typically a schedule analysis for delay claims and cost segregation for cost claims. The pillar most often attacked.
- **Damages methodology** — The recognized method used to quantify injury — actual cost, measured mile, total or modified total cost, or time impact analysis — and why it fits these facts.
- **Cost damages detail** — The quantified extra cost: labor, material, equipment, extended overhead, and impact or inefficiency, each substantiated by records.
- **Time damages / delay analysis** — The days claimed and the schedule method proving them, addressing critical-path impact and any concurrent delay.
- **Notice record** — The dated notices given and their compliance with the contract's notice provisions. The procedural gate that can decide the claim before its merits.
- **Supporting exhibits** — Daily reports, photos, schedules, correspondence, meeting minutes, cost ledgers, and expert analyses — the evidence that turns assertion into proof.
- **Reservation and prior-release check** — Confirmation the claim was not waived by an earlier change order release. A broad release signed upstream can extinguish the claim entirely.
- **Relief sought** — The specific compensation and time demanded, and the alternative resolution the party would accept. Frames the negotiation.
- **Status** — Under preparation, submitted, in initial decision, in negotiation, in mediation, in arbitration or litigation, or resolved — the stage in the dispute path.

## Failure modes

- **Notice blown, merits never reached** — A meritorious claim is denied because the contractor never gave contractual notice within the required window, or gave it in a form the contract does not recognize. The strongest entitlement and damages in the world do not survive a procedural default the contract makes a condition precedent to recovery.
- **Entitlement assumed, not proven** — The claim asserts the owner is responsible without identifying the clause breached or the doctrine relied on. The adjudicator has no legal hook to grant relief, and a genuine injury goes uncompensated because no theory of entitlement was ever articulated.
- **Causation defeated by concurrency or self-inflicted delay** — The contractor proves delay but cannot separate the owner-caused portion from its own inefficiency or from concurrent delays it caused. The causation pillar collapses, and the time and cost claim collapses with it, even where some owner responsibility clearly existed.
- **Total-cost claim with no basis** — The contractor claims the entire cost overrun as damages without proving its bid was reasonable, its own performance was not at fault, and the overrun was caused by the owner. Courts disfavor the total-cost method absent those predicates, and the whole quantum is discounted or thrown out.
- **Claim released by a prior change order** — A broad full-and-final release signed on an earlier change order, without a reservation, is later found to have waived the cumulative-impact or delay claim the contractor is now asserting. The claim is extinguished by the contractor's own signature months earlier.
- **Damages built on reconstructed records** — Because contemporaneous cost and schedule records were not kept, the damages are reconstructed after the fact from memory and estimates. The reconstruction is easily attacked as self-serving, and provable damages shrink to a fraction of the real injury.
- **Pursued despite unfavorable cost-benefit** — A small or weak claim is pursued through expensive arbitration on principle, consuming more in fees and management time than the best-case recovery. The business decision to pursue was never made rationally against the cost and probability of success.

## Metrics

- **Notice compliance rate** — Share of claims where contractual notice was given within the required window and form. The single strongest predictor of whether a claim's merits will ever be heard.
- **Entitlement strength assessment** — A graded judgment of how clearly the contract or law supports the right to relief. Filters which disputes are worth developing into claims.
- **Causation robustness** — How defensibly the impact is tied to the responsible action, accounting for concurrency and self-inflicted contribution. The pillar most often decisive at adjudication.
- **Damages substantiation ratio** — Share of claimed damages backed by contemporaneous records versus reconstruction. Drives realized recovery in negotiation and adjudication.
- **Claim realization rate** — Recovered value as a share of claimed value across resolved claims. The bottom-line measure of the claims program's effectiveness.
- **Cost-to-pursue ratio** — Fees and management cost of pursuing a claim relative to recovery. Informs the business decision to pursue, settle, or drop.
- **Cycle time to resolution** — Duration from submission to settlement or award. Long cycles tie up management and cash and increase the pressure to settle low.

## The AI shift

- **Conversational** — The claim record becomes interrogable. You ask which disputed changes have strong entitlement but thin causation, whether notice was given and in what form, and whether any prior change order release could have waived the claim — each answer cited to the contract clauses and the contemporaneous record, so the weak pillar in a claim is identified before an adjudicator finds it.
- **Generative** — From the change history, daily reports, schedule updates, and cost records, a model drafts the claim's factual chronology cited to source records, articulates a proposed entitlement theory against the specific contract clauses, and assembles the damages detail in a recognized methodology — a structured draft the claims manager and counsel refine, not a finished legal position.
- **Orchestrated** — The claim stops being assembled from scratch under deadline. The contemporaneous record is pulled together across change events, CORs, CCDs, RFIs, daily reports, and schedules into a single evidence set; notice compliance is checked against the contract; prior change order releases are scanned for waivers; and the schedule delay analysis is tied to the CPM baseline and updates so causation rests on the actual project record.
- **Autonomous** — AI does not run claims unattended, and it should not. The routine motion it can safely operate is preparation and monitoring: continuously preserving and organizing the contemporaneous record, flagging approaching notice and claim-submission deadlines, and surfacing prior releases that threaten a claim. Entitlement theory, causation judgment, damages methodology, and every decision to assert or settle a claim remain with humans and counsel, always.

## Prompts

### Conversational — A change was rejected and you need to assess whether you actually have a claim worth pursuing.

```text
We have a rejected COR for owner-caused delay on the foundation phase that we believe is a claim. Assess it across the three pillars. Entitlement: identify the specific contract clauses that would support our right to relief and how strong that basis is. Causation: from our daily reports and schedule updates, tell me how cleanly the owner's action ties to the delay and whether concurrent or self-inflicted delay weakens it. Damages: tell me what recognized methodology fits and whether our records substantiate it. Then check whether we gave contractual notice within the required window and whether any prior change order release could have waived this. Give me a candid strength assessment on each pillar and a recommendation on whether to pursue.
```

**Expected output:** A candid three-pillar assessment with the notice and release gates checked and the weakest link named — a basis for a business decision to pursue, settle, or drop, not an assertion that the claim is strong.

**Follow-ups:**

- Where is this claim weakest, and what evidence would most strengthen it?
- What is a realistic recovery range versus the cost of pursuing it?
- Did we blow notice, and if so is there any way to cure it?

### Generative — You have decided to pursue a claim and need the factual chronology and entitlement draft built from the record.

```text
Draft the factual chronology and entitlement section for our delay claim on the foundation phase. Build the chronology strictly from the contemporaneous record — daily reports, RFI response dates, schedule updates, and correspondence — with each fact cited to its source document and in date order. Then draft the entitlement section identifying the specific contract clauses supporting our right to relief and how the documented facts satisfy each element of those clauses. Do not overstate: where the record is thin or a fact is inferred rather than documented, flag it explicitly rather than asserting it. Keep the tone factual and precise; this will be reviewed by counsel.
```

**Expected output:** A source-cited factual chronology and an entitlement draft tied to specific clauses, with inferred or thinly supported facts flagged rather than asserted — a foundation for counsel to build on, not a finished claim.

**Follow-ups:**

- Highlight every fact that is inferred rather than documented so counsel can shore it up.
- Draft the notice-compliance section showing when and how we gave notice.
- What contemporaneous evidence is missing that we should locate before submitting?

### Orchestrated — You are assembling the full evidence set for a claim under a submission deadline.

```text
Assemble the complete evidence set for our foundation-phase delay claim. Pull together, from the project record, every relevant change event, COR, CCD, RFI, daily report, schedule update, meeting minute, and cost ledger entry that bears on this dispute, organized chronologically and by pillar. Tie the delay analysis to the CPM baseline and the monthly updates so the critical-path impact is grounded in the actual schedule record. Check notice compliance against the contract's notice clause and confirm no prior change order release waived this claim. Return an organized evidence index with each item mapped to the entitlement, causation, or damages pillar it supports, and flag every gap in the record.
```

**Expected output:** A pillar-mapped, chronologically organized evidence index grounded in the contemporaneous record and the CPM baseline, with notice and release checked and every gap flagged — the assembled foundation of the claim.

**Follow-ups:**

- Which pillar has the thinnest evidence, and what would fill the gap?
- Produce the schedule fragnet showing the owner-caused critical-path impact.
- Confirm nothing we signed released this claim, and quote the release language you checked.

### Autonomous — Standing policy for claim readiness — what AI may run and what it must never touch.

```text
Operate claim readiness continuously under these strict rules. Preserve and organize the contemporaneous record as it is created — daily reports, schedule updates, RFI response times, change events, CORs, CCDs, and correspondence — so any potential claim rests on real-time evidence. Monitor every contractual notice deadline and claim-submission deadline and escalate approaching ones to me and to counsel. Scan every change order release we are asked to sign and flag any that could waive an open or developing claim before we sign it. You may draft factual chronologies and evidence indexes for human review. You must never articulate a final entitlement theory, never decide causation, never select or finalize a damages methodology, and never assert, settle, drop, or withdraw a claim. Every one of those is a human and counsel decision, and you route all of them to me.
```

**Expected output:** A claim-readiness process that preserves the record, guards deadlines, and warns on releases automatically, while entitlement theory, causation, damages methodology, and every assert-or-settle decision remain firmly with humans and counsel.

**Follow-ups:**

- Show me every approaching notice and submission deadline this month.
- Which releases you flagged did we end up signing, and were the claims reserved?
- What contemporaneous records are we failing to capture that a future claim would need?

## Maturity ladder

- **Level 0 — Level 0 — Reactive and reconstructed** — Claims are assembled after the fact from memory and scattered emails. Notice is often missed, records are thin, and recovery depends on reconstruction that is easily attacked.
- **Level 1 — Level 1 — Documented** — A claims process exists, notices are given, and a claim register tracks status. Evidence is gathered manually and late, and entitlement and causation are argued without systematic support.
- **Level 2 — Level 2 — Record-linked** — Claims draw on a preserved contemporaneous record — change events, daily reports, schedules — with notice tracked and delay analysis tied to the CPM baseline. Prior releases are checked for waivers.
- **Level 3 — Level 3 — Assisted** — Factual chronologies and evidence indexes are drafted from the record for human and counsel review, notice and submission deadlines are surfaced, and releases are scanned for claim-waiving language.
- **Level 4 — Level 4 — Prepared, human-decided** — Record preservation, deadline monitoring, and release scanning run continuously inside guardrails, while entitlement, causation, damages methodology, and every decision to assert or settle a claim remain with humans and counsel.

## FAQ

### What are the three things a construction claim must prove?

Entitlement, causation, and damages. Entitlement is the contractual or legal right to relief — the clause breached or the condition that qualifies. Causation is the link between the responsible party's action and the impact, which is where concurrent and self-inflicted delay are fought. Damages is the quantified injury, proven with a recognized methodology and contemporaneous records. All three are separate burdens, and failing any one defeats the claim regardless of the strength of the others.

### Why do so many valid claims still lose?

Most often on procedure or causation rather than merit. A missed notice deadline can bar an otherwise strong claim outright, because notice is frequently a condition precedent to recovery. And even with entitlement and damages, a contractor that cannot separate owner-caused delay from its own inefficiency or from concurrent delay fails the causation pillar. Meritorious injury is not enough; it must be timely noticed and cleanly proven.

### What is the total-cost method and why is it disfavored?

The total-cost method claims the entire difference between actual cost and the bid as damages, effectively assuming every overrun was the owner's fault. Courts disfavor it because it ignores the contractor's own inefficiencies and bid errors, so it is generally allowed only when the contractor can show its bid was reasonable, its performance was not at fault, and the impacts cannot be segregated any other way. A modified total-cost method that removes the contractor's own contribution is more defensible, but actual-cost or measured-mile methods are stronger where the records support them.

### Should we always pursue a claim we believe is valid?

No. Pursuing a claim is a business decision measured against the cost of proving it, the probability of success, the relationship consequences, and the time it consumes. A small or evidentially weak claim can cost more in fees and management attention than the best-case recovery, and a claim already barred by a missed notice or a signed release is not worth the effort regardless of the underlying merit. The discipline is to invest in the claims that can actually be won and to let the others go.

## Related objects

- [Change Order Request (COR)](https://briq.ai/acu/object/change-order-request)
- [Construction Change Directive (CCD)](https://briq.ai/acu/object/construction-change-directive)
- [Delay Notice & Time Impact Analysis](https://briq.ai/acu/object/delay-notice-tia)
- [CPM Schedule](https://briq.ai/acu/object/cpm-schedule)
- [Change Event](https://briq.ai/acu/object/change-event)
- [Daily Report (Daily Log)](https://briq.ai/acu/object/daily-report)