AI Contract Analysis: Extract Clauses from PDF Agreements

Tested prompts for extract clauses from contract pdf compared across 5 leading AI models.

BEST BY JUDGE SCORE Claude Haiku 4.5 9/10

You have a contract PDF and you need to pull out specific clauses — indemnification, termination, payment terms, non-compete, governing law — without reading 40 pages line by line. That is exactly what AI clause extraction solves. Instead of ctrl-F guessing at keyword variations or hiring a paralegal for routine review work, you paste the contract text into an AI prompt and get structured clause output in seconds.

The core workflow is straightforward: extract the PDF text, feed it to an AI model with a clear instruction about which clause types to identify, and get back labeled excerpts with the original language preserved. The hard part is writing a prompt precise enough that the model returns clean, usable output rather than a summary that paraphrases away the legally relevant wording.

This page shows you a tested prompt, compares how four leading models handle a real contract input, and explains when this approach works reliably and when it fails. If you are a lawyer doing initial contract review, a procurement manager screening vendor agreements, a startup founder reviewing a term sheet, or an ops team processing lease renewals at volume, this is the workflow you are looking for.

When to use this

AI clause extraction is the right tool when you need to locate, label, and preserve specific contract language quickly across one or many documents. It works best when clause types are standard enough to name explicitly in a prompt and when the underlying PDF text is machine-readable rather than a scanned image.

Screening NDAs, vendor contracts, or employment agreements for specific risk clauses before legal review
Comparing termination or liability clauses across multiple versions of the same contract
Extracting payment, delivery, or SLA terms from supplier agreements to populate a procurement database
Reviewing lease agreements for renewal options, rent escalation clauses, and break clauses
Pulling governing law and dispute resolution clauses from a portfolio of signed agreements

When this format breaks down

The PDF is a scanned image rather than a text-layer PDF — the model receives no readable text and will hallucinate or return nothing useful; run OCR first
You need a legally binding interpretation or opinion on whether a clause is enforceable — AI extraction surfaces language, it does not provide legal advice
The contract uses highly non-standard or proprietary clause structures with no conventional headings — models trained on typical contract formats will mislabel or miss them
The document is over roughly 100 pages and exceeds the model context window — clause extraction breaks silently at the truncation point and you will get incomplete results without knowing it

The prompt we tested

You are an expert contract analyst. Extract and categorize all clauses from the contract text provided below.

Rules:
Output a structured list grouped by clause type (e.g., Confidentiality, Termination, Indemnification, Payment Terms, Governing Law, Liability, IP Rights). For each clause, provide: clause name, a 1-2 sentence plain-English summary, the verbatim quoted text, and the section/page reference if available. Flag any missing standard clauses or unusual/risky language at the end under a 'Risk Flags' section.

Contract text:
This Master Services Agreement is entered into on March 15, 2024 between Acme Corp ('Client') and BlueTech Solutions LLC ('Provider'). Provider shall deliver software development services for a fee of $150,000, payable in three installments. Either party may terminate this agreement with 30 days written notice, and all confidential information shared during the engagement shall remain protected for a period of five years following termination.

Return the extracted clauses now.

Model comparison

Model	Quality	Cost	Latency	Tokens
Claude Opus 4.7	9	$0.1197	22.1s	339 / 1528
Claude Haiku 4.5	9	$0.0034	5.0s	239 / 638
GPT-5.4	9	$0.0138	14.8s	207 / 883
Gemini 2.5 Pro	8	$0.0011	17.3s	214 / 170
Grok 4.1 Fast Reasoning	9	$0.0004	8.5s	352 / 609

Outputs

Claude Opus 4.7 9/10

# Contract Clause Extraction: Master Services Agreement

**Contract Date:** March 15, 2024
**Parties:** Acme Corp ("Client") and BlueTech Solutions LLC ("Provider")

---

## 1. Scope of Services / Deliverables

- **Clause Name:** Services Scope
- **Summary:** Provider agrees to perform software development services for the Client.
- **Verbatim Text:** *"Provider shall deliver software development services..."*
- **Reference:** Not specified (single-paragraph agreement)

---

## 2. Payment Terms

- **Clause Name:** Fees and Payment Schedule
- **Summary:** Client will pay a total fee of $150,000, broken into three installments. Specific installment amounts, due dates, and invoicing procedures are not defined.
- **Verbatim Text:** *"...for a fee of $150,000, payable in three installments."*
- **Reference:** Not specified

