Claims management
Automated evidence files for construction claims
Astora reconstructs the factual timeline from all project documents. Every contradiction is identified, every claimed amount traces back to its supporting document.
Request a DemoThe problem
A claim is won or lost on the quality of documentary evidence
Timeline reconstruction happens after the fact, under pressure
The claim is formalized 6 to 18 months after events. The contract manager must reconstruct the sequence of facts from 500 to 1,000 documents: correspondence, meeting minutes, work orders, successive schedules, emails. Weeks of archival work, with inevitable gaps. One unfound letter, one misfiled set of meeting minutes, and a head of claim collapses.
Contradictions between documents are weapons for whoever finds them first
The project manager's letter notifies a delay on March 15. The meeting minutes from the same week make no mention. The schedule updated in April does not incorporate the change. These discrepancies exist in the documents. Whoever identifies them first turns them into arguments. Whoever discovers them on defense suffers them.
Quantum is contestable if every amount does not trace to its source
The stated damages rely on aggregated estimates. The opposing party demands detail. Every amount must trace back to a triggering event, a document, a date. Without native traceability between quantum and supporting documents, negotiation focuses on the credibility of the figures instead of the substance.
What you get
A structured, sourced, and auditable evidence file
Timeline reconstructed in days, not weeks
Every letter, meeting minutes, work order, change order, and email is dated, attributed to its author, and linked to the relevant trades, obligations, and stakeholders. A sourced chain of events, filterable by trade, by stakeholder, or by period. A new contract manager picks up the context of a dispute without reconstruction.
Contradictions between documents identified and ready for use
Astora cross-references every document against all others and flags discrepancies. The project manager claims to have notified a delay on March 15? The meeting minutes from the same week make no mention. The schedule updated in April does not incorporate the change. These elements are identified, sourced, and structured as arguments. Across 850 documents, the cross-referencing is exhaustive and reproducible.
Every claimed amount linked to its source document
Quantum is backed by the project documents. Every line of the claim submission traces to the supporting document and the date of the triggering event. The file is auditable end to end. In negotiation, the discussion focuses on substance, not on the reliability of the figures.
Contractual deadlines monitored before time-barring
45 days after receipt of the final account to submit the claim. 28 days after an event for FIDIC notification. 6 months to initiate proceedings. Every deadline is extracted from the contract and monitored.
Deployment
Concrete results from the first deployment
On a EUR 6M dispute related to a civil engineering project (18 months of execution, 9 stakeholders), Astora reconstructed the complete timeline from 850 execution documents in 5 days. The cross-analysis identified 27 contradictions between the project manager's correspondence, site meeting minutes, and successive schedules, of which 9 were used as arguments in the claim submission. 3 late contractual notifications on the owner's side were identified and incorporated into the file. Preparation time dropped from 6 weeks to 5 days.
850 over 18 months
Documents cross-referenced
27, incl. 9 used in the claim
Contradictions identified
5 days vs. 6 weeks
File preparation
Beyond structuring
What your claims data reveals about your contractual practices
Which contract clauses generate claims
Late project manager approvals, unforeseen site conditions on technical trades, delayed work orders on interim deadlines: recurring dispute types become visible. The contract manager feeds the drafting of future contract conditions with field-tested clauses.
Arguments and amounts obtained on previous claims
Every resolved claim enriches a base of typical contradictions, validated arguments, and amounts obtained per head of claim. The next submission builds on documented internal precedents.
Early detection during execution
Contradictions detected in real time during execution feed alerts before the dispute forms. The contract manager notifies on time instead of reconstructing after the fact.
Dispute cost benchmarking
Average cost per claim type, per contract, per stakeholder. The legal department manages on consolidated data.
Integration
No change to your workflows
Documents stay in your systems. Astora structures them and produces the evidence elements directly usable for the claim submission.
Your systems
What Astora feeds
Test Astora on an active claim file
Send us the documents from a dispute. In 5 days, you have the factual timeline and identified contradictions.
Request a demo