Quick Reference

Group Models
Contracts & Parties Contract · ContractParty · Clause · Organisation · Person
Obligations Obligation · ObligationOccurrence
Notices & Events Notice · ContractEvent
Variations, Claims & Breaches Variation · Claim · Breach
Evidence & Governance Evidence · EvidenceLink · Approval · Task

16 models in total.

The models

Model Purpose
Organisation Legal entities (principal, contractor, subcontractor, …)
Person Individuals, with role/authority, tied to an organisation
Contract The head agreement — parties, value, dates, governing law, risk
ContractParty An organisation's role on a contract + its notice address
Clause The clause register (self-nesting; material flag)
Obligation A contractual requirement — trigger, due rule, recurrence, status
ObligationOccurrence A dated instance of a recurring obligation
ContractEvent Something that happened (delay, site condition, dispute)
Notice An inbound/outbound contractual notice with service tracking
Evidence The evidence register — custody, verification, privilege
EvidenceLink Links a piece of evidence to what it supports
Variation A change to scope/value/time
Claim A claim for time and/or cost, with deadlines and assessment
Breach A breach — identified → cure → remedied / escalated
Approval An approval step gating external issue
Task A follow-up action

Status vocabularies (enums)

  • Contract: draft · under_review · active · suspended · expired · terminated · completed · archived
  • Obligation / Occurrence: draft · pending · active · due_soon · overdue · submitted · satisfied · waived · disputed · breached · closed
  • Notice: draft · internal_review · approved · issued · received · acknowledged · disputed · superseded · withdrawn · closed
  • Notice type: general · contractual_notice · delay · extension_of_time · variation · claim · breach · default · cure · suspension · termination · payment · dispute · reservation_of_rights · other
  • Claim: potential · notified · submitted · assessed · negotiated · accepted · rejected · withdrawn · settled · closed
  • Variation: proposed · instructed · priced · approved · rejected · implemented · closed
  • Breach: identified · notified · cure_period · remedied · unresolved · escalated · closed
  • Risk / priority: low · medium · high · critical
  • Direction: outbound · inbound

The demo data set — one coherent story

An active civil works contract, CON-2026-001 "Riverside Interchange Upgrade" (principal Riverbend Infrastructure Authority, contractor Meridian Civil, subcontractor Delta Earthworks).

  • A recurring monthly progress-report obligation (OBL-001): July and August occurrences satisfied, September overdue → a breach (BRC-001).
  • Unforeseen ground conditions at Pier 3 (EVT-001) triggered an inbound delay notice (NOT-001) and an outbound superintendent response (NOT-002).
  • A submitted extension-of-time claim (CLM-001, 12 days + $142.5k) and a proposed variation (VAR-001, +$185k / +12 days) both trace back to the event.
  • Evidence for the August report and the Pier 3 delay, linked to the obligation and the event; approvals for the response notice and the variation; tasks to chase the report and assess the claim.

36 seeded rows across all 16 models.

Key demo codes

CON-2026-001 (contract) · OBL-001…003 (obligations) · EVT-001 (event) · NOT-001/002 (notices) · CLM-001 (claim) · VAR-001 (variation) · BRC-001 (breach) · EV-001/002 (evidence).

Notes

  • Fields named name on Contract/Obligation/ContractEvent/Evidence/Person exist so referencing lists show a short label rather than a description paragraph or a job title (a framework display-field convention).
  • The Notice & Deadline Engine (auto due-date calc, recurrence generation, acknowledgement/expiry scans, notice/obligation state transitions) is Phase 2; the demo models those outcomes statically.