New: Document Integrations with Aconex and Procore are live. See what your AI can read now

Use cases / Disputes and claims

Disputes and claims

Can we prove what caused the delay and who owns it?

Trace what changed, when, and who owns it, with an evidence pack that holds up.

Book a demo
See the proof
AI ModeDC EchoAuditable
Can we prove what caused the delay and who owns it?
Routed throughDelay NavigatorChange HistoryChange Control
  • What changed, and when
  • Delay cause and ownership
  • An evidence pack you can export
Delay cause and ownership traced. Evidence pack ready to export.

Ask the AI. Or check the math yourself.

Same ground truth models underneath. Flip between the answer and the Delay Navigator view behind it.

DC Echo Latest scheduleAI Mode
Can we prove what caused the delay and who owns it?

Client reviews and approvals caused 53% of the delay to handover. E.G.2470 alone added 74 days. The evidence pack is ready to export.

  • Client reviews and approvals53%
  • E.G.2470 Client review, F00374 days
  • Contractor-side activities45%
Delay ownership, H.B.1002+385 days total
Top causesC.B.1034Entrance structureContractor100 daysE.G.2470Client review, F003Client74 daysE.G.3520Approve temporary works, piling matClient48 daysE.G.2390Design package F002Client44 days
Project slip by version
In the evidence packDelay causes and ownershipChange history, v1 to v6End dates across 6 schedule versionsField changes, v6 vs. v5
Delay NavigatorChange HistoryChange Control
Evidence trail attached

Asked in AI Mode

Real questions. Real answers.

Build your position on evidence. Large owners and contractors use AI Mode to assess extension of time claims and delay causes, with activity-level proof behind every number.

Real customer projects, anonymized

AI ModeElectricity gridAuditable

“Compare this month’s contractor schedule with last month’s, and give me a conclusion for each chart.”

What AI Mode found848 logic changes

Completion moved 112 days, the critical path grew from 7 to 140 activities, and 848 logic changes were made in a single revision.

Why it mattered. The owner had the evidence to respond under its NEC4 contract and ask for credible corrective measures.

From your data to a decision you can defend.

01 · Your data
  • Schedule versions
  • Change orders
  • RFIs
  • Contracts
02 · Ground truth models
  • Delay Navigator
  • Change History
  • Change Control
03 · Evidence trail
  • What changed, and when
  • Delay cause and ownership
  • An evidence pack you can export

Open any answer in Platform Mode and check the math yourself. How it works

Decisions that paid off.

All customer stories
Electricity grid · Owner
112 days
of slip, with a clear NEC4 position
Read the story
“This is a really good tool to use especially if you’re filing claims.”
Head of Project Controls, Etihad Rail

More decisions it answers

Quality and compliance
Progress verification
Change management
Risk and forecasting
Delay recovery
Acceleration

FAQ

Questions, answered.

Questions about disputes and claims.

Talk to our team

Yes. Scenario-based attribution isolates what each change caused and tags every contribution by reason.

No. Contracts and legal frameworks differ, so Dates mode shows every raw date and your experts make the call.

Delay causes and ownership, change history across every version, end dates across schedule versions and field-by-field changes.

Across every schedule version you’ve loaded, from the baseline to the latest update.