Clash naming sounds like cosmetics. It isn't. The name of a clash group is the only thing your audience (consultants, contractors, the project director) sees in a list of 200 items. If they have to click into each one to understand it, your meeting takes three hours. If they can scan the list and triage in their heads, it takes 45 minutes.
This is a practical guide to designing a Navisworks clash naming convention that holds up at scale — what a good name contains, the patterns that keep working on real projects, and how to enforce a convention so it's still intact in month six.
What a name has to do
A clash group name has to answer four questions in under 80 characters:
- Where is it? (Level, zone, grid)
- What disciplines are in conflict?
- What specific elements?
- What's the severity hint? (optional but useful)
If the name answers those, the consultant receiving the BCF knows whether to open it now or in the morning.
A convention that works
The pattern most teams converge on after a project or two:
[Level] — [Discipline A] vs [Discipline B] — [Element A] / [Element B] — [Zone]
Real examples:
L02 — MECH vs STR — 12" supply duct / W21x44 girder — west bayL05 — PLBG vs ARCH — 4" sanitary stack / restroom partition — core CB01 — ELEC vs MECH — 600A bus duct / 24" return — main electrical room
Five things this convention does well. It sorts by level naturally when listed alphabetically. The discipline pair is searchable: "Show me everything Mech vs Struct on L02" is a text filter. Element specificity means a reviewer doesn't need to open the viewpoint to understand the conflict. The zone gives spatial context, so "west bay" is a meaningful answer in a coordination meeting. And it fits in the BCF title field without truncation.
What doesn't work
Numeric IDs alone. Clash847 says nothing. Even worse, the number changes if the test is re-run with different parameters.
Discipline initials nobody agrees on. M, MEC, MECH, Mechanical, HVAC. Pick one and write it down. International teams especially need this; "PLB" and "PLG" both mean plumbing depending on who you ask.
Free-form descriptions. "Big duct hits beam near the west wall I think" is what people produce when there's no convention. Helpful in the moment, useless to anyone reading it next month.
Names that include the date. Names should describe the clash, not when it was named. The date belongs in metadata.
Levels and zones
Levels seem easy until you hit a project where the structural engineer calls them L01, L02, L03 and the mechanical engineer calls them 1F, 2F, 3F. Pick one. Force everyone to use it. Map at the federation level if a consultant won't change.
Zones are where projects diverge. Some use grid intersections (A.5/3), some use named zones (west bay, service corridor), some use room numbers when room data is reliable. The right answer is whatever your team will actually use without thinking. Test by asking three coordinators to name the same clash and see if their zones match.
Disciplines at the right resolution
Two-letter codes are too short, full words are too long. Three to four letters is the sweet spot:
| Code | Discipline |
|---|---|
| ARCH | Architecture |
| STR | Structure |
| MECH | Mechanical (HVAC) |
| PLBG | Plumbing |
| ELEC | Electrical |
| FP | Fire protection |
| LV | Low-voltage |
| CIV | Civil |
| LAND | Landscape |
Sub-disciplines (HVAC supply vs. exhaust vs. hydronic) live in the element part of the name, not the discipline part. Otherwise the naming gets hierarchical and unreadable.
Element naming
Elements are the part most teams underspecify. "Pipe" doesn't help. Useful element names contain:
- Type (supply duct, return duct, sanitary stack, sprinkler main, bus duct, beam, girder, column)
- Size (12", 24", W21x44, 600A)
So MECH vs STR — 12" supply duct / W21x44 girder is the right resolution. MECH vs STR — pipe / beam is not.
Most BIM models have this data in element parameters. The work is extracting it consistently, which is why automated naming tools exist. Pulling Family Name, Mark, Pipe Type, Size from each side and templating them into a name is mechanical work that scales badly with manual labor and trivially with automation.
If manual naming is already eating your coordination week, this is the point to automate. Start a free 14-day trial and run AI naming on one of your real clash tests.
Picking a standard instead of inventing one
You don't have to design a convention from a blank page. ClashWise ships six naming standards, and knowing which one fits your project is most of the decision:
- Basic — level, disciplines, elements. The 80-character workhorse; start here.
- Detailed — adds sizes, zones, and richer element descriptions for teams that triage from the list alone.
- Component ID — includes element IDs for teams that reconcile against schedules or fabrication models.
- By Discipline — leads with the discipline pair, for meetings organized trade-by-trade.
- AI Preferred — lets the AI pick the clearest structure per clash based on what the element data actually contains.
- Mixed — combines standards per discipline pair, for projects where MEP wants detail and structure wants brevity.
Whichever you pick, the win is the same: names look identical on Tuesday and on Friday, whoever ran the triage.
Multi-language teams
If your project team works across languages (common on European, Middle Eastern, and Asian projects), name in the language each consultant works in. The structural engineer in Stuttgart should get the German version; the MEP consultant in London gets English. The clash is the same; the readable summary should be local.
This is one of the cases where AI naming earns its keep: rendering the same underlying clash in any of 11 languages from a single template, instead of maintaining parallel naming conventions per consultant.
And if your models can't leave the building — defence, healthcare, anything under strict IP terms — Local AI naming runs entirely on your own machine. Element names, levels, and discipline tags never touch the cloud, and it works offline once the model is downloaded.
Enforcement
A convention is worthless if it's not enforced. Two enforcement patterns:
Manual enforcement. The coordinator names every clash and consultants never get to set names. Works on small teams; fails at scale.
Automated enforcement. Names are generated from element data via rules. Works at any scale, but requires the tooling. The win is consistency: names look the same on Tuesday as they did on Monday, regardless of who triaged them.
The middle ground (convention documented in the BEP, applied by anyone who triages) drifts within a month. Don't bother.
Where to start
Write your convention down in 200 words or less. Stick it at the top of your BEP coordination section. Apply it to one project for a month. Adjust based on what consistently breaks down.
If you're already at the point where manual naming is eating coordinator hours, automate it: download the ClashWise plugin for Navisworks Manage 2024–2027 and generate clash names to your standard, in 11 languages, free for 14 days.