From IFC model to review report

Try the guided sample

Select Try a sample on the starting screen or in the Help menu. A separate tab opens with an original, fictional IFC4 model, matching training IDS requirements and the General IFC Quality Review profile. Your existing model tab stays intact. The sample is not a buildingSMART reference model or a real project.

1. Wait for Sample ready, then select Run checks.
2. Open the IDS tab. Expect one PASS, one FAIL and one NOT TESTED. The validator calculates these results from the sample files.
3. Named doors on a building storey — PASS: both doors have names and are contained on Ground floor.
4. Doors need a 90-minute fire rating — FAIL: DOOR-01 has FireRating 90; DOOR-02 deliberately has 30. Select the finding description or DOOR-02 in the Model tree to locate it. The simplified Properties tab shows basic identity, while the sample IFC includes the fire-rating values.
5. Door names follow a pattern — NOT TESTED: the rule uses a pattern constraint that this version does not evaluate. Even though the example names fit the pattern, the app must not claim a pass.
6. Return to Findings to see the IDS issue and additional baseline findings, then select Export findings JSON to save the review with open issues.

Practice exporting a QA PDF

For this fictional training run only, you can practice documenting accepted exceptions: use Verify on each finding, enter a reviewer name and an explicit note such as “Training exercise only; this issue is intentionally retained in the fictional sample.” Save each verification, then Acknowledge locally and select Export → Export QA PDF. Failed and untested IDS results remain in the report. This does not fix the model or approve any real project.

On a real project, correct the source model and rerun checks, or document only exceptions that are actually accepted. Never waive a real issue just to unlock PDF export.

The walkthrough offers downloads of the sample IFC and IDS. To start your own review, return to the original viewer tab or use Open an IFC model (or Replace in the model panel) in the sample tab; opening your own model removes the automatically loaded training IDS. Import your project's IDS separately if needed. Changing the profile or IDS hides the sample tips because the expected results may change.

Prepare and open a model

Have your .ifc model ready. Export native authoring files, such as Revit files, to IFC before using BIM Validate. Start with a small model for your first review; large files can take longer and use substantial browser memory.

In the viewer, select Open an IFC model (or Replace in the model panel). Wait for loading to finish and check the status message at the bottom of the model view. Use Fit view if the model is outside the visible area.

Models and imported IDS files are processed locally in your browser by this viewer. An internet connection is needed to load the app and its supporting libraries. Keep your original files; the viewer does not edit the IFC.

Choose your requirements

The QA profile determines the baseline and client checks. Start with General IFC Quality Review unless your project specifies a different profile. Other starters cover selected buildingSMART information conventions, ISO 19650 delivery information, infrastructure and example owner requirements. Choose one that matches your intended delivery.

Use a client profile

1. Select Manage profiles.
2. To adapt a starter, choose Clone current profile. Use the form to set project units, coordinate requirements and rules, then select Add requirement to profile for each new rule.
3. If your client supplied a JSON profile, choose Import JSON profile instead.
4. Review the settings and choose Save client profile. Close the dialog and confirm the intended profile is selected.
5. Use Download JSON profile to keep or share a copy.

Saved profiles stay in this browser only. A JSON profile is a BIM Validate configuration; an IDS file is a separate information-requirements document. Neither file substitutes for the other.

Add an IDS file

An IDS (Information Delivery Specification) describes information expected in the model. If your project provides one, select Import .ids and choose the file. The importer accepts IDS XML files up to 1 MB. Open the IDS tab to inspect the specifications, then run checks.

The selected QA profile and the imported IDS are both evaluated. Use Remove IDS when you no longer want that specification included. Changing the model, profile or IDS clears the previous review results and acknowledgement; run checks again.

What is covered?

v1.6 supports selected attribute, single-value property, classification and relationship checks, including spatial containment, plus selected text and numeric restrictions. Supported optional requirements permit absent information while checking present values. Support is limited by the exact facet, datatype and relationship used.

Patterns, materials, predefined-type constraints, many datatype/unit comparisons and other unsupported features make the affected specification NOT TESTED. Read the reason shown for each specification. The technical coverage notes give the detailed scope.

Choose Requirements to select your QA profile, manage profiles and import an optional IDS. The panel folds after checks complete; reopen it to change requirements. Fit view, zoom, select and pan are grouped inside the model viewport. Export options appear after a check run; the QA PDF stays unavailable until local acknowledgement is complete.

Run and inspect checks

Select Run checks and wait for completion. Review each panel:

