Use Case Roadmap

ArchiCAD Standards Audit

ArchiCAD Standards Audit enforces firm BIM standards inside ArchiCAD by checking Layer Combinations, Element Classifications, Attribute consistency, Library Object hygiene, project-preference drift, and MasterTemplate adherence against a structured rule pack. VitruAI’s Studio QA/QC Agent runs the ArchiCAD rule set per project and is available now as a Labs engagement under MSA + Appendix.

  • Firm-standards violations flagged across Classifications, Attributes, and Layer Combinations, with rule-pack references for each issue.
  • Library Object hygiene reviewed alongside project-side standards so office libraries and project modules stay aligned.
  • MasterTemplate drift detected and reported per project, with a compliance score BIM Managers can track over time.
Join the waitlist See capabilities ↓
How it works

From annual ArchiCAD MasterTemplate spring-cleans to per-project standards reports.

Workflow today

  1. 01

    MasterTemplate published

    Quarterly, the BIM Manager publishes or updates the firm’s MasterTemplate, including Layer Combinations, Classifications, Attributes, Project Preferences, and office-standard Library Objects. New projects start from this baseline, but drift starts on day one as teams copy old projects, import external content, and edit Attributes directly instead of using Attribute Manager.

    Quarterly
  2. 02

    Designers work to internal standards

    On each project, designers try to follow the standards manual, but Layer Combinations, Classifications, and Attributes drift as deadlines bite. Library Object usage varies as people pull content from legacy PLN files, external libraries, or ad‑hoc modules. Module and hotlink structures diverge from the intended pattern, and nobody has time to reconcile everything against the MasterTemplate.

    Per project
  3. 03

    BIM Manager spot-checks

    Periodically, the BIM Manager opens live PLN files and runs manual ArchiCAD-side audits for 2–4 hours per project. They filter by Layer, scan Classifications, and sample Attributes in the Info Box, but high element counts and nested Library Objects mean many violations never surface. Issues that a Revit model audit checklist would catch on the Revit side stay hidden in ArchiCAD.

    Periodic · 2–4 hrs
  4. 04

    Issues flagged via email

    When problems surface, they move by email, chat, or markups on PDFs exported from ArchiCAD. Resolution lag is days to weeks, and the same Layer Combination or Classification mistake appears across multiple projects. Annual MasterTemplate “spring-cleans” clear some drift, but there is no per-project standards report like firms already run with Revit standards enforcement.

    Periodic

Workflow with VitruAI

  1. 01

    Run the agent

    Per audit, the BIM Manager triggers the Studio QA/QC Agent against the ArchiCAD project, typically on ArchiCAD 26 or later. The agent reads the PLN or teamwork file, loads the firm’s rule pack derived from the standards manual, and walks every relevant element, Library Object, and Attribute in single-digit minutes per typical model. Each Beta deployment ships a per-project accuracy report calibrated to the customer’s pipeline.

    Per audit · single-digit-minutes per typical model
  2. 02

    Review violations in ArchiCAD

    On Day 1, the BIM Manager reviews a structured violations list tied back to specific standards-manual sections. Each issue carries the Element ID, current Attribute or Classification, expected value, and the relevant Layer Combination or Project Preference. The report mirrors the style of the firm’s Revit model audit checklist so mixed Revit–ArchiCAD estates can adopt a single QA/QC pattern.

    Day 1
  3. 03

    Auto-fix the auto-fixable, escalate the rest

    Across Day 1–2, Attribute-value violations and Layer Combination drift resolve in bulk via scripted fixes or guided edits, while structural issues such as incorrect Classifications, misused Library Objects, or broken module structures route to the responsible designer. The agent distinguishes between safe batch changes and items that need design judgment, so production teams keep control of geometry and intent.

    Day 1–2
  4. 04

    Per-project compliance score

    After each audit, the BIM Manager receives a per-project compliance score across the ArchiCAD estate, broken down by Classifications, Attributes, Layer Combinations, Library Object hygiene, and MasterTemplate adherence. Scores trend over time so you can see whether a studio, office, or region is converging on the standard. The same scoring framework used for Revit standards enforcement applies, making cross-platform reporting straightforward.

    Per audit
Common questions

