Contract Clause Review | Real Minds AI
Professional Services /Document Generation live field guide · 9 min

Contract Clause Review

First-pass triage of an inbound contract against your firm's playbook — every clause classified, the risky ones flagged with a suggested redline, before a lawyer opens the document.

theater/demos/profsvc_contract-review.html · sandbox · read-only
Open
FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads each clause of an inbound contract, matches it to your firm's playbook, flags the departures with a draft redline, and surfaces every flag for an admitted practitioner to approve before anything reaches the counterparty.

Input 01
The contract + the playbook

An inbound agreement (PSA, MSA, supply agreement) as machine-readable text, plus your firm's clause playbook — preferred position, fallback and red line for each clause type.

Agent 02
Classifies, scores, drafts

Parses every numbered clause, matches it to the playbook position for its type, and rates the departure green / amber / red with a suggested redline and the playbook rationale.

Output 03
A first pass, for the lawyer

A clause-by-clause risk summary with draft redlines, every flag shown with its working, for an admitted legal practitioner with a current practising certificate to review, edit or reject before anything is sent.

Where it works well

It does the first pass mechanically, in full, on every clause — so the lawyer opens the document already pointed at the risk.

  • On a 47-clause services agreement, most clauses match your standard accepted position; the value is buried in the uncapped indemnity, the reverse IP assignment, the 30-day termination notice below your 60-day minimum.
  • Best for a firm or in-house team with high volume of broadly similar contracts — services agreements, supply agreements, NDAs — and a settled house view on the common clauses.
  • The reviewer who triages a stack of inbound contracts by hand gets that triage as a draft, and redirects the recaptured hours to negotiation and the genuinely novel clauses.

The slow, invisible cost of an inbound contract is the first pass — the hour or two a lawyer spends just locating the four or five clauses that matter among forty-odd that are boilerplate, before any real thinking starts.

Where it works badly

It is confidently wrong when your positions aren't settled — and a clean redline looks more authoritative than the playbook behind it.

  • Weak where three partners would mark up the same indemnity three different ways — with no single preferred position to measure against, the flags become noise.
  • Weak on bespoke, heavily negotiated or one-off agreements — a joint-venture deed, an unfamiliar drafting idiom — where a real risk can be scored green because it doesn't pattern-match the playbook.
  • A scanned PDF, bad OCR, or unusual clause numbering can cause clauses to be missed entirely, so the flagged list is never a substitute for reading the document.
The honest test

Write down how your firm would mark up an uncapped indemnity, a reverse IP assignment and a short termination notice. If three reviewers produce three different answers, the tool will only amplify the inconsistency — fix that first.

The dangerous failure mode is a false green: a clause that matches the playbook on its face but is dangerous in this deal because of the counterparty, the dollar value, or how it interacts with another clause two pages away. The tool rates clauses one at a time; it does not weigh the contract as a whole.

What it doesn't do — and shouldn't

It drafts a redline and flags the departure. An admitted practitioner decides. That boundary is not optional.

WHAT IT DOES
Surfaces where a clause departs from the playbook, with the position it measured against
Drafts a suggested redline citing the playbook rationale
Reports how many clauses it parsed and which it flagged, so the parse itself can be checked
WHAT IT WON’T
Give legal advice or approve any clause
Send a redline or anything else to the counterparty
Weigh the contract as a whole, or judge whether a clause is right for this deal

Reviewing and advising on a contract is reserved legal work in Australia — under the Legal Profession Uniform Law, only a person who is admitted and holds a current practising certificate may engage in legal practice, and unqualified practice is an offence. A wrong call lands on the practitioner and the firm's professional indemnity cover, not on the tool — so the practitioner owns the advice, the negotiation and the signature.

What your data has to look like

An explicit, current firm playbook, and contracts that arrive as machine-readable text.

32%
Typical readiness
across orgs we see, before the first job
A written playbook of preferred positions
Needs shaping
Recorded thresholds to flag against
Needs shaping
Contracts as machine-readable text
Usual weak point
A single, agreed house view per clause type
Usual weak point
An owner and a review cadence for the playbook
Needs shaping
The real first job

