Start with what you usually search for
Think of three documents that took time to find. Did you try remembering date, subject, project or a related person? The answer helps order filename elements. A system for invoices may differ from one for photographs or drafts. You need not invent a convention for every computer file. Begin with a specific collection where improvement is easy to observe and maintain.
Use a short, consistent structure
One option is year-month-day, subject and status: 2026-10-23-guide-meeting-notes. Dates in this format support chronological alphabetical sorting when complete and consistent. Choose simple separators and keep the same logic. Avoid excessively long names trying to include the entire document. If a code makes sense only to you today, write a short explanation. The name should remain understandable when the project is less fresh in memory.
Define versions without multiplying the word final
Names such as final, final-new and really-final make a work’s status difficult to understand. Use numbered versions such as v01 and v02 and a clear status where necessary. Define where the delivered or published version belongs too. With collaborators, agree the convention before renaming shared files. Some systems and links depend on paths or names, so bulk changes can create problems beyond visual organisation.
Preserve originals and extensions
Before reorganising an important collection, keep a copy and test with a small group. Do not change extensions to attempt format conversion: renaming does not transform file contents. If a system generates its own identifiers, check how to preserve them. Avoid unnecessary personal data in names, especially for documents to be shared or displayed in screenshots. A functional description is usually enough to locate the material.
Test the convention through a real search
After renaming some documents, try finding one without opening the folder where you know it resides. Search by subject, date or version and check whether the name helps. Adjust while the collection is still small. Keep an example in an instruction file inside the folder if useful. Organisation works better when incoming documents already have a defined step rather than depending on a major clean-up that is repeatedly postponed.
