ClearIFC checks an IFC model for the data defects that get submissions rejected — broken spatial structure, missing property sets, duplicate GUIDs, unbuildable geometry — and validates it against your client's buildingSMART IDS. In a browser. Nothing to install.
They show you geometry. They won't tell you the storeys are missing, the GUIDs are duplicated, or half the walls have no property sets.
Solibri and Navisworks do this properly — at a price that makes no sense for a subcontractor checking a handful of models a month.
And you find out days later, from the head contractor, after the deadline. ClearIFC is the check you run before you send.
Every check reports the specific elements that failed, by GlobalId, type and name — so the report tells you what to fix, not just that something is wrong.
Confirms the file parses, declares a supported schema, carries units, and conforms attribute-by-attribute — catching files a viewer displays happily but a receiving system rejects.
Project → site → building → storey, correctly aggregated, with every element actually contained somewhere. A broken tree means nobody can filter by level.
The property sets and properties your rule set requires — including properties that exist but were exported blank. Type-inherited properties count.
Duplicate and malformed GlobalIds. Duplicates quietly corrupt model federation, revision comparison and any asset register keyed on GUID.
Elements with no representation, empty representations, solids the geometry kernel cannot build, and solids that enclose zero volume.
Uniclass and other classification coverage, including whether codes match the pattern your client's standard actually requires.
IDS is the open standard for information requirements: a client states once what a compliant model must contain, in a machine-readable file, and any IDS-capable tool checks it automatically. Free viewers don't support it at all. Enterprise tools do — at enterprise prices.
<!-- every wall must carry a fire rating --> <specification name="Walls carry a fire rating"> <applicability> <entity><name> <simpleValue>IFCWALL</simpleValue> </name></entity> </applicability> <requirements> <property cardinality="required"> <propertySet> <simpleValue>Pset_WallCommon</simpleValue> </propertySet> <baseName> <simpleValue>FireRating</simpleValue> </baseName> </property> </requirements> </specification>
Working IDS examples are still scarce, so here are three you can use or adapt today. Standard IDS 1.0 files — they work in any IDS-capable tool, not just this one. Treat them as starting points and tailor them to your project before issuing them to suppliers.
You export IFC from Tekla or Revit and submit it to someone else's CDE. Check it yourself first, instead of finding out at rejection.
You receive models from a dozen suppliers of wildly varying BIM maturity. Use ClearIFC as the first-pass gate before spending senior time on review.
You publish a DE framework and need every supplier checked against the same machine-readable requirements — not against whichever reviewer got the file.
This is the first question every government and infrastructure client asks, so it is answered in the architecture rather than in a policy document.
The file is streamed to temporary storage, parsed, and deleted as soon as the report exists — whether validation succeeded, failed, or crashed.
Only the report is kept, and only if you are signed in: the verdict, per-check summaries, and the failing elements by GlobalId. Never the model.
Hosted in Australia. For clients who will not upload to a third party at all, a self-hosted option runs entirely inside your own network.
Pricing is being set with our beta users and will be published at launch. Early access participants keep free use of everything through the beta.
ClearIFC is working and in private beta. We are onboarding a small group of firms who deliver or receive IFC regularly — you get free use through the beta, and direct influence over which checks get built next.
We'll only email you about ClearIFC, and never share your details. No model files are involved in signing up.