---

## 3. Termination

- **Clause Name:** Termination for Convenience
- **Summary:** Either party may terminate the agreement by providing 30 days' written notice, without requiring cause.
- **Verbatim Text:** *"Either party may terminate this agreement with 30 days written notice..."*
- **Reference:** Not specified

---

## 4. Confidentiality

- **Clause Name:** Confidentiality / Survival Period
- **Summary:** Confidential information exchanged during the engagement must remain protected for five years after termination.
- **Verbatim Text:** *"...all confidential information shared during the engagement shall remain protected for a period of five years following termination."*
- **Reference:** Not specified

---

# 🚩 Risk Flags

### Missing Standard Clauses (High Concern)
The contract as drafted is dangerously thin. The following standard MSA clauses are **absent**:

1. **Governing Law & Jurisdiction** — No choice of law or venue specified. Disputes could be litigated in any jurisdiction.
2. **Indemnification** — No allocation of risk for third-party claims (e.g., IP infringement, negligence, data breach).
3. **Limitation of Liability** — No cap on damages; Provider has unlimited exposure. No exclusion of consequential/indirect damages.
4. **Intellectual Property Rights** — Critical omission for a software development contract. No clarity on ownership of deliverables, work-for-hire status, pre-existing IP, or license grants.
5. **Warranties & Disclaimers** — No express warranties regarding service quality; no disclaimer of implied warranties.
6. **Dispute Resolution** — No arbitration, mediation, or escalation mechanism.
7. **Insurance Requirements** — No minimum coverage obligations on Provider.
8. **Acceptance Criteria / Deliverable Standards** — No testing, acceptance, or performance benchmarks.
9. **Force Majeure** — No protection for unforeseeable events.
10. **Assignment** — No restriction on either party assigning the contract.
11. **Data Protection / Privacy** — No GDPR/CCPA or data security obligations (critical for software engagements).
12. **Non-Solicitation** — Common in services agreements; absent here.

### Unusual / Risky Language

- **Vague Scope:** "Software development services" is undefined — no Statement of Work, deliverables list, timeline, or milestones. High risk of scope disputes.
- **Undefined Payment Triggers:** "Three installments" lacks trigger events (e.g., kickoff, midpoint, completion) and due dates. Risk of payment disputes.
- **Termination Without Payment Reconciliation:** The 30-day termination right does not address payment for work-in-progress, refund of prepaid amounts, or wind-down obligations. Either party could walk away mid-project with ambiguous financial consequences.
- **Termination Without Cause Symmetry:** Mutual convenience termination may disadvantage Provider if Client terminates after Provider has staffed up.
- **Confidentiality Scope Undefined:** "Confidential information" is not defined; no carve-outs for publicly available information, independently developed information, or legally compelled disclosure.
- **No Survival Clause:** Unclear which obligations (besides confidentiality) survive termination.

### Recommendation
This document is more accurately a **term sheet or letter of intent** than an enforceable MSA. Before signing, negotiate a full-form agreement incorporating the missing clauses above, and attach a detailed Statement of Work.

Claude Haiku 4.5 9/10

# Contract Clause Analysis
**Master Services Agreement – Acme Corp & BlueTech Solutions LLC**
**Date: March 15, 2024**

---

## PAYMENT TERMS

**Clause Name:** Fee and Payment Schedule

**Summary:** Provider will deliver software development services in exchange for $150,000, paid in three equal installments.

**Verbatim Text:**
> "Provider shall deliver software development services for a fee of $150,000, payable in three installments."

**Section/Page Reference:** Not specified in provided text

---

## TERMINATION

**Clause Name:** Termination for Convenience

**Summary:** Either party may end the agreement by providing 30 days of written notice.

**Verbatim Text:**
> "Either party may terminate this agreement with 30 days written notice"

**Section/Page Reference:** Not specified in provided text

---

## CONFIDENTIALITY

**Clause Name:** Confidential Information Protection

**Summary:** All confidential information disclosed during the engagement is protected for five years after the agreement ends.

**Verbatim Text:**
> "all confidential information shared during the engagement shall remain protected for a period of five years following termination."

**Section/Page Reference:** Not specified in provided text

