Naming Conventions Need Automation, Not Enforcement

Naming Conventions Are Architecture, Not Aesthetics

Naming conventions function as organizational architecture because they define the interface through which knowledge moves: between project phases, between team members, and between the people who built the files and the AI systems that need to read them.

As The Dynamic Power Disciple observes²: "Naming is a shared language. It acts as an interface. Just like schema definitions." This framing matters because it changes the question from "how do we get people to follow the naming guide?" to "how do we build a naming system that knowledge can actually flow through?"

In AEC projects, the stakes are particularly high. According to Build Syntec Group³, only about 20% of total project effort is spent on physical construction— the remaining 80% is dedicated to organizing information, coordinating teams, and managing workflows. That's not a surprising statistic once you've been on a complex project. It's mostly information work— which means naming architecture isn't an administrative nice-to-have. It's load-bearing.

And yet Onsite confirms⁴ that information management is "one of the most neglected subjects discussed at the beginning of a new construction project."

What ISO 19650 actually requires

ISO 19650 provides the international framework for structured information exchange throughout the project lifecycle⁵. The standard defines a 10-component naming structure: Project, Originator, Volume/System, Location, Type, Discipline, Classification, Number, Suitability, and Revision.

In practice, a compliant BIM filename looks like this:

NEWP-ABC-XX-ZZ-SP-S-0001

That structure can be parsed by humans and machines alike. Floor3_East_FINAL_v2_JCrev.rvt cannot.

When names are consistent and structured, your files become a source of truth— the organizational record of what was decided, when, by whom, and at what stage. When they're not, that knowledge lives in someone's memory. And memories leave when people leave.

Why Manual Enforcement Always Fails

Manual enforcement fails because naming convention compliance depends on human discipline, memory, and consistency— and none of those scale under delivery pressure, across staff turnover, or when schemas grow complex enough to require a reference guide just to remember them.

This isn't a critique of AEC professionals. It's a structural diagnosis. The ServiceNow community deals with naming governance at enterprise scale. They frame it plainly⁶: "Naming conventions rely on goodwill, memory, and consistency— none of which scale particularly well."

Three failure modes, in order of frequency:

1. Delivery pressure collapses discipline. When a project is behind schedule, file names get shortened, skipped, or improvised. The convention was written during project setup— before the 11pm deadline when someone just needs to get the drawing out. As the ServiceNow community notes⁷: "If a convention can't hold up during a tight sprint or a production issue, it was never sustainable in the first place."

2. Staff turnover resets the system. Every new hire, new subcontractor, and new PM brings their own naming habits. Renamer.ai captures it simply⁸: "The moment you're busy, you forget. The moment a colleague joins, they do it differently." In AEC, where subcontractors rotate in and out across a project lifecycle, this is constant.

3. Stricter schemas produce more avoidance. Organizations respond to naming chaos by adding stricter rules, longer prefixes, more required fields. But complexity is the enemy of adoption. More rules = more opportunities to get it wrong = more people giving up entirely.

The same pattern appears across every industry that has tried to solve this with documentation. Marketing analytics firms (Claravine), IT governance teams (ServiceNow), and AEC project managers all arrive at the same failure¹. The convention gets written. The enforcement doesn't hold.

And the cost is real. McKinsey found in 2012⁹ that employees spend an average of 1.8 hours every day searching and gathering information. That number is now 14 years old— but nobody who has worked on a project with poor file naming would call it wrong.

An AI governance strategy for your firm has to start here. Governance frameworks built on top of inconsistent file naming are just expensive policy documents with the same enforcement problem.

What Naming Convention Automation Looks Like in Practice

Naming convention automation embeds compliance into the creation workflow itself— so the correct name is either the only option available (for plugin-enforced tools) or applied automatically before files enter the project workflow, not as an additional step to remember after the file is created.

This approach differs in kind, not just degree. Instead of writing a policy and hoping people follow it, you build naming rules into the tools people use. Compliance becomes the path of least resistance. Non-compliance requires extra effort.

