How to Map Originator and Project Codes When You Start a New Project's EIR

If you've worked across more than two or three ISO 19650 projects, you already know the real friction isn't learning the naming rule once — it's re-learning it every single time you start with a new client.

Your own company might have a clean, consistent internal naming template. But the moment a new project's Exchange Information Requirements (EIR) lands on your desk, that template often needs to be partially or fully rebuilt — new project code, new originator code, sometimes an entirely different field order.

Every appointing party defines their own project-specific values for the naming fields in ISO 19650 — most commonly:

• Project code — usually 3–6 characters, unique to that specific project, assigned by the appointing party
• Originator code — usually 3–6 characters identifying your company specifically on that project (and this code can differ from project to project, even for the same company)
• Volume/System or Functional Breakdown — which field is used, and how strictly it's enforced, can vary depending on whether the project follows the 2018 or 2021 UK National Annex

None of this is standardized industry-wide. It's set per project, in the BEP, by whoever is appointing you.

A mismatch here doesn't usually mean a typo — it means a structurally wrong filename that still looks plausible at a glance. A drawing might pass your own internal QA, then get rejected the moment it hits the client's Common Data Environment (CDE), because the originator code doesn't match what's defined in their BEP.

This is especially common for smaller subcontractor teams without a dedicated document controller cross-checking every submission against the specific project's EIR.

1. Pull the BEP naming convention table before any drawings are started — not after the first rejection
2. Confirm your originator code specifically for this project — don't assume it's the same as your last project, even with the same client
3. Check which annex applies — 2018 (fixed character lengths) or 2021 (project-defined lengths set in the BEP) — since this changes whether your existing template will even fit
4. Update your internal naming template or macro for this project specifically, rather than reusing a previous one
5. Validate a sample filename against the BEP table before bulk-producing drawings — catching a mismatch on file one is far cheaper than catching it on file fifty

Even with a careful process, it's easy to miss a single inconsistent code across a large batch of files — especially under deadline pressure. A lightweight filename validator that checks structure, character counts, and field order against the ISO 19650 standard can catch this kind of mismatch before submission, without requiring a full enterprise CDE setup.

ISOCheck is a free, browser-based tool built for exactly this — paste your filenames in, and it flags structural issues before they become a rejected submission.