Check model standards before the issues spread.

When to use this starter

BIM teams repeating the same model review before coordination or handover.

Bring these details

• The Revit categories or element selection to check.
• Your standards or naming rules, with examples that pass and fail.
• How to group issues: by severity, category, or the rule that needs attention.

Shape the first version

1. Check your chosen model elements against the rules you define.
2. Present an issue list that makes the failing rule and affected element clear.
3. Ask for an exportable issue summary when the review needs to leave Revit.

A brief you can adapt

Start with this example, then add your project’s requirements and rules.

Build a read-only Revit QA tool for selected elements. Check their names against the naming rules I provide. List the affected element, the rule that failed, and its severity. Group the issues by category and let me export the summary. Ask me for the exact rules before building.

Check the result before sharing it

• Use examples with a valid name, an invalid name, and a missing value. Confirm the report distinguishes them.
• Check that elements outside the selected scope are not included.
• Compare the reported issue count and grouping with a small manual review.

From your first build to your team

Test your generated app in Revit, refine it in the Builder, and choose the version to deploy. One Desktop Runner install delivers assigned Conduit-built apps to each teammate and keeps them updated.

Your versions stay in Conduit. Every app reports how it’s running for your team, helping Conduit diagnose problems and make improvements.