Build a file naming convention your team will actually use.

What makes a file-naming convention people actually follow

A convention only works if it is easy to apply under deadline. The ones that stick share three traits:

• Short, consistent parts in your chosen order. Every filename uses the same building blocks in the same sequence, so the next person can read a name without guessing.
• Dates as YYYYMMDD. An eight-digit date (for example 20260612) sorts correctly in any file list and never gets confused between day-first and month-first formats.
• Microsoft 365 and SharePoint safe characters. Skip slashes, colons, and other reserved characters. Use letters, numbers, hyphens inside a part, and underscores between parts so the file syncs and opens cleanly.

The DNM naming grammar, with examples

DNM builds each name from four parts joined by underscores: Division_Date_Description_Type. In the General DNM standard, Description comes before Type; some standards put Type first. Here is the same grammar across three fields.

Why standardize at all

Consistent names make dates, document types and project references easier to identify without opening each file. DNM turns your saved rules into name suggestions for review. For a team, configure the policy on one PC and share its export for import on the others. Naming is not a substitute for document review, backups or an audit process.

Read the DNM Standard to see all four parts in detail, or start the 14-day free trial (no credit card) and apply your convention to real files today.