Information container file name checker (ISO 19650 / UK National Annex)
Paste a file name to test it against the seven-field information container ID used on UK projects. Each field is checked in turn, and the guide below explains what goes in it and what stays out.
What a pass means
On a UK project run to ISO 19650, every file shared in the common data environment (CDE) carries an information container ID: a unique name built from coded fields joined by a delimiter. BS EN ISO 19650-2 requires the delivery team to agree a convention; the UK National Annex to that standard sets out the recommended fields, their order and a starting set of codes. The 2021 revision of the annex also makes clear that this field codification applies to files. Layers follow BS EN ISO 13567-2 instead.
A “Pattern matches” result means the string fits the pattern you selected. It does not mean the project code exists, that the originator code is the one assigned to your organisation, that the number is unused in the CDE, or that the container is ready to share. Those checks sit with the project’s information standard and the CDE workflow.
The checker offers two modes. The 2018 mode uses the field lengths and two-character type codes that the 2018 National Annex recommended, which many live projects and CDE templates still use. The 2021 mode follows the revised annex, which removed the recommended lengths. It checks that there are seven fields and that each is a clean code, then leaves the lengths to the project.
The seven fields
The fields always appear in the same order. The names below are the familiar 2018 labels, with the 2021 label in brackets where it changed.
1. Project
One code for the whole project, used by every organisation on it. The appointing party sets it in the project information standard. A consultant’s internal job number does not belong here, even if it is the number on their timesheets. The 2018 annex recommended 2 to 6 characters. The 2021 annex removed that limit but still recommends keeping codes as short as possible.
2. Originator
The organisation that produced the information. The 2021 annex clarifies that this is the organisation of the information author named in the task information delivery plan (TIDP), not automatically the lead appointed party. So a drawing produced by a steelwork fabricator carries the fabricator’s code, even if the main contractor manages the delivery team. Each organisation should have one code, assigned once and listed in the information standard. The 2018 recommendation was 3 to 6 characters.
3. Volume or system (functional breakdown)
A subdivision of the project. Under the 2018 annex this was usually a zone, building or system, with ZZ for all volumes and XX for none, and a recommended length of 1 or 2 characters. The 2021 annex renamed it “functional breakdown”, because “volume” is not a term used in the ISO 19650 series. It can now group information by function, for example a design package. If the breakdown has not been worked out when the information standard is first written, UK BIM Framework guidance suggests stating that XX should be used.
4. Level or location (spatial breakdown)
Where the information applies. Under the 2018 annex this was a two-character level or location code such as 00 for ground level, 01 for the first floor, ZZ for multiple levels and XX for none. The 2021 annex renamed it “spatial breakdown” and removed the length limit. It can now describe more than floors, for example a building and level together, a section, a riser or a chainage. Again, XX can stand in until the spatial breakdown is agreed.
5. Type (form)
What kind of container it is. The 2018 annex used two-character type codes such as DR for a drawing and M3 for a 3D model. That list mixed content (a survey) with presentation (a drawing), so one file could fairly take two codes. The 2021 annex replaced it with “form”, meaning how the information is presented, using single-character standard codes such as M for model, D for drawing, T for text, I for image and L for list. Content is left to classification metadata. Where a container mixes forms, use the principal one: a report with photographs is still text, and a drawing taken from a model is still a drawing.
6. Role (discipline)
Under the 2018 annex this was the role of the author, such as architect or structural engineer, with codes that also covered contractual positions like client, contractor and subcontractor. That mix caused the same specialist to be coded differently on different jobs. The 2021 annex changed the field to discipline, the technical activity the information relates to. The organisation is already identified by the originator field. Codes are normally one letter, and a project can add two-character codes.
7. Number
A sequential number that makes the whole ID unique when the other six fields are the same, for example several sheets of one plan. Keep the length fixed across the project and pad with leading zeros so names sort correctly: 0012, not 12. The 2018 annex recommended 4 to 6 digits. Under the 2021 annex the project sets the length. Do not use the number to repeat information that another field already carries.
Delimiter and character rules
The UK National Annex uses the hyphen-minus (-, the ordinary key next to zero) as the delimiter between fields. UK BIM Framework guidance on the 2021 revision says the structure of the ID is now guided mainly by the delimiter rather than fixed lengths, so a clean delimiter matters more than ever. In practice:
- Use only the hyphen-minus between fields. An en dash (–) pasted from a word processor looks the same but is a different character, and the checker flags it.
- Do not use the hyphen inside a field. A code such as L-01 turns seven fields into eight.
- Do not use underscores, spaces or full stops as separators. A full stop before the file extension is fine; the checker strips extensions such as .pdf.
- Stick to letters A–Z and digits 0–9 in codes. This checker also expects upper case, which most project standards ask for. Check what yours says.
- Never leave a field empty. Use the agreed placeholder (often XX or ZZ) so every later field stays in its place.
EXAMPLE: one name, field by field
EXAMPLE: illustrative codes only, not taken from any real project.
PRJ-ABC-ZZ-01-DR-S-0001
| Field | Code | Meaning here |
|---|---|---|
| Project | PRJ | Project code issued in the information standard |
| Originator | ABC | The organisation that authored the drawing |
| Volume / system | ZZ | Applies to all volumes |
| Level / location | 01 | Level 01 |
| Type | DR | Drawing (2018 type code) |
| Role | S | Structural |
| Number | 0001 | First container in this series |
Run it through the checker above and every field matches in both modes. Under a project that has adopted the 2021 form codes, the same drawing might be PRJ-ABC-XX-01-D-S-0001. That fails the 2018 mode, because D is not a two-letter type, and passes the 2021 mode.
Now the invalid example: PRJ-ABC-ZZ-01-M3-ST-12-P01. It has eight fields because the revision P01 has been added to the name, and the number 12 is too short. The fix is PRJ-ABC-ZZ-01-M3-S-0012, with the revision recorded in the CDE. ST passes the two-letter rule, but check it against the codes your project actually lists.
Common type and role codes
These are a selection, not the full lists. Check the edition of the National Annex your project has adopted, and any extra codes in its information standard.
Type codes (2018 National Annex)
| Code | Type | Code | Type |
|---|---|---|---|
DR | Drawing rendition | RP | Report |
M2 | 2D model | SP | Specification |
M3 | 3D model | SH | Schedule |
CM | Combined (multi-discipline) model | CA | Calculations |
CR | Clash rendition | SU | Survey |
VS | Visualisation | MI | Minutes or action notes |
BQ | Bill of quantities | RI | Request for information |
Under the 2021 annex the type field becomes form, with single-character codes. The examples given in UK BIM Framework guidance are M model, D drawing, T text, I image and L list. The annex lists the full set.
Role and discipline codes
| Code | 2018 role | 2021 discipline |
|---|---|---|
A | Architect | Architecture |
B | Building surveyor | Building surveying |
C | Civil engineer | Civil engineering |
E | Electrical engineer | Electrical engineering |
M | Mechanical engineer | Mechanical engineering |
S | Structural engineer | Structural engineering |
G | Geographical and land surveyor | Ground engineering |
X | Subcontractor | Non-discipline specific or not applicable |
Some letters changed meaning between editions, as G and X show. A register that mixes 2018 and 2021 codes can no longer be read reliably, so record the edition in the information standard and stick to it.
The name versus status and revision
The ID says which container this is. It should stay the same from the first work-in-progress version to the archive. Three other attributes change as the container moves through the CDE, and the UK BIM Framework guidance says the CDE should let each container carry them as metadata alongside the ID:
- Status (often called suitability): what the information may be used for. Under the 2021 annex, Shared codes run from S1 to S5, with S4 for lead appointed party authorisation and S5 for appointing party acceptance. Published information takes A codes, whose meaning the project information standard defines. The 2018 codes S6, S7 and CR were removed, and the B codes are deprecated.
- Revision: which issue of the container this is. Projects commonly use a preliminary series for shared work and a contractual series once published, written as something like P01 and C01. Take the exact format from your information standard.
- Classification: the content, using Uniclass 2015. The 2021 annex points to the PM table where possible.
If you write the revision or status into the name, every new issue becomes a new container, links break and the register fills with near-duplicates. The four CDE states (work in progress, shared, published and archive) are explained in the CDE states guide. A container moves between them without being renamed.
How a project sets its own codes
The National Annex gives the structure and a starting set of codes. The project fills in the rest in its information standard, which the appointing party writes and maintains in agreement with the lead appointed parties. UK BIM Framework guidance suggests that, at the start, it states that IDs follow “BS EN ISO 19650-2:2018 & Revised NA” and then records:
- the project code, which everyone must use
- an originator code for each known organisation
- functional and spatial breakdown codes, or a note that XX is used until they are agreed
- any additions to the form and discipline codes, or a note that none apply
- the length of the number field
If your project uses different lengths or extra codes, the information standard takes precedence over this checker. Use the 2021 mode for structure, then check the codes against the project lists. For how to agree all of this before the first upload, and how to handle a change part-way through a project, see agreeing a file naming convention on a project.
Common mistakes
- Revision or status in the name, such as -P01, -S2 or “final”. Keep these in metadata.
- Mixed separators: hyphens on one file and underscores or spaces on the next, or an en dash pasted from a document.
- A dropped placeholder. PRJ-ABC-01-DR-S-0001 has six fields, so a system expecting seven reads the level as the volume.
- Numbers without leading zeros, which sort 10 before 2.
- House codes in shared fields: a consultant’s own job number in place of the project code, or the lead appointed party’s code on another organisation’s work.
- Invented codes that are not in the project’s list, or a 2018 type code on a project that adopted the 2021 forms.
- Folder as identity. Shared/Structural/GA final.pdf loses its meaning once someone downloads it. The ID has to make sense outside the folder.
- Renaming a published container to satisfy a checker. Fix the convention for future containers instead.
Questions
Is this file naming convention mandatory under ISO 19650?
ISO 19650-2 requires an agreed, documented convention for container IDs. The fields and codes on this page come from the UK National Annex, which is the recommended UK approach. Your appointment and the project information standard decide what applies on a given job.
Should the revision be in the file name?
No. Under the UK approach, status, revision and classification are metadata held by the CDE alongside the ID, so the name stays the same as the container is revised.
What is the difference between the 2018 and 2021 National Annex?
The 2021 revision removed the recommended field lengths, renamed volume/system, level/location, type and role to functional breakdown, spatial breakdown, form and discipline, replaced the two-character type codes with single-character form codes, and revised the discipline and status codes. The seven-field order and the hyphen delimiter stay the same.
What do ZZ and XX mean?
In the 2018 annex, ZZ means multiple or all and XX means none or not applicable, for the volume and level fields. UK BIM Framework guidance on the 2021 annex suggests XX where a functional or spatial breakdown has not yet been agreed. The project information standard should say which applies.
Does a pass mean the name will be accepted in our CDE?
No. It means the string fits the pattern selected. The CDE and the project team still check the codes, uniqueness and metadata before the container is shared.
Official sources
- BS EN ISO 19650-2:2018 & Revised NA (BSI Knowledge): the standard and the 2021 UK National Annex. Paid publication.
- UK BIM Framework, ISO 19650 Guidance 2, Edition 6 (February 2021), section 3, “About the 2021 National Annex”.
- IMI Framework: the UK BIM Framework web address now redirects here.
Sources
Last checked 4 November 2026. See methodology and the disclaimer.