This will take one to three days. In my opinion, there's no way around it. The exercise requires a pause in production. A convenience you likely don't have, considering the project is probably live.

Here's what's likely. Eight to twelve focused hours on a detached model, whilst no one progresses work on the central file. The updated model will eventually replace the existing central file. It's probably a weekend or three evenings. I know it has been for me. I'll leave it to you to decide whether the sacrifice is worth it.

It might be if a slow model is forcing you to work evenings and weekends anyway.

• Rule one: take a backup and keep it until the job is signed off. Not the automatic `.rvt.0001` backups. A dated copy, in a folder, that you control.

• Rule two: record the baseline. Cleanup without measurement is decoration. You need before-and-after numbers to justify the day you spent, and to prove the model is improving rather than drifting.

• Rule three: do the work on a detached copy, then bring it back as the new central. Cleaning a live central file while six people are synced into it is how you turn a messy model into a lost one.

Tell the team the model is locked for the duration. 8 to 12 hours of nobody working beats a week of recovery.

Open the file and spend ten minutes writing down nine numbers. This is your baseline sheet. It takes longer to explain than to do.

Autodesk's long-standing rule of thumb is that Revit wants roughly twenty times the compacted central file size in available RAM. A 600MB model on a 16GB machine is not a Revit problem. It is an arithmetic problem.

If your team runs models in Autodesk Docs, Model Analytics now does most of this for you. It ships inside Forma Insight. It reports sync times, file size growth, Revit minor version mismatches across the team, and content trends like CAD imports and in-place families. It is included with Design Collaboration subscriptions, so check whether you already own it before buying a dashboard.

Write the nine numbers down. You will need them at Step 11.

Close the model. Now reopen it with two boxes ticked.

• File > Open > select the central file
• Tick Audit
• Tick Detach from Central, and choose Detach and preserve worksets
• Open the file with all worksets closed if it is slow to open

Audit checks the model database for corruption and repairs what it can. It is slow on a large file, so start it and go and make a coffee. Run it whenever you take on a model you did not build.

If the audit fails or the file will not open, jump to the corruption triage section near the end, then come back here.

Save the detached file as a new local working copy with a dated name.

Every step from here happens in this file.

Manage tab > Warnings. Export the list to HTML so you have a record, then sort it.

Most teams get this backwards. They start at the top of the dialog and work down. So the first hour goes on room tag warnings, while the constraint failures sit untouched. Warnings are not equal. Triage them.

A model with four hundred warnings and no duplicates is in better shape than a model with sixty warnings where twelve are constraint failures. Count matters less than composition.

Two working notes. Duplicate instances are the highest-value fix on the list because they distort quantities, and quantities become someone's cost plan. And do not delete a warning by deleting the element until you know what the element does. Warnings tell you where the model disagrees with itself, not where the rubbish is.

For bulk repeat warnings, use Dynamo or pyRevit rather than clicking. Off-axis walls and duplicate marks are exactly the kind of repetitive fix a script does in seconds.

Set a target before you start. Getting to zero is a fantasy on a live project. Getting under fifty, with no items from the Fix First band, is realistic in an afternoon.

Imported CAD is the single worst thing in most messy models. Not linked CAD. Imported.

An import brings every layer, every hatch, every block definition and every text style into the Revit database and keeps them there. If somebody exploded it, you now have thousands of individual Revit line elements that purge cannot see and nobody can select.

• Manage tab > Manage Links > CAD Formats. In Revit 2026 this dialog now shows imported CAD as well as linked, which makes the audit far quicker than it used to be.
• Insert tab > Import CAD is where they came in. Check for them in every view, including drafting views and legends.
• Delete imports. Do not hide them, do not put them on a switched-off workset. Delete.
• Where you still need the reference, link it instead, and clean the DWG in AutoCAD first with PURGE and AUDIT.
• Never explode a CAD link. Ever.

Then the images. Manage tab > Images shows every raster in the model. A single uncompressed site photograph on a sheet can carry more weight than a floor of walls. Delete what is unused, and replace what you keep with compressed versions or a linked PDF.

CAD imports and raster bloat routinely account for the largest single share of an oversized file. This step alone often does more than everything after it.

Manage tab > Settings panel > Purge Unused.

Purge only removes the top layer of unused content on each pass. A family type sitting inside an unused nested family cannot be seen until the parent is removed. So you run it, save, run it again, save, run it a third time. The third pass usually finds almost nothing, which is how you know you are done.

