A folder becomes difficult to navigate when every file is called final, new or updated. Useful names answer a more practical question: what does this item contain, and where does it belong? A small naming convention can reduce the time spent opening files just to identify them.
Start with the subject, add the kind of document and include a date when sequence matters. Keep the order consistent across related work. Avoid adding information that changes frequently if it can be captured more reliably inside the document itself.
Choose one place for working material and another for approved outputs. That distinction should be understandable from the folder structure rather than from a long chain of suffixes. When sharing a file, include enough context in its name for someone outside the original project to recognize it.
Review the convention after using it on a real task. If a name requires a private explanation, simplify it. A system works when it makes ordinary decisions easier, including finding the latest draft and understanding an older one. The aim is a readable collection, not a perfect taxonomy that becomes another job to maintain.
