Name files for the moment you need them later
A file name often makes perfect sense when you create it. “Notes” or “Final draft” feels specific because the project is fresh in your mind. Months later, surrounded by other notes and final drafts, that context is gone. A useful naming convention puts enough context in the name that you can recognize the document in search results or a folder list without opening it.
Start with a flexible pattern: date-topic-document type-version. For example, “2025-04-18_team-workshop_agenda_v01” tells you when the document belongs, what it concerns, what it is, and which working copy you are seeing. You do not need every part for every file. The goal is a predictable order, not a rule that makes saving a quick note feel like paperwork.
Choose details that distinguish one document from another
Use a date when timing matters, such as for meeting notes, reports, invoices, or recurring plans. Write it as year-month-day so dated files sort in chronological order when listed by name. Decide what the date means for each document type: for meeting notes, it might be the meeting date; for a monthly plan, the month it covers. If the date adds nothing useful, leave it out rather than inserting one by habit.
Make the topic specific enough to separate similar projects. “Website” may be too broad if you work on several parts of a website; “website-navigation” gives you a better clue. A short document type, such as agenda, notes, brief, draft, or checklist, answers a different question: what can you expect to find inside? Together, topic and type are often more useful than either one alone.
Keep names readable. Consistent separators, such as hyphens between words and underscores between major parts, make a pattern easier to scan: “2025-04-18_website-navigation_meeting-notes”. Avoid stuffing in every possible keyword. A file name is a signpost, not a summary of the entire document.
Handle versions without creating a trail of “final” files
Add a version marker when several copies genuinely need to coexist, especially during review. “v01”, “v02”, and “v03” sort neatly and show a clear sequence. You can add a status where it helps someone choose the right copy, such as “v03_for-review” or “v04_approved”. Agree on what “approved” means within a shared project before using it as a label.
Not every edit needs a new file. If your document tool keeps an accessible revision history, one working document may be simpler than a series of copies. Reserve separate versions for meaningful handoffs or milestones. Once a document is approved, consider moving older working copies into an archive folder so a search is less likely to surface an outdated draft first.
Make the pattern fit the people and tools you use
For a personal folder, you can use words you naturally remember. In a shared folder, favor terms a teammate would search for rather than private shorthand. If a project has an agreed name, use it consistently. A small reference note with two or three examples can help collaborators follow the same pattern without memorizing a long set of rules.
Check how names behave in the places you store and share files. Simple letters, numbers, hyphens, and underscores tend to travel more comfortably between tools than unusual punctuation. Keep sensitive details out of file names when they could appear in shared links, notifications, or search results. The document can hold details that the file name does not need to reveal.
Test the convention before renaming everything
Try the pattern on one active project or one document type for a couple of weeks. When you need a file, search for the words you would ordinarily use. If the right document is hard to spot, notice what is missing: perhaps the project name is inconsistent, the document type is too vague, or several copies have no version marker. Adjust the pattern based on that friction.
There is no need to rename an entire archive at once. Start with files you still use, and rename older ones when you encounter them. A sustainable convention should make saving a document nearly automatic and finding it noticeably less puzzling. If it demands too many decisions each time, simplify it until you can use it without stopping your work.
