---
title: 06.11 Extracting Contract Terms with AI
description: Have the AI provider read a vendor contract's PDF or Word document and propose values for its key terms, dates, total value and service levels, then…
---

[Skip to content](https://support.simplerisk.com/kb/06-11-vendor-contract-term-extraction#main-content)

English

Show submenu for translations

[Customer portal](https://support.simplerisk.com/tickets?hsLang=en)

[![SimpleRisk logo of a man walking a tight rope](https://support.simplerisk.com/hs-fs/hubfs/simplerisk_logo_long_small-4.png?width=377&height=72&name=simplerisk_logo_long_small-4.png)](https://www.simplerisk.com/)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://support.simplerisk.com/tickets)
- [Contact us](https://www.simplerisk.com/about-us/contact-us)

[Contact us](https://www.simplerisk.com/about-us/contact-us)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [SimpleRisk Knowledge Base](https://support.simplerisk.com/kb?hsLang=en)
2. [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en)
3. [06 Assessments](https://support.simplerisk.com/kb/user-guide?hsLang=en#06-assessments)

# 06.11 Extracting Contract Terms with AI

## Have the AI provider read a vendor contract's PDF or Word document and propose values for its key terms, dates, total value and service levels, then check each proposal against its quoted passage and accept, edit or reject it. Covers what is sent, what the quote does and doesn't prove, replacing a value someone entered, interrupted and failed runs, and the hourly and per-document limits.

> **Requires:** *Vendor Risk Management Extra*
> 
> Term extraction works on the contracts of the **Contracts** tab, so it comes with the Vendor Risk Management Extra. It also needs an AI provider set up in SimpleRisk, and an administrator must switch on **Vendor Contract Term Extraction** under **Artificial Intelligence**, then **Capabilities**. The AI Extra is not needed: the provider settings and that switch are part of SimpleRisk itself.

## Why this matters

Filling in a contract's terms by hand is the slow part of contract tracking. Someone has to open a forty-page master services agreement, find the liability clause, work out whether the cap is twelve months of fees or a fixed sum, then do the same for breach notification, audit rights and the rest. Multiply that by every vendor and the terms matrix stays half empty, which is exactly when it can't answer "which vendors don't give us audit rights?"

Extraction does the first pass for you. The AI reads the contract's document and proposes a value for each term your administrator has enabled, plus the contract's start, end and renewal dates, its notice period, its total value with the currency, and a summary of its service levels. Each proposal comes with the passage it was taken from. Nothing reaches the contract until a person with contract management rights looks at the proposal and accepts it.

Treat the AI as a fast junior reviewer, not as the reviewer of record. It's good at finding the clause. It's less reliable at reading what the clause means, and contract language is written by lawyers who are paid to be subtle. Read the quoted passage every time.

## Before you start

- **The right permissions.** Everything here needs **Allow Access to "Vendor Risk" Menu**, **Able to View Vendors** (or a permission that includes it) and **Able to View Vendor Contracts** (or **Able to Manage Vendor Contracts**, which includes it). On top of that:
- **Able to Extract Terms from Vendor Contracts** lets you start an extraction, cancel one, and read the proposals.
- **Able to Manage Vendor Contracts** lets you read the proposals and accept, edit or reject them.

Administrators hold both automatically. Someone with only **Able to View Vendor Contracts** sees neither the extraction nor its proposals: unconfirmed AI output is shown only to the people who ask for it or act on it. - **An AI provider, and the capability switched on.** Your administrator sets the provider and API key in SimpleRisk and turns on **Vendor Contract Term Extraction** under Artificial Intelligence, Capabilities. Until they do both, the **Extract terms** button doesn't appear, and the proposals panel tells extraction holders *The AI provider is not configured. Unable to produce live results until you set the provider and API key on the Provider Configuration tab.* - **A contract with a PDF or Word (.docx) document.** The button appears only on a contract whose stored document is one of those two types. Older Word `.doc` files, spreadsheets and images aren't read. - **A document with real text in it.** SimpleRisk doesn't recognize text in images (there's no OCR), so a scanned contract with no text layer can't be read.

> **Encryption availability.** In this release, proposed term values and the passages quoted with them are stored as entered, not encrypted. They will be encrypted once SimpleRisk's built-in encryption is available; the Vendor Risk Management Extra does not use the Encrypted Database Extra. Until then, don't put secrets in these fields. After encryption arrives, saving or reading them also needs a working encryption key, and your administrator restores it if it goes missing.

## Step-by-step

### 1. Start an extraction

Open the vendor and choose the **Contracts** tab. On a contract that has a PDF or Word document, select the **Extract terms** button (the wand icon) in the row.

A confirmation opens with the contract's title and this note:

*Extracting terms sends the text of this contract's document to the AI provider configured in SimpleRisk, together with the names, descriptions, types, choices and units of your contract terms. The document's own text usually names both parties and states the amounts. Nothing else from SimpleRisk's records is sent: not the vendor record's name or the contract's title, value or notes. The AI only proposes values: nothing is saved to the contract until someone accepts it.*

Be clear about what that means. The document's text is the contract itself, so the provider sees whatever it says: both parties' names, addresses and signatories, the fees, the liability cap. What SimpleRisk keeps back is its own records. Along with the document's text, the provider gets your term catalog (an internal number for each term, plus its name, description, type, choices and unit), the four date field names and SimpleRisk's fixed instructions for the task. That's the whole list. The vendor record's name, the contract's title, value and notes, and anything about you stay on your server. The note is there so that each request is a deliberate choice. If a contract is covered by a confidentiality clause that rules out sharing it with a third-party service, this is the moment to stop.

Select **Extract terms** to confirm. The dialog closes, SimpleRisk confirms with *Term extraction was requested. The proposed values appear here when it finishes.*, and the **Proposed terms** panel opens on the new run.

A request can be refused before anything is sent:

- *An extraction is already in progress for this contract, or another of your extraction requests is being processed. Wait for it to finish.* One extraction per contract runs at a time.
- *You have reached your hourly limit of term extractions. Try again in {minutes} minute(s).* See step 6.
- *The model call or token budget for this contract document has been used up. An administrator can raise the budget, and a replaced document starts a new budget.* See step 6.
- *This document is too large to extract terms from.* The message gives the limits for each type. That check uses the file's size alone.
- *The extraction could not be queued. Try again later.*

The document itself is read later, by the background worker, so a few problems only show up then. A file over the worker's memory limit is accepted here and fails as a run with the same *too large* message; so does a Word file whose text unpacks to far more than its file size suggests. A scan with no text layer is accepted and fails with the no-text message. Step 3 lists every way a run can end. Your administrator can tell you the real size limit, which is usually lower than the message states.

### 2. Follow the run

The extraction runs in the background, so you can close the panel and come back. Open it again with the **Proposed terms** button (the question-mark file icon) on the contract's row. While the run is active, the panel checks for progress every few seconds, and less often the longer it runs. It pauses while the browser tab is in the background. The status line reads, in order:

- *The extraction is waiting for the background worker to start it.*
- *The background worker is reading the contract document.*
- *Extracting terms. Model calls made: {done} of {total}.*
- *The extraction has finished. Nothing is saved to the contract until you accept a proposed value.*

A short contract with the sixteen standard terms is one model call. A long one is split into parts of about 48,000 characters each, read part by part, and the answers are merged.

**Cancel extraction** appears under the status line while the run is waiting or running, for people who can extract. Cancelling stops the run before its next call to the provider. A call already in progress finishes and still counts against the budget, and the run stores no proposals.

### 3. When a run fails

A run that can't finish shows why, in the panel's status line. Nothing is written to the contract in any of these cases, and a failed run keeps no partial proposals.

- ***No text could be found in this document. Scanned (image-only) documents cannot be read.*:** Upload a version of the document that has a text layer, for example one saved from the original file rather than scanned.
- ***This document is too long to extract terms from. Documents of up to about 384,000 characters (roughly 100 pages) can be read.*:** Extract from the part that matters, such as the main agreement without its schedules, or enter the terms by hand.
- ***This document is too large to extract terms from. PDF files of up to 24 MB and Word (.docx) files of up to 16 MB can be read, and less when the server is short of memory.*:** The file didn't fit in the background worker's memory, or it's a Word file whose text part unpacks to more than 16 MB. Upload a smaller copy, such as a PDF saved without embedded images, or ask your administrator about the worker's memory.
- ***Terms can be extracted only from PDF and Word (.docx) documents.*:** The file is labelled as a Word document but isn't one SimpleRisk can open, for example a damaged file or an older format renamed. Save it again from the original program as `.docx` or PDF.
- ***The model call or token budget for this contract document has been used up. An administrator can raise the budget, and a replaced document starts a new budget.*:** The run would have gone over the document's budget, either in its plan or part way through. See step 6.
- ***The AI provider is not configured. Unable to produce live results until you set the provider and API key on the Provider Configuration tab.*:** The provider's key was removed while the run waited or ran. Ask your administrator.
- ***The AI provider could not be reached or returned an error. Try again later.*:** Try again later. If it keeps happening, tell your administrator.
- ***The AI provider returned a reply that could not be read. Request the extraction again.*:** Request it again. SimpleRisk already retried once.
- ***The contract document has changed since the extraction was requested. Request a new extraction.*:** Someone replaced the document while the run waited. Extract from the new one.
- ***The extraction was stopped because the person who requested it can no longer extract terms from this contract.*:** The requester lost a permission, or the vendor moved out of their teams, while the run waited or ran. It's checked before every call to the provider, so nothing more is sent once access is gone. Someone who still has access can request it again.
- ***The extraction was interrupted before it finished. Request it again.*:** See below.

**Interrupted runs aren't resumed.** If the server or its background worker restarts in the middle of a run, the run stops as interrupted. SimpleRisk never picks it up again on its own, because that would send the document to the provider a second time without anyone asking. Request the extraction again. That new request counts against your hourly limit, and the model calls the interrupted run already made still count against the document's budget.

A request that sits at *waiting for the background worker* for a long time usually means the worker isn't running. Use **Cancel extraction** and let your administrator know.

### 4. Read a proposal

When the run finishes, the panel lists one card per term, date and contract field, in the order of the contract's terms, with the dates and then the value, currency and SLA summary after them. A found proposal shows:

- **Current value**: what the contract holds now, or a dash.
- **Proposed value**: what the AI read from the document.
- **Quoted passage**: the passage the value was taken from, followed by **Page {page}** for a PDF. A Word document has no fixed pages, so it shows **Page not available**.
- **Confidence**: **High**, **Medium** or **Low**, as the AI judged it.

Terms, dates and fields the AI couldn't find, or whose passage didn't check out, are grouped under **Not found in this document** with their count, collapsed. Those cards show only the current value.

**What the quote proves, and what it doesn't.** SimpleRisk checks every quote against the text it pulled from the document. A quote that isn't there is thrown away, and so is its value: the term shows as not found. So a quoted passage proves one thing, that those words are in the document. It doesn't prove that they support the proposed value. An AI can quote the right clause and still read "Vendor shall not be liable for more than twelve months of fees, except in cases of gross negligence" as a plain twelve-month cap. Read the passage before you accept.

A few details of the check are worth knowing:

- The comparison ignores capital letters, spacing and typographic differences such as curly quotes and dashes, and it joins words hyphenated across a line. The passage shown is the AI's own copy of the text, matched that way, so it can differ from the document in those details.
- Spaces don't count either. That's what lets a passage match in a Word document, where adjacent paragraphs can run together, but it also means word boundaries are no evidence.
- A passage must be at least 12 characters long, eight of them letters or digits, to count. A passage longer than about 400 characters isn't checked at all, so its value shows as not found.
- The page is the one where the passage begins, worked out by SimpleRisk from the document, not taken from the AI.

**Conflicting passages.** In a long contract, different parts can give different answers, for example a liability cap in the main agreement and a different one in a schedule. The card then says *Different passages of the document gave different values for this; the one with the highest confidence is proposed. Check the document before accepting it.* It usually means an amendment or an order form overrides the main terms. Find out which one governs before you accept.

**A contract can steer the AI, not the contract.** Text inside the document is treated as data, never as instructions, and a run can only create proposals. A contract written to mislead the AI can still change which passages it proposes. It can't change a term value, because only a person accepting a proposal does that.

### 5. Accept, edit or reject

With **Able to Manage Vendor Contracts**, each pending card has buttons:

- **Accept** saves the proposed value to the contract. It's offered only for a found proposal. The card then reads **Accepted**.
- **Edit and accept** opens the term's own control, filled with the proposed value, so you can correct it before saving. A not-found term offers this too, so you can enter the value yourself while you're here. Saving reads **Edited**.
- **Reject** marks the proposal **Rejected** and leaves the contract alone.

The value, currency and SLA summary cards are worth a word. The **Contract value** is proposed only when the contract states the total outright; the AI is told never to add up instalments or multiply a rate. The **Currency** is proposed only when the contract names one next to the amount. The **SLA summary** is the contract's own wording about availability, response times or service credits, kept as a passage for you to read, not a rating. Edit it freely: it is a note for people, not something SimpleRisk scores.

A contract holds a value and its currency together, as on the contract form. If the contract has neither, accepting the **Contract value** also accepts the **Currency** proposal from the same run, and the other way round, so you aren't stuck; if there is no usable proposal for the other half, the save is refused with the contract's message *Enter both the contract value and its currency, or neither.* and you can enter the missing half with **Edit and accept**. Replacing a value or currency the contract already holds asks first, like any other value.

An accepted value is checked by the same rules as a value entered on **Edit terms**. A date is checked against the contract's other dates, so an end date before the start date is refused with the contract's own message. The notice period must be a whole number of days from 0 to 3,650.

**Accept never clears a value.** Accepting always needs a value. If the contract holds a value the document doesn't support, clear it with **Edit terms** on the contract, as described in [Vendor Evidence and Contracts](https://support.simplerisk.com/kb/06-08-vendor-evidence-and-contracts?hsLang=en).

**Replacing a value someone entered asks first.** When the contract already holds a different value, Accept doesn't save straight away. The card asks *The contract already holds {current}. Replace it with {proposed}?*, with **Cancel** and **Accept** under it, the warning icon beside it. The confirmation applies to the value you were shown. If someone changes that value in the meantime, the save is refused with *The contract already holds a different value, or it changed after you opened this proposal. Review the current value and confirm that you want to replace it.*, and the card asks again with the value stored now, as long as that's still a different value. If someone cleared it in the meantime, select **Accept** again. Accepting a value equal to what the contract already holds doesn't ask, but it's still a save: the audit trail records the accept and an update of the contract's terms (or of the contract, for a date), and the term records you as its last editor. The value itself hasn't changed, so read that update entry as "confirmed", not "changed".

The question can appear for a multiple-choice term whose value already matches, when your administrator has reordered that term's choices since the value was stored. Check the two values and confirm.

**Not valid and Document changed.** Some proposals can no longer be accepted as they stand:

- *Not valid: this value no longer fits the term as it is now defined, or the term was turned off. You can enter a value that fits, or reject it.* Your administrator changed the term's choices or type, or turned the term off, after the run. **Edit and accept** still works with a value that fits the term now, unless the term is off, in which case you can only reject it. A deleted term takes its proposals with it.
- *Document changed: the contract's document was replaced after this proposal was made, so it can only be rejected.* The proposal came from a document the contract no longer holds. Reject it, or extract the terms again from the new document.

Every decision writes an entry to the audit trail with the proposal, contract and vendor by number, never the value or the quote.

### 6. Know the limits

Two limits keep extraction costs and provider usage bounded. Your administrator sets both.

**The hourly limit** is per user: 10 requests in any rolling hour unless your administrator changed it. Every request counts, including one that later fails, one that's cancelled and one that's interrupted. Deleting the contract doesn't give the request back.

**The budget** is per contract document: 20 model calls and 200,000 tokens unless your administrator changed them. It's the total over every extraction of that document, so running the same contract again and again eventually stops with the budget message. Replacing the contract's document starts a new budget. Before anything is sent, SimpleRisk plans the whole run (how many calls the document's length and the number of terms need) and refuses it if the plan doesn't fit in what's left. A run also stops when the actual token count, checked before every call, runs out. Text in scripts such as Chinese, Japanese, Arabic or Cyrillic takes more tokens than the plan estimates, so those runs can stop sooner than a similar English contract.

## Things to know

- **A newer finished run replaces the proposals shown.** The panel shows the proposals of the contract's latest finished run. When a new run finishes, older proposals that nobody decided are retired. If a run finishes while you have **Edit and accept** open on an older proposal, the panel redraws and your half-typed value is lost.
- **A failed run doesn't hide the last good one.** If the latest run failed, its message shows above the proposals of the last run that finished.
- **Proposals aren't values.** The terms matrix, the contract's terms and every report show only what people entered or accepted, never a pending proposal.
- **Undecided proposals don't expire.** They stay pending until someone decides them, a newer run finishes, or the document is replaced.
- **Who requested a run is recorded.** The audit trail names the requester for the request and for the run finishing, and the API's read of a run includes the requester's name for anyone who can read the proposals.

## Common pitfalls

- **Accepting on the strength of the confidence pill.** **High** confidence is the AI's opinion of itself. The quoted passage is the evidence; read it.
- **Accepting a proposal from the main agreement when an amendment changed it.** The AI reads what it's given. If the amendment is a separate file, it isn't part of the run. Check the conflict note, and check whether the contract has later paperwork.
- **Extracting from a scan.** It fails with the no-text message and still counts against your hourly limit. Check that you can select text in the PDF first.
- **Extracting from a Word file with tracked changes.** SimpleRisk reads all the text in the file, including deleted text that Track Changes still keeps and hidden text. A redlined contract can hand the AI the struck-out liability cap next to the agreed one, and the quote will still check out because those words are in the file. Accept or reject all changes, and save a clean copy, before you upload a Word contract.
- **Re-running to "get a better answer".** Each run costs a request and part of the document's budget, and the same document tends to give the same answer. Use **Edit and accept** instead.
- **Expecting a value to be cleared.** Accept and Edit and accept only ever set a value. Clear one with **Edit terms**.
- **Sending a contract that mustn't leave the building.** The confirmation says exactly what goes to the provider. If your contract's confidentiality clause rules out third-party processing, enter the terms by hand.

## Related

- [Vendor Evidence and Contracts](https://support.simplerisk.com/kb/06-08-vendor-evidence-and-contracts?hsLang=en)
- [Using the Vendor Register](https://support.simplerisk.com/kb/06-05-the-vendor-register?hsLang=en)
- [Vendor Overview, Reports and Control Coverage](https://support.simplerisk.com/kb/06-10-vendor-overview-reports-and-control-coverage?hsLang=en)
- [The Vendor Risk Management Extra](https://support.simplerisk.com/kb/12-09-the-vendor-risk-management-extra?hsLang=en) in the Administrator Guide
- [Configuring AI Providers](https://support.simplerisk.com/kb/10-05-configuring-ai-providers?hsLang=en) in the Administrator Guide

- [FAQs](https://support.simplerisk.com/kb/faqs?hsLang=en)
- [SimpleRisk Extras](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#main-content)

    - [Vulnerability Management Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#vulnerability-management-extra)
    - [Team Separation Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#team-separation-extra)
    - [Import-Export Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#import-export-extra)
- [Administrator Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#main-content)

    - [00 About This Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#00-about-this-guide)
    - [01 Installation and Deployment](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#01-installation-and-deployment)
    - [02 Upgrades and Maintenance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#02-upgrades-and-maintenance)
    - [03 Users and Permissions](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#03-users-and-permissions)
    - [04 Authentication](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#04-authentication)
    - [05 Customization](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#05-customization)
    - [06 Configuring Risk and Compliance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#06-configuring-risk-and-compliance)
    - [07 Integrations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#07-integrations)
    - [08 The API](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#08-the-api)
    - [09 Encryption and Data Security](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#09-encryption-and-data-security)
    - [10 Workflows and Automation](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#10-workflows-and-automation)
    - [11 Reporting and Auditing](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#11-reporting-and-auditing)
    - [12 Operations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#12-operations)
    - [13 Reference](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#13-reference)
- [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en#main-content)

    - [00 Foundations of GRC](https://support.simplerisk.com/kb/user-guide?hsLang=en#00-foundations-of-grc)
    - [01 Risk Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#01-risk-management)
    - [02 Compliance Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#02-compliance-management)
    - [03 Governance](https://support.simplerisk.com/kb/user-guide?hsLang=en#03-governance)
    - [04 Asset and Data Inventory](https://support.simplerisk.com/kb/user-guide?hsLang=en#04-asset-and-data-inventory)
    - [05 Threat and Vulnerability Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#05-threat-and-vulnerability-management)
    - [06 Assessments](https://support.simplerisk.com/kb/user-guide?hsLang=en#06-assessments)
    - [07 Incident Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#07-incident-management)
    - [08 Audit and Reporting](https://support.simplerisk.com/kb/user-guide?hsLang=en#08-audit-and-reporting)
    - [09 Day-to-Day SimpleRisk](https://support.simplerisk.com/kb/user-guide?hsLang=en#09-day-to-day-simplerisk)
    - [10 Continuous Improvement](https://support.simplerisk.com/kb/user-guide?hsLang=en#10-continuous-improvement)
    - [11 Business Continuity and Disaster Recovery](https://support.simplerisk.com/kb/user-guide?hsLang=en#11-business-continuity-and-disaster-recovery)
- [SimpleRisk User Guides](https://support.simplerisk.com/kb/simplerisk-user-guides?hsLang=en)
- [Troubleshooting](https://support.simplerisk.com/kb/troubleshooting?hsLang=en)
- [SimpleRisk Hosted](https://support.simplerisk.com/kb/simplerisk-hosted?hsLang=en)
- [How To videos](https://support.simplerisk.com/kb/how-to-videos?hsLang=en)

[![favicon-1](https://support.simplerisk.com/hs-fs/hubfs/favicon-1.png?width=35&height=35&name=favicon-1.png "favicon-1")](https://www.simplerisk.com)

<https://www.facebook.com/simplerisk/> <https://www.twitter.com/simpleriskfree/> <https://www.linkedin.com/company/simplerisk/>

Copyright © 2026, SimpleRisk, Inc.