Home›Documents

Send your lawyers only the contracts that need them.

Most NDAs and order forms that reach legal look like the last one. Your lawyers still read every one, because they are the only people who know the playbook. The business waits, and the contracts that matter wait behind the routine ones.

LegalOperator does AI contract review against your playbook. A contract that meets it goes back to the employee as a pass. One that does not reaches the right lawyer with the summary written and the findings in Word.

Book a demo See it in action
Demo environment sample data. A reviewed sample mutual NDA with Meridian Alloy Systems open beside its findings. Each term shows a green or yellow verdict, and a short reason.
A sample mutual NDA reviewed in the demo environment (sample data; SkyWalker and Meridian Alloy Systems are fictional companies). The document is on the left, and the findings are on the right with a verdict for each term.

Let the playbook do the first read

Thursday, 11:05
A procurement manager sends legal a supplier’s NDA. Iris names the document type, pulls out the parties, dates and dollar amounts, and checks each term against your playbook: green, yellow or red, with a reason. Every term is in range, so the manager gets a pass in the channel they asked from. No lawyer is involved.
Thursday, 3:40
A logistics vendor sends its own master services agreement, and your deal-breaker term is off. The contract goes to the right lawyer with a plain-language summary, what the business should and should not do in the meantime, and the deadlines, parties and dollar amounts.
Friday, 9:00
The lawyer opens the reviewed contract in Word, each finding a comment on the exact text. She asks for redlines, then accepts or rejects each tracked change before anything goes to the vendor.
The next week
A licensing deal arrives under another country’s law, beyond what your team covers. Your lawyer turns the request into a matter in one step and engages a firm. The contract and the playbook findings are already on the matter, and the firm’s invoices land there too.

Most contracts never leave your team. The ones that do keep their history: the matter carries the contract, and the firm’s invoices are read in E-billing. When a similar contract comes in later, matter research finds this one. Contracts arrive like any other request, through the Intake.

Document generation

Draft standard documents on your own paper.

Most of what legal drafts is the same document with new details: another NDA, another order form, another engagement letter. Retyping names, dates and amounts into last month’s version is slow, and it is how the wrong counterparty ends up in a signed contract.

Once
An admin loads your Word templates: your NDA, your MSA, your order form, your engagement letter. There are no merge fields to set up. Iris reads each template and works out which details change each time.
Monday, 9:20
A sales lead asks Iris in Slack for a mutual NDA with a new prospect and gives the company name, the effective date and the term. Iris shows what it will fill in before it starts.
The draft
It comes back in the same thread as a Word file on your own paper, every detail filled in as a tracked change, and anything Iris was unsure of flagged for a second look.
Next quarter
Legal updates the NDA. The new version replaces the old one, and the details from earlier drafts carry over, so any of them can be made again on the new paper.

Ask from the web app, Slack, Teams, email, or inside Claude, ChatGPT or Microsoft Copilot. The draft comes back where you asked.

Your lawyers set the standard once

Your lawyers write the playbook in a guided chat. For each term they state the standard ask, the acceptable fallback and the hard no, and they mark one deal-breaker per document type. When a rule is vague, AI proposes clearer wording for a lawyer to accept or reject.

Common questions

Can LegalOperator draft documents from our own templates?

Yes. An admin loads your Word templates once, such as an NDA, an MSA, an order form or an engagement letter, with no merge fields to set up. Anyone can ask Iris for a draft, and it comes back as a Word file on your own paper, with the details filled in as tracked changes and anything Iris was unsure of flagged.

Can AI review a contract against our playbook and return Word redlines?

Yes. LegalOperator compares each term with your standard ask, acceptable fallback and hard no, and exports the reviewed contract as a .docx with each finding as a Word comment. Ask for redlines and they come back as tracked changes that a lawyer on your team accepts or rejects in Word. Redlines run as a background job, not instantly.

Does it review against our own playbook?

Yes. Your lawyers write the playbook in a guided chat: for each term, the standard ask, the acceptable fallback and the hard no, with one deal-breaker term per document type. If a rule is vague, AI proposes clearer wording for a lawyer to accept or reject.

Who decides what goes to the counterparty?

A person on your team. Redlines come back as tracked changes, and a lawyer accepts or rejects each one in Word. The playbook your lawyers wrote decides whether a contract passes or goes to a lawyer.

Which documents are graded and which are only read?

An admin decides, per document type. Contracts such as an NDA or an MSA are graded term by term against the playbook. Notices and subpoenas are fact-extract only: the document is read and the key facts are pulled out.

How does the AI check its own work?

One AI pass grades each term and a second pass checks it. For redlines, one pass proposes the minimal edit and a second pass drops any edit it is not confident about. A lawyer accepts or rejects every redline.

See a contract review in a demo.

Watch a contract compared with a playbook, with the findings and redlines in Word. Prices are on the pricing page.