Contract Review

Contract review: clauses you can trace, judgement stays with people

Contract knowledge inside a legal team is never one template. The same indemnity clause reads differently across customers and across years, while payment milestones, acceptance criteria and dispute forums sit in the body, in annexes and in email threads. Finding an old agreement comes down to folder names and memory. Comparing two revisions means reading both line by line. Review comments stay in someone's annotations, so a new owner starts the reading over.

RatioMax handles three steps. It consolidates agreements, annexes and review notes into one knowledge base, routes a question to the clause text with a citation, and shows what changed between revisions. It also assembles a first draft from language your team has already approved. It does not make the legal call: whether a clause is acceptable, which risk to carry and whether to sign remain decisions for your legal and business owners, and their sign-off closes the file.

Where it breaks

  1. Agreements spread across inboxes and laptops

    Signed agreements live on laptops, in email attachments and on shared drives, filed by customer name, with annexes and amendments kept somewhere else. Locating a comparable clause from two years ago is guesswork, and even then someone has to verify it is the executed version.

  2. Comparable clauses written every which way

    Indemnity, acceptance and payment terms are drafted per project, so no two are directly comparable. To reference a similar deal, a reviewer must find the old contract, read it end to end and then decide what carries over. Most of the hour goes to re-reading.

  3. Review judgement stranded in annotations

    Which clause was changed, why, and which compromise was finally accepted mostly survive in tracked changes and email. When the reviewer leaves, the reasoning leaves with them, and the next contract reopens the same argument from a blank page.

  4. Scans and legacy contracts return nothing

    Older agreements and counterparty scans ship without a text layer, so full-text search returns nothing at all. Checking one historical commitment means paging through images, and how fast and how accurately that goes depends entirely on the reader.

How RatioMax responds

  • One library for contracts and annexes

    Contract bodies, amendments, annexes and review notes are filed in one knowledge base with metadata for customer, project and signing year, and each knowledge base can bind its own object-storage bucket. Complex-layout PDFs go through OpenDataLoader, scans and images through PaddleOCR-VL, across ten-plus formats, so legacy contracts need no manual re-keying.

    Platform capability: Dual-engine parsing

  • Clause answers with their source

    Hybrid vector and keyword retrieval with a ReRank pass takes a question about acceptance criteria straight to the clause text, and every answer carries a clickable citation that opens the page it came from. Where the documents are silent, the system says so instead of inventing a term.

    Platform capability: Traceable citations

  • Revision differences you can see and undo

    Every edit keeps a chunk-level snapshot, line-level diff highlights additions, deletions and rewrites, and any version can be rolled back. Revisions appear side by side so legal can decide what to accept; comparable clauses from different contracts are listed as candidates for a person to judge.

    Platform capability: Version snapshots

  • First drafts from approved language

    Auto-generated wiki pages organise approved clauses, review conventions and template notes into interlinked pages. When a draft is needed, the system retrieves the language that already passed review and assembles it into a structured first pass for a person to rewrite. Pages keep snapshots, diffs and rollback.

    Platform capability: Auto wiki

Deployment scenarios

  • Before a sales contract goes to legal

    Sales receives the customer's paper. Before submitting it, the commercial owner pulls acceptance, payment and indemnity clauses and checks them against approved wording, flagging only what legal actually needs to see.

  • Renewals and revision checks

    On renewal, pull the previous version with the review notes recorded at the time, diff the two, and confirm which terms are settled and which must be renegotiated, so the same concession is not made twice.

  • Payment and delivery milestones

    Mid-project, ask how this contract sets payment milestones and acceptance conditions. The answer points at the original page, so commercial, finance and delivery check against one agreed text instead of three recollections.

  • Aligning supplier agreements

    When a new supplier framework arrives, retrieve how comparable agreements were handled, list the clauses that diverge, and negotiate from that list rather than from verbal recollection.

Terms and knowledge entities

