A claim becomes expensive long before anyone calls a lawyer if the project has failed to preserve the evidence needed to understand what happened.
The Week 11 Discussion Forum describes a practical sequence for claims: issue notice, analyse rights and cause, analyse delay, analyse damage and work through settlement. The tutor material similarly emphasises written claims, cause-and-effect evidence, formal registers and compliance with the process established by the contract.
The supplied AS 4000—1997 historically contains claim-notification mechanisms, prescribed notices, superintendent assessment and dispute escalation.
The strategic lesson is that a claim is first an evidence problem.
Legal interpretation matters, but legal analysis cannot recreate missing contemporaneous records with certainty.
The Strategic Context
Claims arise where a party believes the commercial baseline has been disturbed.
Common triggers include:
- variation;
- delay;
- latent conditions;
- suspension;
- access problems;
- defective information;
- acceleration;
- additional work;
- default;
- termination.
The Week 11 forum references a secondary list of claim categories, but the attribution and contemporary applicability should be verified before publication as an authoritative taxonomy. [FACT CHECK REQUIRED]
The durable point is that claims have different causes but similar evidence needs.
Someone must show:
- what occurred;
- when it occurred;
- what obligation or entitlement is engaged;
- what causal effect followed;
- what reasonable mitigation occurred;
- what additional time or money resulted.
Without those elements, positions harden around assertion.
What Leaders Commonly Misread
The first mistake is treating notice as hostility.
A timely notice can protect both parties by making an issue visible early enough to manage.
The second is assuming a strong relationship allows formal requirements to be ignored.
Collaborative behaviour can improve resolution, but it should not depend on forgetting the agreed commercial process.
The third is collecting evidence only after quantum becomes significant.
By then, labour records, program logic, site conditions and decision context may be difficult to reconstruct.
The fourth is combining entitlement and valuation into one argument.
A party may have a valid entitlement but weak evidence of quantum, or strong cost records but no contractual basis for recovery.
The fifth is allowing claims teams to become detached from the project team that actually experienced the event.
Reframing the Issue
Claims management should be designed as an evidence stack.
Contract layer
What clause, scope boundary, direction or obligation is engaged?
Event layer
What happened and when?
Notice layer
What was communicated, to whom and within what required timeframe?
Causation layer
How did the event affect work, cost or time?
Mitigation layer
What was done to reduce the consequence?
Quantum layer
How was the claimed amount or time calculated?
Decision layer
What was assessed, agreed, rejected or escalated?
This stack makes the claim understandable before it becomes adversarial.
Strategic Analysis
The supplied AS 4000—1997 historically requires notification of claims and includes a mechanism under which failure to communicate can have consequences without necessarily invalidating the claim itself. It also provides time periods for particulars and superintendent assessment.
Those specific mechanisms should not be generalised to current contracts or legislation. [FACT CHECK REQUIRED]
The management principle is still useful:
Notice and evidence should travel with the event.
For delay, that means connecting claim records to the live program.
For variation, it means connecting the claim to instructions and revised scope.
For latent conditions, it means recording physical evidence before disturbance where possible.
For additional cost, it means separating actual incremental cost from normal planned expenditure.
Claims quality is therefore a product of project controls, document control and field discipline.
Executive Value
Good claims management is not only about defending or recovering money.
It reveals systemic issues.
Frequent access claims may indicate poor principal-interface planning.
Repeated variation claims may indicate immature design.
Recurring delay claims may show weak approval governance.
High claim-value growth late in projects may indicate poor commercial forecasting.
At portfolio level, claims data can identify where contracts or internal capabilities are failing repeatedly.
Strategic Analysis: Good Evidence Creates Settlement Options
Evidence is valuable not only because it strengthens a legal position. It creates more options for commercial settlement.
When both parties can agree on the event, chronology, affected activities and actual cost records, negotiation can focus on the real areas of disagreement. When facts themselves are contested, every settlement discussion becomes harder.
A hypothetical civil-works claim may involve late access to part of the site. If daily records, revised programs, labour allocation and correspondence are available, the parties can test how much delay actually resulted. If records are weak, the contractor may present a broad estimate while the principal rejects the entire claim.
Poor evidence pushes both sides towards extreme positions.
Contemporaneous evidence also helps separate project-management problems from contractual entitlement. A contractor may have incurred additional cost but still need to show why the principal is responsible under the contract. Conversely, a principal may believe the contractor should have mitigated more but need evidence showing what alternatives were reasonably available.
The project should therefore treat claim files as structured decision packages rather than correspondence archives.
For material events, an early neutral chronology can be useful internally: what happened, what documents exist, what remains uncertain and what analysis is required. That discipline helps senior leaders understand exposure before advocacy hardens the narrative.
Decision Framework
For each material claim, leadership should ask six questions.
Entitlement
What contractual basis is relied upon?
Notice
Was the issue communicated in accordance with the applicable process?
Cause
What event created the claimed effect?
Effect
What changed in time, cost, scope or performance?
Mitigation
What reasonable action reduced or could have reduced the effect?
Quantum
How is the amount or extension calculated and evidenced?
If one element is weak, decision-makers should know exactly where the uncertainty sits.
From Strategy to Execution
Immediate action: create a claims register linked to correspondence, variations, delay events and cost records.
Medium-term capability building: train site, technical and project-controls staff to recognise claim-relevant events and preserve evidence without turning every issue into confrontation.
Long-term strategic positioning: analyse claim causes across completed projects and feed them into tender design, risk allocation and capability development.
The objective is fewer surprises, not simply better arguments.
Signals to Monitor
Watch for notices issued long after events, large claims emerging near project completion, unsupported global claims, cost records that cannot distinguish baseline work from additional work, schedule claims disconnected from contemporaneous programs, recurring “without prejudice” meetings with no formal issue resolution, or claims registers that contain value but not cause.
Another warning sign is a project team viewing claims management as the legal department's responsibility.
Questions for the Leadership Team
- What event created this claim?
- What evidence was captured when it occurred?
- What contractual entitlement is relied upon?
- Can the claimed delay or cost be causally demonstrated?
- What mitigation occurred?
- Which part of the claim is genuinely disputed?
- What recurring claims pattern should change how we procure future work?
Closing Perspective
Claims do not begin with legal submissions.
They begin with project events.
The quality of the eventual commercial decision depends heavily on whether the project recognised the event, preserved evidence and understood causation while facts were still accessible.
That makes claims management a delivery discipline first and a dispute discipline second.
Related article: Variations Are Where Project Economics Quietly Change
Related article: Time Is a Contractual System: Delay, EOT, Acceleration and Damages
Related article: Keep Delivering While the Dispute Exists
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.