File automation for lawyers: sort case files

Every lawyer knows the folder. A court portal saves a filing as 28391_document.pdf. Opposing counsel emails final_v3.pdf. The e-signature service returns envelope-cc19.pdf. None of those names tell you which matter they belong to, so you open them one by one, rename each, and drag it into the right client folder. Do that forty times a week and you have spent an afternoon being a filing clerk instead of a lawyer.

The good news: the document already knows which case it belongs to. The case number is printed inside almost every filing, order, and brief. The parties’ names are printed inside every contract. Those words are there even when the file name is gibberish. Elegant File Explorer can read them and file the document for you — and everything it reads and moves happens on your own PC, with nothing sent anywhere.

Why file names fail lawyers#

Legal documents arrive from systems you do not control. Court e-filing portals name files by internal ID. Clients scan a signed page and send scan0023.pdf. A paralegal downloads three exhibits and gets download (7).pdf. A rule that only reads the name is helpless against all of this — the name is noise.

So the honest starting point is this: stop trying to organize by name, and start organizing by what is written inside the document. That is the whole shift, and it is the thing plain Windows Explorer cannot do.

Read the case number inside the file#

The most reliable marker a filing carries is its own case number. Elegant File Explorer has a condition that looks at the content of a document — PDF, DOCX and TXT — not just its name. When a rule uses “Content contains (PDF, DOCX, TXT)”, the app reads the text of the document for you, and it does this even for a scanned PDF: the reading is built-in OCR, 100% on your PC. The signed order that arrived as a flat scan is read the same as a born-digital one.

The practical payoff for an active matter: build one rule per case, keyed to that case’s number.

1. Open Auto-organization and click + New rule.
2. Rule name: the matter, e.g. Acme v. Doe — 24-cv-01822.
3. Monitored folders: click + Add folder, Browse… and pick your Downloads (add the Desktop too, if filings land there).
4. When to run: “Automatically, when a file arrives (real time)”, so a filing is put away the moment it downloads.
5. Which files (conditions): add two conditions joined with All (AND):
   • “Extension is” with the value .pdf, so only PDFs are read.
   • “Content contains (PDF, DOCX, TXT)” with the case number, e.g. 24-cv-01822.
6. What to do (actions): add, in order:
   1. “Apply tag” → Acme.
   2. “Move to” → Documents\Cases\Acme v. Doe\{year}.

Click “Simulate effect” to see the Preview — nothing is actually changed, then “Save rule”. From that point, any PDF that carries 24-cv-01822 in its text lands in that matter’s folder, tagged, no matter what the file was called. One rule per active case, and your Downloads folder files itself by matter.

The first read of a full folder runs in the background and can take a little while — the app is reading each document once. After that the text is remembered, and each new file is recognized instantly.

The ready-made recipes that already fit#

You do not have to build everything by hand. Open the Recipe Gallery (the wizard offers it with “How about starting from a ready-made recipe?”) and two content recipes do a lot of a lawyer’s filing on their own:

• “Contracts by content (PDF and DOCX)” reads the anatomy of an agreement — it recognizes the phrases every contract prints, including “between the parties” and “hereinafter” — and files the document into Documents\Contracts with the Contract tag. It catches the draft that got saved as final OK.docx and the scanned agreement with no useful name.
• “Signed digitally, by content” recognizes the stamp that e-signature platforms leave in the text — “DocuSign Envelope”, “digitally signed” — and moves the executed copy to Documents\Signed with the Signed tag, in real time. The legally binding version never gets mixed up with the draft again.

Both are honest about the same thing: they read printed phrases, not the file name, so they work on the badly named files that defeat everything else.

File by where it came from, too#

There is a second signal you already have and never see: Windows quietly records where each download came from — the site behind it. Almost no program shows it. Elegant File Explorer does, and a rule can act on it.

Use the condition “Downloaded from site (domain)” with your e-filing portal’s address, and every document you pull from that court files itself into a court folder automatically. Point another rule at your practice-management tool the same way. The {origin} token can even stamp the source site straight into a folder name. This is reading only — the app never changes the file, never “unblocks” anything.

If you want to search inside those filings later — to find the one brief that cites a particular statute, across hundreds of scanned PDFs — that is the same built-in reading engine at work. Our guide on searching text inside PDFs, even scanned walks through it end to end.

Nothing is deleted, everything is reversible#

The professional worry with any automation is that it will move the wrong thing. Two guardrails answer that. First, “Simulate effect” shows you exactly what would happen — a full preview — before a single file moves. Second, every run can be reversed: the run history keeps each execution, and “Undo” puts everything back. Moving is moving, never deleting; a file sent to the wrong matter is one click from home.

For a firm, the destination folder is where this compounds. Point a rule’s “Move to” at a folder your document-management system or a synced drive already watches, and local filing becomes firm-wide filing for free — no email, no zip, no “please find attached.”