Skip to main content
A manufacturer has 300 supplier contracts and a new rule: each must give the buyer a right to audit. A review tool listed the contracts without such a clause. Some of them had it, on a scanned schedule that the tool could not read. The list said “no clause” where the truth was “not read”, and the company wrote to suppliers whose contracts were in order. This page builds a review in which those 2 cases never look alike.

The run in 5 steps

Upload each contract with the checklist

Send each file once, with your checklist as a template and your open questions as highlights. A scanned contract is recognized page by page, and a long one runs as a job.
Fields sent with each file to upload_contents
One call returns the outline of the contract, the filled checklist, and the place of each passage that bears on a question.

Read each item of the checklist

Each field comes back with a status. This response is for one contract, cut to the status, the words, and the printed page of each field.
Part of the response
The contract has no clause on price changes and none on subcontracting: both are absent, and that is a finding. The audit right is unread: a part of the contract was not read well enough to say that the clause is missing. This contract goes to a person, and not onto the list of contracts without the clause.

Count the pages that were read

pages in the record says how the read went: how many pages the file has, how many were read, which failed, and for each scanned page how sure the recognition is, from 0 to 1. This part of the record is cut to 2 of its 10 scanned pages.
Part of the response
Page 23 was recognized with a confidence of 0.58. The notice recognition_uncertain names every such page, and that page is why the audit right is unread. In a contract whose pages were all read with high confidence, absent means that the clause is not there.

Send one page to a person, not one contract

Each scanned page comes with a picture of the page. The reviewer opens the picture of page 23, reads the schedule, and fills in the one open field. Of 300 contracts, a person looks only at the pages that need a person.

Read the schedules as tables

A price list in a schedule is a table, and the link between a product and its price is the row. From a Word file or a PDF with structure, the table comes cell by cell, so a price cannot slide to the product in the next row.

What the general counsel can check

Know the limits

A model fills the checklist, and each value is bound to words of the contract. Treat a found field as a passage to read, and quote the words, not the model. Handwriting on a scan comes as flat text or not at all, so a handwritten amendment can be missed without a notice. Tracked changes in a Word file are shown as accepted. A strikethrough that is only a line drawn over the text is not detected. For the calls, see Fill your fields, each with the words it came from and Turn PDFs, Office files, and scans into evidence you can cite by page.