The 10 most common errors in IFC models — and how to find them
Missing names, wrong classifications, empty property sets: these IFC issues cost BIM teams hours. A guide to systematic quality assurance.
Anyone who coordinates IFC models knows the pattern: the file looks fine in the viewer, but checking it against the project requirements surfaces dozens of issues. Missing attributes, wrong classifications, empty property sets — problems that get expensive on the construction site.
This article walks through the ten most common IFC errors, explains why they matter, and shows how to find them systematically.
1. Missing name on building elements
What happens: IFC elements like IfcWall, IfcDoor, or IfcWindow have no Name attribute, or only a generic value like "Generic Wall".
Why it matters: Without meaningful names, building elements cannot be identified in bills of materials, room books, or coordination reports. With hundreds of walls in a model, attribution becomes impossible.
How to find it: Check systematically that every element of a given type has a non-empty Name. Automated validation tools do this in seconds across all elements.
Typical cause: In Revit, the IFC name is generated from the family name. If families are not cleanly named, the name is missing in the export. In ArchiCAD, the ID/description controls the IFC name.
2. Missing or wrong classification
What happens: Building elements have no classification (Uniclass, eBKP, OmniClass, DIN 276) or are classified incorrectly — a load-bearing wall is tagged as a façade.
Why it matters: Classifications are the foundation for quantity take-off, cost planning, and facility management. Without correct attribution, automated evaluations are unusable.
How to find it: Check whether all elements have an IfcClassification reference and whether the code matches the expected system (e.g. eBKP-H for Swiss projects, Uniclass for UK projects).
Typical cause: Classification is often assigned manually in BIM software and forgotten on IFC export. Many offices have no unified classification template.
3. Missing quantities
What happens: Building elements have no Qto_* property sets — i.e. no exported quantities like area, volume, or length.
Why it matters: Without quantities in the model, take-offs have to be done manually or via external tools. That costs time and is error-prone.
How to find it: Check for each element type (e.g. IfcBuildingElement) whether at least one quantity set (Qto_WallBaseQuantities, Qto_SlabBaseQuantities, etc.) is present.
Typical cause: In Revit, the option "Export quantities" must be explicitly enabled in the IFC export settings. By default it is often turned off.
4. Wrong IFC schema
What happens: The project requires IFC4 or IFC4x3, but the delivered file uses IFC2x3 — or the other way around.
Why it matters: Different schema versions support different entities and property sets. An IFC2x3 model cannot contain IfcBridge objects; an IFC4x3 model is not read by older viewers.
How to find it: The schema is in the first line of the IFC file (FILE_SCHEMA). Automated validation tools check it against the project requirements.
Typical cause: The modeller selects the wrong IFC version on export. "IFC2x3" is often kept out of habit, even though the project requires IFC4.
5. Missing fire rating
What happens: Walls, slabs, or doors have no FireRating in Pset_WallCommon / Pset_DoorCommon.
Why it matters: Fire protection requirements are mandated by building code. If the value is missing in the model, it has to be added manually later — often only when the fire safety designer receives the model.
How to find it: For all room-bounding elements (IfcWall, IfcSlab, IfcDoor), check that the FireRating property is present and non-empty in the corresponding Pset_*Common.
Typical cause: Fire rating is often kept as a custom parameter in the authoring tool, but not mapped to the right IFC property.
6. Missing material assignment
What happens: Building elements have no IfcMaterial, IfcMaterialLayerSet, or IfcMaterialConstituentSet.
Why it matters: Material information is essential for energy calculations, sustainability assessments (e.g. DGNB, Minergie), and tendering.
How to find it: Check that all relevant element types have at least one material assigned — ideally with a meaningful name (not "Default" or "Generic").
Typical cause: In Revit, materials are assigned at family level. If families are used without a material, or the material is called "Standard", the information is missing in IFC.
7. Missing storey assignment
What happens: Elements are not assigned to any IfcBuildingStorey — they "float" in the model with no spatial classification.
Why it matters: Without storey assignment, elements cannot be filtered, sorted, or evaluated by floor. Floor-by-floor take-off, room program reconciliation, and coordination become impossible.
How to find it: Check the spatial containment structure (IfcRelContainedInSpatialStructure) — every physical element should be assigned to a storey.
Typical cause: Elements that span multiple floors (e.g. continuous columns, stair shafts) or elements added later are often not properly assigned.
8. Incomplete property sets
What happens: Standard property sets like Pset_WallCommon, Pset_DoorCommon, Pset_SpaceCommon are present, but individual properties are missing — e.g. IsExternal, LoadBearing, or IsAccessible.
Why it matters: Automated evaluations rely on complete property sets. If IsExternal is missing on walls, exterior and interior walls cannot be distinguished — relevant for energy calculations and façade design.
How to find it: Define the expected properties per element type and check systematically for completeness. IDS files (Information Delivery Specification) are a great fit for this.
Typical cause: BIM software only exports properties that are also configured as parameters. If the parameter is missing in the family, the property is missing in IFC.
9. Missing description
What happens: The Description attribute on elements is empty.
Why it matters: The description provides context for coordination and documentation. In room programs it serves as a long name; on building elements as additional explanatory information.
How to find it: Check for relevant element types (especially IfcSpace, IfcBuilding, IfcProject) that a description is present.
Typical cause: Description is simply forgotten in many BIM workflows — it is not a mandatory field and has no visual impact in the model.
10. Wrong model coordinates / missing georeferencing
What happens: The model is exported with the wrong reference points — internal origin, project base point, and survey point get mixed up. Or georeferencing is missing entirely: IfcSite.RefLatitude/RefLongitude is empty, an IfcMapConversion block (IFC4 / IFC4.3) is absent. In some cases coordinates appear twice — once in IfcMapConversion, once in IfcSite.ObjectPlacement.
Why it matters: Models from different disciplines do not align when merged. The architect delivers with a relative origin, the structural engineer with survey coordinates — and the models sit 1500 metres apart. Terrain interfaces, alignments, and infrastructure BIM require correct georeferencing. Without it, coordination is a matter of luck, and the hourly rate for fault-finding rises with every additional model.
How to find it: Check whether IfcSite contains sensible RefLatitude and RefLongitude values, or whether an IfcMapConversion block is present. Spot-check: a known element — say, a column at the building entrance — against the expected real-world coordinates. In IFC4.3, IfcMapConversion is the clean solution; older IfcSite coordinates alone are not enough for infrastructure projects.
Typical cause: In Revit there are three reference points (project base point, survey point, internal origin), and the IFC export offers several "coordinate base" options — anyone who does not actively choose "Shared Coordinates" often exports the wrong point. In ArchiCAD the issue lives in project setup; in Allplan in the world and construction coordinate systems. The first model in a project rarely hurts; the second or third hurts more.
Conclusion: automated checking saves hours
All ten errors share one trait: they are systematically findable. Instead of searching every model by hand, you can define validation rules once and then apply them automatically to every new IFC delivery.
That is exactly what IFClint was built for: upload IFC models, check them against your requirements, and identify errors immediately — directly in the browser, no installation.
Interested? Sign up for a test account and check your first model in under 30 seconds.