IFC Level Consistency Check
Audit building storeys: flags storeys missing an elevation, multiple storeys sharing the same elevation (duplicate or mis-merged levels), and storeys with no building elements. Run it on its own, or stack it with other checks in the Validation Center.
Check an IFC model's storeys for the defects that break level-based workflows: storeys with no elevation, two storeys at the same elevation, and storeys that contain nothing at all. Upload the model and each problem comes back anchored to the specific storey.
Levels are the axis almost every coordination workflow filters and sorts on. A drawing set is issued per level, a takeoff is broken down per level, a clash review is walked level by level, and a federation aligns models by matching them up. When the level structure is wrong, all of that degrades quietly — elements land on the wrong sheet, quantities double-count, and a federated set produces two "Level 3"s that nobody can tell apart.
When to reach for it: After merging discipline models, where duplicate or mis-elevated storeys are a common federation artefact. Catches levels that will misalign floor-based views and schedules.
What you get: A findings list of storeys missing an elevation, multiple storeys sharing the same elevation (duplicate / mis-merged levels), and storeys with no building elements — exportable to BCF, HTML, or CSV.
Example: Catch duplicated or mis-elevated storeys after merging discipline models.
Three defects, each anchored to its storey
- Missing elevation — MEDIUM. A storey with no elevation value cannot be placed on the vertical axis, so anything that sorts or snaps by level has to guess where it goes.
- Shared elevation — MEDIUM, and the classic federation defect. Two storeys at the same elevation usually means a level was duplicated, or two models each brought their own copy of the same physical floor. Everything downstream then has two candidates for one level and picks arbitrarily.
- Empty storey — LOW. A storey that directly contains no building elements is nearly always a leftover template level. Spaces alone deliberately don't count as content: a level holding only rooms and no construction is exactly the pattern this is looking for.
Why these are Medium rather than errors
None of the three makes the model invalid, and the geometry is unaffected — which is precisely why they survive to the point of causing trouble. A model with two Level 3s opens, renders and validates against most schema checks perfectly well. The severity reflects consequence rather than legality: these break coordination workflows without breaking the file, and that combination is what makes them worth a dedicated check.
Every finding is anchored on the offending IfcBuildingStorey, so clicking it isolates that storey in the 3D viewer and you can see immediately whether the duplicate is a real second floor or an empty artefact.
Where level problems come from, and what fixes them
Duplicated levels typically arrive from a merge, from a template that shipped with levels nobody deleted, or from two consultants naming the same floor differently and a tool creating both. Manage IFC Storeys renames, re-elevates and reorganises the storey structure, and can move elements between levels — which is the fix for elements assigned to the wrong one. Merge IFC Files and Split IFC Model are worth checking after, since both touch spatial structure.
Run this before issuing a drawing set, before a level-based takeoff, and on every incoming model before federating. It stacks with the other atomic checks in the Validation Center, and pairs naturally with the Spatial Structure Check — one covers the levels themselves, the other covers whether elements are attached to them.
How to check IFC storeys and levels
- Upload your IFC file
- Click Run — no configuration needed
- Review storeys missing an elevation, storeys sharing an elevation, and empty storeys
- Export to BCF, HTML, or CSV
Under the hood
BIMCamel parses IFC files in the browser using the open-source web-ifc engine and renders models with @thatopen/components + three.js. Heavy operations (clean / optimise / validate / convert) run on disposable server-side workers using the same web-ifc stack plus our own .NET pipeline; results stream back to your browser as soon as they're ready. Uploads sit on our servers only as long as your tier's retention window allows and are never used to train AI.
Frequently asked questions
How do I find duplicate levels in an IFC model?
Run this check — it reports storeys that share an elevation, each anchored to the specific IfcBuildingStorey so you can isolate it in the viewer and see whether it's a real floor or a duplicate.
Why do two storeys at the same elevation matter?
Because everything that filters by level then has two candidates for one floor and picks arbitrarily. Drawings, takeoffs and clash reviews all break down by level, so a duplicated storey produces double-counted quantities and elements on the wrong sheet — with no error anywhere.
What counts as an empty storey?
A storey that directly contains no building elements. Spaces alone don't count as content on purpose: a level holding only rooms and no construction is the exact signature of a leftover template level, which is what the finding is looking for. It's rated Low — untidy rather than harmful.
How do I fix the levels it finds?
Manage IFC Storeys renames, re-elevates and reorganises the storey structure and can move elements between levels. For elements not attached to any storey at all, run the Spatial Structure Check.
Why aren't these reported as errors?
Because the model is still valid and its geometry is unaffected — which is why the problems survive long enough to cause trouble. The severity reflects consequence, not legality: they break coordination workflows without breaking the file.
What's the maximum IFC file size?
Up to 25 MB as a guest, 100 MB with a free account, 500 MB on Pro, and 1 GB on Team. The caps are on upload size only — every tool itself is available on every tier.
What happens to my file after processing?
Your file is uploaded over HTTPS and processed on our servers. Guest uploads are stream-only — the working files are deleted as soon as your download finishes. Free accounts keep results for 7 days; Pro keeps them 90 days and Team 180 days. Files are never shared with third parties or used to train AI.
Is IFC Level Consistency Check free?
Yes. IFC Level Consistency Check is free to use — guests get 3 runs a day with 25 MB uploads, and a free account raises that to 10 runs a day with 100 MB uploads. No trial clock, no watermarks.