Start with the question you ask when searching

If you usually search by project, put the project name near the beginning. If you compare recurring reports, a date may matter more. A filename such as “zeorgo-content-review-2026-11-17.md” gives more useful context than “notes-new-final.md.”

Avoid adding every possible attribute to the name. Folder names already provide context, and excessive repetition makes scanning harder. Pick a convention that you can use when tired and in a hurry.

Make dates and status unambiguous

A year-month-day format sorts naturally when used consistently. Distinguish the date of an event from the date a file was exported. If both matter, explain that distinction inside the document instead of expecting the filename to carry the entire history.

Use status words only when they have a defined meaning, such as draft or approved. Repeated labels like final-final do not provide a trustworthy version history. For collaborative work, decide who can mark a document approved and where that decision is recorded.

Test the convention before renaming everything

Apply the system to one active project first. After a week, try to locate a document without using recent-files history. Ask another person to identify its purpose from the name alone. Revise the convention if it requires explanation every time.

Bulk renaming can break references, shortcuts, and shared links. Keep a backup and a mapping of old names to new names before a larger change. Consistency is useful, but preserving access to existing work is more important than making every historical filename match.

Further reading

Original sources and related references. These links lead to independent websites; inclusion does not imply a partnership or endorsement.

Browse the complete resource shelf →