ArchicAD Standards Audit — FAQ

  • How does ArchiCAD Standards Audit differ from the Revit version?

    ArchiCAD Standards Audit follows the same workflow shape as the Revit standards workflow but uses ArchiCAD-native concepts instead of Revit categories and View Templates. The rule library targets Layer Combinations, Classifications, Attributes, Library Objects, Project Preferences, and MasterTemplate adherence. For firms already running Revit standards enforcement, this gives a parallel path on ArchiCAD so QA/QC reporting aligns across platforms.

  • Which ArchiCAD versions are supported?

    The Labs engagement focuses on ArchiCAD 26 and later, where most multi-office estates are currently standardised. Older versions are scoped case by case, based on how many live projects still sit on each version and how the firm plans upgrades. During scoping, the team reviews your actual versioned estate and decides which versions to support in the first rule pack.

  • Does the agent handle MasterTemplate adherence?

    Yes, MasterTemplate adherence is a core part of the ArchiCAD standards audit. The agent diffs each live project against the source MasterTemplate, checking Layer Combinations, Attributes, Classifications, and default Library Objects for drift. It then reports deviations with enough detail for the BIM Manager to decide whether to push the project back to the template or update the template to match current best practice.

  • What’s the Labs engagement timeline?

    Typical Labs engagements run 6–10 weeks from kickoff to a working agent against the customer’s first ArchiCAD project. The rule pack is co-built with the BIM Manager and standards team, starting from the written standards manual, existing MasterTemplate, and any current audit checklists. Once the first project is live, additional projects and offices add faster because the core rules and reporting format are already proven.

  • When does this ship as a productised Live release?

    ArchiCAD Standards Audit sits on the roadmap and is available now as a Labs engagement under MSA + Appendix. The timing for a productised Live release depends on feedback and volume from the second and subsequent ArchiCAD design partners. Firms that join the waitlist influence rule-pack priorities and integration depth with the VitruAI + ArchiCAD integration.

More from VitruAI

Related

Adjacent agents, use cases, integrations, and regulations that pair with this one.

Agent VitruAI Labs

Structural Sizing Agent — preliminary member sizing from the architectural model

The Structural Sizing Agent reads the architectural Revit model, applies the firm’s preliminary-sizing rules, and emits concept-stage member sizes — beams, columns, slabs — for early…

IFCRevitGlobal
Agent VitruAI Labs

Document AI Agent — ai document parsing for aec drawings, PDFs, and DWGs

The Document AI Agent extracts structured data — door and window schedules, mechanical components and dimensions, RFI responses, submittal answers, and plan-archive search results — from…

AutoCADIFCRevitGlobalMENA
Agent Live

Comms Agent — AEC project comms agent for meetings to action items

The Comms Agent reads project-meeting transcripts from Zoom, Microsoft Teams, Google Meet, and Slack huddles, extracts decisions and action items with assigned owner and due date,…

Global
Agent Beta

Project Memory Agent — ai project memory for aec, claim-ready timelines on demand

The Project Memory Agent ingests project correspondence, meeting minutes, RFIs, design submissions, change orders, and contract documents into a structured project memory, then produces decision logs,…

BIM 360 / ACCProcoreGlobal
Agent Roadmap

RFI Agent — ai rfi drafting and tracking for aec

The RFI Agent drafts RFIs grounded in the project record—drawings, specifications, prior RFIs, and meeting minutes—and tracks each item’s schedule, scope, and cost implications inside Procore…

BIM 360 / ACCProcoreGlobal
Agent Beta

Contract Agent — ai contract clause monitoring for aec

The Contract Agent reads signed project contracts—owner-architect, design-build, owner-contractor, and subconsultant agreements—and monitors insurance, indemnity, and payment-terms clauses across the project lifecycle. It tracks which clauses…

Global
Agent Beta

Scope Agent — ai scope drift detection for aec projects

The Scope Agent reads the signed contract scope of services and watches RFIs, meeting minutes, design submissions, and email correspondence for asks that fall outside that…

ProcoreGlobal
Agent Roadmap

Clash Review Agent — the BIM coordination AI agent that prioritises the three clashes you need to look at today.

The Clash Review Agent ingests Navisworks and BIM 360 / ACC clash reports with thousands of issues and ranks each clash by cost-of-late-discovery, trade dependency, and…

BIM 360 / ACCNavisworksRevitGlobal
Next step

On the roadmap. Want first dibs?

Join the waitlist