Revit worksharing allows multiple team members to work on the same model simultaneously. Without it, only one person can have the file open at a time — unworkable on any project with more than one modeller. Worksharing solves this through a system of worksets and local file copies, with a central file acting as the single source of truth.
How Worksharing Works
When worksharing is enabled, a Central Model is created — typically stored on a server or cloud platform (Autodesk Construction Cloud, BIM 360, or a network drive). Each team member creates a Local Copy of the central model on their own machine. They work in their local copy and periodically Synchronise with Central (SWC) to push their changes to the central model and pull in changes made by others. The central model is never opened directly for editing.
What Are Worksets
Worksets are groups of model elements — effectively layers of ownership. Common worksets include Shared Levels and Grids (reference geometry everyone needs), Architecture, Structure, Interior, Site, and Linked Models. Each workset can be checked out by one user at a time, preventing conflicts. Elements not in a checked-out workset are visible but read-only to other users.
Worksets also control visibility — opening a model with certain worksets turned off reduces file size and improves performance significantly. On large projects, loading only the structural and MEP worksets without the interior fitout workset can cut load times dramatically.
Setting Up Worksharing
Enable it via the Collaborate tab — Collaborate — In the Cloud or In a Network Folder. Revit prompts you to define initial worksets. Create worksets that match your discipline breakdown, then save the file to the server location to create the central model. Each team member then opens the central model and immediately uses Save As — Local to create their local copy.
Synchronise with Central: Best Practices
SWC at the start of every session before beginning work — this pulls in overnight changes. SWC regularly during the day (every one to two hours) to reduce conflict risk. SWC at the end of every session and relinquish all worksets so other users can check them out. Never leave worksets checked out overnight — it locks other team members out until you return.
When SWC throws a conflict warning, read it carefully before resolving. “Accept yours” keeps your version; “Accept theirs” accepts the version from the central file. Getting this wrong can silently overwrite someone else’s work.
Borrowing Elements
You do not need to own an entire workset to edit an element in it. Revit uses element borrowing — you request permission to edit a specific element, Revit checks whether it is free, and grants the borrow. This is more granular than workset ownership and allows multiple users to work in the same workset simultaneously as long as they are editing different elements.
Common Worksharing Problems and Fixes
Corrupt central models usually come from network interruptions during SWC — always keep a recent backup. Slow SWC is usually caused by too many elements in a single workset or an oversized model; audit and purge regularly. “Cannot borrow” errors mean another user has the element checked out — coordinate with them directly rather than forcing the borrow.
Conclusion
Worksharing is what makes collaborative Revit modelling possible on real projects. The system is robust when used correctly — local copies, regular SWC, disciplined workset management — and fragile when shortcuts are taken. Invest time in setting it up properly at project start and it runs smoothly for the project’s entire life.