Worksharing is what lets a whole team work on one Revit project at the same time. It is also where many projects get into trouble: overwritten changes, endless "element is owned by" messages, and syncs that seem to take forever. The good news is that most of these problems disappear with a few solid habits. This guide covers Revit worksharing best practices, from setting up the central model to using Synchronize with Central the right way, based on Autodesk's own documentation and proven team workflows.
How Revit Worksharing Works
In a workshared project there is one central model that stores the shared project data and keeps track of who owns which worksets and elements. Each team member never edits that file directly. Instead, everyone opens their own local copy, makes changes there, and then uses Synchronize with Central to push their work to the central model and pull in everyone else's changes. Ownership is handled through worksets and element borrowing: when you edit an element, you temporarily take ownership of it so nobody else can change it until you relinquish it.
The central model can live on a shared network drive, on Revit Server, or in the cloud with Revit Cloud Worksharing through Autodesk Docs. The habits below apply to all three.
Setting Up the Central Model Correctly
A clean start prevents many headaches later. Autodesk's help describes this process for a file-based central model:
- Open the project you want to share, go to the Collaborate tab and, in the Manage Collaboration panel, click Worksets.
- In the Worksharing dialog, rename the default worksets if you wish ("Shared Levels and Grids" and "Workset1" are created for you), then click OK.
- Use File > Save As > Project and save to a network location every team member can reach. Give the file a name that clearly marks it as the central model.
- Click Options and confirm Make this a Central Model after save is selected (it is locked on for the first save), then choose an Open workset default for local copies.
- Click Save.
Two details from Autodesk are worth remembering: avoid file names that end with a period followed by numbers (use hotel_2010.rvt, not hotel.2010.rvt), and remember that opening "All" worksets by default can noticeably slow large projects. After that, each user creates a local copy by selecting the central model in the Open dialog with Create New Local checked.
Synchronize with Central: Doing It Right
On the Collaborate tab, the Synchronize panel offers two choices under the Synchronize with Central drop-down. Synchronize Now syncs immediately with your current settings. Synchronize and Modify Settings opens a dialog where you can:
- Check or browse to the central model location.
- Tick Compact Central Model to reduce file size (the save takes longer).
- Choose which worksets and elements to relinquish after syncing, so colleagues can edit them.
- Add a comment of up to 1000 characters, which you can later review with Show History.
- Keep Save local file before and after synchronizing with central selected so your local copy stays in step.
Autodesk also warns that syncing at the same moment as other users can slow things down. On cloud models, the Sync Activity Indicator in the status bar shows whether the central model is available or busy; if it is synchronizing, use Reload Latest to pick up the newest changes without syncing.
For timing, Novedge's workflow guide suggests syncing at natural milestones, roughly every 30 to 60 minutes, and always before printing or exporting, before major model changes and at the end of the day.
Worksets, Ownership and Performance Habits
Good worksharing is as much about etiquette as settings. Autodesk's performance guidance recommends splitting the model into logical worksets, such as separate buildings, core and shell, furniture, or levels and grids, and placing links and imports on their own worksets. A few habits make a big difference:
- Borrow, do not check out. Prefer element borrowing over making entire worksets editable. Checking out a workset is useful mainly to protect key items like grids or linked files.
- Open only what you need. Close worksets you are not using to save memory and reduce clutter, especially link worksets.
- Relinquish often. Release ownership when you finish a task, before breaks and before you close the file.
- Refresh your local copy. Many teams create a fresh local copy each day rather than reusing an old one for weeks.
- Talk to your team. Respond quickly to editing requests and mention long syncs in your team chat.
Add-ins can help too. Tools such as pyRevit add useful utilities, and batch exports with Exstream Pro are easier when everyone has synced first.
Conclusion
Revit worksharing runs smoothly when the central model is set up carefully, everyone works in their own local copy, and Synchronize with Central becomes a regular, deliberate habit rather than an afterthought. Use Synchronize and Modify Settings to relinquish and comment, keep worksets lean, and communicate with your team. As of November 2026, these workflows are described in Autodesk's current Revit help for file-based, Revit Server and cloud worksharing, so they are a safe foundation for any team project.