How is the file naming standard determined?

Why is a file naming standard necessary?

Files named "Document1.docx", "new quote.xlsx" or "scan_0034.pdf" cannot be understood without opening. When hundreds of such files accumulate in a folder, finding the desired document requires opening files one by one.

A standard name serves three purposes: it describes the content without opening the file, makes alphabetical ordering meaningful, and enhances search by name. Moreover, when everyone follows the same rule, finding a file saved by someone else becomes as easy as finding your own.

What components make up a good file name?

For most organisations, these three or four parts are sufficient. What matters is not which parts you choose, but that the order remains the same for every file:

• "Date: in YYYY-MM-DD format (2026-09-24). This format automatically provides chronological order in alphabetical sorting.
• "Party or project: customer, supplier, or project name; space-free and abbreviated (e.g., AcmeLogistics, WarehouseProject).
• "Document type: From a fixed list such as Contract, Quote, Invoice, Minute.
• "Brief explanation if needed: e.g., “Appendix1”, “Signed”, only when differentiation is required.

Which characters should be avoided in file names?

Forward slash (/) is used as a folder separator in many systems, so it is not used in file names. Backslash, colon, asterisk, and question mark also cause issues on different operating systems. Using underscore or hyphen instead of space prevents the name from breaking in emails and links.

Turkish characters do not cause issues in modern systems; however, if files are frequently sent to external organisations, it is a safe preference to write letters such as ğ, ş, ı as g, s, i, anticipating that the recipient may be using an older system.

Also limit the length of the file name: very long names are truncated and unreadable in lists. As a rule, the first thirty characters of the name should be sufficient to identify the file.

Should version information be written to the filename?

In a system with version control, no. Attachments like 'v2', 'latest', or 'final' create copies of the same document and make it unclear which one is valid. The current version should always be saved under the same name, while older versions should be kept in the system's version history. For details: file version control guide you can check.

How is it rolled out in a standard organisation?

1. Write the Rule on a single page and place it somewhere visible to everyone, along with three examples.
2. "Fix the document type list. Keeping types to no more than fifteen ensures consistent names.
3. "Start with new files. Instead of bulk-renaming old files, correct them as they are used.
4. "Assign audit tasks to area owners. Once a month, they should correct files that do not comply with the rules.

What are example file names by department?

• "Finance: 2026-09-30_SupplierA_Invoice_F2026-1182
• "Human Resources: 2026-09-01_PersonnelName_EmploymentContract
• "Sales: 2026-09-24_CustomerB_Quote
• "Project: 2026-09-15_WarehouseProject_Minutes_Weekly
• "Law: 2026-08-12_SupplierC_Contract_Signed

What are common mistakes in file naming?

The first mistake is using personal abbreviations. A name like “MB_tklf_rev” is meaningful only to the person who wrote it, not to others. Standards aim for names to be read identically by everyone; therefore, abbreviations must also be defined in the rule.

The second error is writing dates in different formats. When “24.09.2026”, “24-09-26” and “September 2026” are together in the same folder, sorting loses its meaning. A single format must be selected and applied without exception.

The third mistake is repeating information already present in the folder name in the file name. Having a file named “Finans_2026_Fatura” inside the “Finans/2026/Faturalar” folder lengthens the name but adds nothing. The folder structure and file name should complement each other, not repeat.

How does it work with standard search and AI?

Searching by name becomes most powerful with standard naming: typing “SupplierA” brings all contracts, quotes and invoices belonging to that supplier in a single list. For questions about document content, names alone are insufficient; for such queries, AI summary and document questioning are used. A good name speeds up finding the correct document; AI speeds up extracting the correct information from it.

Short template for naming standard

You can edit the following template according to your organisation and publish it as a one-page policy. What matters is not the number of important items, but that everyone follows the same rule.

• "Sequence: Date_Party_DocumentType_Description (description optional).
• "Date: YYYY-MM-DD; the date the document was edited or signed.
• "Party: customer, supplier or project; no spaces, capitalise the first letter of each word.
• "Document type: One of Contract, Quote, Invoice, Minutes, Report, or Correspondence list.
• "Separator: underscore between parts; no spaces between words.
• "Forbidden: slashes, version suffixes (v2, last, final), personal abbreviations.
• "Length: The first thirty characters should suffice to introduce the file.

Should old files be renamed according to the new rule?

Renaming thousands of old files in bulk takes time and can break links and habits associated with those files. A more efficient approach is to apply the rule to new files and correct old files as they are used. Frequently opened documents will automatically comply with the new rule within a few months; names of files never opened do not slow anyone down anyway.

The only exception is documents shared frequently with external organisations. The name of a document going to a customer or supplier should make it easy for the other party to find it too. Naming such documents according to the rule before sending clarifies that both parties are referring to the same document.

How does SmartFiles solve this?

SmartFiles does not accept slashes and invisible control characters in file names; the name can be up to 255 characters long. Two files with the same name cannot exist in the same folder: if a file with the same name exists in the destination during renaming or moving, the operation is not performed and a warning is shown.

If the file is uploaded with the same name to the same folder, it becomes a new version. This eliminates the need to add version suffixes to names. The search box in the top bar instantly returns results in the current area based on any part of the name; versions and notes of renamed files remain intact.

Renaming is done via the Rename button in the details panel and is open only to persons with Editing permission; thus preventing anyone from changing names according to rules. Every rename appears in the area's activity history with person and time. Since files can also be marked with area-specific tags, status information does not need to be written in the name.

SmartFiles featuresRename file or folderFile with the same name already exists warning

Frequently asked questions

In what format should the date be written in the filename?

YYYY-MM-DD format (2026-09-24) is recommended. This format automatically provides chronological order in alphabetical sorting and avoids confusion with date formats from different countries.

Can Turkish characters be used in file names?

SmartFiles handles Turkish characters seamlessly. If files are frequently sent to external organisations, it may be safer to simplify Turkish characters according to the recipient's system.

Should the version number be written in the file name?

Should not be written in a system with version control. In SmartFiles, a file uploaded with the same name becomes a new version; previous versions remain in the version history.

Does renaming a file lose its history?

No. In SmartFiles, the renamed file retains its versions and notes as they were.

Can two different files with the same name be kept in the same folder?

Cannot be retained in SmartFiles. A file uploaded with the same name becomes the new version of the existing document; if a file with the same name exists at the destination during renaming or moving, the operation is not performed and a warning is shown. This prevents two documents from being mixed, as is natural with standards.