Best practices

Naming files is not a filing system: what to do instead

A naming convention is the most popular substitute for a filing system, and it holds until a second person arrives. What a filename can carry, and what has to move somewhere else.

Peter Wenzel
Consultant & co-founder
2 November 2026
6 min read
Error loading image

The most popular substitute for a document management system is a naming convention. Somebody writes it on an A4 sheet, pins it above the printer, and for a while the drive looks beautiful. 2026-03-14_Invoice_Hoffmann_4711_signed.pdf. Sortable, searchable, self explanatory.

We are not going to tell you that is a bad idea. A good convention is genuinely useful, and we recommend one even to organisations running a full system. What we are going to do is be precise about what it can carry, because the failure mode is specific and it always arrives the same way.

Why conventions feel like they work

A date at the front in ISO order makes a folder sort itself chronologically. Putting the document type in the name means a search for "invoice" returns invoices. Adding the counterparty means you can find everything from one supplier with a wildcard. None of that is an illusion. For a single person with a tidy drive, a convention does the two things that matter most: it makes documents findable and it makes the folder legible at a glance.

So if you are one person, your drive is tidy, you follow your own convention without thinking about it, and nobody else needs to find anything, you do not have a filing problem. You have a backup problem, possibly, and a retention problem if you keep books. Buying a document management system will not hand you anything you are missing. Go and spend the money on something that will.

Where conventions break

The first break is arrival of a second person. A convention lives in the head of whoever wrote it, and the sheet above the printer answers the easy cases while the awkward ones were never written down. Is a credit note an invoice? Does the date mean the document date or the day it arrived? Is it Hoffmann or Hoffmann GmbH? Each ambiguity produces two variants, and two variants mean every future search has to guess which one somebody chose.

The second break is enforcement. Nothing stops anyone from saving Scan_0042.pdf. There is no mechanism, only goodwill, and goodwill degrades under deadline pressure. In practice a convention holds for the documents that arrive on a calm Tuesday and fails for the ones that arrive during the week you are closing the quarter, which are the important ones.

The third break is the one people do not see coming. A filename is editable by anyone with write access to the folder. Whoever can rename a file can rewrite what the organisation believes about it. Change _draft to _signed and the document has, as far as your filing is concerned, been signed. There is no record that this happened and no way to ask when it changed. That is the point at which a naming convention stops being a weak filing system and becomes a liability, because it looks like evidence and is not.

The fourth break is mechanical. Names that carry five pieces of information get long, paths that carry five levels of folders get longer, and Windows applications still fall over at path lengths that long names reach surprisingly quickly. People respond by shortening and abbreviating, and the convention quietly stops being readable.

The underlying problem

A filename is a label. Filing is a record.

A label describes a document to whoever is looking at it right now. A record answers questions later: who decided this, when did it change, who was allowed to see it, how long must it be kept, which case does it belong to. You cannot put any of that in a filename, not because the string is too short, but because a filename has no author, no history and no permissions of its own.

In Germany this distinction has a legal edge. Tax law expects bookkeeping records to be traceable and expects you to be able to describe the process that produced them in a Verfahrensdokumentation, with the retention obligations themselves in § 147 of the Abgabenordnung and § 257 of the Handelsgesetzbuch. Those are German rules applying to organisations that keep books in Germany. A convention that anyone can edit without trace is a difficult thing to describe in that document with a straight face. We go into what the description has to cover on procedural documentation and into the archiving side on audit proof archiving.

What to take out of the filename

The move is not to abandon naming. It is to move each piece of information to the place that can be responsible for it.

The document date, the arrival date and the retention class become fields on the document, which means they can be queried, reported on and used to decide when something may be deleted. The counterparty becomes a link to a contact rather than a spelling. The document type becomes a category with a defined list, so nobody has to decide between "Invoice" and "Rechnung" at half past five. The status becomes a status, with a history of who changed it and when. The case or project becomes the container the document sits in, so the relationship survives even if every other attribute changes.

What is left in the filename after that is a short human readable remainder, and it stops mattering very much, which is the point. The filename becomes a convenience for the person who downloads the file, not the load bearing structure of your organisation's memory.

What a convention is still for

Two things, and they are worth keeping.

It is still the right tool for documents in transit, before they have been filed. Scans coming off a multifunction device, exports from a bank, batches from a payroll bureau: these arrive as files in a folder, and a predictable name makes automatic filing rules possible. A rule that recognises a pattern in a filename is a perfectly reasonable piece of plumbing.

And it is still the right tool for documents leaving the organisation. When you send a client eleven PDFs, the names are the only metadata that travels with them. A client who receives 2026-03-14_Invoice_4711.pdf can file it. One who receives document_17.pdf cannot. If you work with external parties through a portal rather than email, the same applies to what they download, which is one of the quieter reasons the client portal matters more than it sounds.

Do not rename forty thousand files

One last thing, because it is the most common mistake when organisations decide to take filing seriously. The instinct is to go back and apply the new convention to the existing drive. Resist it.

Renaming historical files costs weeks, breaks every link and shortcut pointing at them, and produces a drive that is consistently named and no better organised. The documents that matter are the ones arriving from now on and the open cases people actually touch. Import those properly, leave the archive where it is with its inconsistent names, and let search do the work on the old material. You can see what that looks like in practice on features, and the price for the whole thing is 360 euros per user per year with no setup fee.

Topics

File namingFiling structureMetadataAudit trail

More posts