Peer-reviewed BIM research from Leeds Beckett University confirms¹⁰ that the Auto-BIMName plugin— developed specifically for ISO 19650 compliance— "eases the process of file naming, facilitates collaboration efficiency, naming consistency across project teams and lifecycle stages, and provides time-saving benefits." That's not vendor marketing. That's a controlled test in academic research.

AEC automation tools, compared:

Dynamo, built into Revit, enables automation of batch renaming and naming convention rules without traditional scripting expertise— though there is a visual programming learning curve¹¹. It's the most accessible starting point for firms already inside the Autodesk ecosystem. Autodesk Forma (formerly Autodesk Construction Cloud, renamed March 2026) integrates with Workato to enable batch file renaming and organization using custom metadata attributes¹²— a more powerful option for larger firms managing complex folder structures.

The same principle holds across industries. Claravine's controlled vocabulary model— used in marketing analytics— prevents naming variations like Social_Paid vs. Paid_Social vs. paid-social from ever entering the dataset¹. You don't remediate the data downstream. You prevent the problem at creation.

An AI workflow automation guide covers this pattern in more detail across professional services contexts. The mechanism is the same: build compliance into the workflow, not onto it.

There's a setup cost. Automation requires upfront configuration, platform buy-in, and someone to maintain the rules as projects evolve. But the return is compound. Every project after setup runs on consistent naming with substantially lower enforcement overhead— though schema maintenance as project types evolve is part of the ongoing cost.

And building an AI culture in your firm gets significantly easier when the infrastructure it depends on is already automated rather than hoped-for.

Why This Is the Real AI Readiness Problem

Consider what an AI system sees when it reads your project files. NEWP-ABC-XX-ZZ-SP-S-0001 can be parsed, categorized, and searched. It knows the project, the originator, the discipline, the document type, the revision. Floor3_East_FINAL_v2_JCrev.rvt knows nothing— the AI can't classify it, retrieve it intelligently, or learn from it.

For firms with consistent naming, that means AI can search, classify, and surface project knowledge across every completed job. For most AEC firms right now, inconsistent naming blocks all of it.

Box's 2025 State of AI research¹³ found that high-ROI organizations are significantly more likely to use advanced AI capabilities like metadata extraction and process automation. Naming conventions are the metadata layer that makes those capabilities possible. You can't extract metadata from filenames that carry no structured information.

Build Syntec Group positions standardized naming directly as "the prerequisite for automation and AI-assisted processes throughout a building project's lifecycle"³. That's not a future concern. It's a current one.

Every inconsistently-named file is a file your future AI system can't read, search, or learn from. You're making that decision today— with every project, whether you mean to or not. The hidden costs of AI projects almost always trace back to data infrastructure that was never structured for machine use.

This isn't a filing discipline problem. It's an AI infrastructure problem. And you're building it right now.

FAQ

Why do we need naming conventions in AEC?

Naming conventions are the infrastructure that makes project information findable, transferable between staff, and readable by AI systems. Without them, institutional knowledge exists only in the heads of the people who created the files— and it leaves with them. According to Onsite⁴, information management is consistently the most neglected aspect of AEC project starts, which explains why firms regularly find themselves unable to retrieve or reuse work from completed projects.

Why can't we just enforce naming conventions with a policy?

Policies depend on human compliance, which collapses under delivery pressure and staff turnover. The ServiceNow community⁶ notes that naming conventions rely on "goodwill, memory, and consistency"— and none of those hold at scale. Enforcement only works sustainably when it's built into the creation workflow, not written into a document that nobody opens mid-project.

What is ISO 19650 naming convention?

ISO 19650 defines a 10-component naming structure for BIM files in AEC projects, covering Project, Originator, Volume/System, Location, Document Type, Discipline, Classification, Number, Suitability, and Revision⁵. A compliant filename looks like NEWP-ABC-XX-ZZ-SP-S-0001. The AEC Associates confirm that ISO 19650 "provides the structure for effectively sharing data between all parties throughout the lifecycle of the project."

How do you automate naming conventions in Revit?