---

## RISK FLAGS ⚠️

| Risk Category | Issue | Severity |
|---|---|---|
| **Missing Clauses** | No Indemnification clause | HIGH |
| **Missing Clauses** | No Governing Law/Jurisdiction clause | HIGH |
| **Missing Clauses** | No Intellectual Property Rights clause | HIGH |
| **Missing Clauses** | No Limitation of Liability clause | HIGH |
| **Missing Clauses** | No Dispute Resolution/Arbitration clause | MEDIUM |
| **Payment Terms** | No specification of installment amounts, due dates, or payment method | HIGH |
| **Payment Terms** | No late payment penalties or interest defined | MEDIUM |
| **Confidentiality** | Definition of "confidential information" is not provided | MEDIUM |
| **Termination** | No termination for cause provision specified | MEDIUM |
| **Termination** | No clarity on obligations upon termination (e.g., work product delivery, data return) | HIGH |
| **General** | No scope of work or deliverables defined | CRITICAL |
| **General** | No representations or warranties from either party | MEDIUM |

---

## SUMMARY

This contract is **substantially incomplete** and unsuitable for execution. While three basic clauses are present, the agreement lacks critical protective provisions typical of professional services contracts. The absence of IP Rights, Indemnification, and Liability Limitation clauses creates significant exposure for both parties. Immediate legal review and expansion of terms is strongly recommended before execution.

GPT-5.4 9/10

## Parties / Agreement Formation

### Clause Name: Parties and Effective Date
- **Plain-English Summary:** This clause identifies the contracting parties and states when the agreement was entered into. It establishes that the agreement is between Acme Corp and BlueTech Solutions LLC as of March 15, 2024.
- **Verbatim Quote:** “This Master Services Agreement is entered into on March 15, 2024 between Acme Corp ('Client') and BlueTech Solutions LLC ('Provider').”
- **Section/Page Reference:** Not provided

---

## Scope of Services

### Clause Name: Services
- **Plain-English Summary:** This clause states the provider’s core obligation under the agreement. BlueTech Solutions LLC is required to deliver software development services.
- **Verbatim Quote:** “Provider shall deliver software development services”
- **Section/Page Reference:** Not provided

---

## Payment Terms

### Clause Name: Fees and Installment Payments
- **Plain-English Summary:** This clause sets the total contract price and indicates that payment will be made in three installments. It does not specify installment amounts, due dates, invoicing procedures, or consequences for late payment.
- **Verbatim Quote:** “for a fee of $150,000, payable in three installments.”
- **Section/Page Reference:** Not provided

---

## Termination

### Clause Name: Termination for Convenience
- **Plain-English Summary:** This clause allows either party to end the agreement without needing to state cause, as long as they give 30 days’ written notice. It does not address payment obligations upon termination or transition assistance.
- **Verbatim Quote:** “Either party may terminate this agreement with 30 days written notice”
- **Section/Page Reference:** Not provided

---

## Confidentiality

### Clause Name: Confidentiality Obligation and Survival Period
- **Plain-English Summary:** This clause requires confidential information exchanged during the engagement to remain protected for five years after termination. It creates a post-termination confidentiality obligation but does not define “confidential information” or list exceptions.
- **Verbatim Quote:** “all confidential information shared during the engagement shall remain protected for a period of five years following termination.”
- **Section/Page Reference:** Not provided

---

## Risk Flags

### Missing Standard Clauses
- **Governing Law:** No governing law or venue clause is included.
- **Indemnification:** No indemnity obligations are stated.
- **Limitation of Liability:** No cap on damages or exclusion of indirect/consequential damages appears.
- **Intellectual Property Rights:** No ownership or license terms for work product, software, code, or pre-existing IP.
- **Warranties / Disclaimer of Warranties:** No performance warranties or disclaimer language is included.
- **Acceptance Criteria:** No deliverable standards, acceptance testing, or rejection process is provided.
- **Payment Mechanics:** No due dates, invoice process, taxes, reimbursement terms, or late-payment remedies are stated.
- **Confidentiality Definitions and Exceptions:** No definition of confidential information, permitted disclosures, or standard exclusions.
- **Data Protection / Security:** No data privacy, security, or breach-notification terms are included.
- **Dispute Resolution:** No escalation, mediation, arbitration, or litigation procedure is specified.
- **Force Majeure:** No force majeure provision is included.
- **Assignment / Subcontracting:** No assignment restrictions or subcontractor permissions are stated.
- **Independent Contractor Status:** No clause clarifies employment/tax relationship.
- **Notices:** No formal notice mechanics beyond “written notice.”
- **Audit / Compliance:** No compliance with laws, audit rights, or regulatory obligations are addressed.

