The Most Common ISO 19650 Filename Mistakes That Cause Rejections

Most ISO 19650 filename rejections aren't caused by a fundamental misunderstanding of the standard — they're caused by small, easy-to-miss errors in an otherwise correct filename. Here's what tends to trip people up most, in order of how often they actually occur.

Mixing hyphens and underscores within the same filename, or using one separator type when the project's BEP specifies another. This is one of the most common — and most invisible — errors, since both characters look similar at a glance and the filename can still read as correct to the eye.

ISO 19650 filenames are typically expected in a consistent case (commonly uppercase for most fields). A single lowercase letter slipping into an otherwise correctly structured filename is a frequent, easy-to-miss cause of rejection — especially when filenames are typed manually rather than generated by a template.

Each field in the naming string has a defined position — project, originator, volume/system, level, type, role, number (with some variation depending on which annex applies). Transposing two fields, especially when working quickly across multiple disciplines, produces a filename that's structurally invalid even if every individual code used is correct.

Using a previous project's originator code on a new project, or a slightly wrong variant of your company's code, is common on multi-project teams.

Particularly relevant if you're unsure whether a project follows the 2018 (fixed-length) or 2021 (project-defined length) UK National Annex. A code that was the right length on your last project may be too long or too short for this one.

A structural drawing tagged with an architectural discipline code, or similar mismatches, are easy to make when producing files quickly across a multi-disciplinary submission batch.

Using a draft status code (e.g. S0/S1) on what should be a shared or published status, or vice versa — often a leftover from copying a previous file as a starting template without fully updating every field.

Most of these errors are genuinely hard to catch by eye, especially across a batch of dozens of files under deadline pressure. A filename validator that checks structure, separators, casing, and field order systematically can catch what manual review often misses.

ISOCheck is a free browser-based tool that checks filenames against ISO 19650 structure — built specifically to catch this category of small, easy-to-miss errors before they reach a client's CDE.