Where IFC Checker is heading

Checking a model. Check an IFC model against an IDS file, or against a predefined test and the stage you choose.

The Model Correctness Index. One number for the share of tested elements that pass, always shown with how many elements were tested.

Results for every element. Pass, Fail or Untested for every element, with only the failing value marked.

The IDS editor. Write an IDS from a model, one of our predefined tests or a blank page, with live counts on a loaded model.

More tests in the IDS editor. Choose a kind of test for a rule, give one test to many properties at once and set one test for a whole property set.

A list and a grid in the IDS editor. Start an IDS from a list of sets and properties, and see the rules as a grid with the properties down and the kinds of test across.

BCF, Excel and CSV. Export the issues as BCF 2.1, and the results as an Excel workbook and a CSV file.

The 3D view. See the model in 3D, passed elements green, failed red and untested grey.

Model health. Check whether every record of the file can be read and whether it matches its IFC schema, apart from the index.

Pictures in BCF. Each BCF viewpoint comes with a picture of its elements, drawn from the 3D view.

The sample model. Run a complete check on the sample model with IFC Checker's sample checks, with nothing of your own.

Saved results and a share link. Save a check's results and send a read-only link that opens them.

Release notes. One dated page of what changed in each version, on the Workflows and help page.

IDSxAI. Additional tests that IDS cannot express, kept in a file of their own beside your IDS and marked as not part of it.

Accounts and projects. Sign in and keep a project's models, tests and checks together.

An AI panel in the app. A panel beside every page that sees what is on screen and uses the same actions as the buttons, while the engine decides pass or fail and the AI explains what fails and drafts requirements.

A BCF topic server. Keep a project's BCF topics on a server, with an API and webhooks, so every tool sees and answers the same topics.

A Revit plugin. Check directly from Revit and take the round trip of the parameter checks, writing the corrections you accept back into the model.

A desktop app. Check models larger than the web version can, and each new export that lands in a folder you choose.

The phone version. Choose a model, run a check and read the results on a phone, with the numbers first and the details on request, within a size limit measured on real phones.

Plugins for more authoring tools. The same round trip and write-back in two more authoring tools, after the first.

An MCP connection. Connect your own AI assistant to IFC Checker (through MCP), so it can read your results and use the same actions as the buttons, while the engine decides pass or fail and the AI explains what fails and drafts requirements.

Document Checker. The start of Document Checker, which cross-checks documents against each other.

Clash Engine. The start of Clash Engine, an AI-driven clash detection engine that connects to your software and works from inside it.

A PDF report. The results as a report to send with a delivery.

Building-code checks. Checks against building codes are not planned before late 2027.