File-name checker
Paste a name without relying on the folder. The checker tests a common seven-field pattern used on UK information-management projects.
Method
Fields, in order: project, originator, volume/system, level/location, type, role, number. Hyphen-separated. Extension ignored.
Example that matches: PRJ-ABC-ZZ-01-DR-S-0001. Example that fails: Ground Floor Plan final v3.
ISO 19650 requires a naming convention to be agreed. It does not fix these field widths. Status codes and revision stay in metadata in this check. National annex tables are not reproduced here.
What the checker is judging
The checker splits a name on hyphens and tests the field count and the patterns this project convention uses. It is a naming screen. It is not a statement that ISO 19650 mandates those widths.
A container name is how a federation finds a file. The standard requires a defined convention. The field names and the codes inside the fields are project information, agreed in the information standard. A name can be unique and still fail this checker if the project uses a different pattern.
The 2021 UK national annex language is Project, Originator, Volume or system, Level or location, Type, Role, Number. Older pages said Volume, Level, Type, Role in a shorter form. If a name uses the annex fields and this checker rejects it, the checker is the narrower convention. Read the naming guide before you rename a published container.
Use it on a file that is about to be shared, not as a audit of a whole common data environment. State, revision and status sit outside this string on many projects. The checker does not read those.
- Related: file-naming guide
- CDE states
Last checked 3 October 2026. Worked figures are scenarios. See methodology and the disclaimer.