Home · Calculators

Bulk ISO 19650 file name checker

Check a whole register at once. Your list stays in your browser.

Your project's allowed codes (optional)

Separate codes with commas or spaces. A blank box accepts any code that fits the pattern. Copying the link keeps these lists, so you can share them with your team.

What this checks

It checks structure, character rules, your project's code lists and duplicates within the list you paste. It cannot see your common data environment, so it cannot confirm that a name is unique there or that a container has been accepted.

Build a name

Using it on a project

  1. Enter the codes from your information standard in the allowed lists.
  2. Export file names from your CDE or a folder listing, and paste them in.
  3. Download the report and send each originator its own corrections.
  4. Copy the link to give your team the same code lists. The file names are not included in the link.

For how to agree the codes in the first place, read ISO 19650 file naming: agreeing a convention on a project.

Worked example

The default list holds three names, and the last two are the same. On the 2021 revision all three lines fit the pattern, but the repeat counts as a duplicate, so the tool reports two of three as matching and one duplicate. Download the CSV report to see each line with what needs checking.

What differs between the editions

Field2021 revision2018 edition
ProjectLetters or digits, length set by the project2 to 6 characters
OriginatorLetters or digits, one code per organisation3 to 6 characters
Third fieldFunctional breakdownVolume or system, 1 or 2 characters
Fourth fieldSpatial breakdownLevel or location, 2 characters
Fifth fieldForm, such as D, M or TType, a two-letter code such as DR, M3 or RP
Sixth fieldDiscipline, such as A, C, E, M or SRole, 1 or 2 letters
NumberDigits, fixed length set by the project4 to 6 digits

Because the 2021 revision leaves lengths to the project, the pattern check is looser. Fill in your project's allowed codes so the tool can catch a wrong code as well as a wrong shape.

Problems it often finds

  • Lower-case letters, or spaces where a hyphen belongs.
  • Six or eight fields because a hyphen was added to a description or left out.
  • An originator or discipline code that isn't on the project's list.
  • Numbers with different lengths in the same register, such as 001 and 0001.
  • The same name issued twice by two task teams.

Questions

Do I need to remove file extensions?

No. Each line loses its extension before it is checked, so a list straight from a folder works.

Is my list uploaded?

No. The check runs in your browser and the list is left out of any link you share.

Does a pass mean a name is valid on my project?

It means the name fits the pattern and any lists you entered. Whether the number is free and the container has been correctly issued can only be seen in your common data environment.

Sources

Last checked 9 November 2026. See the methodology and the disclaimer.