Give files names you can find later
A simple naming pattern for photos, documents, and versions without relying on memory.
“New final document 2” makes sense for a few minutes. Months later, it does not explain which property it concerns or whether a newer version exists.
Choose a short pattern
You could combine date, property, and subject: “2026-09-05_apartment-a_inventory_v01.” The exact pattern matters less than using it consistently.
Avoid unnecessary personal information in filenames. A name can appear in a notification, shared download, or screenshot. Use internal identifiers your team understands when they are sufficient.
Separate versions from copies
A content change deserves an identifiable version. Downloading the same document again does not necessarily create a new version. Keep a recognizable location for the current file and avoid distributing unexplained copies across conversations.
If other people are involved, agree who updates the document and how changes are communicated. You do not need an elaborate naming system to begin.
Test whether it works
Ask someone to find a file using only the date and subject. If they need three more explanations, reconsider the system.
A filename helps retrieval; it does not replace access permissions or a backup. Those are separate tasks worth keeping separate.