### Unusual or Risky Language
- **Termination is broad and unconditional:** “Either party may terminate” on 30 days’ notice gives both sides a broad exit right, which may create delivery and resource-planning risk.
- **Payment clause is incomplete:** “Payable in three installments” is vague because it omits timing and conditions for each installment.
- **Confidentiality period may be insufficient for some information:** A five-year protection period may be too short for trade secrets or highly sensitive proprietary information.
- **No IP ownership language in a software development deal:** This is a significant risk because ownership of custom code, deliverables, derivative works, and background technology is not addressed.

Gemini 2.5 Pro 8/10

Of course. As an expert contract analyst, here is a structured breakdown of the clauses from the provided text, along with a risk analysis.

### **Extracted Contract Clauses**

**Parties and Effective Date**
*   **Summary:** This clause identifies the two parties entering into the agreement, Acme Corp (Client) and BlueTech Solutions LLC (Provider), and establishes the start date of the agreement as March 15, 2024.
*   **Verbatim Text:** "This Master Services Agreement is entered into on March 15, 2024 between Acme Corp ('Client') and BlueTech Solutions LLC ('Provider')."
*   **Reference:** Not available.

**Scope of Services**
*   **Summary:** This clause broadly defines the Provider's core obligation, which is

Grok 4.1 Fast Reasoning 9/10

### Parties and Effective Date
- **Clause Name**: Agreement Parties and Date  
  **Summary**: Identifies the contracting parties as Acme Corp (Client) and BlueTech Solutions LLC (Provider), with the agreement dated March 15, 2024.  
  **Verbatim Quoted Text**: "This Master Services Agreement is entered into on March 15, 2024 between Acme Corp ('Client') and BlueTech Solutions LLC ('Provider')."  
  **Section/Page Reference**: N/A

### Services
- **Clause Name**: Scope of Services  
  **Summary**: Provider agrees to deliver software development services to the Client.  
  **Verbatim Quoted Text**: "Provider shall deliver software development services"  
  **Section/Page Reference**: N/A

### Payment Terms
- **Clause Name**: Fees and Payment Schedule  
  **Summary**: Client pays Provider a total fee of $150,000 in three installments for the services.  
  **Verbatim Quoted Text**: "for a fee of $150,000, payable in three installments."  
  **Section/Page Reference**: N/A

### Termination
- **Clause Name**: Termination Rights  
  **Summary**: Either party can terminate the agreement at any time by providing 30 days' written notice.  
  **Verbatim Quoted Text**: "Either party may terminate this agreement with 30 days written notice"  
  **Section/Page Reference**: N/A

### Confidentiality
- **Clause Name**: Confidentiality Obligations  
  **Summary**: All confidential information shared during the engagement must remain protected for five years after termination.  
  **Verbatim Quoted Text**: "and all confidential information shared during the engagement shall remain protected for a period of five years following termination."  
  **Section/Page Reference**: N/A

### Risk Flags
- **Missing Standard Clauses**: No provisions for Intellectual Property Rights (critical for software development—who owns the deliverables?), Governing Law, Dispute Resolution/Arbitration, Indemnification, Limitation of Liability, Warranties/Representations, Force Majeure, Non-Solicitation/Non-Compete, Insurance requirements, or detailed Scope of Work/Statement of Work (services are vaguely defined).
- **Unusual/Risky Language**:
  - Termination allows no-fault termination by either party with only 30 days' notice, potentially exposing Provider to early exit without compensation for work-in-progress.
  - Payment terms lack specifics (e.g., installment timing, milestones, late fees, or invoicing process), creating ambiguity and payment risk.
  - Confidentiality is vague—no definition of "confidential information," no exceptions (e.g., for public info), no obligations on how to protect/handle it (e.g., return/destruction), and survival is tied only to termination (not clear on pre-termination duties).
  - Overall, this is an unusually brief "Master Services Agreement" lacking essentials for enforceability and protection in a software services context; highly risky for both parties, especially Provider on IP and payment. Recommend full redraft.

