Application Overview

What this app is for

Claims and Dispute Management gives a contracts/legal team one controlled workspace for running contractual claims and disputes to resolution. It keeps the three things that decide a claim — entitlement (is there a right?), causation (did the event actually cause the effect?) and quantum (how much?) — as first-class, separately-tracked assessments, backed by evidence and notices, so a claim's position is always defensible and its deadlines never missed.

It models both sides of the correspondence (inbound/outbound), preserves privilege and without-prejudice status, and follows a claim all the way from the triggering event to a settlement deed.

The operating chain

FRAME                   CLAIM                       ASSESS                      RESOLVE
matter + contract   ->  claims + issues + events -> entitlement + causation ->  responses + negotiation ->
+ clauses               + notices                   + quantum + evidence        disputes -> determination -> settlement
                                                                                |
                                                                       tasks · exceptions

Read left to right, that is the sidebar: Matters & Contracts → Claims → Entitlement/Causation/Quantum → Evidence → Responses/Negotiation/Disputes → Tasks & Exceptions.

The six functional areas

1. Matters & Contracts — the frame

DisputeMatter (the overarching matter — status, risk, exposure/recovery), Contract and ContractClause (the instrument the claim arises under), and the Organisation / Person directories.

2. Claims — the claim and its narrative

Claim (typed, with entitlement/causation/quantum status and claimed/assessed/ agreed amounts), ClaimIssue (the discrete points in contention), ClaimEvent (the factual events, with programme/cost impact) and ClaimNotice (the contractual notices that preserve rights and time bars).

3. Entitlement, Causation & Quantum — the merits

EntitlementAssessment (contractual/legal basis, conditions precedent, defences), CausationAssessment (causal chain, concurrency, programme analysis) and QuantumItem (the line-by-line quantum build-up with claimed/assessed/agreed).

4. Evidence — the proof, and its privilege

EvidenceItem (custody, hash, confidentiality and privilege status) and ClaimEvidenceLink (which evidence supports which claim/issue, and how strongly).

5. Responses, Negotiation & Disputes — the resolution path

Response (the counterparty's position), NegotiationRecord (without-prejudice offers and concessions), Dispute (a crystallised dispute in a forum), DisputeClaimLink, Determination (the decision/award) and Settlement (the deed).

6. Tasks & Exceptions — the controls

Task (follow-up actions) and ExceptionRecord (time-bar, privilege and completeness risks).

Two ideas that make it trustworthy

  • Entitlement, causation and quantum are tracked separately. A claim's overall position is only as strong as its weakest axis, and each is assessed, versioned and evidenced on its own — so "we have a good claim" is always broken down.
  • Notices and privilege are first-class. ClaimNotice records time-bar preservation and service; EvidenceItem carries a privilege status and produced-to-counterparty flag — so a time bar is never missed and privilege is never accidentally waived.

Build status

Phase 1 (this build): the full schema (22 models), navigation, dashboards and a coherent seeded demo are complete and browsable as AI-Safe CRUD.

Phase 2 (documented, not built): the executive dashboard metrics/panels, the deadline engine, and the derived fields (days_to_notice, notice_overdue, recovery_variance, quantum variance_to_claim). Today those outcomes are modelled statically in the seed.