Contract obligation register

Register

The obligations and key dates you extracted from a contract, and who is watching each one.

CompliMaint has not seen the contract

It reads nothing, interprets no clause, derives no date and calculates no notice period. Every row is a reading list you made while going through the document yourself — which is the work, and the work is why the register is useful. It takes no view on whether anybody is in breach, entitled to anything or obliged to do anything.

There is no Contract object here, deliberately

The obvious next step from a register of obligations is a canonical Contract that owns them, with parties, terms and renewal logic — and the step after that is a product that interprets one. The obligations hang off a matter, which already exists in this product, and the contract stays a document you keep wherever you keep it.

Related contract tools: Contract review tracker · Confidentiality agreement register · Document execution log

Obligations and dates you extracted yourself. CompliMaint reads no contract, interprets no clause, derives no date and reaches no conclusion about breach, entitlement or obligation. Not legal advice. Everything runs on your device.

Questions people ask

Does it read my contract?
No. Nothing is uploaded, nothing is parsed and no clause is interpreted. You read the document and write down what you found.
Does it calculate the notice date?
No. The key date on a row is the one you read off the document. CompliMaint derives no date and counts no period.
Does it tell me if we are in breach?
No. It reaches no conclusion about breach, entitlement or obligation. That is legal analysis and this is a list.
Why is it attached to a matter rather than a contract?
Because a Matter already exists in this product with a stable id, and a canonical Contract object would be the start of a tool that interprets contracts. The document stays yours.