- contact@insightcontractsai.com
From the business’s request to the decision record, and on to renewals and obligations. Each capability below is in the product today, shown on the demo company’s data.
The intake queue holds what the business asked for: the contract type, the counterparty, whether it is their paper or ours, whether the counterparty will process personal data, the value and the date it is needed. Opening a matter brings the drafts with it, or a draft is uploaded as PDF or Word.

The reader turns a draft into its clauses: parties, term and renewal, the auto-renewal notice, termination, limitation of liability, indemnity, intellectual property, confidentiality, data protection, governing law, payment terms and assignment. Each is quoted with the page and line it came from, the same in the PDF, the Word file and the text layer, alongside the terms read from it.

Each clause is compared with the playbook row for its contract type and the company’s role. It is preferred, within the fallback, a deviation, a walk-away position, or missing. The severity and the approver come from the playbook, and the suggested redline is the playbook’s own fallback language, copied verbatim.

Some of the most expensive problems are not in any one clause. The review reads the draft against the rest of the contract family and raises what it finds as findings of their own, with the evidence quoted.

Every draft is kept as a version. When the counterparty sends a new one, it is read and reviewed at once and compared with the last: which clauses changed, the words removed and added, and the playbook position before and after. A redline the counterparty takes resolves its finding on the next draft; one it ignores is reopened.

When something is missing or redlines are ready, an agent drafts the request; a counsel can write one too. Every request is held until a person sends it. The counterparty answers through a link with no login, and what it uploads is filed at once: a revised draft becomes the next version, read, reviewed and compared.

Approval controls from Rules Studio decide what blocks a matter and what goes to the General Counsel. The counsel submits; another person approves. The decision record keeps the draft and version, each control’s outcome, and every deviation’s position and resolution as they stood.

Every signed contract is read the same way as a draft, so the repository holds its key terms with page and line: the term, renewal and notice, liability, governing law, assignment and the rest. A matter signed in InsightContracts joins it the same way.

For an auto-renewing contract the date that matters is the last day to give notice: the end of the current term less the notice period, both as the executed copy states them. The calendar shows which windows are closing, which have passed and which contracts simply end.

Obligations are read from the executed copy: certificates and reports the supplier owes, access the company must provide, information to return or destroy at the end. Each has an owner, a due date and its recurrence, and the tracker shows what is overdue and due soon.

The approval controls are rules, not code. Legal operations can see exactly what blocks a matter and what refers it to the General Counsel, try a change against a real matter, and publish it with a record of who changed what. The playbook itself is data too.

The copilot answers questions about the open matter with read-only tools: the summary, the clauses, the playbook review, the playbook positions, the versions and what changed, requests, what the agents did, obligations, renewals and a search of the repository. It reads; it never sends, signs, approves or changes anything.
