A model health check looks at the condition of an authoring model itself, rather than its design content: is it set up correctly, does it open quickly, is it free of errors and clutter, can others use it safely? Healthy models are faster to work in, crash less and export cleaner IFC. Checks are usually run by the author or the BIM coordinator before each sharing cycle.
At a glance
| Applies to | Native authoring files (Revit, ArchiCAD, Tekla, Civil 3D…) |
| Run by | Model authors and task team BIM leads, sometimes the lead coordinator |
| Frequency | Before sharing, and on a regular schedule for large models |
| Tools | Built-in audit tools, add-ins and dashboards, scripts |
| Complements | Model checking (content against requirements) and clash detection |
Typical checks
| Area | What is looked at |
|---|---|
| Set-up | Correct template, units, project information, shared coordinates, levels and grids from the agreed source |
| Warnings and errors | Number and type of warnings (overlapping walls, duplicate instances, elements off axis) |
| Size and performance | File size, load time, number of views, groups, imported CAD and images |
| Links | Linked models and files loaded from the CDE, correct revisions, no broken paths |
| Unused content | Unused families, types, materials, view templates |
| Naming | Views, sheets, types and families named to the standard |
| Work sharing | Worksets used as agreed, elements on the right workset, no editable ownership left behind |
| Objects | In-place or generic elements, imported geometry, elements far from the origin |
| Export readiness | IFC mapping present, classification and required parameters filled |
Why it matters
- Performance: a model with thousands of warnings and imported CAD files opens slowly and crashes, costing every user time.
- Reliability: duplicates and overlaps produce wrong quantities and false clashes.
- Coordination: wrong coordinates or levels make federation fail.
- Handover: clean, consistent content is easier to turn into asset information.
Recording health
Many teams keep a simple dashboard per model: warning count, file size, unused families, link status, with a trend over time. A rising warning count is an early sign of trouble.
Common mistakes
- Ignoring warnings until there are too many to fix.
- Importing CAD files instead of linking them, and exploding them.
- Purging content that is still needed by schedules or templates without checking.
- Health checks run only at milestones, when fixes are most disruptive.
Where to read more
Authoring software vendors publish model performance guidance. The project BEP or modelling guidelines set the targets (for example a maximum warning count before sharing).