Home · Guides

ISO 19650 file naming: agreeing a convention on a project

Check an information container file name

A file naming convention only works if every organisation on the project uses the same one from the first upload. This guide covers the agreement: who sets the codes, what goes into the project information standard, and how to roll it out or change it without breaking the register. For what each of the seven fields means, the type and role codes and a working checker, use the information container file name checker and field guide.

Who sets the codes

The appointing party (the client) writes the project information standard and maintains it in agreement with the lead appointed parties. That standard says how information containers are identified. Delivery teams then work to it; they do not invent their own codes at upload.

In practice the information manager on the client side, or the lead appointed party acting for the client, drafts the code lists. Originator codes, though, belong to organisations. Collect them once, early, and publish them in one place. A code invented by each company as it joins tends to clash with one already in use.

Pick one National Annex edition

The UK National Annex to BS EN ISO 19650-2 was revised in February 2021. The revision kept the seven fields and the hyphen delimiter, but removed the recommended field lengths, renamed four fields, replaced the two-character type codes with single-character form codes, and revised the discipline and status codes. Some letters now mean something different. For example, X was “subcontractor” as a 2018 role and is “non-discipline specific or not applicable” as a 2021 discipline.

Either edition can be made to work. Mixing them on one register cannot. State the edition in the information standard, configure the CDE to match, and tell anyone arriving from a project that used the other one.

What to write down

UK BIM Framework guidance on the 2021 annex suggests the information standard states that container IDs conform to “BS EN ISO 19650-2:2018 & Revised NA”, then records the project particulars:

  1. The project code, which every organisation uses.
  2. An originator code for each known organisation, added to as new parties are appointed.
  3. The functional breakdown codes, or a note that XX is used until they are agreed.
  4. The spatial breakdown codes, or the same XX note.
  5. Any additions to the form and discipline codes, or a note that the annex codes apply unchanged.
  6. The length of the number field.

Add two things the list does not spell out but that save arguments later: the character set (letters and digits, upper case) and which file types the convention applies to. The 2021 annex makes clear its field codification is for files, not layers.

EXAMPLE: an information standard extract

EXAMPLE: an illustrative extract for a fictional warehouse scheme. The codes are invented for this page.

ItemAgreed value
ConventionBS EN ISO 19650-2:2018 & Revised NA (2021 annex)
Project codeWHS
OriginatorsACM structural engineer, BLD main contractor, FAB steelwork fabricator
Functional breakdownXX until the federation strategy is issued at stage 3
Spatial breakdownBuilding and level, for example A01; XX where not applicable
Form and disciplineAnnex codes, no additions
NumberFour digits, leading zeros

With that extract, a Level 01 general arrangement drawing by the structural engineer would be WHS-ACM-XX-A01-D-S-0001. A connection model by the fabricator carries FAB, not BLD, because the 2021 annex makes the originator the organisation of the information author.

Before the first upload

  1. Publish the information standard extract to every task team, not only the lead appointed parties.
  2. Set the CDE’s naming rules or templates to the agreed fields, so a bad name is rejected at upload rather than found at the next audit.
  3. Run a handful of real names from each team through the checker. Use the 2021 mode if your lengths differ from the 2018 recommendations, then check the codes against your own lists.
  4. Agree where status, revision and classification are recorded. They are CDE metadata, not part of the name. The CDE states guide covers the four states.
  5. Name one person who can issue a new originator or breakdown code, and say how quickly they will respond.

Changing the convention mid-project

Sometimes a convention has to change: a new appointing party, a move from the 2018 to the 2021 annex, or a breakdown that did not survive contact with the design. Treat it as a change to an appointment resource, agreed with the parties already appointed.

  • Apply it to new containers. Do not rename published containers to the new pattern. Their IDs are already referenced in registers, transmittals and models.
  • Keep a mapping. Where old and new codes overlap, publish a table from one to the other so searches still find both.
  • Watch reused letters. A discipline or type letter that means something different in the new list is the change most likely to cause a quiet error.
  • Record the date. Note in the information standard when the change took effect, so anyone reading the register later knows which convention a name follows.

The checker tests a pattern. It does not know your project’s code lists, and it is not a reason to rename a container that has already been shared.

Questions

Can we keep our own drawing numbering?

Inside the number field, often yes, as long as the length is fixed and it does not repeat information another field already carries. Your internal job number does not replace the project code.

Who issues a code for a new subcontractor?

Whoever the information standard names, usually the appointing party’s information manager or the lead appointed party for that delivery team. The code is added to the standard before the subcontractor’s first upload.

Should a live project move to the 2021 annex?

Only by agreement, and only for new containers. A mid-project switch changes code meanings, so it needs a mapping and a clear start date.

Can I rename a file after it is shared?

Avoid it. Other teams may already reference the ID, so a rename breaks links and history. Correct the convention for future containers instead.

Related: File name checker and field guide · What a CDE is · ISO 19650 in plain English · Information requirements · Glossary

See also: batch exporting SolidWorks drawings to PDF.

Sources

Last checked 4 November 2026. Official requirements stay in BS EN ISO 19650-2 and its UK National Annex, with UK BIM Framework Guidance 2 (the framework site now redirects to the IMI Framework). This is original guidance. Not a design sign-off.