What makes these work

01

Name clause types explicitly
Vague instructions like 'extract important clauses' return inconsistent results across models. List the exact clause types by their conventional names: indemnification, limitation of liability, termination for convenience, governing law. Models trained on legal text recognize these labels and locate them reliably even when the contract uses non-standard headings.
02

Always instruct verbatim output
Add 'quote the exact original text, do not paraphrase' to every clause extraction prompt. Without this instruction, models summarize clause language, which strips out the specific wording that actually matters legally. The difference between 'gross negligence' and 'negligence' in a liability clause is enormous; a summary loses that distinction.
03

Request structured label-plus-text format
Ask the model to return output as CLAUSE TYPE | Section Reference | Verbatim Text. This structured format makes the output directly usable in a spreadsheet or database without post-processing. It also makes gaps obvious: if a clause type you asked for is missing, a structured format surfaces that absence rather than burying it in prose.
04

Process long contracts in sections
If a contract exceeds 20,000 words, split it into logical sections before extraction — definitions, core obligations, liability, dispute resolution — and run separate prompts on each. This avoids context-window truncation, which silently drops the end of a document, and keeps the model focused on a smaller block of text where clause boundaries are clearer.

More example scenarios

#01 · SaaS vendor agreement — extracting liability and indemnification clauses

Input

You are a contract analyst. From the contract text below, extract every clause related to: (1) limitation of liability, (2) indemnification, (3) warranty disclaimers. For each clause, return the clause type as a label, the section number if present, and the exact original text. Do not paraphrase. Contract text: [paste full agreement text here]

Expected output

LIMITATION OF LIABILITY | Section 12.3 | 'In no event shall either party be liable for indirect, incidental, special, or consequential damages... aggregate liability shall not exceed fees paid in the preceding 12 months.' INDEMNIFICATION | Section 13.1 | 'Customer shall indemnify and hold harmless Vendor from any third-party claims arising from Customer's use of the Service in violation of this Agreement.'

#02 · Employment contract — isolating non-compete and non-solicitation terms

Input

Extract all restrictive covenant clauses from this employment agreement, specifically: non-compete, non-solicitation of employees, and non-solicitation of customers. For each, include the label, duration, geographic scope if stated, and verbatim clause text. Do not summarize. Agreement text: [paste document text]

Expected output

NON-COMPETE | Duration: 12 months post-termination | Geography: United States | Text: 'Employee agrees not to directly or indirectly engage in or assist any business that competes with Company within the Territory for a period of one (1) year following separation...' NON-SOLICITATION (Customers) | Duration: 24 months | Text: 'Employee shall not solicit or accept business from any customer with whom Employee had material contact during the final 12 months of employment.'

#03 · Commercial lease review — renewal options and rent escalation

Input

From the commercial lease agreement below, extract all clauses covering: (1) lease renewal or extension options, (2) rent escalation or CPI adjustment, (3) early termination rights. Label each clause type, include the section reference, and quote the text exactly as written. Lease text: [paste lease document]

Expected output

RENEWAL OPTION | Section 4.2 | 'Tenant shall have two (2) options to renew this Lease for successive periods of five (5) years each, provided Tenant gives written notice no later than 9 months prior to the expiration of the then-current term.' RENT ESCALATION | Section 5.1 | 'Base rent shall increase annually by the lesser of 3% or the change in CPI-U for the preceding calendar year.'

#04 · M&A due diligence — change of control clauses across supplier contracts

Input

Review the supplier agreement below and extract any clause that addresses: change of control, assignment rights, or consent requirements triggered by an acquisition or merger. Return the clause type, section number, and exact language. Flag any clause that requires third-party consent. Contract: [paste text]

Expected output

CHANGE OF CONTROL | Section 18.4 | CONSENT REQUIRED | 'This Agreement may not be assigned by either party without the prior written consent of the other party, which shall not be unreasonably withheld, except that either party may assign this Agreement without consent in connection with a merger, acquisition, or sale of all or substantially all of its assets, provided the acquiring entity assumes all obligations hereunder.'

#05 · Freelance contractor agreement — payment terms and IP ownership

Input

