An attachment called proposal-new.pdf may make sense inside its project folder. In a customer's Downloads folder, it loses most of that context. A useful filename explains what a file is even after it leaves home. The aim is not to invent an elaborate code. It is to select a few recognizable details that match how people will later search for, send, and check the document.
Start with the question someone will ask
Think about what you will remember three months from now. For an event, that might be its name and the document type. For meeting notes, the date may matter more. Names such as summer-fair-room-plan-v03.pdf and 2026-10-08-planning-notes.docx make those details visible. These are suggested patterns, not universal standards. A community group, a design project, and a family photo archive need different clues.
Keep the order consistent within one collection. Putting the project first in some names and last in others makes an alphabetical view harder to scan. Prefer recognizable words over private abbreviations. A name like sf-rp-ak.pdf is short, but every new participant needs a translation. Keep the most useful search terms even when the enclosing folder already contains some of that information.
Separate dates, versions, and approval
A date might identify the contents, the release, or the event itself. Decide which meaning your collection uses. The format 2026-10-08 avoids the month/day ambiguity that can appear when files cross borders. A simple revision sequence can use v01, v02, and v03. A revision number does not, by itself, mean that a document has been approved.
Labels such as final, final-new, and really-final stop helping as soon as another correction arrives. Record approval in the agreed delivery folder or a short handover note. A change after approval should receive an identifiable new release. Before casually renaming a file that other people have linked to, check whether the application preserves or updates those references.
Try the rule on a small collection
For files that travel between systems, short names using letters, numbers, hyphens, and underscores reduce avoidable friction. Windows reserves characters including colons, question marks, and slashes for other purposes. Keep the extension intact when renaming: changing the letters after the dot does not convert a PDF into an editable Word document.
Try the rule on ten representative files. Can you tell two similar documents apart? Is the useful word visible in a narrow file-list column? Can someone else find a requested document without an explanation? Put two or three examples in the project folder. You do not need to rename an entire historical archive before improving new files; address older problem areas when their use justifies the work.