Contract and renewal obligation watcher
Contracts get extracted into a structured register so renewal dates, notice periods and price escalators stop living in one person's head.
This is a reference design we build from — one of a set that are not delivered client projects, and the figures are estimates rather than measured results.
Trigger
New document in the contracts store, plus a daily schedule
Timeline
1 wk evaluation set → 3 wks build → 2 wks supervised
Stack
Document AI / Azure Document Intelligence · LLM extraction with a strict schema and confidence scoring · Postgres register · SharePoint or Drive connector · Calendar and email alerting · Full audit log of every extraction
Outcome
No renewal is missed by accident. Obligations become queryable. Every extracted field traces back to the clause it came from.
The process today
Contracts sit in a drive; renewal dates, notice periods and price escalators live in one person’s head or a stale spreadsheet.
What the automation does
Extracts parties, term, renewal date, notice window, auto-renew clause, price-review mechanism and liability cap. Writes them to a structured obligations register with a link and page reference back to the source clause. Alerts the owner ahead of each notice window on a configurable ladder. Flags low-confidence extractions for legal review rather than guessing.
Where a human stays in the loop
Every low-confidence extraction goes to legal review instead of being guessed at, and every field in the register links back to the source clause so it can be checked, not just trusted.
What you end up owning
The Postgres register, the extraction schema and confidence rules, the connector configuration, and the full audit log — all queryable in your own environment.