

Do | Don't |
Create unique, specific names by starting with the project/category and ending with the version number. Good: ProjectName_v2.pdf | Avoid spaces. Apps replace spaces with awkward codes like %20 that break file paths and links. Bad: Project Plan Final.docx |
Follow the naming convention provided by your manager/lead | No vague titles; name should instantly describe the content |
Use leading zeros to maintain proper numerical order for sequential items | Don't rely on case sensitivity; stick to all lowercase or camelCase |
Separate distinct elements using only underscores (_) or hyphens (-) | Windows systems reserve these symbols for backend coding logic, so never use / \ : * ? " < > | [ ] & $ |
Keep the names under 30 characters | Use a period only to separate the filename from its native format extension Bad: Data.v01.csv |
| Track iterations by using clean version control Good: ..._v01 | Never write "Final" |
Keep folder structures shallow and group files logically | Avoid creating unnecessary subfolders and deeply nested folder paths |
Keep navigation simple and ensure every file and folder is distinctly identifiable | Avoid reusing the same name, even if they're in different folders |
