Skip to content
Azenye
Sign up

AI Clause Reviewer · Stage 2 of 7 · Review

Their paper, checked against your playbook, clause by clause.

When a vendor or customer sends their own contract, Azenye reads all of it, compares every clause to the positions your Legal team has approved, flags what is risky or missing, explains why in plain English and drafts redlines from your own fallback clauses.

Try 14 days freeContact us
Exhibit C
AI Clause Reviewer · CloudServe MSA
9.2Limitation of liabilityHigh risk
Each party's total liability under this Agreement shall not exceed the fees paid in the one (1) month preceding the claim twelve (12) times the fees paid in the twelve (12) months preceding the claim, excluding liability for breach of confidentiality, data protection and IP indemnities.

In plain English

If CloudServe loses your customer data, the most you could recover is one month of fees. Your playbook asks for twelve.

Source of redline

Your fallback 9.2(b), MSA playbook v4, approved by Legal.

Accept redlineEdit
AI Clause Reviewer · CloudServe MSA, product screen

Section 2. AI Clause Reviewer

Operative clauses
  1. 2.1

    Your playbook is the reference

    Azenye does not judge contracts against a generic idea of what is reasonable. It compares them to the positions you have approved for each contract type: liability caps, indemnities, payment terms, renewal, termination, data protection and governing law.

  2. 2.2

    Missing clauses are caught too

    A contract can be risky because of what it leaves out. If an MSA has no data processing obligations under the Digital Personal Data Protection Act, no security audit right or no exit assistance, the review lists it as missing.

    The silent risks are usually the costly ones.

  3. 2.3

    Explanations a business owner can follow

    Each flag comes with a short explanation of what the clause means in practice, so the person who requested the contract understands why Legal is asking for a change.

  4. 2.4

    Redlines from your own wording

    Suggested changes are drawn from the fallback clauses in your Template Vault. Reviewers can accept, edit or reject each one, and the tracked-changes document goes back to the counterparty in Word.

  5. 2.5

    Scanned and messy documents

    PDFs, scanned copies and Word files with heavy tracking are read with OCR and clause detection. Numbering that does not match your template is mapped by meaning, not by heading.

  6. 2.6

    Review straight into approvals

    Once Legal has reviewed, the contract moves to the Approval Chain with every deviation listed, so Finance and leadership see exactly what changed from standard terms before they approve.

How AI is used here

  • Azenye is software. It is not a law firm and does not give legal advice.
  • Flags and suggested redlines are based on your company's own playbook. Lawyers or authorised staff review and decide.
  • Contracts are confidential and encrypted, never used to train AI models for other customers and never sold.
Read our Responsible AI policy

Questions about AI Clause Reviewer

Q1Does the AI decide what we sign?

No. It flags, explains and suggests. A lawyer or an authorised person on your team reviews and decides on every change.

Q2Is our data used to train AI?

No. Your contracts and playbooks are never used to train models for other customers, and they are never sold.

Q3How do we build a playbook?

Start from your existing templates and guidance notes. We help you set up positions for your most common contract types during onboarding, and you can refine them as you go.

Works alongside

The executed copy

Trial agreement · Schedule 1

Try Azenye free for 14 days.

  1. 1.1Every feature on the Agreement plan, for your whole team.
  2. 1.2No card needed. Nothing renews automatically.
  3. 1.3Bring your own templates and playbook from day one.
  4. 1.4Your contracts stay yours, and leave with you if you go.
Azenye

For Azenye · signed

Want a walkthrough with your own contracts first?Contact us