What's on the audit checklist by default?

The default Revit model audit checklist covers file size, Revit version, and whether the file is a true central model with recent syncs. It inspects warnings count and the most common warning types, view and sheet counts, and family counts split between loaded and in-use. It also checks worksharing setup, linked Revit and CAD files, imported geometry, purgeable elements, and high-level view-template adherence so BIM Managers see a consistent health baseline across projects.

Can we customise the checklist?

Yes, checklist customisation is part of the Beta engagement so your BIM team can add project- or firm-specific items. The default set stays focused on universal Revit model health, while naming standards, view-browser structure, and sheet conventions belong in the dedicated Revit standards enforcement workflow. During onboarding, we map which checks belong in the health pass and which live in standards, so your reports stay readable and actionable.

How long does an audit take?

Audit duration depends on model size, linked-file complexity, and Revit version, but the agent runs in the background once triggered. Manual audits typically consume 2–4 hours of interactive BIM Manager time per model, spread across dialogs and spreadsheets. With the checklist automated, interactive time drops to single-digit minutes per typical model, and each Beta deployment ships a per-project runtime report calibrated to the customer’s pipeline.

Does it auto-fix issues or only flag?

The model audit checklist primarily flags issues with clear measurements and locations, so BIM Managers can decide how to respond. Some categories, like purgeable elements and warning patterns, pair naturally with automated cleanup using the Revit warnings cleanup workflow. Structural topics such as linked-file paths, worksharing setup, or view-template coverage stay as flagged items with remediation notes, because they often involve project-specific decisions or coordination with other teams.

Who is in the Beta cohort?

The Beta cohort consists of 1–3 design partners running a weekly or bi-weekly model-audit cadence on live production projects. Cohort criteria include Revit 2023 or later on Windows, a BIM Manager or digital practice lead available for a short checklist-design sprint, and at least one multi-model project where central models, links, and worksharing are actively used. This ensures feedback covers both single-discipline and coordinated models, not just small test files.

Use Case Beta

Revit Model Audit Checklist

The Revit Model Audit Checklist runs an automated end-to-end model health check on the central model, covering file size, warnings count, view counts, family counts, worksharing structure, linked files, imported CAD, purgeable elements, and naming sanity. The Studio QA/QC Agent produces a citable health report per run and is currently shipping with 1–3 design partners.

Run an end-to-end model audit on the central model with every checklist item scored, documented, and pinned to specific elements where applicable.
See trend reports across audits that show whether model health is improving or degrading project-over-project and across teams.
Export a citable health report ready for BIM-manager review, weekly status meetings, or project-handover gates and archives.

Apply to the beta See capabilities ↓

How it works

From hand-walked checklist audits to one-click model-health reports.

Workflow today

01

Open the central model

For each audit, the BIM Manager opens the central model, waits through the full load, and watches file size and warnings count as Revit spins up. Large linked models and heavy imported CAD stretch this to the upper end of the 5–10 minute range. Any crash or failed sync often restarts the entire process.

Per audit · 5–10 min
02

Walk the audit checklist

The BIM Manager walks the audit checklist item by item: file size, total warnings, repeated warning types, view counts, sheet counts, family counts, worksets, linked files, imported CAD, and purgeable elements. Each check is a separate Revit operation across dialogs like Manage Links, Worksets, and Purge Unused, so a full pass takes 2–4 hours per model.

Per audit · 2–4 hrs
03

Note findings

Findings are recorded manually in Excel, OneNote, or a wiki page, with columns for date, Revit version, file path, and issues. Consistency depends on the same BIM Manager using the same template every time. If someone forgets to log a metric like view-template coverage or central-model status, that gap makes cross-audit comparison unreliable.

Per audit · 30–60 min
04

Email findings to the project team

The BIM Manager emails the audit notes to the project team, often as a spreadsheet or pasted bullets. Designers reply inline, so the history fragments across threads. Resolution lags days to weeks, and the BIM Manager re-explains concepts like purgeable families, linked-file paths, or worksharing expectations on every cycle.

Per audit · 30 min
05

Repeat next month

Audit cadence varies: some teams run a check at project start and pre-issue, others only before handover. Mid-project models often go un-audited for months, so linked-file bloat, unused views, and warning buildup surface as late-stage surprises. Worksharing issues that should have been caught by a Revit worksharing workflow stay buried until a critical deadline.

Periodic

Workflow with VitruAI

01

Run the agent

For each audit, the BIM Manager triggers the Studio QA/QC Agent against the central model inside Revit. The agent walks the full Revit model audit checklist in the background, covering file size, warnings, view and sheet counts, family usage, worksharing structure, linked files, imported CAD, and purgeable elements. Interactive time drops to single-digit minutes per typical model.

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

Review the health report

On Day 1, the BIM Manager opens a structured health report that lists each checklist item, the measured value, and a pass/fail status. Where issues are element-level, the report includes specific element IDs and view names so the team can jump directly to the problem in Revit. High-level items like central-model status, sync history, and workset configuration appear as project-level checks with clear remediation notes.

Day 1 · ~15 min
03

Trend across audits

Each audit run is timestamped and tied to a specific model path, Revit version, and project code, so trend charts show whether warning counts, purgeable elements, and file size are improving or drifting. BIM Managers can compare health across projects, or before-and-after a Revit warnings cleanup effort. The same checklist structure makes quarterly portfolio reviews repeatable instead of anecdotal.

Per project
04

Hand over with confidence

Pre-handover, the team runs a final audit and attaches the health report to the deliverable package alongside any Revit standards enforcement checks. The report documents rule-by-rule evidence that the model met the agreed health baseline on a specific date, including linked-file status and purgeable element counts. Owners and downstream consultants receive a model with a clear audit trail instead of a one-line “model reviewed” email.

Per project

What the Revit Model Audit Checklist covers

The Revit Model Audit Checklist focuses on universal model-health items that apply across firms, templates, and sectors. It runs inside Revit 2023+ on Windows and inspects the live central model, not a detached copy, so worksharing status and sync behaviour are captured accurately. The same checklist structure works whether the model originates in a native Revit workflow or passes through a VitruAI + Revit integration path.

File characteristics: RVT file size, Revit version, central vs local, sync-with-central recency.
Warnings: total count, top repeated warning types, views with concentrated warnings.
Views and sheets: total views, placed vs unplaced, detail vs model views, sheet count.
Families: loaded vs in-use counts, nested families, heavy families flagged by instance count and size.
Worksharing: workset count, model vs view worksets, non-editable worksets, user ownership anomalies.
Linked files and imports: Revit links, CAD links, images, path types, unloaded vs missing links.
Purgeable elements: unused families, line styles, fill patterns, view templates, and other purge-ready items.
Naming sanity: obvious outliers in view, sheet, and workset names that complicate coordination and search.

Firm-specific rules, such as project browser organisation or naming patterns for views and sheets, sit in the Revit standards enforcement workflow. The model audit checklist stays focused on model health, while standards and Revit worksharing hygiene checks layer on top for a complete QA/QC stack.

Common questions