Naming files so anyone can find them

TL;DR:

• Put the date first as YYYY-MM-DD so files sort in time order on any computer.

• Use a fixed pattern: date, subject, kind, version. Write the pattern down once.

• Count versions with v01, v02 and keep the latest obvious. Never name anything "final-final".

You open a folder and see "report.docx", "report (2).docx", "Report FINAL.docx" and "report final NEW.docx". Which one did your manager approve? Nobody knows, including the person who made them. A file name is the cheapest label you will ever write, and a few rules make it work for people who were not there when you saved it.

When a naming rule pays off

Any time a file will be found by someone else, or by you in six months. That includes shared folders, email attachments, files you upload to a form, and anything you download and keep. A name that makes sense only on the day you wrote it is a name that fails later.

Before you pick a pattern

1. Ask what people search for: the project, the person, the date, or the kind of document. Put the most-used one first.

2. Check what your computer does with characters. Avoid slashes, colons and other symbols that some systems do not allow, and avoid very long names that get cut off in lists.

3. Agree on one pattern with everyone who shares the folder. A convention used by one person is just a habit.

Why the date goes first and how to write it

Write dates as year, month, day, with leading zeros: 2026-11-09. Sorted by name, text compares character by character from the left, so 2026-11-09 comes before 2026-11-10, and January 2027 lands after December 2026. Other formats break this. "9 Nov 2026" sorts under N, and "11-09-2026" puts every November, from any year, together.

Pick one order and stay with it. This format also removes the confusion over whether 03-04 means the third of April or the fourth of March, since the year-first form is read the same way by everyone.

Step by step

1. Choose the parts: A good set is date, subject, kind of document, and version. Keep it to those four unless you truly need more.

2. Choose separators: Use underscores between parts and hyphens inside a part, for example 2026-11-09_pricing-update_memo_v02. Avoid spaces if files might go on the web, because they can turn into odd characters in a link.

3. Write the pattern in a README: Put one plain text file at the top of the folder that says the pattern and gives two examples.

4. Name new files as you save them: Renaming later is far more work. Make the first save the correct one.

5. Rename old files in batches: Do one folder at a time, newest first, and stop when the folder is no longer used.

Worked example: a naming convention with dates

A small bakery team keeps supplier paperwork in one folder. The pattern they agree on is: date of the document, supplier, document kind, version.

YYYY-MM-DD_supplier_kind_vNN

2026-10-28_millworks_invoice_v01.pdf
2026-11-02_millworks_quote_v01.pdf
2026-11-04_millworks_quote_v02.pdf
2026-11-04_dairyco_contract_v01.pdf

Sorted by name, the list falls in date order with no extra effort. Filtered by "millworks" in search, they see three files. And the second quote is clearly newer than the first: v02 replaced v01 after the supplier changed the numbers.

Versions without chaos

Check the example: v01 to v03 is three saved versions, and the signed copy is the fourth file but not a fourth draft, because signing ends the drafting. That is why "signed" replaces a number. You never need "final", because the signed file is the final one and says so.

Note: If your app already keeps a version history inside one file, you may not need v01, v02 in the name at all. Put versions in the name when you send copies out or save snapshots by hand.

Mistakes to avoid

• "final", "final2", "final-final", "latest". Each word is true for exactly one hour. Use numbers, or "signed" or "sent" for a real state.

• Putting the person's name where the subject belongs. People move on, topics stay.

• Using dd-mm-yyyy or month names at the front. They break the sort order.

• Changing the pattern every few months. A convention only helps when older files follow it too.

• Names so long that the part that matters is cut off. Keep it under about sixty characters.

Doing it faster

Most computers can rename many files at once. Select the files, then look for a rename option in the file manager and try it on a copy first, since you cannot always undo a batch rename. A spreadsheet can also build names for you: with the date in A2, supplier in B2, kind in C2 and version in D2, this formula joins them.

=TEXT(A2,"yyyy-mm-dd")&"_"&B2&"_"&C2&"_v"&TEXT(D2,"00")

If A2 holds 4 November 2026, B2 holds millworks, C2 holds quote and D2 holds 2, the result is 2026-11-04_millworks_quote_v02. If a rename gets confusing, DuckyHelper can look at your screen and talk it through while you work; it is one option, not a requirement.

Frequently asked questions

Should names be lowercase?

It is easier to be consistent with lowercase, and some systems treat capital letters as different from lowercase ones. Pick one and keep to it.

What about files that have no natural date?

Use the date you created or last changed it, and say which in your README. Templates and policies can drop the date and keep a version.

Do I rename everything I already have?

No. Apply the rule from today and rename only the folders people still open.