Whether you're an architect, engineer, or BIM manager, working with Revit® cloud models on Autodesk Forma® Cloud (formally ACC) offers tremendous advantages — real-time collaboration, centralized data, and streamlined project delivery. But cloud-based worksharing also introduces new ways for things to go wrong. Even experienced Revit users can fall into habits that cause slow performance, synchronization failures, and worst of all, model corruption.
At Hagerman & Company, we work with AEC teams every day and see the same pitfalls come up time and again. Here's a rundown of the most common Revit cloud model mistakes — and what you can do to avoid them.
1. Opening Cloud Models the Wrong Way
The Mistake: Clicking File > Open to open an AFC workshared model — just like you'd open a local file.
Why It's a Problem: When you open a cloud model using the standard Open button, you bypass the proper AFC workflow entirely. This can lead to synchronization errors, detached local copies, and coordination breakdowns across your team.
The Fix: Always open AFC workshared models from the Home screen by selecting Autodesk Projects. This is the only supported method for cloud worksharing and ensures your local copy stays properly connected to the cloud central model.
💡 Pro Tip: Another recommendation if you have been in the model for a few days, refresh the model before opening it. Make this a standard part of your team's onboarding checklist, so no one defaults to old habits.
2. Not Syncing Frequently Enough
The Mistake: Going hours — or entire days — without synchronizing with the central model.
Why It's a Problem: Infrequent syncing means your local copy drifts further from the rest of the team's work. When you finally do sync, you're more likely to encounter conflicts, errors, or lost work. It also means other team members can't see your progress.
The Fix: Sync with Central regularly — at a minimum, every few hours, and always before stepping away from your workstation. Before leaving for lunch or ending your day, sync and relinquish your worksets so teammates can access those elements.
💡 Pro Tip: Use the Worksharing Monitor to keep an eye on who's syncing and how often.
3. Ignoring Workset Management
The Mistake: Leaving worksets disorganized, borrowing elements without purpose, or failing to relinquish worksets when done.
Why It's a Problem: Poor workset management creates bottlenecks. If team members hold onto worksets they're no longer actively editing, others are locked out. This kills productivity and creates unnecessary friction in collaborative workflows. Also, opening all worksets all the time can affect performance.
The Fix:
- Organize worksets logically at the start of the project (by discipline, floor, or system — whatever fits your workflow).
- Relinquish all worksets and elements when taking a break or ending your session.
- Avoid opening worksets that aren't needed for your current task.
- Open workset in views as needed.
4. Using Detached Mode for Collaboration Tasks
The Mistake: Opening the model in Detach from Central mode when you actually need to be working in the live cloud model.
Why It's a Problem: Detached mode prevents synchronization entirely. Any work done in this mode exists in isolation and cannot be pushed back to the cloud central model. It's appropriate for archiving or troubleshooting — not active collaboration.
The Fix: Reserve Detach mode for specific scenarios like model auditing, creating backups, or investigating issues. For all active project work, always open directly from Autodesk Projects on the Home screen.
5. Working Across Different Revit Versions
The Mistake: Some team members upgrade to a new Revit version mid-project while others remain on the previous version.
Why It's a Problem: Revit is not backward compatible. If even one person upgrades the cloud model to a newer version, everyone else must follow — or be locked out. This can cause serious disruption for ongoing projects with multiple collaborators.
The Fix: Establish a clear version policy before the project begins. All team members and external collaborators must use the same Revit version. Plan version upgrades carefully, ensuring all active project work is complete before making the switch. Use the AFC Home screen to confirm version alignment across your team.
6. Neglecting Model Health — Warnings, Bloat, and Corruption
The Mistake: Ignoring Revit warnings, stuffing the model with high-detail families, or failing to regularly purge and audit.
Why It's a Problem: A bloated, warning-riddled model slows everything down — opening, syncing, navigating. As errors accumulate, Revit becomes increasingly unstable and may eventually be unable to recover. According to Autodesk's own guidance, corruption can be introduced during editing sessions and silently compound with every save.
The Fix:
- Audit the model periodically — at least once a week, or more often on fast-moving projects. The Audit function clears problematic data and serves as an early warning system.
- Purge unused families and elements to keep file sizes manageable.
- Use Level of Development (LOD) standards so families are only as detailed as the current project phase requires.
- Review and resolve Revit warnings regularly rather than letting them stack up.
- Ensure at least 5 GB of free hard disk space is available on local machines — Revit needs room to write temporary files during sync operations.
7. Linking Models Incorrectly
The Mistake: Linking reference models through incorrect methods, or not understanding how AFC handles linked files.
Why It's a Problem: Linked models behave differently in a cloud worksharing environment than in a traditional file-based setup. Using the wrong linking method can result in broken links, coordination failures, or models that teammates can't resolve.
The Fix: Understand the specific linking workflows that AFC supports. When linking a Revit model hosted in AFC, use the proper AFC path rather than a local or network path. Assign linked models to dedicated worksets for easier management and troubleshooting. If a linked file causes issues, isolate it by closing its workset and reloading links one at a time.
8. Publishing Too Many Sheets at Once
The Mistake: Attempting to publish a large number of sheets simultaneously when printing or exporting from a cloud model.
Why It's a Problem: Publishing an excessive number of sheets in a single operation can significantly slow the process and cause errors — sometimes requiring you to start over entirely.
The Fix: Batch your sheet publishing into smaller, manageable sets. Prioritize and publish only what's actively needed, rather than bulk-exporting the full sheet set in one go.
9. Skipping Regular Revit Updates
The Mistake: Running an outdated version of Revit without the latest updates and fixes applied.
Why It's a Problem: Autodesk regularly releases updates that address known corruption triggers and stability issues. Skipping these updates means you're working with known vulnerabilities that Autodesk has already fixed.
The Fix: Keep Revit up to date by installing the latest available updates for your version. Check Autodesk Access for a list of the current updates recommended for your software, security, and licensing. This is one of the simplest steps you can take to protect model integrity.
10. Skipping Team Training on Cloud Workflows
The Mistake: Assuming that because team members know Revit, they automatically know how to work in a cloud worksharing environment.
Why It's a Problem: Cloud worksharing introduces workflows, tools, and behaviors that are distinctly different from traditional local or network-based models. Without proper training, even skilled Revit users will make the mistakes listed above — often repeatedly.
The Fix: Invest in targeted training for your team on AFC and Revit cloud workflows. Understanding why the rules matter — not just what they are — is what makes the difference between a team that struggles and one that collaborates efficiently.
At Hagerman & Company, we offer Revit and Autodesk Construction Cloud training designed for real-world AEC workflows. Our Solutions Engineers work alongside your team to implement best practices, troubleshoot issues, and help you get the most from your Autodesk investment.
Final Thoughts
Cloud-based Revit workflows are powerful, but they reward teams that are disciplined and well-trained. Most of the mistakes above aren't the result of carelessness — they're the result of habit, assumptions carried over from older workflows, and a lack of formal guidance.
The good news? Every one of them is preventable.
If your team is struggling with performance issues, sync errors, or model corruption in your cloud Revit projects, Hagerman & Company is here to help. From custom training and project model support to BIM Workflow Process Assessments, we help AEC firms build better habits and better outcomes.
Contact Hagerman & Company to learn how we can support your Revit cloud workflows.
Comments