What purge will not remove, and what you have to do by hand:

• In-place families. Purge cannot touch them. Schedule them, then rebuild them as loadable families or delete them.
• Anything greyed out in the dialog is in use somewhere. Find out where before you go hunting.
• Imported CAD categories. Covered in Step 4.
• Unplaced rooms and areas. Create a schedule filtered to Not Placed, then delete them from the schedule.
• Unused materials, line patterns, fill patterns and object styles, some of which live outside the purge list.

Read the dialog before you click OK. Purge Unused is not fussy about your view templates or your carefully authored title block families if nothing is using them yet. On a live job, use 'Check None' and select what you actually want gone.

Purging unused views, sheets and families is commonly reported to cut 15 to 25 percent off a file. Combined with view deletion and a compact save, teams report 20 to 40 percent.

Families are where messy models hide their weight. One badly authored family, placed two hundred times, is worse than a hundred good ones.

Save the whole library out of the model and sort the folder by size. That single move tells you more in thirty seconds than an hour of clicking.

• Anything over 1.5MB gets investigated. Anything over 5MB gets replaced.
• Look for nested CAD inside families. This is common in manufacturer content and it is a direct import into your model.
• Reduce nesting. Three levels deep is already a problem.
• Strip unused parameters, especially in downloaded manufacturer content.
• Replace high-polygon entourage with simplified equivalents. Furniture from a free download site is often the heaviest content in the model.
• Swap tiny 3D detail, hinges, screws, brackets, for 2D detail components.
• One physical material and one appearance asset per family. No decorative complexity.

Set the rule going forward: no family enters the project without a BIM manager approving it. Free content is not free. You pay for it in sync times for the rest of the project.

Every open view is a live drawing operation. Every saved view carries its own settings.

• Delete every view not on a sheet and not needed for coordination. Be brutal. If it mattered, it would be on a sheet.
• Delete duplicate 3D views. Most models carry a dozen called {3D} with somebody's initials.
• Consolidate legends. Ten legends where three would do is normal and pointless.
• Apply a view template to every remaining view. Not most. Every one.
• Set working views to Coarse detail. Fine is for printing.
• Switch off shadows, ambient occlusion and Realistic mode in working views.
• Use scope boxes and crop regions so views load only the geometry they need.
• Close all windows except one before you save. A 3D view left open costs you memory on every save.

If you inherited a model with no view templates, build a small set and apply them in one pass. Five templates applied to four hundred views beats four hundred views each with bespoke settings.

Your model can be clean and still crawl because of what it is loading:

• Manage Links > Revit. Unload every link you are not actively coordinating against.
• Set link type to Overlay, not Attachment, unless you have a reason. Attachment pulls nested links through.
• Check every link is placed by Shared Coordinates, not Auto Origin to Origin.
• Reload links from a controlled folder path, not somebody's desktop.
• Switch off unneeded categories on linked models in your working views.

Then the origin problem. Revit works within a fixed distance limit: all geometry should sit within 10 miles, or 16 kilometres, of the internal origin. The work plane is 20 miles across. Past that limit, Autodesk is explicit that the way Revit displays geometry becomes less reliable and less accurate.

If you have a 'geometry is far from the model origin' warning, it's not cosmetic. It usually arrives with a survey DWG that was drawn on national grid coordinates and imported at origin to origin. Fix it by relocating the project, setting the survey point, and re-linking the survey by shared coordinates. Then tell the whole delivery team what the agreed origin is, in writing, in the BEP.

Coordination failures are more expensive than file size failures. This step earns its place.

Worksets are not layers. They were never layers. Fifteen years of people treating them as layers is why your sync takes eight minutes.

Their actual job is visibility control, collaboration ownership and performance. That is the whole list:

• Split by discipline, zone or system. Not by category, and not by whoever created the element.
• Kill Workset 1 as a dumping ground. Move its contents into real worksets with a schedule and a filter.
• Give every Revit link its own workset so it can be closed at open.
• Delete empty and orphaned worksets.
• Set worksets to closed by default at open, so the team loads only what they need.
• Make sure nobody is holding elements. Relinquish all before you finish.

Set the workset structure once, write it into the BEP, and audit it monthly. Closing unneeded worksets at open is one of the cheapest wins available on a federated job.

The last sweep before you compact. These are the items most cleanups skip:

