Why Construction Claims Fail Before They Are Submitted

A construction claim rarely fails because the final document lacks impressive language. It usually fails because the project did not create, connect or preserve the evidence needed to prove the claim while the events were unfolding.

By the time a claims team is asked to prepare a submission, the decisive weaknesses may already be embedded in the record: a notice was late or unclear; the baseline programme cannot be reconciled with later updates; daily records do not identify the affected work; costs cannot be linked to the event; or mitigation decisions were never documented.

The submission can organise the evidence. It cannot manufacture contemporaneous facts that the project never recorded.

A claim is a chain, not a narrative

A defensible construction claim normally has to establish a connected chain:

contractual basis → compliant notice → event → responsibility → cause and effect → impact on time or cost → mitigation → substantiated relief

If one link is missing, a long narrative and a large appendix may still leave the decision-maker unable to answer a basic question: why does this event entitle this party to this amount of time or money?

The Society of Construction Law's Delay and Disruption Protocol emphasises that good records and proper use of programmes reduce uncertainty, support early assessment and may lower the cost of analysing delay and disruption. That is an operational lesson, not merely a disputes lesson: claim quality is created during project delivery.

Seven ways a claim can fail before drafting begins

1. The team treats notice as paperwork rather than a contractual act

A progress report, meeting minute or informal email may describe a problem without satisfying the contract's notice requirements. The notice may need to identify the event, contractual basis, expected effect, relevant clause, required particulars and continuing nature of the impact. Some contracts also impose strict time limits or conditions precedent.

The practical control is a live notice register that records the trigger date, due date, clause, responsible person, submission, acknowledgement, follow-up particulars and current status. The contract and governing law determine the consequence of non-compliance; the project team should not assume that general awareness by the other party cures a defective notice.

2. Entitlement is considered only after costs arise

Project teams often record what happened but not why it is contractually compensable. An instruction may change the work, but the relevant mechanism could be a variation, employer-risk event, change in law, access delay, differing site condition or another contractual route. Each route may have different notice, proof and valuation requirements.

Before building quantum, the team should create an entitlement map: the relied-upon clause, required elements, known facts, supporting records, opposing facts and open questions. This prevents a submission from mixing multiple legal and contractual theories without proving any one of them.

3. The programme record does not show the real project

An accepted baseline by itself does not prove delay. A credible EOT case ordinarily needs reliable programme updates, actual progress, changes in logic, critical and near-critical paths, constraints, mitigation and the effect of relevant events.

Weaknesses arise when updates are overwritten, native schedule files are lost, actual dates are inserted retrospectively, logic changes are unexplained or progress data conflicts with site records. AACE Recommended Practice 29R-03 reinforces that the method and source data used in forensic schedule analysis must suit the facts and the available contemporaneous information.

4. Site records describe activity but not causation

"Work delayed" is a conclusion. A useful record identifies what work was planned, what happened, where it happened, the affected activity, the responsible constraint, resources available, resources used, output achieved and action taken.

Daily reports, photographs, inspection records and minutes become far more valuable when they share consistent references—location, work package, activity ID, issue ID and date. Without those links, the claims team may have thousands of documents but no reliable way to demonstrate cause and effect.

5. Cost records cannot be traced to the event

Total project overspend is not automatically the cost of a compensable event. A claim must separate baseline cost, event-related cost, concurrent or unrelated cost, recovered cost and avoided cost. Labour, plant, subcontract, material, site overhead and head-office records need appropriate allocation and supporting documents.

If cost codes were never designed to capture the event, retrospective allocation becomes vulnerable to challenge. The SCL Protocol recommends cost records detailed enough to link costs, at least at a meaningful level, to delay or disruption events.

6. Mitigation exists in practice but not in the record

Teams frequently resequence work, move crews, change methods, expedite approvals or deploy additional resources. If the decision, instruction, cost and result are not documented, the submission may fail to show that reasonable steps were considered and taken.

A mitigation record should state the problem, options considered, decision-maker, date, selected action, forecast effect, actual effect and associated cost. It should also preserve rejected options and the reasons for rejection.

7. Claim ownership is fragmented

Planning holds the programme, commercial holds the cost, document control holds correspondence, engineering holds RFIs, and the site team holds diaries and photographs. Each function may maintain a separate register with different names for the same event.

The result is late discovery of gaps, contradictions and missed deadlines. A claim needs one accountable owner and a cross-functional review rhythm. The owner does not replace each specialist; the role is to maintain the evidence chain and escalate missing links while they can still be corrected.

The pre-submission claim health check

Before drafting a detailed claim, ask:

• What exact contractual relief is sought?
• Was each required notice issued on time and in the required form?
• Can every material fact be traced to a contemporaneous source?
• Does the programme evidence demonstrate impact on completion or a relevant milestone?
• Have concurrency, float, pacing and mitigation been addressed where relevant?
• Can every claimed cost be reconciled with normal accounting records and payment evidence?
• Are contrary documents and alternative explanations disclosed and evaluated?
• Can a reviewer move from a conclusion to the source document without searching several systems?

A "no" does not always end the claim. It identifies the work needed, the limitation to disclose or the risk management decision to make. Discovering that gap early is far better than finding it during determination, adjudication or arbitration.

Build the claim while delivering the project

The strongest claim process is continuous. It captures events, controls notices, preserves schedule versions, links records, records decisions and reviews gaps at agreed intervals. The final submission then becomes a controlled synthesis of an evidence base that already exists.

ContraClaim DMS is designed to support that discipline by bringing contractual correspondence, notices, programme references, records and claim issues into a connected workspace with traceable sources and review history. The purpose is not to decide entitlement automatically. It is to help the project team see whether the evidential chain is complete before the claim reaches a decision-maker.

Explore how ContraClaim DMS can help your team move from scattered project files to source-linked contractual records.

Sources and further reading

• Society of Construction Law — Delay and Disruption Protocol, 2nd edition
• AACE International — Recommended Practice 29R-03: Forensic Schedule Analysis
• FIDIC — Making Claims for Time and Money: Understanding Notice Provisions

This article provides general contract-administration information, not legal advice. The contract terms, facts and governing law applicable to each project must be reviewed by appropriately qualified professionals.