• Findings: errors, warnings and information from the enabled checks. Read the description, affected count and example identifier.
• IDS: per-specification outcomes and reasons, when an IDS file is loaded.
• Properties: select an element in the model tree or 3D view to inspect its information. Clicking a finding description selects its first sample when one is available.
• Coordinates & units: review the units and coordinate reference declared in the IFC. These values are not an independent survey check.

Use the model tree to locate elements. Select, Pan, the zoom buttons and Fit help you navigate. Click a face of the orientation cube to change the viewing direction.

Find and share issues

Use Export → Export issue list CSV after any check run, including reviews without an IDS. In the IDS tab, use Show results to filter PASS, FAIL, NOT TESTED or NOT APPLICABLE. Supported attribute and property failures show expected and actual values. Select Show element to inspect the affected element in the model. Some elements have no visible geometry.

Export issue list CSV saves all failed and untested IDS results plus baseline findings, regardless of the selected filter. This export is available before local acknowledgement. Evidence is sampled: at most 32 failed requirements per specification and 8 recorded values per requirement. Long evidence values and requirement descriptions are shortened and marked; consult the source IFC and IDS for complete values. Element IDs apply only to the exact IFC file; use the GlobalId and model fingerprint when coordinating corrections. Unsupported features remain NOT TESTED. CSV and JSON contain the BIM Validate name; the QA PDF and this guide include the supplied logo.

Understand the results

Finding severities (ERROR, WARNING, INFO) indicate issues to review. Finding states (OPEN, VERIFIED) track the local review record. VERIFIED does not mean the model was corrected or that an IDS failure became a pass.

Record your review

If a finding identifies a problem, correct it in the authoring software, export a revised IFC, open that file and run checks again.

If an exception is acceptable for your project, record that decision explicitly:

1. On the finding, select Verify.
2. Enter the reviewer name and a meaningful justification or evidence note (at least eight characters).
3. The available disposition is Waived / accepted exception with documented justification. Choose Save verification only when that accurately describes the decision.
4. Repeat for any other accepted exceptions. Use Reopen if a decision needs reconsideration.

Once every finding has a recorded disposition, enter your name in Local review acknowledgement and select Acknowledge locally. If there are no findings, you can acknowledge after the run completes and the model fingerprint is available.

Export and keep records

• Export findings JSON: available after checks complete, including while findings remain open. Save it to share the structured results and review record.
• Export QA PDF: available after local acknowledgement. The report includes the model identity, selected checks, findings, review notes and limitations.

Keep the report alongside the exact IFC, IDS (if used), and client profile JSON. Export records before closing or refreshing the viewer: the current model, findings and acknowledgement are not a persistent project archive. Downloaded reports cannot currently be imported to resume a review.

To save this help document, choose Download guide at the top. For a PDF copy, choose Print / Save as PDF, then select your browser's PDF destination. This prints the guide, not the model's QA report.

8. Save and reopen a review

After running checks, select Save review to choose a filename and project folder in supported desktop browsers. The suggested name includes the IFC model name. Every save opens the picker so you can choose a different project folder. Cancelling leaves your review unchanged. It contains findings, saved reviewer notes, any local acknowledgement, and a copy of the validation profile. Complete or cancel an open verification form before saving. If the browser does not support the file picker, you can enter a filename and use a normal download. Enable “Ask where to save each file” in browser download settings to choose its folder. A fallback download request does not confirm successful saving. If company policy blocks the picker, your review stays in the tab; contact IT about permitted file saving.

The review does not contain the IFC geometry or the IDS file. Keep the original IFC, original IDS (if used) and saved review together. Treat the review file as project information: it includes names and notes. No review is uploaded to a server by this feature.

1. Select Open review and choose a file created by Save review. A findings JSON export is a report and cannot be reopened as a review.
2. Open the original IFC, import the original IDS if used, and select the same profile. For custom requirements, select Download saved profile, then Manage profiles → Import JSON profile → Save client profile.
3. Select Run checks. BIM Validate compares IFC and IDS fingerprints, all normalized profile settings, the engine version and freshly calculated results.
4. If everything matches, saved decisions and any local acknowledgement are restored. If something differs, the message explains what to correct. No saved decision is applied to mismatched results.

Unsaved review appears after a completed check run or changes to reviewer decisions. Save review clears it only after the chosen file finishes writing, or when a fallback download is requested. Cancellation and write errors keep it unchanged. Exporting a report does not save a resumable review. The browser warns before leaving or refreshing with unsaved work where supported; changing models, requirements or rerunning checks also asks before replacing it. Browser and device restrictions may prevent a close warning, so save regularly.

Reopened decisions remain editable and unauthenticated. They are not evidence of an independently verified identity or official approval. The JSON format is not tamper-proof. An engine update or changed results requires a new review.

Troubleshooting