BIM VALIDATE · BETA

Help shape the next release

beta.3 · engine v1.6 · released 2026-10-19

Try a complete review and tell us where BIM Validate helps, where it is confusing, and where its results need investigation. Start with the guided sample, then use a model you are permitted to test.

Beta 3 — email feedback

Guided workflow navigation, IFC checks, the supported IDS 1.0 subset, saved reviews, and PDF/CSV/JSON exports. Save review now asks for a filename and project folder in supported desktop browsers. Other browsers use a filename prompt and their download settings. Feedback now opens your email app addressed to support@markupvalidate.com, with copy and download options for longer reports. The validation engine remains v1.6.

Start the guided sample ↗

A 20–30 minute test

  1. Open a model. Note your browser, approximate model size, and how long loading takes. Confirm that geometry and the model tree appear.
  2. Choose requirements. Select a QA profile. If you have an IDS file, import it and confirm its title.
  3. Run checks. Record the time and any error. In the guided sample, expect one PASS, one FAIL, and one NOT TESTED in IDS.
  4. Investigate a result. Locate an element, read the expected and actual evidence, and compare it with your source model. Record any disagreement.
  5. Save and reopen. Save your review, reload the app, reopen the same IFC/IDS, and open the saved review. Rerun checks as prompted; confirm your saved notes return.
  6. Export. Try findings JSON and issue CSV. Practice PDF acknowledgement with the fictional sample; do not waive real issues just to unlock a PDF.
  7. Send feedback. Tell us what blocked you, what was unclear, and whether you would use BIM Validate again.

How to interpret the results

PASS means a supported check passed. FAIL means it found a mismatch. NOT TESTED means unsupported or unreadable evidence prevented evaluation; it is not a pass. NOT APPLICABLE means the specification does not apply.

This is an IDS subset, not full schema validation or buildingSMART certification. Remaining gaps include XML Schema patterns, material facets, several relationship types, and numeric datatype/unit semantics. Read detailed coverage ↗. Large-model performance and browser compatibility are part of this pilot.

Your files and feedback

Model checking runs in your browser. The app loads software dependencies from external services. The feedback report includes only the text you enter and the release identity shown above. It does not automatically include model files, filenames, or review notes.

Choose Open email to prepare a message to support@markupvalidate.com in your configured email app, then review and send it there. Short reports are included in the message body. For long reports, copy and paste the full report or download and attach the .txt file manually. Automatic attachments are not supported. If no email app opens, use your usual email service. Omit confidential client information.

What happens next

During a two-to-four-week pilot, we will prioritize incorrect results, crashes, lost work, and blocked workflows before adding features. A broader release should follow successful repeat use with representative models and resolution of critical defects.

Prepare feedback