Gathersense

Contract review

Your playbook, on every contract.

Gathersense reads each contract against the standards your firm already wrote. The lawyer keeps the judgment. The platform keeps the record.

Caspian Supply Agreement

v3 · reviewed against your playbook

Chat with AI
SummaryRiskCommercialPlaybookTemplate

Risk heatmap

DraftingLiabilityRiskIPComplianceTerm
57/100High

Top risks

  • Data-processing controls missingcritical
  • Liability cap below markethigh
  • Auto-renewal on short noticehigh
  • Indemnity scope unclearmedium

Recommended resolution

Add a data-processing addendum with hosting, retention, and sub-processor terms.

The problem

A second reviewer catches what the first one missed.

Most contracts never get a second reviewer. The work piles up, the standards live in a document no one opens, and consistency depends on who happened to read it.

What it does

Every angle of a contract, in one read.

A structured first read on every contract, in the language of legal review.

The firm's standards applied to every document, every time.

Several angles of analysis running in parallel, not several separate runs.

Findings written the way a careful associate would write them, ready to edit.

How it works

From upload to signed-off review.

The review is a loop your team already knows. Gathersense runs the consistent part; the lawyer runs the judgment.

  1. 01

    Upload the contract

    A new draft, a counterparty's paper, or a redline that just came back. Scanned documents are read too.

  2. 02

    The review runs against your playbook

    Summary, parties, risk, compliance, commercial terms, and template fit run in parallel. The standards applied are the ones your firm wrote, versioned.

  3. 03

    Findings come back as they finish

    Each finding is written the way a careful associate would write it, with the source cited and your preferred clause at hand.

  4. 04

    You read, decide, and sign off

    Agree, disagree, edit. Every step is recorded the moment it runs, so the review can be replayed later.

Template check · Limitation of liability

Counterparty redline v2 · against MSA template v4

3 deviations

Clause 11.2

The Supplier's aggregate liability under this Agreement shall not exceed the fees paid in the twelve (12) months the fees paid in the twenty-four (24) months preceding the event giving rise to the claim, excluding losses arising from a breach of clause 9 (Confidentiality) or clause 12 (Data Protection).

Below your floor · Playbook §4.2

Your playbook holds a 24-month floor on the liability cap. The counterparty's edit restores it; the carve-outs in their v2 still narrow clause 12.

Your clause 7.1

In the product

Summary, parties, risk, compliance, commercial terms, and playbook fit.

Upload a contract. Gathersense runs it against your firm's playbook from several angles at once. Findings come back as they finish. You read, edit, agree, disagree, and sign off.

Document analysis · Findings

7 open
  • Uncapped data-processing liability

    No DPA; controller obligations unmet.

    critical
    Add a data-processing addendum (your clause 7.2)Apply
  • Liability cap below your floor

    Capped at 12 months’ fees vs. your 24.

    high
  • Consequential-damages exclusion

    Broad carve-out favours the counterparty.

    high
  • Auto-renewal, 90-day notice

    Shorter window than your standard.

    medium

Every angle, in one read

Summary, parties, risk, compliance, commercial and financial terms, and playbook fit, all in parallel against your standards.

Your playbook in the loop

The standards your firm wrote are the standards Gathersense applies, versioned, so each review records the exact version it used.

Your clauses as the reference

Preferred clauses, fallback positions, and red lines feed the review, so a contract is measured against what your firm actually accepts.

A redline-aware template check

When a contract comes back redlined, Gathersense shows what moved against your template and where the deviation matters.

A contract-scoped assistant

Ask questions about a specific contract or its review. The assistant stays inside that scope.

Findings ready to edit

Each finding is written the way a careful associate would write it. You read, agree, disagree, and sign off.

Governed and secure

A record per review.

See security & compliance

What was read, which playbook version applied, and what the AI returned, all recorded the moment the review runs. Replayable, exportable, and audit-ready, so the answer to “show me how the AI got there” is already written.

  • Each review records the exact playbook version it applied.
  • The contract-scoped assistant stays inside the contract.
  • EU-based. Built to ISO 27001 standards. GDPR compliant.

In practice

Where teams put it to work.

The same review, earning its keep on different desks.

NDA triage

The volume work. Every NDA gets the same read against your standard positions, so the queue moves without the standards slipping.

Redline rounds

A draft comes back marked up. The template check shows what moved against your paper and which deviations actually matter.

M&A due diligence

A room full of agreements. Every one gets the same in-depth read, with findings traceable to the page they came from.

Playbook enforcement

New standards land. The playbook is versioned, so every review records which version applied and the audit stays clean.

Who it's for

Built for the lawyer and the function.

For the lawyer

The review your firm would run, on every contract, every time, with findings you can edit and a record you can stand behind.

For the function

Cycle time on contract review drops, external counsel spend on routine review stays inside, and every contract carries an audit trail.

See it read one of your contracts.

Bring a real contract and your standards. We will show you the review on your own work.