Comparison against your playbook is not an opinion about the contract
Reviewing a contract starts with a mechanical task that takes most of the time: finding where this document differs from the kind you usually accept. Going through 40 pages to find 6 differences is a lot of work, and it is not work a lawyer is suited for.
Separate that step, and advisers no longer receive the full contract. They receive a list of deviations, with the clause text and your standard position, so they focus on judging rather than searching.
The comparison does not lead to any legal conclusion. It is a statement that the contract differs from your standard position. Anyone giving legal advice decides whether that difference is acceptable.
Absence is the kind of deviation that is easiest to miss. If you always include a clause and this contract does not have one, there is nothing in the document to notice. That is why the comparison must run against your standards, not from the document.
How the ActionFlow runs on the canvas
The standard positions are stored in a Notion or Airtable node. Each clause type occupies its own row and contains your chosen wording, your acceptable range, and whether the clause is required.
The Document Upload node takes the contract. The PDF4me node extracts it.
A Generate Object node returns the contract as a clause map: clause type, text, and position in the document. That mapping lets the next step check both differences and the absence of clauses.
The Loop node walks your standards, not the clauses in the contract. That difference matters because it is the only way a missing clause can be recognized as a finding.
Another Generate Object node examines each standard against the map and returns one of four results: it matches, it differs from the quoted text, it is absent, or it is present but ambiguous.
The Sort node orders the findings by the priorities that you have set for each clause row, so the deviation that matters most to you appears first rather than the one that came earliest.
A Notion node writes the review as a table, with your entry and their text in side-by-side columns. A Slack node then tells the reviewer that it is ready.
The flow has not signed, accepted, or negotiated anything.
Nodes this ActionFlow uses
- Notion (Integration): holds your standard positions, one row per clause type. Airtable fits the same slot.
- Document Upload (Data) plus PDF4me (Data): take the contract and extract its contents.
- Generate Object (AI Core): returns a clause map before any comparison happens.
- Loop (Control): walks your standards, not their clauses, so absence is detectable.
- Generate Object (AI Core): returns matches, differences, absent, or ambiguous per standard.
- Sort (Data): orders findings by the priority set on each clause row.
- Notion (Integration): writes your position and their text side by side for the reviewer.
- Slack (Communication): tells the reviewer the comparison is ready.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.