> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Check model information

> Build a focused check for missing or inconsistent model data, review exceptions and verify corrections.

QA/QC starts with a clear requirement. Use your BIM execution plan, parameter checklist or schedule requirements to explain what the model should contain. This example checks door information before producing a schedule or exchanging the model.

## Define the check

Open your own project and choose one level. Specify the doors to include, the phase and whether linked models are in scope. Supply the relevant requirements and identify the exact parameters to check, such as **Mark**, door type and fire rating.

State which values are required and where exceptions apply. If a parameter comes from a shared-parameter definition, provide that definition rather than relying only on its displayed name. Ask Ideatura to confirm how each rule maps to the model before running the check.

## Build the checking automation

Start a new chat with the intended Revit document connected. For example:

> Create an automation to check door information on the selected level and phase. Check missing or duplicate Marks, identifiable family and type, and positive width and height. Create or update a Revit QA view listing exceptions with door ID, location and issue. Flag blank fire ratings for review. Preserve existing door values.

Ask for inputs to select the level and scope. Define where Marks must be unique: within a level, building or the whole project. A level-only check cannot establish project-wide uniqueness.

![Generated door-information automation; open its parameters using the marked control.](https://mintcdn.com/ideatura/J00j1ZpJ92MBqCeu/images/qa-qc/model-created.svg?fit=max\&auto=format\&n=J00j1ZpJ92MBqCeu\&q=85\&s=cccac0f6dac99211cf28c34365c18713)

## Test a small scope

Choose a few doors whose values you can verify in Properties or a schedule. Include a complete entry and known exceptions where available. Run the automation, open its QA output in Revit and confirm that it identifies the expected issues. Check that the original door values remain unchanged.

The form below chooses **1 level**, **2 phase** and **3 output name**. Select **4 Run** to create or refresh the QA view.

![Level, phase and output name inputs, with Run marked 4.](https://mintcdn.com/ideatura/J00j1ZpJ92MBqCeu/images/qa-qc/model-controls.svg?fit=max\&auto=format\&n=J00j1ZpJ92MBqCeu\&q=85\&s=83b4664ce8e6f368d7be8fecb488c2db)

Checking that a fire-rating value is present is an information check. Assessing whether that rating is appropriate requires a separate, explicit requirement.

## Review the findings

Keep the chat report short: how many doors were checked, what needs attention and what to do next. Put detailed findings in the QA view, with **element ID, location, parameter and issue**. Separate confirmed issues from missing information and checks that could not be completed.

Inspect the affected doors in Revit. A blank displayed value may involve the wrong parameter or an instance/type mismatch; establish the cause before filling it in. Do not infer ratings or other specification values from appearance.

The tested view below records **79 doors checked and no exceptions**. Running it again updated the same output without duplicates. These findings cover the stated data rules, not the suitability of every door specification.

![Native Revit QA view: 79 doors checked, zero exceptions, and a fire-rating scope note.](https://mintcdn.com/ideatura/J00j1ZpJ92MBqCeu/images/qa-qc/model-result.svg?fit=max\&auto=format\&n=J00j1ZpJ92MBqCeu\&q=85\&s=ac28e102db0a2bbcf63ebdb1a64e0f96)

## Correct and recheck

Provide the approved values or numbering rule and request a correction for the affected elements only. Keep corrections separate from the check: rerunning it should refresh the QA output without overwriting door information.

Rerun the same scope, compare the findings and inspect representative corrected elements. Save the checked automation with its requirements and exclusions. Test it again when using another project; see [Reuse and share](https://docs.ideatura.ai/v2/essentials/automations.md#run-it-again).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.