Choose what belongs first
The opening element influences which files sit together when sorted by name. A year-month-day date at the beginning can suit a chronological series. For several projects running in parallel, the project reference may matter more. Choose according to the question that usually brings you to the collection rather than adopting a rule designed for a different office.
For recurring meeting notes, an example might be “2026-10-16_Project-North_Meeting”. If every file already sits inside a Project-North folder, repeating that reference may be unnecessary. If individual documents frequently leave the folder, it can help recipients identify them. The folder structure and filename should support each other rather than automatically repeat the same information.
Describe the contents in a few clear words
Choose a consistent term for each recurring document type. If the same collection uses “minutes”, “meetingnotes” and “notes” with no meaningful distinction, a simple search becomes less dependable. A shared vocabulary can be only a few lines long. It does not need to anticipate every document that might ever be created.
Avoid abbreviations understood by only one person. A slightly longer, readable description often helps retrieval more than a short unexplained code. Use characters supported by the systems involved too. Where files move between devices or services, test a sample through the complete handover route before applying a convention to a large collection.
The name does not need every property. A project, sender or reference number may help identify an invoice; its full amount and every line item need not be included as well. Information that changes regularly creates repeated renaming work. Keep the identifier stable wherever the workflow allows it.
Separate versions from approval
A version number identifies an editing stage but does not automatically establish approval. When several people handle a document, agree how the approved copy is recognised and where it belongs. Names such as “final_new_reallyfinal” do not resolve that process. They reveal that competing editing stages have accumulated without a clear rule.
A straightforward local workflow might use a sequence with a consistent number of digits, such as v01 and v02. A shared editing system with its own version history may call for a different approach. Establish what the system already records reliably before maintaining that information manually as well. An incomplete second history inside the filename can introduce confusion.
Change existing files carefully
Start with new documents and one manageable section of the older collection. Before renaming, check whether other files or colleagues refer to the current name. A tidier collection is less useful if important links stop working. Make the change known when the collection is shared rather than leaving people to discover unfamiliar names during an urgent search.
Create several realistic example names and sort them in the file view you normally use. Can you distinguish the date, topic and status when the name column is narrow? After a trial handover, open the intended file on the second device. If this small sequence works clearly, the rule is ready for everyday use. Record it in a short note in the main folder so that new files continue to follow the same logic.
