The Document Diff Workflow: Two Versions, and Exactly What Changed

Fourth piece in the “automation workflow” series, aimed at “document handling / comparison” — a pain 25 companies named. Click through the sample data first to see how it runs.

---

Can you really read every clause they changed?

Contracts go back and forth, suppliers send a new version of the quote, the company SOP gets updated — and every time, you open both side by side and read clause by clause looking for what was touched. The nightmare case is the other side quietly dropping the late-delivery penalty from clause 7, and you signing without noticing.

Clause-by-clause comparison is mechanical work with clear rules, but missing one clause can cost you a fortune. That’s exactly the kind of thing to hand to a workflow, so your attention goes to the negotiation instead.

---

What this workflow does for you

Feed it the old version and the new one. The AI compares them clause by clause and marks each as unchanged, edited, deleted or added, lays out “before → after” for every edit, calls out specifically the changes that work against you (payment, delivery, penalties, acceptance…), and closes with a plain-language list of what you must negotiate before signing.

---

Understand it in the cloud, run it locally

The demo above runs in the cloud, and the point of it is simply to let you see how the workflow operates. When you’re ready to run it against your company’s real contract documents, the same workflow also has a local mode — it executes on your own machine and not a single record leaves it. We won’t go into that here; for now it’s enough to know that the local path exists.