• Model groups. Useful in repetitive residential work, destructive everywhere else. Where a group has excluded members or attached detail groups nobody understands, ungroup it or convert it to a link. Autodesk's own long-standing guidance is to prefer families over groups where the choice exists.
• Design options. Delete the ones that lost. Keeping the abandoned scheme 'just in case' costs you on every regeneration. If a variant needs to survive long term, park it in a separate linked file.
• Phases and phase filters. Check nothing is stranded in an unused phase. Elements in a phase that no view displays are still elements.
• Arrays. Once a parametric array is placed and settled, ungroup it to drop the association.
• Unplaced rooms and areas. Schedule them, filter to Not Placed, delete.
• Duplicate line styles, text types and dimension types. Consolidate them. A model with forty text types has no standard.

Now save the file with Compact enabled:

• File > Save As > Options > tick Compact File.
• Compacting physically rewrites the file rather than appending to it. On a neglected model this alone has been reported to cut file size by up to 38 percent.
• Recreate the central file from the cleaned model, in the correct project folder, with the correct name.
• Have every user delete their old local file and take a fresh one. This is not optional. Old locals will drag the old data back in.

Then take the nine measurements from Step 1 again and put them side by side.

That before-and-after table is the most valuable thing you produce all day. It gets you the budget for the next cleanup. It proves to a project director that model hygiene is a cost, not a hobby.

If you want a second opinion on the result, run the free Autodesk Model Checker for Revit. It runs on Revit 2022 to 2026, ships with dozens of ready-made checksets, and produces a compliance report that points at the offending elements. As of version 10.0 the API is no longer supported. Build custom checks in the Configurator rather than scripting against it.

Sometimes the model is not messy. It is broken. The signs: a file that fails to open, an audit that errors out, an element that throws the same error whatever you do.

Work through this in order:

1. Open with Audit ticked. If it fails but the file opens without auditing, you are probably looking at a corrupt loaded family.
2. Find the family. Save each suspect family out via File > Save As > Library > Family and watch for a 'family cannot be saved' warning. That is your culprit.
3. Delete the corrupt family from the Project Browser, replacing it with a healthy version first if the project needs it.
4. If the file still will not open, open it with all worksets closed and every link unloaded, RVT, DWG, IFC and PDF. Save. Reopen with Audit.
5. Reload links one at a time, auditing between each. This isolates which link carries the problem.
6. Audit and purge any DWGs in AutoCAD before you relink them.
7. For Autodesk Docs and BIM 360 models, clear the local Desktop Connector cache before you conclude the model is at fault.
8. If nothing works, roll back. Restore Backup on a workshared model lets you step to an earlier save. Losing a day of work beats losing a week.

Use eTransmit for Revit to package a model with all its links repathed into one folder. It can also upgrade and purge unused objects on the way through. That makes it a decent way to hand a clean bundle to a consultant.

Everything above is a one-off operation. Without governance, you will repeat it in nine months.

ISO19650 already contains the mechanism. Most firms just never wired it to their Revit workflow.

The relevant part is the collaborative production sequence in ISO19650-2. After information is generated, clause 5.6.3 requires a quality assurance check. It tests the container against the project's information standard and its production methods and procedures. Then clause 5.6.4 requires the information to be reviewed and approved before it is shared. Only then does it move out of the work-in-progress state.

Read that again with a Revit model in mind. The standard already says you may not share a model you have not checked. Nobody enforces it, which is why the mess spreads across the federated model.

Wire it up like this:

• Define the check. Write your model health thresholds into the BEP as acceptance criteria: warning count, file size, zero CAD imports, zero unresolved Fix First warnings, all views on templates. Not aspirations. Criteria. If you are on the client side, these belong in the EIR before tender. Our manual on writing an EIR - https://bimcopilot.com/blog/how-to-write-an-eir-2026 covers where they sit.
• Automate the check. Build a Model Checker checkset that tests those criteria and produces a report. That report is your clause 5.6.3 evidence.
• Gate the status code. A model container does not move from S0 work in progress to a shared status until the check passes. S1 for coordination, S2 for information, S3 for review and comment, S4 and S5 for authorisation and acceptance, then A and B codes once published. Confirm the exact code set in your project's own information standard, because they vary.
• Name the container properly. ISO19650 naming is what makes the check auditable across the CDE. Our ISO19650 Revit family and file naming guide - https://bimcopilot.com/blog/iso-19650-revit-family-naming-conventions-2026 covers the field structure.
• Put it in the MIDP. If model health checks are not scheduled against delivery milestones in the MIDP and the task team TIDPs, they are voluntary. Voluntary means they will not happen in month eleven.
• Assign the owner. One named person per information container. The standard assumes a task team information manager exists. Most projects never appoint one

