Legal Document Workflow Automation for Small Firms

TL;DR: A legal document workflow files a document into the correct matter the moment it arrives, instead of leaving it in an inbox until someone has time. The hard part is not the folder structure, it is intake: documents reach the firm through personal mailboxes and never get filed the same way twice. A workflow watching a shared firm mailbox can classify a document, read the counterparty and matter reference off it, rename it, and file it, pausing for a person where a misfile would matter.

Ask a six-attorney firm where the executed lease for the Northwind matter is, and you will get three answers. It is in the matter folder. It is in an associate's Outlook. It is on the shared drive as Lease FINAL v3 (signed).pdf, next to Lease FINAL v2 (signed) (1).pdf.

All three are true. Nobody decided to have a bad filing system; the system is fine on paper. What failed is that documents arrive faster than anyone files them, and a document that sits unfiled for four days gets filed by whoever eventually opens it, using whatever convention they remember. Firms of two to fifty people feel this hardest, being large enough to generate real document volume and too small to fund a six figure document management system.

A legal document workflow is a standing instruction that takes a document at the moment it arrives, decides what it is and which matter it belongs to, names it to one convention, and puts it where the matter expects it to be.

Why does matter-centric filing beat filing by document type?

File by matter first, document type second. Filing the other way means a matter's story lives in six places, and nobody can reconstruct it.

A top-level Contracts folder, a top-level Pleadings folder, and a top-level Correspondence folder feel tidy, because each document has an obvious home. The structure falls apart the day you need everything about one client. Closing a matter, responding to a discovery request, handing a file to successor counsel, and answering a fee dispute all require assembling one matter, not one document type.

The test is simple. Can one person copy a single folder and produce the complete file for that matter? If they also have to visit four other folders and search two mailboxes, you are not matter-centric yet. Retention is the second argument: obligations attach to the matter, and matters close on different dates, so a clock that runs on a folder is workable while one that runs across scattered documents is not.

A matter folder structure that works

Use a shallow structure that every matter gets, whether or not every subfolder is used. Consistency matters more than fit.

Clients/
  Northwind Traders/
    2026-014 Lease Dispute/
      01 Intake and Engagement/
      02 Pleadings and Court Filings/
      03 Discovery/
      04 Correspondence/
      05 Agreements and Executed Documents/
      06 Research and Memos/
      07 Billing/
      08 Closing/

Three things make this work. The matter number sits in the folder name, so the folder is unambiguous when a client has five matters. Every matter gets every numbered subfolder, even empty ones, because an empty folder tells an associate where something goes and an absent folder invites invention. And the tree stops two levels below the matter, because deeper trees get abandoned under deadline pressure. The exception worth making is 03 Discovery, which usually needs Ours and Theirs beneath it.

Naming conventions that survive discovery

Put the date first in ISO format, then the matter reference, then what the document is.

2026-03-14 2026-014 Motion to Dismiss.pdf sorts chronologically, identifies its matter if it is ever separated from its folder, and says what it is without being opened. Compare MTD final.pdf, which is useless the moment it leaves the folder it was created in and misleading the moment a second version appears.

• Dates as YYYY-MM-DD. They sort correctly everywhere, and they settle whether 03/04 means March 4 or April 3.
• The matter reference in the filename, not only the folder. Files get emailed, downloaded, and produced. The filename is the only metadata that travels with them.
• State execution status explicitly. Executed and Unsigned beat final, FINAL, and FINAL v3. A document is not final because someone said so in a filename.

Avoid initials and internal shorthand. If a document may be produced, opposing counsel will read the filename.

Where does filing discipline actually fail?

Filing discipline does not fail at the folder structure. It fails in the twenty minutes after a document arrives, when the person who received it has something more urgent to do.

Trace an executed agreement. Opposing counsel emails it to the associate who negotiated it. She is in a deposition, so it sits in her mailbox. Two days later she forwards it to a paralegal with "please file". The paralegal does not know the matter number, guesses the folder, and keeps the attachment's original name. Nothing here is negligent. Everyone acted reasonably, and the file is still wrong.

