Guide

Contract review in Notion

A contract review workflow that combines a Notion checklist, an AI-assisted comparison, and a structured comments page.

By Raghav R Handa, practising lawyerPublished 27 August 2026Updated 22 September 20269 min read

TL;DR

Each contract gets a Review page with a standard issues checklist.
AI handles the first pass for changes against your standard form.
The lawyer focuses on the issues the checklist surfaces, not the redline mechanics.

Free downloadLawyerOS — Matters, Clients, Billing & AIGet it

The problem

Contract review eats hours and most of those hours are spent reading the parts that have not changed since the last version. The cognitive load is on what is the same, not on what is different. An hour into the review the lawyer is tired before reaching the clauses that actually matter.

The setup

Create a Contracts database. For each contract, the page contains: the uploaded file, the parties, the standard form it should be measured against, a review checklist as a toggle list, an AI-generated diff against the standard form, and a Comments section.

The checklist

Build a template. The checklist is the lawyer's brain externalised. For a commercial supply contract: payment terms, term and termination, liability cap, indemnities, IP, governing law, dispute resolution, confidentiality, assignment, force majeure. Each item is a checkbox plus a one-line comment.

The AI pass

Paste the standard form and the new contract into Claude or ChatGPT with a prompt like: "List every substantive deviation between the new contract and the standard form. For each, state the clause, the change, and whether it favours us, them, or is neutral." Read the output. Mark the items that matter. The AI handles the boring comparison; the lawyer handles judgement.

The structure in full

A contract review tracker keeps issues, positions and versions in one place. It organises the work; the judgement stays yours.

Property	Type	Why
Contract	Title	Counterparty and type
Matter	Relation	Which file
Stage	Select	Received, Reviewing, With counterparty, Agreed, Signed
Issue	Row in an Issues database	Clause, concern, proposed position
Position	Select	Accept, Negotiate, Reject
Owner	Person	Responsible lawyer
Key dates	Date	Renewal, termination notice, milestones

Build it step by step

Create Contracts and Issues databases, related to each other and to Matters.
Write a playbook page with preferred positions per clause type.
For each contract, log issues against clauses with the proposed position.
Track versions and who holds the pen.
Record key dates (renewal, notice) in Deadlines with the clause source.

Views worth creating

View	What it shows
Open issues	What is still unresolved
By stage	Where each contract is
Renewals	Contracts with notice dates approaching

Mistakes we see

Issues kept in a Word comment thread.
No playbook, so positions vary.
Key dates missed because they are buried in the contract.
Treating an AI summary as a review.

Where Notion stops

Notion does not review the contract. If you use AI for first-pass extraction, verify against the document.
Execution and e-signature need a dedicated tool.

A free starting structure is in the LawyerOS Starter Kit. Nothing here is legal advice; check your regulator's rules for anything you depend on.

Frequently asked questions

Can Notion manage contract review?

It can track issues, positions, versions and dates. The review itself is your work, optionally supported by AI with verification.

How do I track renewals?

Record renewal and notice dates in Deadlines with the clause as source and reminders ahead of the notice period.

What is a playbook?

A written list of preferred positions, fallbacks and escalation points per clause type.

Related guides