AI Prompts for Contract Review: Check a Freelance Agreement Before You Sign

AI prompts for contract review turn a client agreement into a clause map, a list of red flags and one verdict: sign, negotiate or walk away. Here are the six clause groups that decide it and the check nobody runs first.

The agreement lands at 6pm and gets skimmed for two things: the payment date and whether the amount matches what you discussed. A model does not replace the lawyer, but it maps each clause group, ranks the red flags, pulls every amount and deadline into one table, and ends with a verdict.

What an AI Contract Review Can and Cannot Do

One line before anything else: this is document triage, not legal advice. A lawyer decides what is enforceable in your jurisdiction.

It Reveals What Is in the Document - and What Is Missing

A model reads structure well: it summarizes each clause group in plain language, ranks red flags by severity with the section reference, and catches what is absent - no kill fee, no cap on revisions, no late-payment interest. Absence matters as much as presence.

It Cannot Tell You Whether a Clause Is Enforceable

No model rules on whether a clause is valid where you live, whether a price is fair, or what a judge would do. The frame is triage, not a legal opinion: the output prepares you for a lawyer, it does not decide for you.

Hallucination Is a Known Failure Mode

Models can invent clauses or cite the wrong rule, which is why the catalog prompt forces a direct quote behind every claim and forbids inventing clauses that are not in the text. Check each line of the report against the quoted line before you negotiate.

The Six Clause Groups That Decide a Client Agreement

Most freelance disputes land in one of six places.

Payment Terms - Net 60, Net 90 and "When Satisfied"

Long terms, and any wording that ties payment to the client being satisfied, turn an invoice into an open negotiation. Ask for a short term, a concrete date, an objective acceptance criterion and late-payment interest.

Scope and Revisions - Where Scope Creep Becomes Legal

Unlimited revisions turns a fixed fee into endless work. The antidote is a number: define the revision rounds and route the rest through a change order.

IP - Ownership Should Transfer on Payment, Not on Creation

The trigger is the critical detail: if ownership moves the moment work is created, you gave up your leverage before being paid. In US copyright law, work made for hire is not automatic - ownership passes only through a written assignment, and some assignments sweep in your pre-existing tools and templates. Reserve in writing the right to show the work in your portfolio.

Termination - The Off-Ramp That Only Works One Way

Termination for convenience lets the client walk out without a reason, wiping out weeks of pipeline. Notice often runs 30 to 90 days; 14 to 30 days plus payment for delivered work is the reasonable ask.

Indemnity and Liability - The Clause Bigger Than Your Fee

Indemnifying someone means promising to cover their legal costs. Boilerplate arrives uncapped, one-sided and triggered by any claim: a small project can expose you to claims that dwarf the fee. Negotiate a cap tied to the contract value and indemnity limited to your own negligence.

Confidentiality and Non-Compete - What You Cannot Take With You

An NDA defines which information you cannot use or show, and for how long; a non-compete defines who you cannot serve afterwards. Check the scope, the duration, and whether the wording blocks you from your own field.

Three Real AI Prompts for Contract Review You Can Run Today

The Full Redline Pass

This prompt does the first sweep. Paste the whole agreement and you get five blocks: a plain-language summary of each clause group; red flags ranked by severity with the section reference; every amount and deadline in one table; five changes written as change X to Y because Z; and a verdict of safe to sign, needs changes or do not sign. The Claude Contract Redline Assistant runs that structure with the honesty rules built in.

The Three Rules That Keep It Honest

Those rules are the reason the output is usable: no inventing clauses that are not in the document, the exact quoted text behind every claim, and a note that the user is not a lawyer. A report with no section reference is useless for negotiating.

Feed It Every Page, Including the Boilerplate

The usual mistake is pasting only the important clauses and leaving out the annexes and the final pages. The text under review is the complete document, and if it arrives as photos the small print has to be readable. A report over an incomplete document is a bad report.

Prompt 2 - Translate Any Clause Into Plain Language

Keep the Meaning, Flag the Ambiguity

Legal text to plain language solves the next moment: you see the clause is there but do not understand what it commits you to. It rewrites legal or policy text in everyday language under three conditions - the legal meaning stays identical, names, dates and numbers are preserved exactly, and anything ambiguous is flagged instead of fixed. What gets flagged is what you renegotiate.

Use It on the Worst Paragraph, Not the Whole Contract

Run it on the densest clause, usually indemnity or termination, and you get a translation you can paste into an email. Translating the whole agreement produces a summary nobody rereads. As with reusable prompts for client work, build it once and reuse it.

Prompt 3 - Turn the Signed Contract Into a Scoreboard

From Clauses to Milestones

Signing does not end the document work: deliverables, dates, acceptance criteria and notice periods have to be operated. The Project Manager Assistant turns the project into a plan with explicit scope of what is and is not included, milestones with owners and dates, and a risk register. The not-included list is the scope clause in practice: a request outside it gets a quote as a change.

The Change-Order Habit

Every request outside the scope gets the same answer with a number attached - that is how the leak gets plugged.

Before You Paste - The Confidentiality Check Nobody Runs

A Contract You Received Is Not Yours to Share

Pasting a document you received under an NDA into a third-party tool can breach that obligation, and the tool's privacy settings do not change it: the duty comes from your agreement with the client. Whether it applies depends on the wording, which is why the safe-paste checklist treats it as a risk to verify.

What to Do Instead

Three steps, in order: read the NDA under which you received the document; strip what the analysis does not need - names, personal data, commercial annexes; and when confidentiality is the core of the matter, use a local or approved environment.

The Step No Model Replaces

The report gets you to the table with the list written. Enforceability, price and signing stay human - in larger agreements, a lawyer's call.

Ready to run it on the next agreement in your inbox? Start with the contract redline pass, translate the worst clause with plain-language legal, then keep the obligations visible with the project manager assistant. The job is not reading a contract - it is arriving at the table with the change list already written. Still document triage, not legal advice.