From the contractor agreement text below, extract clauses relating to: (1) payment schedule and terms, (2) intellectual property ownership and assignment, (3) work-for-hire language. Preserve exact wording. Label each clause. Text: [paste agreement]

Expected output

PAYMENT TERMS | Section 6.1 | 'Client shall pay Contractor net 30 from receipt of invoice. Invoices unpaid after 30 days accrue interest at 1.5% per month.' IP ASSIGNMENT | Section 9.2 | WORK FOR HIRE | 'All deliverables created by Contractor under this Agreement shall be considered works made for hire. To the extent any deliverable does not qualify, Contractor irrevocably assigns all right, title, and interest to Client.'

Common mistakes to avoid

Trusting output without checking coverage
A model that finds no clause matching your request will sometimes say nothing rather than 'not found.' Always include an instruction like 'if a clause type is not present, return NOT FOUND for that category.' Otherwise you cannot tell whether a clause is genuinely absent or was simply missed.
Using summarized text instead of raw PDF text
Copy-pasting a contract summary or abstract into the prompt instead of the full text means the model can only extract from the summary, not the original clauses. Key qualifications buried in subsections — carve-outs, exceptions, definition references — appear only in the full text and will be missing from your extraction.
Ignoring definition sections
Contract clauses frequently reference defined terms whose meaning lives in a separate definitions section. Extracting an indemnification clause that says 'Losses shall mean...' without also capturing the definition of 'Losses' gives you incomplete and potentially misleading output. Include the definitions section in your extraction prompt or run a second pass to capture relevant definitions.
Assuming scanned PDFs are readable
A scanned contract PDF contains image data, not text. Feeding it to an AI without first running OCR means the model has nothing to read. The model may produce hallucinated clause text that looks plausible but has no relationship to the actual document. Always verify the PDF has a text layer before running clause extraction.
Over-relying on section headings
Instructing the model to 'find the indemnification section' works when headings are clear, but contract drafters often embed indemnification language inside unrelated sections like 'Miscellaneous' or 'General Terms.' Prompt for the clause type by concept, not just by heading, so the model searches the full text rather than just matching header labels.

Related queries

Frequently asked questions

Can I extract clauses from a scanned contract PDF?

Not directly. Scanned PDFs store pages as images with no text layer, so an AI model receives no readable input. You need to run OCR first using a tool like Adobe Acrobat, AWS Textract, or Google Document AI to produce a searchable text layer. Once you have the text, standard clause extraction prompts work normally.

Which AI model is best for extracting contract clauses?

GPT-4o, Claude 3.5 Sonnet, and Gemini 1.5 Pro all perform well on standard commercial contract clause extraction. Claude tends to follow structured output instructions most consistently. GPT-4o handles longer documents reliably. The comparison table on this page shows side-by-side output quality on the same contract input so you can evaluate against your specific clause types.

How do I extract clauses from multiple contracts at once?

For batch processing, build an automated pipeline: extract text from each PDF programmatically, pass each document through the same extraction prompt via API, and write the labeled output to a structured format like JSON or CSV. Tools like LangChain, LlamaIndex, or direct API calls to OpenAI or Anthropic support this pattern. For low volume, manual copy-paste works fine.

Will AI clause extraction work on non-English contracts?

Leading models handle Spanish, French, German, and other major languages reasonably well for clause extraction. Accuracy drops for less common languages and for contracts that mix languages within the same document. Always specify the output language in your prompt and verify a sample against the original text before using the output at scale.

Is AI-extracted contract language legally reliable?

AI extraction is reliable for surfacing and quoting text that exists in the document, but it is not a substitute for attorney review. Models can miss clauses, misidentify clause types, or truncate text at context limits. Use extracted output as a starting point for human review, not a final legal record. For high-stakes contracts, always verify extracted clauses against the source PDF.

What if the contract uses non-standard clause names or no section headings?

Prompt by concept rather than by heading. Instead of 'find the indemnification section,' write 'find any language where one party agrees to defend, hold harmless, or compensate the other for losses or third-party claims.' This semantic approach catches embedded clause language regardless of how the drafter labeled it. Increase specificity if the model returns too many false positives.

Try it with a real tool

Run this prompt in one of these tools. Affiliate links help keep Gridlyx free.

Perplexity Pro AI-powered answer engine

Try Perplexity →

CustomGPT ChatGPT trained on your content

Try CustomGPT →