Automations

Organize Contracts by Counterparty and Find a Clause Across All of Them

Someone asks which of your vendor agreements contain a non-compete. There are ninety of them, in four folders, and about a third are scans.

The short answer

Contracts file by counterparty, because a relationship accumulates documents — a base agreement, amendments, statements of work, renewals — and they only make sense read together. A workflow uses the Read Details from File step to pull the parties, the effective date and the agreement type off each document, the Rename step to name it by date and type, and the Move step to file it under that counterparty. Once the set is readable, the useful question changes from "where is that contract" to "which of these contain this clause", which is asked across the whole set rather than folder by folder.

Steps this uses

File UploadedEmail AttachmentOn a ScheduleRead Details from FileCheck File DetailsRenameMoveSend a Message

Before and after

What actually changes

As they arrive

  • agreement.pdf
  • amendment 2.pdf
  • MSA signed scan.pdf
  • SOW.pdf

After the workflow

  • Northwind Logistics/2023-01-01-master-services-agreement.pdf
  • Northwind Logistics/2024-06-01-amendment-01-rates.pdf
  • Northwind Logistics/2025-02-01-statement-of-work-03.pdf
  • Harlan Partners/2024-09-15-nda-mutual.pdf

Two counterparties, each holding the agreement and everything that has modified it, in the order it took effect.

Setting it up

Described once, then it runs

This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.

When a contract or amendment arrives by email or upload, read the parties, the effective date and the agreement type off it, name it by date and type, and file it under that counterparty.

01

One folder per counterparty

The base agreement and everything that modifies it together. Filing by contract type instead separates an amendment from the agreement it amends, which is the one pairing that always has to be read as a unit.

02

Name by effective date and type

The Rename step writes both, so the folder reads as the history of the relationship: signed, amended, renewed, amended again. Effective date rather than signature date, because that is the one that governs.

03

OCR the scanned ones

A third of any contract archive is scans of signed originals. They are read with OCR, which is what lets a clause search cover the whole set rather than only the ones that happen to be digital.

04

Watch the renewal dates

The On a Schedule trigger and Send a Message step report agreements approaching a renewal or notice window — the dates that cost money precisely because nobody was watching them.

The question is rarely about one contract

Nobody asks where the Northwind agreement is; they ask whether any of the vendor agreements cap liability, or which ones auto-renew in the next quarter. Those are questions about a set, and they can only be answered when the whole set is readable — including the scans. A contract archive that is organized but half unsearchable answers the easy question and not the one being asked.

Effective date, not signature date

They differ often enough to matter. An amendment signed in February and effective in April governs from April, and a folder sorted by signature date puts the documents in an order that does not match when their terms applied. Naming by effective date means the sequence in the folder is the sequence that was in force, which is what somebody reconstructing a position needs.

What it does not do

It organizes and searches. It does not draft, redline, negotiate, or judge whether a clause is favourable. It also does not give a legal opinion about what a clause means — a clause search finds the language, and reading it is the lawyer's job. Treating an extraction as an answer rather than a pointer is the failure mode worth avoiding.

FAQ

Common questions

How should contracts be organized?

By counterparty, with the base agreement and every amendment, statement of work and renewal in one folder, each named by its effective date and type. A relationship accumulates documents that only make sense read together, and filing by document type instead separates an amendment from the agreement it modifies.

How do you find a clause across many contracts?

By searching the contents of the whole set rather than opening them one at a time, which requires the scanned ones to have been read with OCR first. The search returns the language and the document it came from; reading and judging it is still the lawyer's work.

Should contracts be named by signature date or effective date?

Effective date. They differ often enough to matter, and the effective date is the one that governs. Naming by signature date produces a folder whose order does not match the order in which the terms actually applied, which is misleading exactly when somebody is reconstructing a position under pressure.

Can it warn me about auto-renewals?

It can report agreements approaching a renewal or notice window, read off the documents themselves, on a schedule. Renewal and notice dates are the clauses that cost money when unwatched, and they are usually only noticed after the window has closed.

Which of these has a non-compete?

Asked across the whole set, including the scanned ones.

Build this workflow

5 GB free · No credit card required