A file name is part of the record. If two people cannot find the same form in ten seconds, the naming system needs simplifying.
Choose four pieces
Use client or project, document type, date and version. Keep the order the same every time so files sort predictably.
Use a date format that sorts
Write dates as YYYY-MM-DD. A consistent date avoids the ambiguity of local formats and keeps versions in order.
Separate final from draft
Use a clear word such as final or draft, and archive old versions rather than adding another suffix to the same file.
Write the rule down
Put the naming pattern where the work happens. A rule that only one person knows is not a system.
Naming pattern
| Item | Example |
|---|---|
| Part | Example |
| Client/project | acme-onboarding |
| Type | intake-form |
| Date | 2026-10-21 |
| Version | v1 / final |
What to watch for
- Using spaces and inconsistent dates.
- Keeping every version in the same folder with no label.
- Naming files differently on each device.
A useful next step
Rename the next five files with the same pattern. If the rule feels too long, remove a part rather than abandoning it. If a file name is longer than the screen, shorten the project label before removing the date or version. The parts that sort and identify the record are more useful than a descriptive sentence. Keep the client or project identifier, document type, date and a consistently formatted version such as v01 or v02 in the same positions. Mark the approved version explicitly. To show the newest files first, sort by the relevant date in descending order and check the version label before opening a file.