Revit model health checks: a routine, not a rescue

Why a routine beats a rescue

When a model becomes slow or unstable, the usual response is an emergency cleanup just before a deadline. That is the worst time to do it: the team is under pressure, the cause is unclear and changes are risky. A routine health check, run on a schedule by someone who knows what to look for, spreads the effort and catches trends early.

This guide describes what to check, why it matters and a simple rhythm. Exact thresholds depend on your projects, hardware and network, so the aim is to watch for change over time rather than chase a universal number. Record a few values at each check and look at the trend.

What to record each time

A small health log, kept for each major model, makes trends visible. Useful values include:

• File size of the central or main model.
• Number of warnings.
• Number of imported CAD instances and linked CAD files.
• Number of views, and how many are not on sheets.
• Number of in-place families and model groups.
• Typical open and synchronize times reported by the team.

None of these is a problem in itself. A steady rise without an obvious reason is the signal to investigate.

Warnings

Revit records warnings for conditions such as overlapping walls, duplicate instances, room separation issues and elements that cannot be kept joined. Individually, most are minor. In quantity, they can indicate modeling habits that cause coordination errors and they can contribute to poor performance.

• Review the warning list regularly, grouped by type.
• Fix the most common types first; they often share a single cause.
• Duplicate instances in the same place are worth removing promptly, because they double-count in schedules.
• Treat a sudden jump in warnings as a sign that something changed, such as a new link or a team member's workflow.

Imported and linked CAD

CAD content in a Revit model is one of the most common sources of clutter. Each import can add layers to object styles, and exploded imports can add many line styles, text types and fill patterns that do not follow your standard.

• List all imported and linked CAD files and check whether each is still needed.
• Prefer linking over importing for reference content, and keep links in a known location.
• Remove imports that were used once for reference and forgotten.
• Check for line styles, text types and patterns that were created by imports and are not part of the standard.
• Where CAD details must become native content, convert or redraw them in a controlled way rather than exploding them in the production model. The detail migration strategies guide compares the options.

Purging unused content

Purge Unused removes families, types, materials and other content that is not used in the model. Run it periodically, but carefully:

• Do not purge types that the team intends to use later in the project, such as standard wall types placed in later stages. Review the purge list rather than accepting everything.
• Never purge a project template blindly; its unused types are often there on purpose.
• Some items need several purge passes, because removing one item can make others unused.

Families, in-place families and groups

• Heavy families: check the largest loaded families. Overly detailed manufacturer content is a common cause of slow views. The family QA checklist helps prevent this.
• In-place families: useful for one-off conditions, but each is unique and cannot be scheduled or reused consistently. Many in-place families often indicate missing loadable families.
• Model groups: useful for repetition, but large or nested groups can make editing slow and generate errors. Check for groups that are no longer repeated and could be ungrouped, and for unused group types.
• Design options: remove options that have been decided, so the model does not carry abandoned alternatives.

Views and sheets

Views accumulate quickly: working views, duplicates for one meeting, abandoned studies. Each view has some cost, and a crowded project browser makes it harder to find the views that matter.

• Review views not placed on sheets, and remove those no longer needed. Agree with the team first.
• Check that sheet views use assigned view templates; see the view template strategy guide.
• Look for views with large numbers of manual element overrides, which are hard to maintain.
• Remove unused legends, schedules and drafting views that duplicate library content.

Links and worksharing

• Check that all linked Revit models load from the agreed location and are the expected versions.
• Remove links to superseded models.
• Confirm that links and their positions use shared coordinates as agreed in the BIM execution plan.
• In workshared models, check that elements are on sensible worksets and that worksets are not used as a substitute for categories or phasing.
• Encourage regular synchronization and remind team members to relinquish elements they no longer need.
• Periodically create a fresh local copy rather than reusing very old local files.

File maintenance

Revit offers maintenance options when opening and saving models, such as auditing a file on open and compacting a central model. These can help with file size and stability. Use them on a schedule and with care: make a backup first, coordinate with the team when working on a central model, and check the official documentation for your version before relying on a specific option.

Reporting results to the team

A health check only helps if the findings reach the people who can act on them. Keep the report short and specific: a few headline measures compared with the last check, the three or four issues worth fixing now, and who will fix each one. Avoid long lists of every warning; they are rarely read.

Present results without blame. Many issues come from template gaps, unclear standards or schedule pressure rather than individual carelessness. When the same issue appears on several projects, it usually points to something the standard or the library should change, which is more useful than asking each team to fix it repeatedly.

Checks before milestones and exchanges

Some moments deserve a fuller check than the routine one:

• Before issuing drawings, confirm sheets use the correct view templates and there are no stray imported styles.
• Before sending models to consultants or clients, remove unused content, confirm shared coordinates and check links, so the recipient gets a clean file.
• Before archiving a stage, record the measures so the next stage has a baseline.
• After a large import or conversion, such as bringing in a batch of details, check for new styles, patterns and types that do not follow the standard.

A practical rhythm

Keep the weekly check short enough to finish in a fixed, small amount of time. If it regularly takes longer, the project needs a deeper cleanup at the next milestone.

Prevention through standards

Most health issues have upstream causes: a template without standard types, a library without QA, no rule on CAD imports. Each finding from a health check is an opportunity to improve the standard so the problem does not recur.

• Repeated non-standard line styles from imports suggest a migration rule and a layer mapping.
• Repeated heavy families suggest a stricter library gate.
• Repeated view clutter suggests a working-view convention.

Tools that create native content using your existing types, rather than bringing in new ones, also help. For example, Codex converts DXF details into drafting views using the project's existing line styles, text types and filled region types instead of leaving exploded CAD imports behind.

Health check checklist

• Health log with file size, warnings, imports, views, groups and in-place families.
• Warnings reviewed by type; duplicates removed.
• CAD imports listed, justified or removed.
• Purge reviewed, not accepted blindly.
• Heavy families, in-place families, groups and design options reviewed.
• Unused views removed with team agreement.
• Links, coordinates and worksets checked.
• File maintenance done with a backup.
• Findings fed back into templates and standards.