The playbook is almost always the weak point — half-written, sitting across partners' memories, old marked-up precedents and a few checklists. Pulling that into one explicit, owned, current set of positions is usually the real first job — capturing what your senior people already know, not buying a tool — and it is bigger and more valuable than the AI layer that sits on top.

Right fit if…
High volume of broadly similar contracts — services, supply agreements, NDAs
A settled house view on the common clauses, written down or close to it
Contracts arrive as clean Word or well-structured, machine-readable PDFs
You want the first-pass triage as a draft, not the advice itself
Walk away if…
Three partners would mark up the same clause three different ways
Most work is bespoke, heavily-negotiated one-off agreements
Your playbook lives in partners' heads and a folder of old Word docs
You want a tool that signs off the contract so a lawyer doesn't have to
Open questions

The worried-buyer questions, answered straight

It can, which is exactly why it never has the last word. It rates each clause green, amber or red against your playbook, but a green only means “matches our standard accepted position” — not “safe in this deal”. Bespoke or unfamiliar drafting can be mis-classified or scored too low, and a clause can be fine in isolation but dangerous because of the counterparty or another clause two pages away. Every flag and every non-flag is a prompt for the reviewing practitioner, never a clearance — and the redline only leaves the firm after a person with a current practising certificate signs off.
Not until the playbook is written down. The tool can only flag a 30-day termination clause as short if it knows your minimum is 60 days, and can only call an uncapped indemnity risky if your position (say, capped at 2x annual fees, consequential loss excluded) is recorded somewhere it can read. Turning tacit partner judgement and scattered precedents into an explicit, current set of preferred positions and fallbacks is the real first job — and usually the more valuable one. It is the work we help with before any AI layer goes near a contract.
No. Reviewing and advising on a contract is reserved legal work in Australia — under the Legal Profession Uniform Law only an admitted practitioner with a current practising certificate may do it, and unqualified practice is an offence. The tool does the mechanical first pass — locating every clause, matching it to the playbook, drafting the redline — so the practitioner spends their time on judgement, negotiation and the clauses that genuinely need a human. It recaptures reviewing capacity; it does not remove the reviewer.
As current as your actual negotiating position. If the firm quietly moved its liability cap or started accepting a clause type it used to reject but the playbook still says the old thing, the tool will confidently flag deals against a stale standard — or wave through something you’d now push back on. The playbook needs an owner and a review cadence, the same as any precedent bank. Stale positions are the most common cause of wrong flags.
Contracts are commercially sensitive and frequently attract client legal privilege, so this matters. The clause text and playbook are sent to the language model that does the classification; which model, where it runs, and its data-retention and training terms are decisions we scope with you up front, including options that keep data within agreed boundaries. We design the data path so confidentiality and privilege obligations under the Australian Solicitors’ Conduct Rules are respected — that is part of the build, not an afterthought.
You don’t take that on faith. The tool reports how many clauses it parsed and which it flagged, and the reviewer works from the full document, not just the summary — the flagged-clause list is a starting point for the human, not a substitute for reading. If the contract is a scanned PDF, badly OCR’d, or structured in a way the parser misreads, clauses can be missed entirely, which is why the practitioner stays responsible for the document as a whole.
What it takes to build
3–5 weeks · 4 phases
Reused from template~65%
Bespoke to this skin~35%
stack · Claude · clause library · review UI
What it would cost

Fixed scope, fixed price, fixed dates.

01
Bite-sized first piece
Encode the playbook, one contained change
02
Pilot build
Most builds land here
03
Embedded support
Scale on proof

Considering this for your firm?

The honest place to start is the playbook — getting your preferred positions written down and owned. Tell us where the first pass hurts; we'll play it back, scope it, and show you what's possible.

More in Professional Services
Evidence Chronology Builder
View →
Inbox Triage
View →
Precedent & Knowledge Finder
View →
Policy Precedent Finder
View →
How We Work Proof Talk to us
How We Work Proof Talk to us
Ask us anything