All standards
Standard
File Naming Standards
Consistent naming convention, discipline codes, folder structure, and version control for all project deliverables.
Last updated: May 2026
1. Naming Convention
All deliverable files follow a fixed, ordered structure separated by hyphens. Use no spaces or special characters other than the hyphen.
[ProjectNo]-[Discipline]-[Type]-[Zone/Level]-[Description]-[Rev]
2. Field Codes
| Field | Codes / format |
|---|---|
| Discipline | AR (Arch), ST (Struct), ME (Mech), EL (Elec), PL (Plumb), GN (General) |
| Type | RVT, RCP, E57, LAS, NWC, NWD, DWG, PDF, MP (Matterport) |
| Zone/Level | L01, L02, RF (roof), ST (site), ALL |
| Rev | R01, R02 … (two-digit, zero-padded) |
3. Examples
| File | Meaning |
|---|---|
| 24118-AR-RVT-ALL-ExistingConditions-R02.rvt | Project 24118, architectural Revit, all levels, rev 2 |
| 24118-GN-E57-L01-RegisteredCloud-R01.e57 | Registered point cloud, level 1, rev 1 |
| 24118-ME-NWC-L02-Ductwork-R01.nwc | Mechanical Navisworks cache, level 2, rev 1 |
4. Folder Structure & Version Control
- 01_Raw, 02_Registered, 03_BIM, 04_CAD, 05_Reports, 06_Delivery at the project root.
- Never overwrite a released revision; increment the Rev field and retain prior versions.
- Only the 06_Delivery folder is shared with the client; keep working files internal.
- Superseded files move to a _Superseded subfolder, never deleted during the project.
Ready to capture your site?
Tell us about your project and we'll assign a local scanner and scope your Scan to BIM deliverables.