ISO 19650 File Naming Convention Generator
Build file names to the UK National Annex to BS EN ISO 19650-2, number a whole series at once, and check names your team has already issued. Setting up a new project? We can set up your Revit template with the same naming.
UK National Annex fieldsType and role code listsNumbered series and CSVChecks pasted file namesRuns in your browser
Build a file name
UK National Annex to BS EN ISO 19650-2: Project-Originator-Volume-Level-Type-Role-Number
2–6 characters, set by the client.
3–6 characters for your organisation.
2 characters. Pick ZZ or XX, or type a project code such as V1 or SW.
2 characters: 00 ground, 01 first floor, B1 basement, M1 mezzanine, ZZ multiple, XX none.
2 characters from the UK NA list, e.g. DR drawing, M3 3D model.
1 letter from the UK NA list; a second character is allowed for sub-disciplines.
Padded with leading zeros.
Project-specific codes: your project's information protocol (or BIM execution plan) may add codes or change field lengths. Codes outside the UK NA lists show as warnings, not errors.
Suitability and revision (optional)
P01 preliminary, P01.01 work in progress, C01 contractual.
File name
Fill in the fields to build a name.
Numbered series
Up to 200.
Check existing file names
Extensions such as .rvt, .pdf or .ifc are ignored. A status/revision suffix (e.g. -S2-P01) is read as metadata. Nothing leaves your browser.
Need a Revit template set up with ISO 19650 naming? We configure sheets, views and exports to your information protocol.
Request a projectName and check files in three steps
Enter your project codes
Type the project and originator codes once; the tool remembers them on this device.
Pick volume, level, type and role
Choose from the UK NA code lists or type your project’s own codes, then copy the name or make a numbered series and download it as CSV.
Check existing names
Paste file names, one per line, and see a pass, warning or fail for every field with a specific fix.
The 7 fields of an ISO 19650 file name
| Field | Example | UK NA recommendation |
|---|---|---|
| Project | PRJ01 | 2–6 characters, one code for the whole project |
| Originator | MHL | 3–6 characters, one per organisation |
| Volume / system | ZZ | 2 characters; ZZ all, XX none, or a project code |
| Level / location | 01 | 2 characters; 00 ground, 01 first, B1 basement, M1 mezzanine, ZZ multiple, XX none |
| Type | M3 | 2 characters from the UK NA list |
| Role | A | 1 character from the UK NA list (2 allowed for sub-disciplines) |
| Number | 0001 | 4–6 digits with leading zeros |
Fields are separated by a hyphen and contain only letters A–Z and digits. Status (suitability) and revision are metadata held by the common data environment, not part of the name.
The February 2021 corrigendum to the UK National Annex renamed the fields (functional breakdown, spatial breakdown, form, discipline), dropped the fixed field lengths and revised the code lists. Many projects still use the lists above; your project’s information protocol decides, so check it first.
ISO 19650 role codes and type codes
| Role | Description |
|---|---|
| A | Architect |
| B | Building surveyor |
| C | Civil engineer |
| D | Drainage, highways engineer |
| E | Electrical engineer |
| F | Facilities manager |
| G | Geographical and land surveyor |
| H | Heating and ventilation designer |
| I | Interior designer |
| K | Client |
| L | Landscape architect |
| M | Mechanical engineer |
| P | Public health engineer |
| Q | Quantity surveyor |
| S | Structural engineer |
| T | Town and country planner |
| W | Contractor |
| X | Subcontractor |
| Y | Specialist designer |
| Z | General (non-disciplinary) |
| Type | Description | Type | Description |
|---|---|---|---|
| AF | Animation file of a model | MI | Minutes/action notes |
| BQ | Bill of quantities | MR | Model rendition (e.g. analysis) |
| CA | Calculations | MS | Method statement |
| CM | Combined model | PP | Presentation |
| CO | Correspondence | PR | Programme |
| CP | Cost plan | RD | Room data sheet |
| CR | Clash rendition | RI | Request for information |
| DB | Database | RP | Report |
| DR | Drawing rendition | SA | Schedule of accommodation |
| FN | File note | SH | Schedule |
| HS | Health and safety | SN | Snagging list |
| IE | Information exchange file | SP | Specification |
| M2 | 2D model | SU | Survey |
| M3 | 3D model | VS | Visualisation |
Codes as listed for the UK National Annex to BS EN ISO 19650-2. Your project’s information protocol can add codes; the tool shows those as warnings, not errors.
ISO 19650 file naming questions
In the UK, file names (information container IDs) follow the National Annex to BS EN ISO 19650-2: Project-Originator-Volume/System-Level/Location-Type-Role-Number, for example PRJ01-MHL-ZZ-01-M3-A-0001. Each field uses letters and digits only, fields are separated by hyphens, and every name on the project must be unique. ISO 19650 itself only requires a unique ID from an agreed convention; the National Annex sets the UK fields and codes.
Yes. BS 1192:2007+A2:2016 and PAS 1192-2:2013 were withdrawn and superseded by BS EN ISO 19650-1 and -2, published at the turn of 2018–2019 (the UK editions with the National Annex appeared in January 2019). The BS 1192 naming fields carried over into the UK National Annex almost unchanged, so a BS 1192 name such as PRJ-ORG-ZZ-01-DR-A-0001 still has the same structure. What changed is the status and revision metadata, which ISO 19650 keeps separate from the file name.
The UK National Annex lists single-letter role codes: A architect, B building surveyor, C civil engineer, D drainage and highways engineer, E electrical engineer, F facilities manager, G geographical and land surveyor, H heating and ventilation designer, I interior designer, K client, L landscape architect, M mechanical engineer, P public health engineer, Q quantity surveyor, S structural engineer, T town and country planner, W contractor, X subcontractor, Y specialist designer and Z general. A second character can be added for sub-disciplines if the project defines it.
Under the 2021 UK National Annex, S0 is work in progress, S1 suitable for coordination, S2 suitable for information, S3 suitable for review and comment, S4 suitable for review and authorization and S5 suitable for review and acceptance. A1, A2 … An mean authorized and accepted (published) for stage n. Older projects on the 2018 annex also use S6 and S7 (PIM and AIM authorization), B codes for partial sign-off and CR for as-constructed records.
No. Status and revision are metadata held by the common data environment alongside the file. Revisions are P01, P02 for preliminary issues, P01.01 for work-in-progress versions and C01 for contractual issues. Add them to the name as a suffix, such as -S2-P01, only when a file leaves the CDE and its metadata would otherwise be lost.
The February 2021 corrigendum renamed volume/system to functional breakdown, level/location to spatial breakdown, type to form and role to discipline. It also removed the recommended field lengths, revised the code lists and replaced the S4/S6/S7 statuses with S4 (authorization) and S5 (acceptance). Because each project now sets its codes in its information protocol, this tool treats unknown codes and unusual lengths as warnings rather than errors.
Keep working with Mahelak tools
Need a custom tool, Dynamo script or Revit family?
Tell us about your project and we will send you a quote before any work starts.