How to Run a Revit Model Health Check (Complete Checklist)

Every BIM coordinator eventually inherits the model nobody wants: 900 MB, 4,000 warnings, forty in-place families, and a survey point that doesn't match the civil DWG. A Revit model health check is the routine that stops a model getting to that state — a repeatable audit you run before every milestone, so problems surface while they're still ten-minute fixes instead of week-long recoveries.

This is the complete checklist. Ten checks, each one you can run in vanilla Revit today, with the why, the how, and — the part most guides skip — what "good" actually looks like so you know when to stop. Work through it top to bottom before a delivery or coordination round, and you'll catch the issues that silently wreck schedules, coordination, and open times. At the end, an honest note on automating the whole Revit model audit in one click.

Grab the one-page checklist (printable) — the CTA at the bottom links to the PDF version you can pin next to your desk.

Before you start

A model health check is a read-only diagnosis first. Resist the urge to fix as you go on the first pass — run the whole checklist, write down what's broken, then decide what's worth fixing before this particular deadline. Half the value is knowing which problems can wait.

The checklist

1. File size

Why it matters: File size is the single best proxy for accumulated neglect. It drives open and save times, sync duration, and how much RAM every team member burns. A model that grew 300 MB in a month didn't gain 300 MB of design — it gained bloat.

How to check it (vanilla Revit): Look at the file on disk, or open Manage → your central/local path. Track it over time — the absolute number matters less than the trend. A sudden jump points at an imported CAD file, a linked point cloud, or an exploded import.

What "good" looks like: No universal number — a hospital central is legitimately large. What's healthy is a size that grows in step with the design, not in spikes. If size jumped without a matching increase in modelled content, something got imported that shouldn't have.

2. Warnings count

Why it matters: Warnings are Revit telling you it did something ambiguous. A backlog of them means data-integrity problems (duplicate instances, broken room boundaries, unsatisfied constraints) are hiding in the model. See the companion article, Revit Warnings, Explained, for the full triage system.

How to check it (vanilla Revit): Manage → Inquiry → Warnings opens the full list. Click Export… to dump it to HTML, open that in Excel, and triage by type — critical (duplicates, rooms, constraints) first.

What "good" looks like: Not zero — a live model always carries some. What's healthy is zero critical warnings and a total that trends down, not up. A rising count is the clearest sign a model is being neglected.

3. Purge unused / unused families and views

Why it matters: Every unused family type, imported line pattern, and orphan view is loaded into memory whether or not it's placed. Unused content is the most common, most reversible source of bloat.

How to check it (vanilla Revit): Manage → Purge Unused lists every unused family, type, group, and pattern. Review the tree before clicking OK — purge is aggressive and will remove content you might want. For unused views, the Project Browser plus a "views not on sheets" schedule (below) is your map.

What "good" looks like: A short Purge Unused list. If it's returning hundreds of items every week, content is being loaded and abandoned faster than it's being cleaned — a process problem, not just a file one.

4. Views not on sheets

Why it matters: Working views multiply. Every duplicated plan, every abandoned 3D view, every section someone cut to check one detail — they all carry view templates, filters, and overrides, and they all cost open time. Views that will never reach a sheet are pure overhead.

How to check it (vanilla Revit): Create a View List schedule (View → Schedules → View List) with a Sheet Number field. Sort by it — every view with a blank Sheet Number is not placed. Now you can judge, per view, keep or delete.

What "good" looks like: A defensible ratio of on-sheet to working views. Some working views are normal and healthy; hundreds of unplaced duplicates named "Copy of Copy of Level 1" are not.

5. Worksets

Why it matters: A coherent workset structure is what makes a federated model workable — it controls what loads, what's visible, and who owns what. Worksets that don't match the team's agreed standard cause elements to land in the wrong place and links to load when they shouldn't.

How to check it (vanilla Revit): Collaborate → Worksets lists them all. Check names against your BEP standard, confirm no rogue user-created worksets, and verify default open/close behavior. Watch for elements sitting on the wrong workset.

What "good" looks like: Worksets that match the project standard exactly, with sensible defaults for what opens on load. Consistency across the team's models matters more than any particular scheme.

6. Linked models & coordinates

Why it matters: Links are how a federated model comes together — and shared coordinates are how the pieces line up. A single link on the wrong survey point or project base point puts an entire discipline in the wrong place, and you often don't notice until clash detection or a site plan is visibly wrong.

How to check it (vanilla Revit): Manage → Manage Links shows every linked Revit, CAD, and point-cloud file and whether each is loaded. For coordinates, use Manage → Coordinates → Report Shared Coordinates and pick a point in each link to confirm it reads the values you expect. Cross-check the survey point, project base point, and true north against your project's agreed origin.

What "good" looks like: Every discipline link loaded, on the agreed shared coordinates, with survey point and project base point matching the host. One misaligned link is enough to hold a delivery.

7. In-place families

Why it matters: In-place families are convenient and quietly corrosive. Each one is unique geometry that can't be scheduled cleanly, reused, or updated in bulk, and a pile of them bloats the file and slows regeneration. A handful is fine; forty is a smell.

How to check it (vanilla Revit): Filter the model by category, or create a schedule that surfaces in-place elements. The count and their categories tell you whether someone modelled a one-off correctly or is using in-place as a shortcut for content that should be a loadable family.

What "good" looks like: As close to zero as the project allows. Genuine one-offs justify an in-place family; repeated content and anything you need to schedule or quantify should be a proper family.

