Every naming convention works for about three weeks. Then someone saves "Copy of Untitled document", someone else uses underscores instead of dashes, and the person who wrote the convention leaves.
The short answer
A file naming convention holds in Google Drive only when something other than a person applies it. Put the date first in ISO form (2026-09-15), then the document type, then who it belongs to — that sorts correctly and reads unambiguously. Then let a workflow apply it: describe the naming once, and a workflow watching the folder uses the Rename step to name each new document from its contents, so the convention is enforced at the moment a file arrives instead of being remembered afterwards.
Steps this uses
Before and after
As they arrive
After the workflow
The same four files, renamed from what is written inside them rather than from how they were uploaded.
Setting it up
Date first in ISO form so files sort chronologically without any help. Then the document type, then the party. `2026-09-15-invoice-acme.pdf` beats `Acme invoice (final).pdf` in every sort order and every search.
You do not write a pattern or a regex. You say what the name should contain — the date on the document, what kind of document it is, and who it is from.
A workflow watching a Google Drive folder picks up each document as it arrives. The Read Details from File step pulls the date and the party off the document itself rather than off the upload.
The Rename step applies the naming to the file in place, in the Drive folder it is already in. Nothing moves to a different system and nobody has to learn a new interface.
Google Drive sorts alphabetically. A name that starts with the date sorts chronologically for free, and an ISO date (2026-09-15) sorts correctly where 9/15/26 does not. A name that starts with the client sorts by client, which is what folders are already for — so you spend the most valuable position in the filename on information the folder structure already carries.
A naming convention is a request that every person remember a rule at the least convenient moment — while doing something else, in a hurry. It holds for as long as the person who wrote it is watching. This is not a discipline problem; it is a design problem. Conventions that survive are applied by the system at the point a file arrives, not asked of the person saving it.
The same naming applies to documents you already have. A workflow can run on a schedule over a folder you point it at, renaming what is there rather than only what arrives next. Files are renamed in place in Google Drive, so links and permissions are unaffected.
FAQ
Put the date first in ISO form (2026-09-15), then the document type, then the party — for example 2026-09-15-invoice-acme.pdf. ISO dates sort chronologically in an alphabetical list, which Google Drive gives you by default. Keep the client or project in the folder rather than repeating it in every filename.
Not on its own. Google Drive keeps whatever name a file arrived with and has no feature that reads a document and renames it. Renaming from contents requires a tool that reads the file, which is what a workflow with a Rename step does.
Dashes. They are treated as word separators by search engines and by most search boxes, where underscores are often treated as part of the word. Whichever you pick, the reason conventions break is inconsistency between people, not the character itself.
No. Google Drive links point at a file ID, not a filename, so renaming a file in place leaves shared links and permissions working exactly as before.
A workflow applies it to every document that arrives, in the Drive folder you already use.
Try The Drive AI Free5 GB free · No credit card required