The YYYY-MM-DD convention works cleanly for most documents — but some file types don't have a natural creation date, or the date is less meaningful than other identifiers. Here is how to handle the common edge cases without breaking your sort order:
Evergreen reference documents
Files like lease agreements or insurance policies that don't change frequently: prefix with CURRENT- (e.g., CURRENT-Lease-2BRFlat.pdf). When a new version arrives, rename the old file with its effective date and replace CURRENT with the new version. This keeps the active document instantly visible at the top of a sort without date-guessing which version matters.
Camera photos with auto-generated names
Modern cameras and phones embed the capture date in EXIF metadata. ExifTool (free, command-line, Mac/Windows/Linux) can batch-rename thousands of photos to YYYY-MM-DD format in a single command. For a GUI experience on Windows, Exif Pilot is free and does the same job visually. Batch renaming a 10,000-photo library typically takes under five minutes and requires no manual file-by-file work.
Files received from other people
Use the document's stated date, not the date you received it. A contract effective January 15 that arrives in your inbox on February 3 gets named 2025-01-15-Contract-ClientName.pdf. This groups it chronologically with related events — invoices, signatures, amendments — rather than with whatever else happened to land in your inbox that February week.
In-progress project files
For actively evolving files, use a project code and version number instead: PRJ-ClientABC-v04-Proposal.docx. Reserve the date prefix for the final delivered version when the project closes. Mixing date and version prefixes on files that are still changing creates confusing sort orders — versions sort out of sequence before the work stabilizes.