ISO 19650 2018 vs 2021 UK National Annex: What Actually Changed in File Naming

If your filenames have always passed validation before, and suddenly a new project is rejecting them, the cause is sometimes not a mistake at all — it's that the project is following the 2021 UK National Annex, not the 2018 version most teams originally learned the standard from.

The 2018 annex defined fixed character limits for each field in the naming string — a specific maximum length for project code, originator code, and so on, the same across every project.

The 2021 revision moves away from fixed limits. Field lengths become project-defined, set out in that specific project's BEP, rather than fixed by the standard itself.

2018 Annex: Field lengths are fixed and standardized. Some field names like Volume/System remain as originally defined. Templates are highly reusable across projects since limits don't change.

2021 Annex: Field lengths are project-defined in the BEP. Some field names are renamed — check your BEP for current terminology. Template reusability is lower since limits must be confirmed per project.

A naming template or macro built around the 2018 fixed lengths can silently produce technically non-compliant filenames on a 2021-annex project, simply because the expected character count is different. The filename might look fine, follow the right structure, and still fail validation because a field is one character over what this specific project's BEP allows.

This isn't always stated explicitly in casual project communication. The most reliable way to check:

1. Look at the project's BEP — it should state which annex version applies
2. Check whether field lengths are described as fixed values or as "as defined by the appointing party" — the latter is a strong signal you're on the 2021 annex
3. When in doubt, ask the document controller or BIM manager directly rather than assuming your last project's rules carry over

Ironically, teams who've used the same naming template successfully for years are often the most exposed here — the template has never failed before, so there's no instinct to double check it against a new project's specific character limits.

A filename validator that lets you check structure and length against the specific rules of the standard can flag this kind of mismatch immediately, rather than after a rejection notice comes back from the CDE.

ISOCheck is a free tool for exactly this kind of pre-submission check — it's worth running a sample filename through before bulk-producing drawings on any new project, especially if you're unsure which annex applies.