Studio QA/QC Agent — AI for Revit QA on every model, every revision
The Studio QA/QC Agent runs every BIM Manager’s model-audit checklist against a Revit central model, sweeping warnings, auditing families, enforcing view templates, and tracking worksharing and naming rules. It supports Revit 2023, 2024, and 2025 on Windows and covers warnings, families, views, worksharing, and naming in one run. It is currently shipping with 1–3 design partners as a focused Beta cohort.
- Full audit report against the studio’s Revit standards, generated in single-digit minutes per typical model and calibrated per deployment to the customer’s central-model size and linked-file pattern.
- Every flag pins to the specific element ID, family name, or view template, with the rule it violated and a suggested fix — no generic “clean up the model” comments.
- The same checklist runs the same way on every project and every revision; the BIM Manager owns the rules, the agent does the nagging and documents each decision.
What the Studio QA/QC Agent does.
-
Warnings sweep with element-pinned remediation
Runs a full warnings sweep on the active Revit 2023, 2024, or 2025 central model, classifying issues like Rooms Not Enclosed, duplicate elements, and identical instances in the same place by severity and impact. Pins each warning to the offending element, view, or workset so the assignee can click directly to the problem. Drafts a remediation checklist the BIM Manager can hand to the team or align with the studio’s existing Revit warnings cleanup workflow.
-
Family audit and classification
Walks every loaded family, nested family, and in-place family instance, then flags Generic Models that should be recategorised as windows, doors, casework, or equipment. Proposes the correct category and OmniClass pair based on how the family is used in the model and how the studio’s Revit model audit checklist defines acceptable content. Surfaces orphaned families, unused types, and duplicate families across worksets so the BIM Manager can keep the content library aligned with the studio’s standards.
-
View-template compliance across projects
Compares every view in the project to the studio’s template library, including discipline views, working views, and sheets, and flags any that drift from the assigned template. Detects overrides, missing scope boxes, non-standard view ranges, and visibility settings that break the Revit standards enforcement rules. Groups violations by view template so the team can fix them in batches rather than view-by-view, and records each correction in the audit log for later review.
-
Worksharing and naming-convention check
Runs the studio’s worksharing rules on each audit: one active user per workset, no direct edits to the central model, regular sync-with-central cadence, and version pinning to Revit 2023, 2024, or 2025. Checks naming conventions for files, views, sheets, and families against the studio’s documented patterns, including shared parameter keys where supplied. Reports drift week-over-week so standards do not quietly erode mid-project, and gives the BIM Manager a clear snapshot before major deadlines or VitruAI + Revit exports.
-
Per-project audit log and QA history
Every run writes a timestamped log of what was checked, what failed, what was fixed, and what the team chose to defer, stored per Revit central model. The log captures warning counts by category, family reclassifications, renamed views or sheets, and worksharing rule breaches. The BIM Manager has a defensible record for IPD agreements, JV partner reviews, and end-of-project handovers, and can show how internal QA differed from external checks like the Code Compliance Agent.
-
The Inspector on every model, every revision
This agent personifies The Inspector: every model, every revision, the same checklist run the same way, regardless of who is on deadline. It does the repetitive review that BIM Managers typically run on Friday afternoons, but it runs on every publish set, not just the big ones. For teams already using VitruAI + Revit, it sits alongside the Code Compliance Agent as the internal counterpart to jurisdictional checks.
Studio QA/QC Agent — common questions
-
Which Revit versions does it support?
The Studio QA/QC Agent supports Revit 2023, 2024, and 2025 on Windows, aligned with the same desktop environment as other VitruAI + Revit deployments. Revit 2022 and earlier are not supported because the EV certificate chain and installer hardening are maintained only for current versions. macOS Revit is not on the roadmap, so the Beta cohort assumes a Windows-based production environment.
-
How is this different from Revit’s own warnings list?
Revit’s warnings dialog lists issues but does not prioritise them against your studio standards or show how they affect sheets, exports, or coordination. The Studio QA/QC Agent classifies warnings by severity, ties each one to the relevant standard in your Revit model audit checklist, and proposes element-by-element remediations. It also correlates warnings with families, views, and worksharing rules so the BIM Manager can decide what to fix now and what to accept for the current phase.
-
Can we customise the checklist to our studio standards?
Yes, the Beta deployment includes a two-week setup sprint where VitruAI works with your BIM lead to encode existing standards into the agent’s rule pack. That includes naming conventions, view-template assignments, worksharing rules, and any special checks you already track in Excel or a Revit standards enforcement guide. Each Beta deployment ships with a per-project accuracy report calibrated to your pipeline so you can see how the rules behave on live models.
-
What does “Beta” mean for our studio?
“Beta” means the Studio QA/QC Agent is currently shipping with 1–3 design partners while we finalise the rule authoring tools and reporting surfaces. The cohort is limited to Revit-first studios on 2023 or later, with an internal BIM lead empowered to define standards and willing to share before-and-after audits for a sample of projects. If that fits your profile, you can apply via the “Apply to the Beta” CTA and we will scope a deployment plan around your Revit model audit checklist and Revit warnings cleanup needs.
-
How long does a single audit run take?
Run time depends on central-model size, number of linked files, and family count, so each deployment is calibrated per customer pipeline. A typical ~200 MB central model with common links and standard view counts completes in single-digit minutes, and larger campus models usually stay within the same order of magnitude. Runs are non-blocking, so BIM Managers often schedule them overnight, before major exports, or as part of a weekly Revit standards enforcement cycle.
-
How does this relate to the Code Compliance Agent?
The Studio QA/QC Agent focuses on internal quality rules, while the Code Compliance Agent checks models against external regulations such as the Dubai Villa Code. Both use the same Revit-API plumbing and EV-signed add-in framework, so they can run on the same models without extra setup. Many teams use Studio QA/QC to keep models clean for coordination and documentation, then hand the same models to the Code Compliance deployment for jurisdiction-specific checks.