Guide

I Need a Tool to Check ISO 19650 Naming — Here's What Actually Works

5 min read · ISOCheck

If you've typed "I need a tool to check ISO 19650 naming" into Google, you're not alone. Document Controllers and CAD Technicians ask this every day — usually after a batch of files just got rejected on Aconex, or after spending an hour manually checking filenames that should have taken five minutes.

Why ISO 19650 naming is so easy to get wrong

The UK National Annex defines a strict 7-field convention: Project — Originator — Volume/System — Level/Location — Type — Role — Number. Each field separated by a hyphen. All uppercase. No spaces. Number field zero-padded to 4 digits.

In practice, errors are everywhere. A lowercase letter slips in. A space gets added. The number field is 001 instead of 0001. On a project with hundreds of files these are invisible until the CDE rejects the upload.

What most people try first (and why it doesn't work)

Manual checking. Works for five files. Not for 500.

Excel formulas. Brittle, hard to maintain, require you to already know what you're checking for.

The BIM Parametrics Excel tool. A good effort, but requires manual setup per project, no bulk validation, no export.

Hoping the CDE catches it. Aconex gives cryptic error messages, rejects the entire batch, and doesn't tell you which field failed.

What a proper ISO 19650 naming tool needs

Must-have features

Validates all 7 fields against the ISO 19650 UK National Annex schema

Tells you exactly which field failed and why — not just 'invalid filename'

Handles bulk input — paste or upload hundreds of filenames at once

Exports results as a downloadable report

Works instantly in the browser — no install, no setup

Common ISO 19650 naming errors

Error	Example	Fix
Lowercase characters	prj123-acme-zz-01-dr-a-0001.pdf	All fields must be uppercase
Wrong delimiter	PRJ123_ACME_ZZ_01_DR_A_0001.pdf	Use hyphens, not underscores
Missing field	PRJ123-ACME-ZZ-01-DR-0001.pdf	All 7 fields are required
Short number field	PRJ123-ACME-ZZ-01-DR-A-001.pdf	Zero-pad to 4 digits minimum
Space in filename	PRJ123-ACME-ZZ-01-DR-A- 0001.pdf	No spaces anywhere

Frequently asked questions

Is ISO 19650 naming mandatory?

The standard doesn't require specific software, but most CDEs enforce naming compliance on upload. Validated filenames are essential on any project with automated workflows.

Can I use spaces in ISO 19650 filenames?

No. Spaces are strictly prohibited — they break automation and cause failures in CDE upload systems.

Where do Status and Revision go?

Status codes and revision identifiers are metadata attributes — they belong in the CDE's metadata fields, not in the filename string itself.

What's the correct field order?

Project — Originator — Volume/System — Level/Location — Type — Role — Number. Always in that order, always hyphen-delimited.

Validate your filenames before the deadline

Check up to 500 filenames at once — free, in your browser, your files never leave your device.

Try ISOCheck Free