Skip to content
Method

Experience, built into the analysis.

Claims experience shapes the questions we ask, the evidence we connect and the systems we build. Our practitioners and engineers turn that knowledge into a method for establishing your entitlement.

The principle

Construction intelligence starts with the work.

Decades spent investigating construction disputes have taught our practitioners which questions matter. That experience shapes the specialist models we train, the analytical algorithms we build and the checks we apply.

This is what we mean by construction intelligence: specialist knowledge and software working on a shared record. Systems handle repetitive preparation and support analysis. Practitioners direct the investigation, challenge the findings and exercise judgement.

01

Recover the context

Bring connected inboxes and project files into a coherent record. Emails retain their dates, participants and source mailboxes, so an exchange can be followed across the people involved. Chronologies connect correspondence with programmes, costs and technical records; gaps and conflicting accounts remain visible.

Illustrative analysis using sample information.

02

Test the connections

Specialist algorithms compare programme revisions and examine cost records. Models trained for defined disciplines help interrogate the material. Our practitioners test the findings against causation, contract and source evidence, including material that challenges the claim.

Illustrative analysis using sample information.

03

Form a considered position

A partner directs the work within the agreed appointment. Advice and reports explain the evidence, method, assumptions and limitations behind the conclusions. An appointed expert forms an independent opinion and remains responsible for it.

Illustrative analysis using sample information.

The method in practice

Follow the finding back to the record.

VeriCase programme reporting

A programme movement, open to examination.

A programme trajectory report compares successive revisions and links the analysis to an evidence appendix. The reviewer can examine the recorded movement, its calculation and its source. That provides a basis for investigating delay; the expert must still assess cause, responsibility and entitlement.

Foresight illustrative scenario

Scattered correspondence, a connected issue.

Foresight's Proof page follows a fictional working week. It shows how messages considered together can reveal an issue for commercial review. The scenario explains the approach; its people, figures and outcomes are illustrative.

Explore the Foresight example
In-house engineering

The same knowledge.
Put to work earlier.

A disputed instruction can expose a broken approval process. A final account can uncover months of unrecorded change. Our engineers work alongside the practitioners who investigate those failures to improve the systems behind the work.

The claim

Evidence ready for scrutiny

Connect the event, its programme and cost effects, and the relevant contract provisions. Keep the supporting record close to the argument.

The live project

Issues brought into view

Bring emerging correspondence, programme movement and contract requirements to the people who need to assess their significance during delivery.

The working practice

A process that carries the detail

Link a drawing issue to its price, approval and completion record. Give the team a working process that preserves the information it will need later.

Beyond the claim

Make the change useful.

Start with one task, one project or one commercial team. Remove the repetitive work that gets in the way, so your people can apply their expertise where it matters.

01

Understand the work

Visit the project and follow the task with the people doing it. Find where information, time or commercial control is lost.

02

Choose what to change

Agree the problem that matters, the people responsible and what a useful improvement would achieve.

03

Build around the task

Connect suitable existing tools, adapt our building blocks and build what is missing. Shape the system around the work.

04

Make it part of the routine

Implement with the team, support adoption and check the result against the problem we set out to solve.

Governance
  • •Practitioners responsible for professional advice and conclusions
  • •Evidence, methods, assumptions and limitations explained
  • •Source references retained for scrutiny
  • •Access and data handling agreed for the matter
  • •Review, implementation and support responsibilities defined

Illustrative review workflow using sample information.

Start with the matter in front of you

Speak with a partner about the claim, project or commercial decision you need to address.

Discuss your matter
Meritus Via