Obligations & key-date tracking
The post-signature layer: renewal, expiry, milestone, and notice dates pulled from executed contracts so a deadline never slips.
Review doesn't end at signature. The obligations register is the post-signature layer — it tracks the renewal, expiry, milestone, and notice-period dates buried in executed agreements so a lawyer never misses an auto-renewal window or a termination-notice deadline.
- Obligations are grounded the same way findings are: the underlying dates and terms come from clause extraction, where typed values (dates, amounts, parties) are parsed deterministically from a verbatim, source-anchored span — not guessed by a model.
- Each obligation ties back to the matter and the clause it came from, so you can jump from a looming date to the exact provision that created it.
Trust
Because every tracked date traces to a located clause, the register is auditable — you can always show *why* a deadline is on the calendar.
Related technical documentation
Clause extraction & the 41-category pack
Pull structured clause facts — type, verbatim text, and typed attributes — with the same grounding discipline as review.
Matters & workflows
The matter is the unit of work everything hangs off — documents, reviews, findings, deadlines, and audit — and workflows turn a repeatable review into one click.
Regulatory monitoring & radar
Subscribe to changes from Nigerian regulators, and let the radar match a change to the matters it affects and draft the briefing.