Layer Naming Standards: ISO 13567 vs BS 1192 vs AIA Compared

Why layer naming is the thing nobody notices until it's missing

I've inherited drawing files where every wall, on every floor, sat on a layer literally called Layer1, or A-WALL copied inconsistently across a dozen sheets with different capitalisation each time, and the frustrating thing is that this kind of mess is completely invisible until you try to do something useful with the file, like turn off every furniture layer at once, or isolate a layer to check what's actually on the structural grid. Layer naming standards exist to solve exactly that problem, agree on a convention once, apply it consistently, and every drawing in an office, or across a whole project team, becomes machine sortable and predictable instead of a guessing game.

The pain compounds the moment more than one person touches a file, because an inconsistent layer name isn't just an annoyance for the original drafter, it's a trap for the next person, someone opens the drawing six months later, sees three different variants of what's obviously meant to be the same wall layer, A-WALL, Awall, A_Wall, and has no reliable way to know which one is actually current without opening every single one and checking. Multiply that across a hundred drawings on a real project and the cost of skipping a layer standard at the start stops being cosmetic and starts being a genuine drag on how fast anyone can work with the file.

What a layer naming standard is actually trying to solve

A good layer naming standard isn't really about which letters you use, it's about what problem it's structured to solve. Most systems break a layer name into segments, something that identifies the discipline, architectural, structural, mechanical, something that identifies the element type, wall, door, furniture, and sometimes something that identifies status, existing, new, demolished, or scale. Once a layer name follows a predictable structure you can filter, search and batch edit by any of those segments instead of reading every single layer name in a long list to find what you need.

The deeper reason this matters is that a layer name is basically metadata, it's the drawing telling you what a piece of geometry is without you having to click on it and check, and a good standard makes that metadata genuinely useful rather than decorative. A well structured layer name lets a BIM coordinator, a QA reviewer, or an automated script pull out every mechanical layer across a hundred sheet set in one filter operation, something that's simply impossible if every drafter invented their own naming logic independently.

This is also exactly why a layer standard tends to matter more, not less, as a firm grows, a single person working alone can get away with whatever loose naming habit they personally remember, but the moment a second, third or tenth person starts touching the same files, that personal shorthand stops scaling, and the office needs something closer to a shared language that doesn't depend on any one individual's memory of what they meant by a particular layer name six months ago.

ISO 13567: the international, discipline-coded system

ISO 13567 is the international standard for organizing CAD layers by discipline, and it structures a layer name around a small set of coded fields, generally starting with a discipline code, A for architecture, S for structural, and so on, followed by an element or presentation code, and it's built to work across different national languages since it relies on short alphanumeric codes rather than full English words. It's most commonly referenced on European projects, and multinational teams sometimes adopt it specifically because it doesn't assume English as the working language, which BS 1192's more UK specific field structure and AIA's American terminology both implicitly do to some degree.

The standard is deliberately structured in tiers, so a project can adopt just the discipline coding at a minimum, or go further and encode presentation status and user defined fields too, which means a small practice can implement a lighter version of ISO 13567 without committing to the full field structure a large multinational programme might need, and still get most of the practical filtering benefit.

BS 1192: the UK convention behind early BIM Level 2 work

BS 1192 is the British standard for the same problem, and it became the backbone of a lot of early UK BIM Level 2 workflows before being succeeded in concept by the ISO 19650 series for full information management, though the layer and naming logic from BS 1192 is still very much alive in day to day UK practice. A typical BS 1192 style layer name strings together fields for discipline, element and sometimes a further descriptive suffix separated by hyphens, so a wall layer on an architectural drawing might read something like A-WALL-INT for an internal wall versus A-WALL-EXT for external, giving you an instantly filterable structure without opening a single drawing.

What made BS 1192 particularly influential in UK practice wasn't just the layer naming itself, it was that it arrived bundled with a broader file naming and collaboration methodology, shared, work in progress, and published states for a model, common data environment principles, and so on, so offices that adopted it for layers often absorbed the whole collaborative mindset alongside it, which is part of why the layer logic has outlived the specific document it originated from.

AIA CAD layer guidelines: the US convention

The American Institute of Architects layer guidelines, usually just called the AIA standard in US offices, use a similar segmented logic but with US specific major and minor codes, so a typical AIA style name looks like A-WALL for architectural walls, A-DOOR for doors, A-GLAZ for glazing, with an optional minor code appended for further detail like A-WALL-FULL versus A-WALL-PRHT for partial height. It's the convention most US architecture and MEP firms default to, largely because most US CAD templates and a lot of commercial content libraries ship pre-structured around it, so adopting anything else on a US project usually means actively overriding what your software already assumes.

One practical detail worth knowing is that the AIA guideline's major code list is broad enough to cover site work, interiors, and equipment as well as core architecture, so even non-architectural disciplines on a US project, landscape, interior design, sometimes fall in line with an AIA-derived prefix purely because it's the convention already baked into the office's shared template, even if their specific discipline isn't the one the standard was originally written around.

