We’ve all seen it: Report final.docx, Report final2.docx, Report FINAL use this one.docx. A simple naming convention fixes this. Files sort themselves in the right order, search finds them instantly, and your team stops asking “which version is the latest?”
The 8 rules
1. Put dates first, as YYYY-MM-DD
Write 2026-11-01, not 1-11-26 or Nov 1. This format sorts correctly by name, so files appear in date order automatically. It also avoids confusion between day/month and month/day formats.
2. Use the same order every time
Pick an order and stick to it. A good default:
Date_Project-or-Client_Document-Type_Version
Example: 2026-11-01_ABC-Trading_Quotation_v02.xlsx
3. Be specific, but short
Include what someone would search for: client, project, document type. Leave out filler words like “document”, “file” or “new”. Aim for under about 50 characters.
4. Avoid spaces and special characters
Use underscores _ between parts and hyphens - inside a part. Avoid characters like / \ : * ? " < > | # % &. Some are not allowed in Windows or OneDrive, and others break links and uploads.
5. Use version numbers, not “final”
Use v01, v02, v03… with a leading zero so v10 sorts after v09. When a document is approved, you can add _APPROVED or move it to an “Approved” folder. Never use “final” because there’s always another final.
Tip: if you work in OneDrive, SharePoint or Google Drive, version history already keeps older versions. You may only need a version number when you send a file outside the team.
6. Use leading zeros for numbers
01_Intro, 02_Plan … 10_Summary sorts correctly. Without the zero, 10 comes before 2.
7. Use clear abbreviations, and write them down
Short codes like PO (purchase order), INV (invoice) or HR are fine if everyone knows them. Keep a short list in your team’s shared folder.
8. Don’t put the person’s name in the file name (usually)
Cloud storage already records who created and edited a file. Add initials only if it really helps, such as for reviewer comments: _v03_AN-comments.
Before and after
| Bad | Better |
|---|---|
| quote final new.xlsx | 2026-11-01_ABC-Trading_Quotation_v02.xlsx |
| Meeting notes.docx | 2026-10-26_Marketing_Meeting-Notes.docx |
| scan0034.pdf | 2026-10-15_Rent-Contract_Signed.pdf |
| photo (2).jpg | 2026-09-30_Office-Opening_012.jpg |
| Budget 2027 (Ahmed’s copy).xlsx | 2027_Budget_Draft_v03.xlsx |
A team naming guide you can copy
FILE NAMING RULES
Format: YYYY-MM-DD_Client-or-Project_Type_vNN
Example: 2026-11-01_ABC-Trading_Quotation_v02.xlsx
- Dates: YYYY-MM-DD
- Separate parts with _ and words with -
- No spaces or special characters
- Versions: v01, v02 … (no "final")
- Approved files: add _APPROVED
- Common codes: INV = invoice, PO = purchase order,
QT = quotation, MOM = minutes of meeting
Save this as a text file at the top of your shared drive so new team members see it.
Combine names with good folders
File names work best with a simple folder structure: by year, by client or by department, never more than 3–4 levels deep. Our guide on how to organize Google Drive shows a structure that works in OneDrive too.
Fix old files faster
- Don’t rename everything at once. Use the new rules for new files and rename old ones when you touch them.
- Bulk rename in Windows: select several files, press F2, type a name and press Enter. Windows adds (1), (2), (3)…
- Microsoft PowerToys has a free PowerRename tool for advanced find-and-replace in file names.
Quick summary
- Start with the date in YYYY-MM-DD format.
- Use the same order: date, client/project, type, version.
- No spaces or special characters, and no “final”.
- Write the rules down and share them with your team.