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
- ✓A reminder job that actually runs, with an idempotency log so a reminder is not sent twice
- ✓Reminders across in-app, email, WhatsApp and push
- ✓Evidence attachments on an obligation
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.
This is the part of the product where deadline tracking genuinely works. A scheduled job sends reminders on each obligation's own lead times, through in-app, email, WhatsApp and push, 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. There is a dashboard, a renewal pipeline for contracts coming up for renewal, and an export of the whole register. Since September 2026 the non-renewal notice deadline and the renewal decision live on the contract record itself rather than in this register: 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 — see Contract lifecycle.
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 across in-app, email, WhatsApp and push. Attach evidence when you complete one.
What you get.
- ✓AI extraction of obligations from a contract, re-runnable
- ✓A reminder job that actually runs, with an idempotency log so a reminder is not sent twice
- ✓Reminders across in-app, email, WhatsApp and push
- ✓Evidence attachments on an obligation
- ✓Dashboard, renewal pipeline, and export of the register
- ✓Tender deadlines, insurance renewals, M&A closing-checklist items and audit remediation all sync into the same register
- ✓Notice deadlines are on the contract record — expiry date minus notice period, flagged at 30, 7 and 1 days, with one system-filed task at 30 days to decide: renew, renegotiate or terminate
- ✓The renewal decision is recorded on the contract with who made it and when; making it completes the open notice-deadline task
Quick answers.
The filing calendar is a researched catalogue of statutory dates whose reminders do not currently fire. This is contract-derived, and its reminders do. If you need deadline tracking that actually chases you, this is the one.
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, and lives in the organisation's one task list. A task can point at an obligation, and the notice-deadline task the sweep files points at its contract; completing a task never discharges an obligation.
More in Compliance & Deadlines.
Daily ingest of RBI and SEBI circulars into a searchable feed.
A researched catalogue of 53 Indian statutory deadlines, seeded into your calendar with recurrence rules.
Point at one regulatory change and see which of your contracts and obligations it actually hits.
A free 15-question DPDP self-assessment on this site, and an evidence-based control assessment inside the product.