A filename should help you recognize a document outside the folder where it was created.
- Choose a short pattern, such as project-subject-date-version, and use it consistently within one project.
- When chronological order matters, write dates as year-month-day. Use a two-digit version number if you need several saved revisions.
- Include a meaningful subject word and remove vague extras such as new or final-final. Keep the filename reasonably short.
- Test the pattern on a few copies and sort them by name. Check that collaborators can identify the current version from the agreed convention.
Avoid characters that your storage system rejects, and do not rename files managed internally by an application. Keep required extensions unchanged and preserve agreed record identifiers.

The conversation
0Have something useful to add? Start the conversation.
Add your perspective.
Share an experience or a practical question. Comments appear after review.