Dynamo, built into Revit, enables automation of batch element renaming and naming rules without traditional scripting expertise— though there is a visual programming learning curve¹¹. The Auto-BIMName plugin was specifically developed to apply ISO 19650-compliant names at file creation, and peer-reviewed research from Leeds Beckett University confirmed it reduces manual effort while improving consistency across project teams¹⁰.

What happens when naming conventions fail in construction?

Files become unsearchable, revisions get mixed up, and institutional knowledge is lost when staff leave. AI adoption is blocked because AI systems can't categorize or learn from inconsistently named content¹³. And the productivity cost is real— McKinsey found in 2012⁹ that employees already lose 1.8 hours per day searching for information, and poor file naming directly compounds that loss.

Conclusion

Naming conventions aren't optional— they're the infrastructure on which AI readiness, staff transitions, and institutional knowledge are built. The question isn't whether to invest in them. It's whether to enforce them manually (and watch them fail) or automate them (and watch them hold).

As Renamer.ai captures it⁸: "Naming conventions aren't about being organized. They are about never having to think about organization again." That's what automation delivers. Not just cleaner files— a system that doesn't require discipline to maintain.

Evaluate your current naming system with a simple test: is compliance enforced by documentation, or embedded in the workflow? If someone has to remember to follow the convention, it will eventually fail. If the tool enforces it at creation, it won't.

If auditing your firm's AI readiness— including its information architecture— is on the roadmap, Dan Cumberland Labs helps AEC and professional services firms build the infrastructure that makes AI actually work. That usually starts with exactly this conversation.

References

1. Claravine, "The Hidden Cost of an Inconsistent Naming Convention" (2024) — https://www.claravine.com/the-hidden-cost-of-an-inconsistent-naming-convention/
2. The Dynamic Power Disciple, "Why Naming Conventions Are Architecture, Not Aesthetics" (2024) — https://thedynamicpowerdisciple.com/why-naming-conventions-are-architecture-not-aesthetics/
3. Build (Syntec Group), "202-DYK: Why Naming Conventions Matter" (2026) — https://build.syntecgroup.com/2026/02/18/202-dyk-why-naming-conventions-matter/
4. Onsite, "File Naming Convention in Construction Projects" (2024) — https://onsite.us/file-naming-convention-best-practices-in-construction-projects/
5. The AEC Associates, "BIM Standards ISO 19650: A Complete Guide 2026" (2026) — https://theaecassociates.com/blog/bim-standards-iso-19650/
6. ServiceNow Community, "Why Naming Conventions Break Faster Than ACLs" (2024) — https://www.servicenow.com/community/content-blogs/why-naming-conventions-break-faster-than-acls/ba-p/3479332
7. ServiceNow Community, "Why Naming Conventions Break Faster Than ACLs" (2024) — https://www.servicenow.com/community/content-blogs/why-naming-conventions-break-faster-than-acls/ba-p/3479332
8. Renamer.ai, "The File Naming Convention System That Actually Works" (2025) — https://renamer.ai/insights/file-naming-conventions-best-practices
9. McKinsey Global Institute, "The Social Economy: Unlocking Value and Productivity Through Social Technologies" (2012) — https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy
10. Leeds Beckett University / Journal of Engineering, Design and Technology, "Facilitating Compliance with BIM ISO 19650 Naming Convention through Automation" (2021) — https://www.sciencedirect.com/science/article/abs/pii/S1726053121001467
11. ArchiLabs, "BIM Automation: AI-Powered Efficiency for Revit Workflows" (2025) — https://archilabs.ai/posts/bim-automation
12. Autodesk University, "Optimizing AEC Workflows with Autodesk Forma and Workato Automations" (2025) — https://www.autodesk.com/autodesk-university/class/Optimizing-AEC-Workflows-with-Construction-Cloud-and-Workato-Automations-2025
13. Box, "What Is AI Metadata, and Why Does It Matter?" (2025) — https://blog.box.com/ai-metadata
14. Newforma, "Newforma Konekt: The Golden Thread of AEC Information Management" (Current) — https://www.newforma.com/newforma-konekt/