Clause-level contract review for teams that redline every day

01 Features

The review engine, clause by clause

Eight capabilities that together replace the first pass of a contract review. Each one is auditable: you can always see which clause produced a finding and which rule it was measured against.

01 — Intake

Clause detection and document structure

Clauzy rebuilds the instrument before it reads it: numbering hierarchy, sub-clauses, schedules, annexes, order forms and incorporated policies.

  • Layout-aware OCR for scanned and photographed executions
  • Defined-term graph, including terms defined only in a schedule
  • Broken cross-reference detection (“as set out in clause 14.3” where 14.3 does not exist)
  • 62 recognised clause types across commercial, data and employment agreements

02 — Judgement

Risk scoring against your standard

Every clause receives a severity, a rationale and a rule citation. Severity reflects your tolerance, not a generic market view.

  • Three-tier ladder: blocking, negotiable, drafting hygiene
  • Value- and region-conditional rules (a €5k renewal is not scored like a €5m MSA)
  • Missing-clause detection: what a contract of this type should contain and does not
  • Document-level risk score with the arithmetic shown

03 — Output

Redline suggestions in your drafting voice

Suggestions are replacement clause text, not advice to “consider negotiating”. They are written to match the register of your own precedents.

  • Native Word tracked changes with attributed comments
  • Preferred, fallback and walk-away wording offered per clause
  • Style learned from your executed precedent set, not a template library
  • Clean and marked-up versions exported together

04 — Governance

Playbook enforcement

The playbook is a living document with an owner, a version and a history. Rules can be authored in plain language and tested against past deals.

  • Plain-language rule authoring with an immediate dry-run against signed contracts
  • Separate playbooks per entity, region, counterparty tier or contract family
  • Override analytics: which rules your team overrules, and how often
  • Versioned rule history with author and effective date

05 — Iteration

Version comparison across negotiation rounds

Round four is where obligations quietly change. Clauzy compares by clause meaning rather than by character diff.

  • Semantic clause diff that ignores renumbering and reformatting
  • Alerts when an accepted position is silently reverted
  • Definition drift tracking across versions
  • Full negotiation timeline per document

06 — Workflow

Approval routing

Blocking findings route to the person who owns that risk, with the clause, the rule and the proposed wording attached.

  • Conditional routing by clause type, deviation severity and contract value
  • Slack and email approvals with a full decision record
  • Standing delegations and out-of-office fallbacks
  • Exportable audit trail per document

07 — Obligations

Post-signature obligation extraction

The review does not end at signature. Clauzy extracts what was actually committed to and when it falls due.

  • Renewal, notice and price-review dates with owner assignment
  • Service levels, reporting duties and audit windows captured as dated items
  • Calendar and ticketing export
  • Portfolio view of upcoming auto-renewals

08 — Assurance

Security and data handling

Contracts are among the most sensitive documents a company holds, so the default posture is retention-averse.

  • EU-hosted processing with a zero-retention model agreement
  • Customer documents never used as training data
  • Configurable retention from 24 hours to 7 years, with hard deletion
  • SSO, SCIM provisioning and role-scoped access to matters

See it read one of your own contracts

Start a trial and put a live inbound agreement through the full loop, or test a single clause in the public analyzer first.