Use case
For claims consultants
Build airtight claims — assemble cause and effect from the document trail and quantify entitlement in a fraction of the time.
Building an extension-of-time, prolongation, variation, or disruption claim means reconstructing what happened from thousands of documents — and proving it with the contemporaneous record. The evidence is usually there; finding it, ordering it, and citing it is the work.
Kritical classifies the entire project record, captures the clauses and parties each document cites, and links every finding to its source — so you can assemble cause and effect and a defensible narrative far faster than working the bundle by hand.
Why Kritical
From documents to chronology
Trace cause and effect across the record and assemble the sequence of events that drives the claim.
Entitlement, evidenced
Tie each head of claim to the contemporaneous documents — and the clauses — that prove it.
Defensible by construction
Every finding cites its source document and page, so the claim package holds up under scrutiny.
Where Kritical fits
The system does the heavy lifting of the early phase: classifying the record across document types, surfacing the correspondence and instructions behind each event, and capturing the clauses they cite — so you spend your time on analysis and entitlement, not document triage.
Because every finding links to its source, the chronology and the claim package are traceable end to end — exactly what they need to be when the other side, or a tribunal, tests them.
Frequently asked questions
- What claim types and documents does it cover?
- Contracts, correspondence, RFIs, instructions, variation orders, daily reports, minutes, and programmes — classified by document type and the clauses each cites, ready for extension-of-time, prolongation, variation, and disruption claims.
- How does it make a claim more defensible?
- Every finding links back to its source document, page, and quote, so each head of claim is tied to the contemporaneous record and the package holds up under scrutiny instead of relying on assertion.
Assembling a claim from a mountain of project documents? We should talk.
Book a demo