An ISO 19650 naming convention gives every file on a project a name that says what it is, who made it and where it belongs - so anyone can find it in the common data environment (CDE) without opening it. Here is the convention most UK and international projects use, field by field, with examples you can copy.
The fields, in order
The UK National Annex to ISO 19650-2 sets out seven fields, separated by hyphens:
| Field | What it says | Example |
|---|---|---|
| Project | The project's code, set by the appointing party | HLX |
| Originator | The organisation that produced the file | ABC |
| Volume or system | Which building, zone or system it covers | ZZ (all) or B1 |
| Level or location | Which floor or location | 02, or XX (none) |
| Type | What kind of information it is | M3 (3D model), DR (drawing) |
| Role | The discipline that produced it | A (architect), S (structural) |
| Number | A unique number within the rest of the name | 0001 |
So HLX-ABC-ZZ-02-M3-A-0001 is the architect ABC's 3D model of level 02, for all zones of project HLX. The status and revision are kept as separate information on the CDE, not in the file name, so the name never changes as the file moves from work in progress to shared to published.
Common type codes
- M2 / M3 - 2D and 3D models
- DR - drawings
- SP - specifications
- RP - reports
- SH - schedules
- MI - minutes and action notes
Common role codes
- A - architect
- S - structural engineer
- M - mechanical engineer
- E - electrical engineer
- C - civil engineer
- W - contractor
- K - client
Check your project's information standard before you start: the appointing party sets the codes, and many add their own for local needs.
Status and revision codes travel with the file, not in its name
Alongside the name, each file carries a status (what it can be used for, such as S1 "suitable for coordination") and a revision (P01, P02 while preliminary; C01 once contractual). See ISO 19650 status codes for the full list.
Four mistakes that break a naming convention
- Putting the status or revision in the file name. The name then changes every time the file moves, and links break.
- Inventing codes on the fly. If a code isn't in the project information standard, nobody else can search for it.
- Different conventions for models and drawings. One convention for every container keeps the CDE searchable.
- Checking names by eye. Let the CDE or your checks validate every name on upload, so a wrong name never gets shared.
Make the convention part of the plan
In Plannerly, each deliverable in your MIDP becomes a named file request on its task, following your naming convention - so task teams see the right name before they create the file, and nothing is renamed later. Connect Autodesk Construction Cloud or BIM 360, and a file shared there with a matching name fills its request by itself (how CDE Connect works).