Every convention you write assumes a person applies it at the moment of arrival, and that assumption fails hardest when the firm is busiest. There are three durable fixes: route intake through a shared address rather than personal mailboxes, make the filing decision at arrival rather than in a later pass, and make the default action correct so that doing nothing still produces a filed document. Our broader guide to organizing case files and contracts covers the structural side; this post is about the arrival side.

Conflict checking and retention are processes, not habits

Conflict checking works when it is a gate nobody can skip, and fails when it is something the firm believes it does. The same is true of retention.

This is not legal advice, and your obligations come from your jurisdiction and your bar. But one operational pattern is consistent. Conflict checks happen before the matter folder exists, not after the first document arrives, and the check is recorded with a date and a name. Retention is decided at matter closing, while someone still knows what the matter was, and written into the closing folder rather than remembered. The filing system's job is narrower: make the record easy to produce, with one folder per matter, a closing date you can find, and documents named so a reviewer can see what they are without opening each one.

How does a legal document workflow run?

You describe what should happen in plain English, once. The steps appear on a canvas, and each one can be edited there. A contract and correspondence intake workflow uses five.

• Email Attachment as the source, on a connected shared firm mailbox in Gmail or Outlook. It runs once per attachment, can be scoped by sender domain or by "Subject contains", and does not save the email itself. Setup is in the Gmail attachment workflow post.
• Ask AI About the File to classify. The branches are the answers the model is allowed to give, so you name them yourself: pleading, correspondence, executed agreement, invoice. The document leaves by the branch that matches. More in AI document classification and routing.
• Read Details from File to pull named values off the document: counterparty, matter reference, execution date. Each field you name is available to later steps, so it can appear in a filename, a folder path, or an approval question. More in extracting data without templates.
• Rename and Move, each taking a plain English instruction such as "date first in YYYY-MM-DD, then the matter reference, then the document type" and "into the client's matter folder, under Agreements and Executed Documents".
• Ask a Person to Approve where a misfile would matter. Nothing downstream happens until an admin, a named person, or anyone in the workspace decides. Set it to Always ask, or to Only when unsure, where confident filing into existing folders proceeds and is logged while new folders and unsure matches wait.

Three properties matter for legal work specifically. An approval shows the file and the planned move before anything moves, so the reviewer approves a plan rather than undoing a mistake. Every run is recorded, can be replayed on the canvas exactly as it happened, and can be retried from the step that failed. And if your documents live in a connected SharePoint, OneDrive, Google Drive, or Dropbox, they are renamed and moved in place inside that storage rather than migrated out of it.

Four workflows worth starting with

Each of these is a sentence you would type. Start with one.

When an attachment arrives in the firm mailbox, ask whether the agreement is fully executed. If it is, rename it with the execution date and the counterparty and file it under the matter's Agreements and Executed Documents folder. If it is unsigned, file it under Agreements and Executed Documents/Drafts and ask Marcus to confirm the matter first.

When a court filing arrives, read the matter reference and the filing date off the document, rename it as the filing date then the matter number then the document title, and move it to that matter's Pleadings and Court Filings folder.

When an attachment arrives from a client domain, read the counterparty and matter reference and move it into that client's matter folder under Correspondence. If the matter is unclear, ask an admin before filing.

Every Sunday, go over every file in Clients/Northwind Traders/2026-014 Lease Dispute and rename anything that does not start with a YYYY-MM-DD date followed by the matter number.

That last one uses the On a Schedule source with "Each run goes through" set to Every file, every run, which is how an existing matter folder gets brought up to one convention rather than only new arrivals. The post on organizing signed documents automatically goes deeper on the executed versus unsigned split.

Manual filing, a legal DMS, Power Automate, and workflows compared

There are four honest ways to run a law firm document management workflow, and they are not close substitutes.

Be clear-eyed about the DMS column. iManage and NetDocuments exist because firms need ethical walls, matter-level security, and records management that stands up to an audit. We do not offer those, and a firm with a genuine conflicts wall requirement should buy a product built for it. Most small firms, though, are choosing between a DMS they will not buy and the filing behavior they have now.

