What Happens When Your CDE Naming Template Doesn't Match the Project's Standard

It's a reasonable assumption: if your company already has a Common Data Environment with naming automation built in, filename errors shouldn't happen. In practice, this assumption causes a specific, recurring problem — one that's easy to miss precisely because you trust the automation.

A CDE template enforces your naming structure consistently. What it doesn't automatically know is whether that structure matches this specific project's EIR.

Every appointing party can define their own values for project code, originator code, and in some cases entirely different field conventions in their BEP. If your CDE's naming ruleset was configured for a previous project — or configured generically — it can continue auto-generating filenames that are perfectly consistent internally, while being structurally wrong for the project you're actually submitting to.

This is part of why even teams with established digital information management processes still encounter naming-related rejections — the tooling solves consistency, not necessarily project-specific correctness.

• Multi-project teams — your CDE was set up around Project A's rules, and Project B has different field-length requirements
• Joint ventures or multi-party submissions — each party's CDE may follow their own internal standard, and these don't always reconcile cleanly into one shared naming convention before submission
• Mid-project rule changes — a BEP amendment changes a field requirement, but the CDE template isn't updated to match

Before assuming your CDE has this fully covered, it's worth asking:

1. When was the naming ruleset in our CDE last configured — was it built generically, or specifically for the current project's BEP?
2. Has anyone manually verified a sample output filename against the current project's BEP table recently?
3. If multiple parties are submitting to the same CDE, has each party's template been checked against the same shared standard?

Even with a properly configured CDE, an independent validation step — checking the actual output filename against the standard, separately from the system that generated it — adds a useful safety net, especially on larger or longer-running projects where rules can shift over time.

ISOCheck offers a free, independent way to do exactly this — paste in filenames your CDE has already generated and confirm they still match ISO 19650 structure before they go out the door.