That is the whole trick. You are not adding process. You are using the process you already signed up to in the BEP, and giving it a measurable pass mark.

Our guide to writing a BEP that does not get rejected - https://bimcopilot.com/blog/how-to-write-a-bep-that-doesnt-get-rejected-2026 covers where these criteria sit in the document.

Print this. Put it in the BEP.

The pattern that works is not heroic. It is small, dull and repeated. A model purged weekly barely grows. A model purged annually needs a manual like this one.

Use these as starting thresholds and tune them to your project type.

A model in the red on three or more rows is not going to be fixed by a plugin. It needs the eleven steps above.

How long does it take to clean up a messy Revit model?

• A single-building model takes one focused day. Add half a day to rebuild the central and get the team back in. Federated projects with multiple task teams take a week, mostly because of coordination.

How do I reduce Revit file size quickly?

• In order of return: delete imported CAD and raster images. Delete views not on sheets. Purge three times. Replace oversized families. Save with Compact File enabled. Teams commonly report 20 to 40 percent reductions from that sequence.

Does Purge Unused delete things I need?

• It removes only unused content, but 'unused' includes families and view templates you have loaded for later. On a live project, use Check None and select deliberately. Always back up first.

How many Revit warnings are acceptable?

• Composition matters more than count. Under 50 is a good target. But 300 annotation warnings with no constraint failures beats 40 warnings that include duplicate instances.

Should I use groups or links for repeated units?

• Groups perform better at high instance counts and edit in place. Links are simpler to manage and harder to break. Choose by team capability, and never mix both approaches on the same project.

What is the Revit distance limit from the origin?

• All geometry should sit within 10 miles, or 16 kilometres, of the internal origin. Beyond that Autodesk states graphical accuracy becomes unreliable.

Can AI clean up a Revit model?

• It can audit one. Revit 2027 ships Model Analytics and an Autodesk Assistant tech preview, and connectors exist for earlier versions. The investigation is now fast. The decisions and the deletions still need a human who knows the project.

Is the Autodesk Model Checker still available in 2026?

• Yes. It is free, supports Revit 2022 to 2026, and ships with prebuilt checksets. The API is no longer supported as of version 10.0, so use the Configurator for custom checks.

If you are reading this with a 900MB file open and a deadline on Friday, you do not need a manual. You need someone to do it.

We take the model and run the full eleven steps. We rebuild the central. You get it back with a before-and-after report your project director can read.

What we fix:

• Bloated files that open in minutes instead of seconds
• Warning backlogs nobody has touched in a year
• Imported CAD, exploded linework and oversized entourage
• Broken links, wrong origins and failed shared coordinates
• Workset structures inherited from a project that ended in 2022
• Corrupt families and models that will not open
• The absence of any standard that would have prevented it

→ Book a Model Rescue Audit with BIMcopilot - https://bimcopilot.com/services

And if the real problem is that nobody wrote the rules, the ISO19650 Compliance Pack - https://bimcopilot.com/product covers it. BEP, EIR, MIDP and TIDP templates. Naming convention spec, responsibility matrix, compliance checklist. That is the governance layer from the section above, ready to use.

• Revit Running Slow in 2026? 18 Proven Performance Fixes - https://bimcopilot.com/blog/revit-performance-18-fixes-2026)
• ISO19650 Fully Explained: The 2026 BIM Information Management Guide - https://bimcopilot.com/blog/iso-19650-made-simple-bim-2026)
• How to Write a BEP That Does Not Get Rejected - https://bimcopilot.com/blog/how-to-write-a-bep-that-doesnt-get-rejected-2026)
• How to Write an EIR (Exchange Information Requirements): The 2026 ISO 19650 Manual - https://bimcopilot.com/blog/how-to-write-an-eir-2026)
• ISO19650 Revit Family Naming Conventions - https://bimcopilot.com/blog/iso-19650-revit-family-naming-conventions-2026)
• Speckle for BIM Managers: Getting Your Revit Data Out of the File - https://bimcopilot.com/blog/speckle-for-bim-managers-2026)