Essential contract terms
The content a contract needs to stand up: parties, subject matter, quantity, price, performance period and liability for breach. A missing element leaves the arrangement ambiguous.
Contracting capacity
Whether the counterparty is lawfully established, holds the required licences and has authority to sign. It is a fact to verify before signature, not something a business card establishes.
Liability for breach
The remedies agreed for non-performance or defective performance: specific performance, damages, liquidated sums, usually paired with a cap.
Force majeure
An event that could not have been foreseen, avoided or overcome. It can excuse performance, provided the notice period and evidentiary duty in the contract are met.
Dispute resolution and forum
Whether disputes go to litigation or arbitration and which court or institution hears them. It drives cost, duration and enforceability, and the two routes cannot both be named.
Clause comparison
Aligning two contract versions paragraph by paragraph to locate additions, deletions and rewrites, so a reviewer can judge whether the change is acceptable. The comparison is input, not a verdict.
Seal and approval control
The internal approval that precedes applying the company seal: who reviews, what they check and what record is kept. It is the last control point before a contract becomes binding.
Performance milestones
The dated points for delivery, acceptance, payment and warranty start. They anchor reconciliation, follow-up and any calculation of delay.
Review comments
The changes a reviewer proposes and the reasons behind them. They only stay usable when stored with the exact version they were raised against.

These definitions are also exposed structurally so search engines and AI engines can read and cite the concepts accurately.

Solution questions

Can this system review contracts in place of legal?
No, and it should not be used that way. The system retrieves, compares and drafts: it puts the relevant clauses, past review notes and revision differences in front of a person, with the source attached. Whether a clause is acceptable, which risk to carry and whether to sign stay with your legal and business owners. It does not replace legal advice or compliance review.
Can scans and legacy contracts be ingested?
Yes. Complex-layout PDFs go through OpenDataLoader and scans or images through PaddleOCR-VL, across more than ten formats including PDF, Word, Excel and images. Recognised text enters the search index rather than staying a preview. Where a character is uncertain, the answer cites the page so it can be checked against the original.
Can it generate a contract first draft?
It can assemble a first pass from approved language already in the knowledge base: retrieval finds comparable clauses and how they were handled, then organises them into a structured draft for legal to rewrite. The draft is not a finished document; wording, liability boundaries and commercial terms still get a line-by-line human pass. What shrinks is the search-and-copy time.
How does clause comparison relate to human review?
Comparison surfaces the differences; a person decides whether they are acceptable. Snapshots are kept at chunk level, line-level diff marks every change, and any revision can be rolled back. Similar clauses from different contracts are only listed as candidates. Keeping that division explicit is what makes the output usable as review input rather than a verdict.
Can confidential contracts sit on a public cloud?
Most will not, and they do not have to. RatioMax supports full on-premise deployment on Docker Compose or Kubernetes, with four core services that scale independently, so data never leaves your network. Each knowledge base can bind a private OSS or S3 bucket, data-source and MCP credentials are encrypted with AES-256-GCM, and outbound requests pass SSRF protection.
Who can see which contracts?
Spaces separate tenants and four-level RBAC narrows access down to a single knowledge base, so legal, commercial and finance each see their own set, with every access written to a per-space audit log. OIDC handles single sign-on and two-tier API keys scope integrations. External counsel gets a controlled slice, not the library.
Do citations point at the actual clause?
Yes. Answers are drawn from passages that hybrid retrieval and ReRank selected, and each conclusion carries a clickable citation that opens the page and paragraph it came from. Metadata filters narrow by customer, project or signing year. Langfuse and W3C cross-service tracing keep the retrieved passages for every answer, so a review can be replayed later.
How does it connect to the contract system we already run?
Through the API and the MCP service. The platform exposes around 360 API endpoints, and the MCP server offers 29 standard tools over stdio, SSE and HTTP with OAuth2 authorisation; sensitive operations wait for human confirmation. Originals stay in your contract system of record, and the knowledge base handles retrieval, comparison and answering.

Other solutions