A contract is the one document where a missed clause has a price. The auto-renewal you didn't notice, the notice period that's 90 days not 30, the liability cap that quietly moved: the risk isn't reading a contract, it's reading it and still missing the thing that matters.
AI is genuinely useful here for finding and surfacing clauses fast, but only if you can check what it tells you. The whole game is answers where every point cites the exact clause, so you verify the wording yourself instead of trusting a paraphrase. Here's how to review a contract that way.
Why "is this contract fine?" is the wrong question
Ask a chatbot whether a contract is "good" and you get a confident, generic answer built from how contracts usually read, not from this one. That's exactly where an AI hallucination hides: a plausible statement about a clause that isn't actually in your document.
- It answers from patterns. Without the contract grounded in front of it, the model fills gaps with what a typical contract says.
- It smooths over the wording. Contract meaning lives in exact phrasing and defined terms; a summary rounds those off, and the rounding is where risk sits.
The better approach: answer only from the contract, cite every clause
Sidenote reads the contract you open - a PDF or a Word document - and answers only from it, with a citation on every point. The principle is answering only from your documents: no clause, no answer.
Step 1 - Load the contract into a reader that cites
Open the contract and the side panel. Sidenote ingests a clean, clause-anchored snapshot and answers from that, so its answers point to your contract's wording, not to contracts in general.
Step 2 - Ask targeted questions, clause by clause
Skip "review this contract." Ask the specific things that carry risk:
What are the termination rights, the notice period, and any auto-renewal?
Then liability caps, indemnities, governing law, assignment. Each answer maps to a clause you can open, and the gaps in the answers tell you what the contract doesn't address, which is often the point.
Step 3 - Read the cited clause in full before you rely on it
Click each citation and read the whole clause, including anything it cross-references and any defined terms it leans on. This is the step that catches the true-but-incomplete answer: the clause exists, but a proviso two lines down changes what it means.
Comparing a contract to its previous version
Redlines are slow and easy to skim past. Bundle the new contract and the prior version into a Collection and ask what changed; each difference cites the wording in both, so a moved liability cap or a new indemnity surfaces with the exact before-and-after. The same works for a contract against your standard template.
Your contract is never used to train AI models and is stored in a UK region isolated per account. Before uploading anything confidential, run through is it safe to upload documents to AI? and see security & compliance.
The short version
- Don't ask if a contract is "good": ask targeted clause questions you can verify.
- Use a tool that answers only from the contract and cites the exact clause for each point.
- Always read the cited clause in full, including cross-references and defined terms.
- To review changes, compare versions in a Collection so each difference cites both.
- Treat AI as a fast first pass, and get a professional to review anything you'll sign.