Contract Obligation & Notice — Documentation

Operational control of contractual obligations, notices, milestones, evidence, variations, claims, breaches and approvals across a contract portfolio.

In this section

• 00_OVERVIEW — what the application is for, the operating chain, and the five functional areas.
• 01_QUICK_REFERENCE — the menu map, all 16 models, the status vocabularies, and the demo data story.
• 02_SYSTEM_DIAGRAM — an interactive entity map (hub tables, per-area tabs and a curated top-level flow).

The application in one paragraph

A contract is registered with its parties, people and clauses. Each contractual obligation is captured against a clause, given a trigger and a due rule, and tracked through its lifecycle (draft → active → due-soon → overdue → satisfied / waived). Recurring obligations spawn dated occurrences. Contract events (delays, site conditions, disputes) are logged and can spawn notices (inbound/outbound), claims, variations and breaches. Evidence is registered and linked to the items it supports, approvals gate external issue, and tasks track the follow-ups — all under the framework's audit trail and soft-delete.