It’s 4:00 PM on a Tuesday. Your lead architect is trying to sync a central model in Revit for a major project submission tomorrow morning. Instead of a quick update, the software hangs. The "Not Responding" ghost appears. Five minutes pass, then ten. Suddenly, the whole team’s productivity grinds to a halt because the model has become a bloated, unstable mess.
In the world of architecture and engineering, your IT infrastructure isn't just "the computers." It is your production line. When AutoCAD or Revit lags, you aren't just losing minutes; you’re losing billable hours, missing deadlines, and burning out your best talent.
Most firms think the answer is just "buying faster computers." While hardware matters, the way you manage your software and the IT environment it lives in is often the real culprit. At Direct Support, we see these same seven mistakes time and again.
Here is how you can stop the bleeding and get your performance back on track.
1. The "Explosion" of CAD Files
This is the most common sin in the Revit world. You receive a DWG from a consultant, you import it into your Revit model, and you "Explode" it to make it editable.
The Problem: Exploding a CAD file in Revit converts every single layer, line type, and text style from that AutoCAD file into your Revit project. If that DWG had 50 layers, you now have 50 new line styles cluttering your project. Do this five or ten times, and your project browser becomes an unmanageable graveyard of useless data. This bloat forces Revit to calculate more data than it needs to, leading to crashes.
The Fix: Never explode CAD files in your production model. If you need to use elements from a CAD file, open it in AutoCAD first, clean it, and link it. If you absolutely must have the data in Revit, bring it into a separate "clean" Revit family first, then load that family into your project.
2. Importing Instead of Linking
When you bring external data into your project, you have two choices: Import or Link. Many users choose Import because it feels "permanent."
The Problem: Importing a file makes it part of the Revit file itself, drastically increasing the file size. Linking, on the other hand, is like a shortcut. Revit just looks at the external file and displays it. When you import multiple large CAD or Revit files, your project file size skyrockets, making it take forever to open, save, and sync.
The Fix: Link everything. Only import if there is a specific, high-level technical reason to do so. Linking keeps your file size lean and allows you to "unload" the data when you aren't using it, which frees up system RAM instantly. This is a foundational step in optimizing your architecture IT.
3. Ignoring the "Warning" Count
Revit has a built-in warning system. Most users treat it like the "check engine" light on a car: they ignore it until the car stops moving.
The Problem: When you have 500+ unresolved warnings (like "Room tag is outside of room" or "Lines overlap"), Revit has to calculate these conflicts every single time the view refreshes. It’s like carrying a backpack full of rocks while trying to run a marathon. The more warnings you have, the slower your software becomes.
The Fix: Set a weekly "Audit and Warning" time. If your project has more than 100 warnings, it’s time to clean house. Resolving a warning takes two minutes now but saves hours of frustration later in the project lifecycle.
4. Opening Every Workset at Once
For firms working on large-scale projects, worksharing is essential. However, the way you open your model matters.
The Problem: If you open a 500MB Revit file and have every workset (Interior, Shell, MEP, Site) open simultaneously, Revit is trying to hold all that geometry in your computer's RAM. If your hardware isn't top-tier, you’ll hit a bottleneck immediately.
The Fix: Practice "Disciplined Workset Management." Only open the worksets you are actually working on. If you are doing interior layouts, keep the "Site" and "Structural" worksets closed. This dramatically reduces the load on your hardware and makes the software feel snappier. If you find your servers are still struggling to keep up with these syncs, you may need to look at engineering server optimization.
5. Over-Modeling for No Reason
Modern BIM allows us to model everything down to the screws in the drywall. But just because you can doesn't mean you should.
The Problem: High-detail 3D families: like a highly realistic office chair with every bolt modeled: are performance killers. If you have 200 of those chairs in a project, Revit has to render thousands of extra polygons that won't even be visible in a 1/8" scale plan. This is called "Over-modeling," and it’s a direct drain on your firm's efficiency.
The Fix: Use Level of Detail (LOD) standards. Use simple 2D representations for plans and only use high-detail 3D components when necessary for renderings. Keep your models lean and purposeful.
6. Keeping Too Many Views Open
Every time you make a change in a BIM model, Revit has to update every open view to reflect that change.
The Problem: Architects often leave 15–20 tabs open at the top of their screen: sections, elevations, 3D views, and plans. Each of these views stays active in the background. When you move a wall, Revit is working overtime to update all 20 views at once. This leads to that "lag" you feel between clicking and the software responding.
The Fix: Use the "Close Inactive Views" button religiously. Keep only 2 or 3 views open at a time. It’s a simple habit that provides an instant performance boost without costing a dime.
7. Failing to "Purge Unused" and Audit
Over months of design, your file accumulates "junk." Old families you tested but didn't use, line styles from old imports, and obsolete views.
The Problem: This junk increases the database size of your project. A larger database means slower sync times to the server and more chances for file corruption.
The Fix: Use the "Purge Unused" command weekly. Additionally, when opening your central file, check the "Audit" box at least once a week. This tells Revit to scan the file for errors and fix them before they become project-ending crashes.
The Business Case: IT Infrastructure as a Growth Engine
If your team is struggling with these issues, it might not just be a "Revit problem." It’s often an infrastructure problem. If your server is outdated or your network speed is lagging, even a perfectly managed Revit model will feel slow.
At Direct Support, we believe architecture and engineering firms should leverage IT for growth, not just "maintenance." When your systems are fast, your team produces more. When your team produces more, your firm scales.
Why On-Demand Support Makes Sense
Many firms feel stuck between two bad options:
- The "Internal IT Guy": He’s expensive, and when things are running well, he’s an overhead cost you don't need.
- The "Managed Service Contract": You pay thousands of dollars a month regardless of whether you use the support or not.
We offer a third way. Flat-rate, on-demand support.
Whether you’re dealing with a specific Revit crash, a server bottleneck, or a workstation that won't boot, we charge a flat $150 per issue. No contracts. No hidden fees. No billing surprises. This allows you to scale your IT expenses directly with your project needs. If you have a busy month with 10 tech issues, you pay for 10. If next month is quiet, you pay nothing.
Key Takeaways for Busy Principals
- Performance is Profit: A 10% increase in software speed across a team of 10 architects can save hundreds of billable hours per year.
- Infrastructure Matters: High-performance software like AutoCAD and Revit requires specialized server setups. Check out our business IT support pricing guide to see how we help firms stay lean.
- Behavior Over Hardware: Most performance issues are solved by better habits (Linking vs. Importing) rather than just buying more RAM.
Stop Guessing, Start Working
If your firm is losing time to tech crashes and slow models, you don't need a complicated long-term contract. You need an expert who understands the specific demands of AEC software.
We provide rapid response and technical expertise for the software your business relies on. Whether it's troubleshooting a Revit central model error or optimizing your office network for faster file sharing, we’re here to help.
Ready to fix your tech without the "financial surprises"?
Get On-Demand IT Support for Your Firm Today
By addressing these seven mistakes, you’ll see an immediate improvement in your team's workflow and your firm's bottom line. Don't let your IT be the bottleneck that holds your next big project back. Keep your models clean, your views organized, and your support direct.