IFC model health check, the step before compliance.
An IFC model health check finds the export problems that stop code rules from running: unbounded spaces, proxies, wrong storeys and unit errors. Use this checklist before any compliance check.
What is ifc model health check?
An IFC model health check tests the model itself rather than the building: are spaces properly bounded, are elements classified and on the right storey, are units consistent, are required properties present. Compliance rules rely on all of that. A model with unbounded spaces or a unit error will not just produce poor results, it can produce confident wrong ones, so health comes first.
What the code asks for
- Every occupiable area is a bounded space, so occupant load and travel distance have a valid start and end.
- Elements are the right IFC class, assigned to the right storey.
- Units and scale are consistent (metres or millimetres), so a distance of 30 m is not read as 30 mm or 30 km.
- Required property sets exist, so ratings and flags can be read.
The exact values (ratings, distances, widths, densities) come from the code edition your authority applies, so a check always reports which edition and clause it used.
How it shows up in an IFC model
| Health item | Where it lives | Why it matters |
|---|---|---|
| Bounded spaces | IfcSpace and its boundaries | Occupant load, travel distance and egress simulations fail on unbounded spaces |
| No critical proxies | IfcBuildingElementProxy | Rules cannot apply to elements that are not recognised |
| Storey assignment | IfcBuildingStorey containment | Vertical rules (stairs, shafts, compartmentation) need the correct level |
| Units and scale | IfcProject units | A 1,000x error corrupts every distance and width check |
| Required properties | Pset_DoorCommon, Pset_WallCommon and others | Ratings and flags cannot be read if the property sets are not exported |
| Duplicates | Overlapping elements | Double-counted walls or doors cause false findings |
Why models fail this check
- Rooms that are not enclosed by walls or virtual separators.
- Fire exit doors and dampers exported as generic proxies.
- MEP elements with no storey, or with the wrong one.
- Mixed units between disciplines, or an export that changed units.
- Property sets not included in the export because an export option was off.
What a Verify AI finding looks like
Example finding: unbounded space
Severity: MEDIUM
Element: IfcSpace "Open office"
Location: Level 6
Detected: space boundary not closed along the east edge
Impact: occupant load and travel distance cannot be calculated reliably
Action: close the room boundary with a wall or room-separation line and re-export
This is an illustrative example. Every finding is pinned to the plan, names the element, and cites the clause it was checked against. See a full sample report.
How to prepare your model
- Close the rooms: add room-separation lines where a space is open to another.
- Replace proxies: map or remodel generic objects that matter for fire.
- Check storeys: confirm every architectural and MEP element sits on the right level.
- Confirm units: check the project units in the export and in the receiving tool.
- Export the properties: turn on common property sets in the export settings.
Frequently asked questions
What is an IFC model health check?
A test of the quality of an IFC file, separate from code compliance: whether spaces are bounded, elements classified, storeys correct, units consistent and properties present.
Why run it before compliance checks?
Rules assume a sound model. If the model has structural problems, results are unreliable. Fixing health first means the compliance report shows real design issues.
Which IFC versions are supported?
Verify AI reads IFC2x3 and IFC4 models, including coordinated models exported from Revit, and drawings in DXF or PDF.
Related
- BIM fire compliance checking: the complete guide
- IFC classification checking
- Fire door rating validation
- Travel distance
- How to check an IFC model for building code compliance