Obligation register
LivePull the obligations out of a contract, then actually track them — with reminders that fire, evidence, and a renewal pipeline.
- ✓AI extraction of obligations from a contract, re-runnable, with the clause it came from kept only when its quote is found in the text
- ✓A reminder job that actually runs, with an idempotency log so a reminder is not sent twice
- ✓Evidence attachments, with the evidence each obligation requires listed and tracked
- ✓Dependencies between obligations, checked for cycles
What it is.
AI extraction reads a contract and produces the obligations it creates: what has to be done, by when, and of what type. From there it is a working register — filter it, update status, mark things complete with who completed them and when, add obligations manually that no contract created.
A daily job sends reminders on each obligation's own lead times, on the notification channels you have switched on, with a log that stops the same reminder going twice. You can attach evidence to an obligation, so a completed item carries proof rather than a tick. The non-renewal notice deadline and the renewal decision live on the contract record itself: the deadline is derived from the expiry date and notice period, flagged at 30, 7 and 1 days, and at 30 days the system files one task to decide.
Three steps.
End to end.
Obligations are pulled out of a contract's text, and can be re-extracted later if the contract changes.
Filter, update, assign a status, complete with attribution, or add obligations by hand.
Reminders fire on each obligation's lead times. Attach evidence when you complete one.
What you get.
- ✓AI extraction of obligations from a contract, re-runnable, with the clause it came from kept only when its quote is found in the text
- ✓A reminder job that actually runs, with an idempotency log so a reminder is not sent twice
- ✓Evidence attachments, with the evidence each obligation requires listed and tracked
- ✓Dependencies between obligations, checked for cycles
- ✓Dashboard, renewal pipeline, and export of the register
- ✓M&A closing-checklist items and audit-readiness remediation sync into the same register
- ✓Notice deadlines on the contract record — expiry date minus notice period, flagged at 30, 7 and 1 days
Quick answers.
Yes. Manual obligations sit in the same register with the same reminders and evidence.
No. An obligation is what the contract binds you to, extracted from its text and tracked here with evidence. A task is what a person decided to do by a date. A task can point at an obligation; completing a task never discharges an obligation.