BIM projects create many information containers: models, drawings, schedules, reports, issue files, exports, documents, registers, and handover packages. Naming, status, revision, and suitability rules help people understand what each item is and how it may be used.
A naming convention should make current information easier to find. Depending on the project, a name may include project, originator, volume, system, level, type, role, number, discipline, zone, or other fields. The exact fields matter less than consistency and clarity.
Revision tells people which version they are looking at. Status or suitability tells people what the information is suitable for. A file may be suitable for coordination, review, pricing, construction, record, archive, or another specific purpose. Without status, people may use draft information as if it were approved.
The CDE workflow should enforce or at least support these rules. Information should move through agreed states, and superseded information should remain traceable without being confused with the current version.
The BEP should explain naming rules, revision conventions, status or suitability codes, who can change them, and what they mean in plain language. It should also explain what happens when a file is named incorrectly or submitted with the wrong status.
Good naming is not bureaucracy for its own sake. It reduces rework, avoids wrong-file decisions, supports audits, and helps new team members understand the information environment quickly.
Related: ISO 19650 Explained in Plain Language, What Is a Common Data Environment?, Document Control Basics.