Contract Review Agent · Use case
How can AI redline contracts against our playbook on our own infrastructure?
A contract review agent reads an uploaded contract, compares each clause with your playbook, and marks where the contract departs from your positions, with suggested wording for each point. It drafts and a lawyer decides: the agent does not send a redline to the other side. It runs on your own infrastructure, so contracts are not sent to a public AI service.
Clause by clause, by hand.
On contracts that are confidential.
- ✗ 01Legal teams review routine contracts clause by clause against the same playbook, and the queue holds up the business.
- ✗ 02Contracts are confidential and often privileged, which rules out a hosted assistant.
Where it stops for a person
Always, before any change is sent.Always. Every suggested change goes to a lawyer, who accepts, edits or rejects it. The agent sends nothing to a counterparty.
It redlines.
A lawyer decides and sends.
Step · 01
The playbook is connected from SharePoint or Confluence.
Step · 02
A user uploads a contract.
Step · 03
The agent compares each clause with the playbook position.
Step · 04
It lists each departure, cites the playbook rule and drafts suggested wording.
Step · 05
A lawyer reviews the points, edits them and sends the redline.
Reads from · connectors
File Upload
SharePoint
Confluence
The contract arrives through File Upload. The playbook is read from SharePoint or Confluence.
Acts through · MCP servers
Nothing: it drafts and a person sends. The suggested changes are a draft for the lawyer.
What you set up
- Write the playbook: your position on each clause, and the fallback.
- Connect the playbook and choose who may upload contracts.
- Score the agent on past contracts your team has reviewed.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does the agent send the redline to the other party?
No. It drafts suggested changes, and a lawyer reviews and sends them.
Does it give legal advice?
No. It compares a contract with the positions your legal team has written and shows the differences. The judgement stays with the lawyer.
What kinds of contract can it review?
Those your playbook covers. The agent works from the positions you write, so it is as specific as the playbook.
Do contracts leave our network?
No. The contract, the playbook and the model stay on your own infrastructure.