Application Overview

What this app is for

Contract Obligation & Notice Management gives a contract administration team one operational picture of what a contract requires, what is coming due, what has happened, and what has been done about it. It turns a static executed contract into a live register of obligations, deadlines, notices and evidence — so time-bars are not missed, notices are issued and acknowledged on time, and every claim, variation and breach is traceable back to the clause and the event that drove it.

It is domain-agnostic (construction, services, supply, ICT) and administered from the principal's side, but models both inbound and outbound correspondence.

The operating chain

REGISTER                 OBLIGE                      RESPOND                 ASSURE
contracts + parties  ->  obligations + occurrences ->  events -> notices  ->  evidence + links
+ clauses                (triggers, due rules,         -> variations           + approvals
                          recurrence)                  -> claims -> breaches   + tasks

Read left to right, that is the sidebar: Contracts & Parties → Obligations → Notices & Events → Variations/Claims/Breaches → Evidence & Governance.

The five functional areas

1. Contracts & Parties — who is bound, and to what

Contract (with principal/contractor orgs, contract manager and legal owner), ContractParty (each organisation's role on the contract), Clause (the clause register, self-nesting), plus the Organisation and Person directories.

2. Obligations — what must be done, by when

Obligation (type, responsible/beneficiary party, trigger, due rule, recurrence, risk, status) and ObligationOccurrence (each dated instance of a recurring obligation with its own due date and outcome).

3. Notices & Events — what happened, and the correspondence about it

ContractEvent (delays, site conditions, disputes — flagged for potential notice/claim/variation/breach) and Notice (inbound/outbound contractual notices with service, acknowledgement and supersession tracking).

4. Variations, Claims & Breaches — the commercial consequences

Variation (scope/value/time change), Claim (time and cost entitlement, deadlines and assessment) and Breach (identified → cure → remedied/escalated).

5. Evidence & Governance — the proof and the follow-through

Evidence (the register, with custody, verification and privilege) and EvidenceLink (what each item supports), Approval (approval chains gating external issue) and Task (follow-up actions).

Two ideas that make it trustworthy

  • Everything hangs off the contract and its clauses — obligations, notices, claims and breaches all carry contract_id (and usually a clause_id), so any item is traceable to the wording that created it.
  • Evidence and approvals are first-class — the register records custody, verification, privilege and reservation-of-rights, and approvals gate a notice before it is issued externally.

Build status

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

Phase 2 (documented, not built): the runtime Notice & Deadline Engine — the proforma actions{} (activate_contract, satisfy_obligation, issue_notice, acknowledge_notice), scheduled_jobs{} (deadline / recurrence / acknowledgement / expiry scans) and the derived fields (days_to_due, overdue, due_soon). Today those outcomes are modelled statically in the seed.