Because AIA has been around long enough to become deeply embedded in US commercial content, a lot of pre-built blocks, symbol libraries and even some manufacturer content arrive already assigned to an AIA-style layer out of the box, which is genuinely convenient if your office already follows AIA, and mildly annoying if it doesn't, since it means imported content needs a quick re-layer pass to match whatever convention your own template actually uses.

Picking or adapting a standard for your own office

For most small to mid sized practices, the honest answer is pick whichever standard your client, your BIM execution plan or your dominant collaborator already uses, rather than trying to pick the objectively best one in isolation, because the value of a layer standard comes almost entirely from consistency, not from which coding logic is superior. If you're working internationally without a client mandate, ISO 13567's language neutral structure is the safer long term choice, if you're squarely in a US AEC market, AIA is what your consultants and contractors will expect to open and immediately understand.

It's also perfectly reasonable to adapt rather than adopt wholesale, plenty of established practices run a hybrid that borrows AIA's familiar major codes for the elements everyone already recognises but adds a couple of office specific minor codes for something specific to their typical project type, a hospitality firm adding extra granularity for furniture and fit out layers, for instance, while keeping the core discipline structure recognisable to any outside consultant who opens the file. The failure mode to avoid isn't deviating from the published standard, it's deviating inconsistently, where the same office produces three subtly different variants of its own hybrid across three different projects because nobody wrote the adapted rule down anywhere.

Setting it up as a working template in AutoCAD

Practically, this means building your layer standard into your AutoCAD template once, with the actual layers pre created, correctly named, with sensible default colors and linetypes assigned, rather than relying on every drafter to type A-WALL-EXT correctly from memory on every project. Add a layer state or a saved layer filter that groups by discipline so switching visibility for an entire trade is one click, and check which layer new blocks land on by default, a north arrow inserted from a library is a good small example, since an inserted block that carries its own stray layer name is one of the most common ways a clean layer standard gets quietly polluted.

A short, written one page reference, not a lengthy manual, listing the office's actual approved layer names alongside a one line description of what belongs on each, tends to get used far more consistently than a link to the full external standard document, because a drafter mid task is far more likely to glance at a one page cheat sheet pinned near their desk than to go digging through a fifty page PDF to confirm whether a new balcony railing belongs on A-RAIL or gets folded into A-WALL-EXT. Keep that reference next to the template file itself, and update both together whenever the standard genuinely needs to change, rather than letting the two quietly drift apart.

Where layer naming discipline breaks down in practice

Where this actually breaks down in real offices is almost always at the boundary between firms, a structural consultant's layers get overlaid into an architectural file via xref, and suddenly there are two competing naming conventions living in the same drawing, or a block downloaded from an external library, ours or anyone else's, carries a plain, ungrouped layer like 0 or a generic name that doesn't match either standard. The fix isn't complicated, just unglamorous, audit incoming xrefs and blocks before they go live in the working set, and rename or re-layer anything that doesn't match your project's chosen convention before it spreads across a dozen sheets.

The other place discipline erodes is under deadline pressure, someone needs a quick fix late on a Friday, adds a new element type nobody had anticipated, and rather than pausing to work out where it fits in the standard, drops it on whatever layer is already active, planning to fix it properly later. Later rarely comes on its own, which is why a genuinely useful layer standard needs a lightweight process for adding a new, previously unanticipated element type on the fly, a quick reference for who to check with, or a sensible fallback naming pattern, rather than relying purely on willpower to prevent the shortcut from happening under pressure.

A note on layer color, freeze states and long term maintenance

A layer standard that only covers naming and ignores default color, linetype and plot behaviour is only doing half the job, because two offices can agree on the exact same name, A-WALL, and still get wildly different plotted results if one assigns it a heavy black lineweight by convention and the other leaves it on a thin default, so a complete standard really needs to pair the name with an agreed default appearance, not just the text string. It's also worth deciding early which layers are safe to freeze or turn off by default when a new sheet is created off a template, dimension and text layers usually stay on, while reference or construction layers often start frozen, so a drafter opening a fresh sheet sees a sensible starting point rather than every layer from every discipline switched on at once.

Long term, the offices that get the most value out of a layer standard treat it as a living document, reviewed and adjusted maybe once a year as new element types show up that the original list didn't anticipate, rather than a rule set frozen in a PDF from a decade ago and never revisited even as the kind of drawings the office produces has clearly changed.

It's worth explicitly assigning the layer for any commonly reused symbol as part of this maintenance pass too, deciding once where a north arrow, a scale bar, or a standard title block element lives in the layer structure, rather than leaving it to whichever drafter happens to insert one first on a given project, since a symbol that lands on a different, inconsistent layer every time it's placed defeats a large part of the point of having a layer standard in the first place.