A naming convention is worth about ten minutes to write and saves an hour a month forever. The three rules that matter are dates first, no spaces, and no words that mean nothing in six months.
A file naming convention is an agreed pattern for naming documents so that they sort sensibly, can be found by search, and still make sense to somebody who was not there when they were created. It is the least glamorous piece of information management and among the highest-return, because every person who looks for a file benefits from it and nobody has to be trained.
The test of a convention is simple: can a colleague, a year from now, find the right file without asking you, and can they tell what it is without opening it? Most ad hoc names fail both.
The date format is the rule that pays for itself immediately. Writing 2026-09-03 rather than 3 Sept 26 makes files sort chronologically in every file list without anybody doing anything, which is the whole point — a convention that requires effort at read time has not saved anything. It is also the standard order in ISO 8601, so it is the one format nobody misreads.
Names cannot carry metadata that changes. Status, owner and approval state belong in the system rather than in the filename, because renaming forty files when a status changes is not going to happen. That is the boundary between naming and records management proper — the point at which you need fields rather than characters, discussed in records management and, for controlled documents, document control system.
Ettex Records holds the structured fields that a filename cannot — status, owner, review date — while the documents themselves sit in Ettex Docs with their versions tracked, covered in document version control.
Being direct: there is no bulk rename tool and no enforcement of naming rules. A convention is an agreement, and the only enforcement that works at small scale is that the person who breaks it cannot find their own file three months later.
Year-month-day, as in 2026-09-03. It sorts chronologically by default and is unambiguous internationally, unlike day-first or month-first orders.
No. Use hyphens or underscores — spaces break links, complicate scripts and become %20 in URLs.
Usually not. Apply the convention going forward; search handles the archive adequately and bulk renaming rarely repays the effort.
Anything that changes — status, owner, approval state — and meaningless words like final or latest. Changing metadata belongs in fields, not characters.
Supplier onboarding is boring paperwork that prevents specific, expensive problems — paying the wrong bank account, discovering an expired certificate mid-project, or having no contract when something goes wrong.
Most reference checks confirm employment dates and nothing else, because nobody asked a question worth answering. A handful of specific questions changes what a former manager is willing to tell you.
A disaster recovery plan is not a binder. It is a short document that says who decides, who calls whom, and in what order things come back — written while nobody is panicking.