Build every file name from the same parts in the same order: project, what it is, date, and version. Then keep folders simple and let the names carry the detail.
Why 'final' is not a version
Words like 'final', 'new' and 'latest' describe how you felt when you saved the file, not what the file is. They stop being true as soon as you make another change. A name such as 'finalFINAL' shows the problem clearly: the writer ran out of ways to say 'this one is newer'.
A version number or a date does the same job and never expires. 'v03' will always mean the third version. A date written year first, such as 2026-10-14, sorts chronologically when the rest of the naming pattern is consistent and the folder is sorted by name; the folder’s sort order still matters.
A naming pattern you can repeat
Choose an order and keep to it. A useful pattern is project, then document type, then date, then version: 'GardenGroup_AnnualReport_2026-10-14_v03.docx'. Use underscores or hyphens instead of spaces, avoid symbols, and keep each part short. The pattern should be something you could explain to a colleague in one sentence.
Putting the project first groups related files together when sorted alphabetically. Putting the date in the standard year-month-day order means files from the same project line up in time order. You do not need every part on every file. Photos, for instance, might only need project, subject and date.
Folders that stay shallow
Deep folder trees create their own problem, because you must remember the path. Two or three levels are usually enough. Start with the project, then split by type of material, and keep a separate place for older versions so the working folder only shows what is current.
An 'Archive' folder inside each project is a calm solution to the question of whether to delete anything. Superseded versions move there, not into the trash, so nothing is lost and the main folder stays readable. Review it occasionally and remove what you are sure you will never need.
See the idea
in a real situation.
Amara runs a small community gardening group and keeps her records on one laptop. Her Documents folder holds forty files, including 'reportfinal2.docx', 'newreport.docx', 'finalFINAL.docx', 'budget.xlsx', 'budget copy.xlsx' and several photos called 'IMG_4471.jpg'. She needs to send the latest annual report to the committee tomorrow and is not sure which file it is.
Documents contains: reportfinal2.docx, newreport.docx, finalFINAL.docx, budget.xlsx, budget copy.xlsx, IMG_4471.jpg, IMG_4472.jpg. Amara cannot tell which report is the most recent, and the budget has two copies with no sign of which is correct.
GardenGroup/
Reports/
GardenGroup_AnnualReport_2026-10-14_v03.docx
Budget/
GardenGroup_Budget_2026-10-10_v02.xlsx
Photos/
GardenGroup_PlantingDay_2026-09-20_01.jpg
GardenGroup_PlantingDay_2026-09-20_02.jpg
Archive/
GardenGroup_AnnualReport_2026-10-02_v01.docx
GardenGroup_AnnualReport_2026-10-09_v02.docx
GardenGroup_Budget_2026-10-03_v01.xlsx
Pattern to copy: Project_DocumentType_YYYY-MM-DD_vNN.extension↗Each name states the project, content, date and version, so consistently named reports can be compared by their stated date and version; confirm which version is actually current before using it.
↗The Archive folder keeps earlier versions safe while the working folders show only current files.
↗The same pattern works for any future project, so Amara does not need to invent a new system each time.
Choose one project today, write down your naming pattern, and rename its files so the current version is obvious at a glance.