Back to the BIM & IFC blog
Validation · 2026-06-30 · 26 min
IFC Model Checker: The Complete Guide (2026)
What IFC model checking actually means, how the three validation layers work, and how to use a checker to enforce quality gates before every model delivery.
IFC Model Checker: The Complete Guide (2026) — IFC Viewer Online article cover
- 44 — quality rules checked automatically
- 3 — validation levels: schema → quality → IDS
- 6 — IDS 1.0 facets validated
- 0 — file uploads needed for browser-local checking
What Is an IFC Model Checker?
An IFC model checker is software that automatically validates the content and structure of an IFC file against a defined set of rules. It goes beyond what the eye can see in a 3D viewer: it interrogates the data layer — GUIDs, spatial hierarchy, property sets, geometry, classifications, and project-specific requirements.
The output is a structured report: which rules passed, which failed, how many issues of each severity exist, and a numerical quality score that can be used as a project delivery gate. BIM coordinators use this to catch problems before they reach the CDE, the coordination model, or the client.
The term is sometimes used loosely to mean any tool that opens an IFC file. This guide uses the precise definition: a checker validates data against rules and produces a pass/fail verdict. A viewer shows geometry. Most professional workflows need both, but they are distinct functions.
Why IFC Checking Matters Now
Three forces are making systematic IFC checking unavoidable in 2026:
- ISO 19650 adoption — information requirements now must be verified, not assumed. Many contracts include data delivery obligations with measurable acceptance criteria.
- Open BIM workflows — as projects exchange IFC between authoring tools and disciplines, accumulated quality debt compounds. A wall assembled from four different authoring tools has four different naming conventions unless checked at each handoff.
- FM handover pressure — building owners receiving digital twins expect property data that actually matches the installed asset. Systematic checking at design and construction stages is the only way to guarantee this.
Three Levels of IFC Model Checking
IFC validation is not a single pass/fail test. It operates at three distinct levels, each catching a different class of problem:
| Level | What it checks | What it catches | Tools that support it |
|---|
| L1 — Schema | EXPRESS schema, entity/attribute types, required fields | Corrupted files, wrong IFC version, invalid entity references | Any serious IFC tool |
| L2 — Quality | 44 quality rules: GUIDs, hierarchy, names, geometry, properties | Duplicate GUIDs, missing storeys, empty names, broken geometry | IFC Viewer Online, Solibri, BIMcollab Zoom |
| L3 — Requirements (IDS) | Project-specific property, classification, material rules | Missing fire ratings, wrong classification codes, absent EIR metadata | IFC Viewer Online, buildingSMART Validator |
The three levels build on each other: a file must pass L1 before L2 makes sense, and L2 before L3.Level 1: Schema and EXPRESS Validation
The IFC standard is defined in EXPRESS, a formal data modelling language. An L1 checker verifies that every entity in the file matches its EXPRESS definition: required attributes are present, values are the right type, enumeration values are valid, and referential integrity is maintained. This is the minimum bar — a file that fails L1 cannot be processed reliably by any downstream tool.
Level 2: Quality Rule Validation
L2 checking applies 44 rules derived from industry best practice, buildingSMART guidance, and common failure modes observed in real project delivery. These rules cover six domains:
Identity
Every element has a unique, spec-compliant GUID. Duplicate GUIDs break CDE version tracking, clash detection, and BCF coordination.
Spatial Hierarchy
All building elements are assigned to a storey; all storeys are in a building; the building is in a site. Broken hierarchy causes elements to disappear in coordination tools.
Property Sets
Standard Psets (Pset_WallCommon, Pset_BeamCommon, etc.) are present and populated. Missing Psets break quantity takeoff and FM handover.
Geometry
Solid geometry closes, Boolean operations resolve, and elements have non-zero volume. Broken geometry causes errors in model review and 4D/5D simulation.
Classification
Elements carry classification codes (Uniclass, OmniClass, NBS) where required by the EIR. Missing classifications break procurement and FM asset registers.
Relationships
IfcRelContainedInSpatialStructure, IfcRelAggregates, and type-instance relationships are correctly formed. Broken relationships corrupt the spatial tree.
Level 3: IDS Validation
IDS (Information Delivery Specification) is the buildingSMART standard for defining exactly what data a model must contain at a given project stage. An IDS file specifies required entities, attributes, property sets, property values, classifications, and materials — and the checker verifies whether each element in the model satisfies those specifications. IDS 1.0 was ratified in 2024 and is increasingly referenced in contracts and EIRs. See the full IDS implementation guide for details on the six facets.
The Health Score: A Single Number for Model Quality
A rule-by-rule report is essential for fixing issues, but it is impractical as a delivery gate. The Health Score condenses 44 rules into a single 0–100 number using severity-weighted logarithmic penalties: errors (blocking issues) carry 3× the weight of warnings. This means a model with two severe errors scores significantly lower than one with dozens of minor warnings.
| Score Range | Grade | Meaning | Action |
|---|
| 90–100 | Excellent | Delivery-ready model with minimal or no issues | Approve for CDE upload |
| 75–89 | Good | Minor issues present; acceptable for most coordination stages | Fix before formal delivery |
| 50–74 | Fair | Multiple issues requiring remediation before delivery | Return to authoring team |
| 25–49 | Poor | Significant data quality problems across multiple rule categories | Mandatory remediation |
| 0–24 | Critical | Fundamental structural or data problems; model unusable for coordination | Do not accept |
Health Score bands and recommended BIM coordinator actions at each gate.The Business Case for Systematic Checking
Faster coordination
Pre-screening models for L2 errors before clash detection eliminates false clashes caused by broken geometry and hierarchy. Coordination meetings become productive rather than remedial.
Accurate quantity takeoff
QS tools depend on correct Psets and classifications. A model that passes L2 checking produces reliable material quantities; one that does not requires manual correction before every BOQ update.
Contract compliance
ISO 19650 information requirements carry contractual weight in an increasing number of projects. A checking audit trail demonstrates compliance and protects against disputes about data quality at handover.
FM handover confidence
Asset management systems ingest property data from IFC. A model with complete Psets, correct classifications, and valid GUIDs populates the CAFM automatically. One without requires expensive manual data entry.
IFC Checking in an ISO 19650 Workflow
ISO 19650 defines information delivery milestones (IDMs) and information requirements (EIRs, AIRs). IFC model checking maps onto this framework at three points:
Authoring tool (Revit / ArchiCAD / Tekla)
│
▼ IFC export
[L1 Schema check] ──fail──▶ Return to author
│ pass
▼
[L2 Quality check (44 rules)] ──fail──▶ Return to author with error report
│ pass (Health Score ≥ threshold)
▼
[L3 IDS check] ──fail──▶ Return to author with IDS non-conformances
│ pass
▼
CDE upload (approved for coordination)
│
▼
Clash detection / coordination
│
▼
[Pre-submission L2+L3 recheck] ──fail──▶ Fix before submission
│ pass
▼
Client / FM handover
When to Check: Six Project Checkpoints
Before CDE upload
Prevent non-conforming models from entering the shared environment. L1+L2 at minimum; L3 if an IDS has been issued.
At each design stage gate
Check all discipline models before combining into the coordination model. Structural, architectural, and MEP each checked independently.
Before clash detection
Broken geometry and hierarchy cause false clashes. A clean L2 report before the clash session saves hours of investigation.
Before client submission
Formal IDS validation with a recorded Health Score. Archive the checking report with the model as evidence of conformance.
After significant revisions
Any revision that touches spatial structure, naming, or property data should trigger a recheck. Automated checking on every export is achievable with CLI or API workflows.
At FM handover
Final LOI check: are all required properties populated? Are classification codes correct? Is the GUID set stable?
Technical Brief: How Checking Works Under the Hood
Modern browser-based IFC checkers use WebAssembly to run the IFC parsing engine and rule evaluation logic directly in the browser, with no server round-trip. The IFC file is parsed into an in-memory schema graph; each rule is evaluated as a query against that graph. The process for a typical architectural model (50–200 MB) takes 15–60 seconds and produces a structured results object that drives the report UI.
For IDS validation, the checker loads the IDS XML file, compiles each specification into a set of element filter criteria and property assertions, then evaluates every applicable element in the model against those assertions. The result is a per-element, per-specification conformance record with pass/fail/not-applicable status.
Choosing the Right Checker for Your Workflow
The right tool depends on your coordination role, project scale, and budget. For a detailed head-to-head, see the best IFC model checkers comparison. For the conceptual distinction between checking and viewing, see IFC model checker vs IFC viewer. The short version:
| Scenario | Recommended approach | Why |
|---|
| Individual BIM author checking own export | Browser-based checker (IFC Viewer Online) | Instant, free, no upload, immediate feedback |
| BIM coordinator reviewing incoming models | Browser-based L2 + IDS check against project IDS | Full three-level validation, no toolchain dependency |
| Large multi-discipline project with Solibri rule sets | Solibri + browser-based pre-screening | Pre-screening reduces Solibri queue; Solibri adds project-specific rules |
| Automated CI/CD quality gate on model revisions | API-driven checker or CLI wrapper | Triggerable without human interaction; integrates with CDE workflows |
| Client requiring certified report | Tool with exportable HTML/PDF report and JSON audit trail | Defensible evidence of conformance at handover |
Scenario-based tool selection guide for IFC checking.Running Your First IFC Check: Step by Step
- Export IFC from your authoring tool. Use IFC4 (IFC2x3 if required by the project). Keep the export settings consistent with your project BEP.
- Open the IFC file in IFC Viewer Online. No account, no upload — drag the file into the browser.
- Navigate to the Validation panel. The L1 schema check runs automatically; the L2 quality check starts immediately. Review the Health Score and the issue breakdown by severity and category.
- Export the report as JSON or HTML for the project record. If an IDS file has been issued for your project, upload it in the IDS panel to run the L3 check.
Try IFC Checking Now
This IFC2x3 architectural model demonstrates the three-level checking process. Navigate to the Validation panel to see the Health Score and full rule breakdown.
IFC2x3 · 2.4 MB
Open the interactive IFC viewer
Catching a duplicate GUID during design costs minutes. Catching it at FM handover costs days. Systematic checking is not overhead — it is the cheapest quality control available.
BIM coordination principle
Three-level validation
Schema → Quality (44 rules) → IDS requirements. Each level builds on the previous.
Health Score as a gate
0–100 severity-weighted score. Set 75 for coordination, 90 for formal delivery in your BEP.
Check before upload
Browser-local checking means no NDA risk, instant feedback, and zero toolchain dependency.
ISO 19650 alignment
Checking at each IDM satisfies the review-and-approve obligation in clause 5.6 with an auditable trail.
Continue reading: what makes a checker different from a viewer — tool categories explained in IFC model checker vs IFC viewer. How eight leading tools compare on checking depth and workflow fit — best IFC model checkers in 2026. A practical step-by-step checking workflow for BIM coordinators — how to check an IFC model before delivery. The ten most common IFC errors and how to detect each one — 10 common IFC model errors. Health Score calculation and use as a quality gate — IFC Health Score guide.
IFC Model Checker: The Complete Guide (2026)