What will it not do?

Legal document automation covers a lot of ground, and workflows cover only the filing part of it. There are no e-signature steps inside a workflow. It can recognize that an agreement is executed and file it accordingly, but it does not send documents for signature.

There is no conflict checking. Nothing in a workflow screens parties against your existing matters, and filing automation should not be treated as any part of a conflicts process.

There is no legal hold feature and no docketing. A workflow does not suspend deletion, does not preserve custodian sets, and does not calculate deadlines from a filing date.

Beyond the legal specifics: AI steps can occasionally be wrong, which is what the approval step is for, and human review works best by exception. Approvals expire after the wait you set, and the file then takes the Expired exit. Workflows on files uploaded to The Drive AI work on every plan; connecting Gmail, Outlook, SharePoint, OneDrive, Google Drive, or Dropbox requires the Max plan on a personal workspace, or any Team plan.

Setting it up

1. Connect the firm mailbox that intake arrives in, and decide that executed documents and court filings go there rather than to individuals.
2. Pick one matter folder and get it exactly right by hand. This is the pattern the workflow copies, so a wrong example becomes a hundred wrong folders later.
3. Connect the storage your documents already live in, whether that is SharePoint, Google Drive, OneDrive, or Dropbox. Nothing moves out of it.
4. Write one sentence describing the intake you want handled, starting with executed agreements, then adjust the naming instruction on the canvas to your convention.
5. Add Ask a Person to Approve before the Move, set to Always ask, and run it for two weeks. Reading what it proposes is how you learn whether the classification is right before it files on its own.
6. Once the proposals are consistently correct, switch the approval to Only when unsure, and add the next document type.

Frequently Asked Questions

What is a legal document workflow?

A legal document workflow is a standing instruction that handles a document when it arrives rather than in a later filing pass. It decides what the document is, which matter it belongs to, what it should be named, and where it goes. In practice it covers contract intake, court filings, and client correspondence, pausing for a person where a misfile would cause real harm.

Does this replace a document management system like iManage?

No. A legal DMS provides ethical walls, matter-level security, and records management built for bar and audit requirements, and we do not offer those. Workflows address a narrower problem: getting documents filed correctly at intake, into whatever storage your firm already uses. Firms with genuine conflicts wall obligations should buy a system designed for that.

Can it tell an executed agreement from an unsigned draft?

Yes. An Ask AI About the File step can decide whether an agreement is fully executed, with branches you name yourself, and each branch leads somewhere different. Executed agreements can be renamed with the execution date and filed into the matter's executed documents folder, while unsigned drafts go to a drafts folder or wait for a person. Like any AI step it can occasionally be wrong.

Will it move our files out of SharePoint or Google Drive?

No. A workflow watching a connected SharePoint library, OneDrive, Google Drive, or Dropbox folder renames and moves files in place inside that storage. Nothing is imported or migrated unless the workflow includes a Save a Copy step, and then only to the location you name. Nothing outside the folder you chose is touched, so existing permissions and backups keep working as they do today.

Does it do conflict checking?

No. Nothing in a workflow screens parties against existing matters or flags adverse representation, and it should not be treated as part of your conflicts process. A conflict check needs to be a gate before a matter opens, run against a complete party list, and recorded with a date and a name. A filing workflow runs after that decision has already been made.

How does the approval step work?

The workflow stops. The file and the planned action appear in the Approvals inbox with the question you wrote, such as "OK to file this in the Northwind lease matter?". You choose who decides: admins, specific people, or everyone. Nothing downstream runs until someone approves or rejects, or the wait expires after 24 hours, 3 days, or 1 week, at which point the file takes the Expired exit.

Start with contract intake

Pick the document type that causes the most confusion when it goes missing, which for most firms is the executed agreement, and write one sentence describing where it should end up. Run it with an approval on every file until the proposals stop surprising you. Each step is described in the complete guide to automated document workflows, there is more for firms on the legal solutions page, or go straight to Workflows and create an account.