Back to the BIM & IFC blog
Validation · 2026-06-30 · 20 min
10 Common IFC Model Errors and How to Detect Them
The ten errors that appear most often in IFC files delivered on real projects — what causes them, how a model checker detects them, and how to fix them at the source.
10 Common IFC Model Errors and How to Detect Them — IFC Viewer Online article cover
A BIM coordinator who has reviewed enough incoming IFC files develops pattern recognition: the same ten errors appear project after project, authoring tool after authoring tool. They are not random — they have consistent causes, and most are preventable with the right export settings and a checking step before the CDE upload.
Overview: The 10 Most Common IFC Errors
| Error | Severity | Detection method | Downstream impact |
|---|
| 1. Duplicate GUIDs | Error | L2 rule check — data level only | CDE version tracking, clash detection, BCF coordination |
| 2. Broken spatial hierarchy | Error | L2 rule check — spatial tree | Elements invisible in coordination tools; wrong storey filters |
| 3. Elements not assigned to storey | Error | L2 rule check — containment | Quantity takeoff by floor fails; coordination filters break |
| 4. Missing property sets | Warning/Error | L2 rule check — Pset presence | QTO inaccurate; FM handover incomplete; EIR non-conformance |
| 5. Wrong / absent classification codes | Warning | L2 rule check — classification | Procurement broken; FM asset register incomplete |
| 6. Invalid geometry | Error | L2 rule check — geometry validity | Clash detection false positives; 4D/5D simulation fails |
| 7. Broken element relationships | Warning | L2 rule check — relationship integrity | Spatial tree corruption; type-instance data loss |
| 8. Naming convention violations | Warning | L2 rule check — naming rules | Filters in coordination tools fail; manual rework |
| 9. Missing ISO 19650 / EIR metadata | Warning/Error | L3 IDS validation | EIR non-conformance; IDS specification failure |
| 10. LOD/LOI inconsistencies | Warning | L2 + L3 rule check | QTO unreliable; stage gate check fails |
The 10 most common IFC errors, their severity, and downstream impact.1. Duplicate GUIDs
Every element in an IFC file must carry a globally unique identifier (GUID) — a 22-character base64-encoded value that is supposed to be unique across all IFC files ever created. Duplicate GUIDs occur when elements are copy-pasted in the authoring tool without triggering GUID regeneration. The result: two or more elements in the same file share an identifier.
Detection and causes
- Invisible in 3D viewer — requires L2 data-level check
- IFC Viewer Online reports each duplicate by element name and type
- Cause: copy-paste in Revit or ArchiCAD without GUID reset
- Cause: linked model import without GUID conflict resolution
- Cause: authoring tool bug in specific exporter versions
Fix and prevention
- In Revit: use the IFC exporter option to regenerate GUIDs on export
- In ArchiCAD: use the GUID management tool before export
- Prevention: never copy-paste between projects via copy/paste — use links
- Prevention: check for duplicates after every major model merge
- Prevention: run Health Score check before every CDE upload
2. Broken Spatial Hierarchy
The IFC spatial hierarchy is the backbone of the model: IfcProject → IfcSite → IfcBuilding → IfcBuildingStorey → IfcSpace/elements. When this chain is broken — a building with no site, or a storey with no building — coordination tools either reject the file or silently produce incorrect results.
Detection and causes
- L2 rule check: missing IfcRelAggregates between hierarchy levels
- Elements appear in the wrong storey filter or not at all
- Cause: manually edited IFC file with incorrect hierarchy edit
- Cause: authoring tool export of partial models (one discipline only)
- Cause: merge of models from different tools without hierarchy reconciliation
Fix and prevention
- Fix in authoring tool: ensure site, building, storeys are modelled, not just implied
- In Revit: check that the project hierarchy in the IFC export options is complete
- Prevention: validate the hierarchy after every federated model merge
- Prevention: never manually edit IFC hierarchy outside the authoring tool
3. Elements Not Assigned to a Storey
An element exists in the model but has no IfcRelContainedInSpatialStructure relationship to an IfcBuildingStorey. The element is technically in the file but effectively unlocated in the building hierarchy. Coordination tools filter by storey; an unassigned element is invisible to those filters.
Detection and causes
- L2 rule check: elements with no spatial containment relationship
- Cause: elements placed on reference planes, not levels, in Revit
- Cause: elements with "No Level" assignment in Revit
- Cause: ArchiCAD elements with an undefined home storey
- Cause: generic model families placed without a host level
Fix and prevention
- In Revit: select each affected element and assign a Level parameter
- Filter by "No Level" in Revit schedules to find all affected elements
- In ArchiCAD: use Element Information to check and set home storey
- Prevention: include storey assignment as a modelling standard review item
- Prevention: run L2 check after every new discipline model integration
4. Missing Required Property Sets
Standard IFC property sets (Psets) like Pset_WallCommon, Pset_BeamCommon, and Pset_SpaceCommon carry the data that downstream tools — quantity takeoff, FM handover, energy analysis — depend on. When a Pset is absent or its properties are empty, those downstream processes produce incorrect or incomplete results.
Detection and causes
- L2 rule check: required Psets absent for element types
- Cause: exporter Pset mapping not configured for this element type
- Cause: custom element types with no IFC Pset equivalent
- Cause: export profile set to "geometry only" for file size reduction
- Cause: incorrect IFC entity type mapped — wrong Pset attached
Fix and prevention
- Review the export Pset mapping table in your authoring tool exporter
- Add explicit mappings for custom element types to appropriate Psets
- Never use "geometry only" export for coordination or delivery models
- Prevention: use IDS to formally define required Psets per project stage
- Prevention: validate Pset completeness in the L3 IDS check before delivery
5. Wrong or Absent Classification Codes
Classification codes (Uniclass 2015, OmniClass, NBS, or national equivalents) are required for procurement, FM asset registers, and increasingly for EIR compliance. Missing or incorrect classification codes mean QS teams cannot generate correct BOQs and FM teams cannot populate the CAFM without manual rework.
Detection and causes
- L2 rule check: classification property absent or not linked to standard system
- L3 IDS check: specific classification code requirements not met
- Cause: classification not configured in authoring tool export
- Cause: classification system in model does not match EIR requirement
- Cause: custom families without classification code parameters
Fix and prevention
- Configure classification system in authoring tool project settings
- Map all element types to the required classification table
- Use IDS to formally define which classification system and codes are required
- Prevention: include classification in the BIM content standards from day one
- Prevention: validate against IDS at each stage gate, not only at handover
6. Invalid or Broken Geometry
Geometry errors in IFC fall into three main types: zero-volume elements (an extruded profile with zero area), unclosed solid geometry (a solid that has holes in its surface), and failed Boolean operations (a void subtraction that produces a non-manifold result). These are invisible when viewing the model because renderers smooth over them; they become visible only when clash detection or simulation tools try to process the geometry mathematically.
Detection and causes
- L2 rule check: geometry validity, volume check, manifold check
- Cause: poorly formed curtain wall panels in Revit
- Cause: complex Boolean operations in ArchiCAD that fail on export
- Cause: imported geometry (from DXF or STEP) that never had valid solid geometry
- Cause: manually drawn geometry with accidental zero-area profiles
Fix and prevention
- Use the checker error report to identify specific elements by name/type
- Re-model identified elements using correct solid modelling techniques
- For curtain walls: check the panel definition, not just the overall wall
- Prevention: avoid importing DXF/DWG geometry directly into BIM models
- Prevention: review geometry in an IFC viewer after every complex Boolean operation
7. Broken Element Relationships
IFC encodes relationships between elements using relationship entities: IfcRelDefinesByType (type-instance), IfcRelAssociatesMaterial (material assignment), IfcRelConnectsElements (structural connections), and others. When these relationships are malformed — referencing non-existent entities, or pointing to the wrong type of object — the data model becomes inconsistent and downstream tools either error or silently ignore the affected elements.
Detection and causes
- L2 rule check: dangling relationship references, wrong entity types
- Cause: manual IFC editing that breaks referential integrity
- Cause: exporter bugs in older authoring tool versions
- Cause: federated model merge with relationship conflicts
Fix and prevention
- Re-export from the authoring tool — do not edit IFC files manually
- Update the authoring tool exporter to the current version
- Prevention: treat IFC as a delivery format only — all edits happen in the authoring tool
- Prevention: validate after every exporter update
8. Naming Convention Violations
BIM projects define naming conventions for element types, layers, views, and object names. When IFC elements carry generic names ("Wall", "Floor 1", "Beam") or inconsistent names across disciplines, coordination tools cannot apply discipline filters correctly and QS teams cannot run automated takeoff without manual rule configuration.
Detection and causes
- L2 rule check: generic or empty names flagged
- Cause: authoring tool families with default names not updated
- Cause: naming convention document shared too late in the project
- Cause: imported content from other projects with different conventions
Fix and prevention
- Use the checker report to identify elements with non-compliant names
- Correct names in the authoring tool — names should not be changed in the IFC file
- Prevention: issue the naming convention document at project start
- Prevention: use IDS to formally enforce naming patterns where critical
9. Missing ISO 19650 / EIR Metadata
An IDS file formalises the metadata required by the EIR: project number, phase, discipline code, responsible organisation, LOD/LOI level, and custom properties. When an IDS is in force, any element that fails to carry the required properties fails the L3 IDS check and the model is non-conformant for delivery.
Detection and causes
- L3 IDS validation: required properties absent or wrong value type
- Cause: IDS not shared with authoring teams early enough
- Cause: custom Psets for EIR metadata not configured in authoring tool
- Cause: elements added after IDS check without checking against IDS
Fix and prevention
- Share the IDS file with all authoring teams at project kick-off
- Configure custom Psets to carry EIR metadata in authoring tool templates
- Run L3 IDS check at every stage gate, not only at final handover
- Prevention: use IDS as the machine-readable version of the EIR data requirements
10. LOD / LOI Inconsistencies
Level of Development (LOD) and Level of Information (LOI) requirements differ by project stage and element type. At construction stage, structural elements should have LOD 400 (fabrication-ready geometry and full material properties) while architectural finishes may still be LOD 300. Inconsistencies — a wall with LOD 200 geometry and LOD 400 property data, or vice versa — cause QTO inaccuracies and stage gate failures.
Detection and causes
- L2 Pset completeness check + L3 IDS LOI properties
- Cause: LOD/LOI matrix not communicated clearly to authoring teams
- Cause: elements at different LODs mixed in a single export
- Cause: LOD matrix not updated when scope changes mid-project
Fix and prevention
- Use IDS to formally define which properties are required at each stage
- Check LOI compliance using the L3 IDS check at each stage gate
- Prevention: issue a LOD/LOI matrix per element type at project start
- Prevention: use the Health Score trend across stages to identify regression
None of the ten most common IFC errors are visible in a 3D viewer. All ten are detectable in under a minute with an L2 model checker. The five-minute check before CDE upload is the highest-leverage quality control available to a BIM coordinator.
IFC quality management principle
For a step-by-step workflow to check and fix these errors before delivery, see how to check an IFC model before delivery. For the tool to run the check, see the best IFC model checkers comparison. For the complete framework behind the checking levels, see the IFC model checker complete guide. For the conceptual distinction between checkers and viewers, see IFC model checker vs IFC viewer. To stop them recurring, put a threshold in the contract: BEP clauses that actually prevent bad IFC deliveries.
10 Common IFC Model Errors and How to Detect Them