Forensic
Claims & Disputes
Claim preparation and review, delay and time-impact analysis, chronology and records — built from the contemporaneous file, not a rewrite.
Why this matters
A claim without a file is a speech.
Outcomes are not promised. Where proceedings require counsel or appointed experts, the role is technical and commercial support. Legal strategy remains with appointed legal counsel.
What we do
Evidence first. Narrative second.
Preparation, review and rebuttal; delay analysis; extension of time; time impact; chronology; records; cause and effect; commercial and technical analysis. Not a courtroom brand.
Core service areas
What the pack must be able to show.
- 01
Claim preparation
Issues, records and recommended sequence of submissions.
- 02
Review and rebuttal
Response to the other party’s analysis, on evidence.
- 03
Delay analysis
Starting from the programmes that were actually used.
- 04
Extension of time
Packages a planner and a contract administrator can both defend.
- 05
Time impact
Consequences coded against the live logic, not a cartoon.
- 06
Chronology
Events in the order the records support.
- 07
Cause and effect
Facts tied to contract mechanics without substituting for legal advice.
How we work
Preserve. Analyse. Submit.
- 01
Preserve
Stop the record rotting while the project is still live.
- 02
Frame
Events, contract mechanics and missing evidence.
- 03
Analyse
Delay, disruption and quantum on the contemporaneous file.
- 04
Submit
A pack the commercial and legal team can stand behind.
- 05
Defend
Rebuttal using the same programmes and cost records.
Outputs
A case the file can carry.
Claims strategy note
Issues, records and recommended sequence.
Records gap assessment
What the file can and cannot currently support.
Delay / TIA pack
Method, programmes used and findings.
EOT / claim narrative
Facts and requested relief — for counsel to settle legally.
Quantum support
Cost build-up from project records.
Negotiation brief
Strength, exposure and record quality.
Relevant markets
Where delivery is decided
Related insight
From the project, not the brochure
Need a claim built from the project file?
Bring a delay, records, or rebuttal constraint. Outcomes are not promised.