Skip to content

Projects

Finance needs the liability caps across every active service agreement by Friday. The manual approach is always the same: open each document, find the clause, copy the value into a spreadsheet, repeat. A comparison across dozens of contracts can take days, and the answers are only as reliable as the person reading each one.

A Project does that reading for you. Pick the contracts, define the data points you want (governing law, expiry date, liability cap, a yes/no flag for a clause you care about), and the AI reads every document and fills a structured grid: contracts down the rows, your data points across the columns. Each cell carries the extracted value, the AI’s reasoning, and a quote from the source clause, so you can verify what it found.

Bulk analysis pipeline
Pick contracts Choose the contracts to analyse from the repository.
Define columns Each column is a question plus an answer type — text, date, number, yes / no.
Run analysis The AI reads every document and fills the grid, one cell per contract per column.
Review the grid Contracts down the rows, your data points across the columns.
What you get
Governing lawExpiryLiability cap
MSA · AcmeNew York14 Aug 2026$5M
NDA · GlobexEngland31 Dec 2025N/A
SaaS · HooliDelaware03 Mar 2027$2M
Inside one cell

Value 14 Aug 2026

Reasoning Clause 9.1 sets a two-year term from the effective date.

“…this Agreement shall expire on 14 August 2026…”

Every cell carries the AI's value, its reasoning, and a quote from the source clause — so you can verify what it found.

Project results grid showing extracted values for counterparty, effective date, governing law, liability cap, and termination across five contracts

In the left nav this is Projects, and it opens as a Tabular Review. Today it does one kind of analysis: extracting data points into a grid, one cell per contract per column.

Projects reads from contracts you already have, so you need contracts in the repository first. You can pull them straight from the repository, or upload files into the project (which also files them in the repository). With an empty repository there is nothing to analyze. For how contracts get there, see Contracts.

A project is visible to the person who created it, to anyone they add to it, and to your company admins. Nobody else in the company can see it or knows it exists.

The person who created it is its owner. Owners and admins can add and remove people, rename, duplicate and delete the project. Use Manage access in the project header to see who has access and to change it.

Adding someone to a project gives them every document in it, including documents added later, and everyone in the project sees the same rows and the same results. That is the point of a project: a shared view of one set of contracts. Add people deliberately, and to hand results to someone who should not have that access, export the grid to Excel and send the file instead.

If the owner’s account is deactivated, the project passes to an admin so it never becomes unreachable.

This section also covers writing good column questions and checking and trusting AI results.

Chat with us

We typically reply within a few minutes