8. CAD imports

Why it matters: Imported CAD (as opposed to linked) is one of the worst things you can do to a Revit model. It bakes foreign line styles, text, and layers permanently into the file, bloats it, and — if someone explodes the import — floods the model with thousands of ungoverned lines that generate warnings for years.

How to check it (vanilla Revit): Manage → Manage Links → CAD Formats shows linked CAD. To find imported (embedded) CAD, look for it per-view and check the Import categories in Visibility/Graphics. Any exploded import shows up as stray line styles you didn't create.

What "good" looks like: Zero imported (embedded) CAD, and zero exploded imports. Reference DWGs should be linked, kept in one working view, and never exploded.

9. Coordinates & origin (survey point, project base point, internal origin)

Why it matters: This is check #6 taken seriously for the host itself. If your own survey point and project base point aren't set deliberately, every consultant who links your model inherits the ambiguity — and geometry far from the internal origin (a model placed at real-world survey coordinates) causes accuracy and display glitches.

How to check it (vanilla Revit): Reveal the survey point, project base point, and internal origin in a site or plan view (Visibility/Graphics → Site). Confirm they're where your project origin agreement says they should be, and that the model isn't sitting kilometres from the internal origin unintentionally.

What "good" looks like: Survey point, project base point, and origin set intentionally and documented, and the model's working geometry near the internal origin. Everyone linking you gets the same, predictable result.

10. Rooms & areas

Why it matters: Rooms and areas feed schedules that go into deliverables — gross areas, occupancy, program compliance. An unplaced room, a redundant room, or an unenclosed region silently produces wrong numbers, and those numbers often aren't checked until a client or code reviewer catches them.

How to check it (vanilla Revit): Create a Room schedule including Area and sort it. Zero-area rooms are enclosure or placement errors. Cross-check against a room-bounding review of your walls — a wall that lost its Room Bounding setting is a classic cause of a room reading zero area.

What "good" looks like: Every room placed and enclosed, no redundant rooms, no zero-area rows, and area totals that match the design intent.

Where the manual checklist breaks

Run once, this checklist is entirely doable in stock Revit — and you should know how, because the day the tool isn't installed, you still have to deliver. It breaks the same way every manual QA routine does: repetition and coverage. Ten checks across a federated model, before every milestone, every week — that's an hour or two of clicking through ten different dialogs and building the same schedules from scratch each time. When the deadline is tight, the health check is the first thing that gets skipped, which is exactly when the model needs it most.

Automating the audit: Check Model Health (free)

Check Model Health collapses most of this checklist into a single read-only scan. On launch it audits the whole document and opens a dashboard with two panels:

• Model Info — project name, number, client, address, plus file name, model size, Revit version, and worksharing status (checks 1 and 5).
• Model Overview — counted totals, each with its used/unused split, for views, legends, schedules, sheets, families and family types, model groups, in-place elements, worksets, view templates, filters, design options, scope boxes, phases, total elements, warnings, and links & imports (checks 2, 3, 4, 6, 7, 8).

1. On the B45 Labs | Coordination tab, open the QA/QC panel and click Check Model Health. A progress window scans the whole model.
2. Read the Model Overview tiles — each shows a total plus its used/unused split, so unused views, unused families, and in-place counts are right there. The Warnings tile turns red if the model has any.
3. Click a heavier tile — Views, Schedules, Elements, Links & Imports, or Warnings — to open its detailed breakdown. The Warnings breakdown groups and triages the warnings for you and exports to CSV or a two-sheet Excel (.xlsx) workbook (one summary row per warning group, one row per affected element) — see the warnings triage article for the full walkthrough.
4. Export the overall audit as a plain-text report for your milestone record.

It's read-only — it reports, it never modifies — and it audits the host model only, so loaded links are counted but their contents aren't scanned. For the checks it doesn't cover directly, the same free QA suite has the dedicated tools: Check Coordinates does the shared-coordinates audit from check #6 and #9 (survey point, project base point, and true north against every loaded link, flagged Aligned / Not Aligned), and Check Rooms turns check #10 into an editable grid with a Placed / Unplaced / Redundant status on every room. Run in sequence, the three cover the whole checklist, and all of it is free.

FAQ

What is a Revit model health check? A repeatable audit of a model's condition — file size, warnings, unused content, worksets, links, coordinates, in-place families, CAD imports, and rooms — run before milestones to catch problems while they're small. It's diagnosis, not cleanup: you audit first, then decide what to fix.

How often should I audit a Revit model? Before every coordination round or delivery at minimum, and ideally on a fixed weekly cadence. The value is in the trend — file size and warning count falling or holding steady means the model is being maintained.

What's the difference between Purge Unused and a model audit? Purge Unused removes unloaded/unused content — one item on the checklist. A model audit is the full diagnosis across all ten checks, of which purging is one action you might take afterward. Audit first, purge deliberately.

Can I check model size without a plugin? Yes — the file on disk, or the central/local path info in Revit, gives you the number. What a tool adds is the used/unused breakdown that tells you why it's large, in one view instead of ten dialogs.

Get the free tool + the checklist

Check Model Health is part of B45 Labs — a free Revit add-in suite, 50+ commands, no credit card. It's free until 2027 — guaranteed.

• Download free: b45labs.com/download
• Grab the one-page checklist (PDF) and join the founding list for release updates.

Whether you run these ten checks by hand or in one click, run them before the deadline. The model health check that takes ten minutes today is the week you don't lose next month.