ISO 19650 filename validator, segment by segment.
Paste a single name or a whole register. See exactly which segment fails and why. Export a cleaned-up register.
Single · Register · Export
Paste one filename. For multiple files, switch to Bulk register.
The 9 segments of an ISO 19650 filename
ISO 19650-2 Annex A defines a structured filename for every deliverable. The goal is to encode enough metadata in the name itself that a file is identifiable even when decoupled from its folder or CDE — critical when documents are emailed, downloaded, or archived years after hand-over.
Project — Project
The project code agreed at kick-off. Short, stable, and the same across every deliverable for the life of the project.
Originator — Originator
The organisation producing the document. Often a three-letter acronym like the practice's initials. Must be agreed in the BEP.
Volume — Volume / System
Identifies a physical or logical section of the asset. For single-building projects this is often just 01 or ZZ.
Level — Level
Which floor or level of the asset the document describes. 00 = ground floor; ZZ = applies to all levels.
Type — Document Type
Document type per the BS EN ISO 19650-2 type list. Common values: DR (drawing), SH (schedule), SP (specification), M3 (3D model).
Role — Role / Discipline
One-letter role code. A=Architect, C=Civil, E=Electrical, L=Landscape, M=Mechanical, P=Public health, S=Structural, etc.
Number — Number
A sequential number within the type/role. Zero-padded. Doesn't have to be sequential globally; unique within the originator and type is enough.
Suitability — Suitability Status
Where the document is in its review lifecycle. S2 = suitable for information. A1/B1 = authorised for construction. Varies by BEP.
Revision — Revision
The revision identifier. Prefixed by P for preliminary pre-contract revisions and C for contractual post-issue revisions.
Note: different firms customise segment rules (longer originator codes, extra volume zones, etc). This validator enforces the canonical ISO 19650-2 definitions — it will flag as invalid names that use a firm-specific convention. For custom regex checks, try the regex playground, or use the full Foreman product where you can build custom rule sets.
Next step: in Foreman, run filename checks and metadata completeness checks together across Forma (ACC) folders, then alert teams before non-compliant files reach submission packs. Get started free.
Free tools
More tools you might like
Time-to-Value Calculator
Estimate yearly hours and cost saved by automating QA and admin checks.
Mini Project Matrix Wizard
Design a folder matrix for your project in under 60 seconds. Download a structure anyone can follow.
AEC Regex Playground
Test patterns against real filenames, or reverse-engineer a regex from examples.
Run this check across every file in your project
Foreman validates filenames and required metadata on upload, on a schedule, or on demand — across every folder in your Autodesk Construction Cloud hubs. AI-assisted regex, custom rule sets per folder.
14-day trial · Full access · No card on file· See the full feature →