Revit Worksharing: How to Collabourate on Large Building Projects Without Losing Your Mind
Large building projects are inherently team efforts. Architects, structural engineers, MEP consultants, and BIM coordinators all need access to the same model, often simultaneously, across different disciplines and sometimes different offices. Managing that complexity without a reliable workflow is a recipe for version-control chaos, overwritten work, and missed coordination issues. Revit’s built-in worksharing system is designed to solve exactly this problem — but only if you set it up correctly from the start.
This guide covers everything you need to know about Revit worksharing: how it works under the hood, how to configure your central model and worksets, best practices for syncing and managing user permissions, and the most common mistakes teams make when first adopting collabourative workflows. Whether you’re setting up worksharing for the first time or trying to untangle an existing project that’s gone sideways, the principles here will help you build a stable, efficient collabourative environment.
If you’re looking to get started with Autodesk Revit, it’s available at GetRenewedTech for €46.99.
What Is Revit Worksharing and Why Does It Matter?
Revit worksharing is the mechanism that allows multiple users to work on a single Revit model at the same time. Rather than passing a single file around and hoping nobody edits it simultaneously, worksharing creates a central model on a shared network drive or Autodesk’s cloud platform, from which each team member creates their own local copy. Users work in their local copy and periodically synchronise their changes back to the central model, making their edits visible to the rest of the team.
This approach is fundamentally different from simply sharing a file on a server. In a non-workshared project, only one person can open the model in an editable state at a time. On a 50,000 m² mixed-use development with an architecture team of six and a structural team of four, serialising access like that is simply not workable. Worksharing removes that bottleneck.
The system also provides granular access control through worksets — logical groupings of elements that can be owned by individual users — so team members aren’t constantly treading on each other’s changes. When you own a workset, you have editing rights to the elements within it; other users can see those elements but cannot modify them until you release ownership.
Setting Up the Central Model
The first step in any workshared project is creating the central model. This should always be done by the BIM manager or lead modeller before anyone else joins the project. Here’s how the process works:
Enabling Worksharing
Open your Revit project file and navigate to the Collabourate tab on the ribbon. Click Worksets and Revit will prompt you to enable worksharing. Once confirmed, the software automatically creates two default worksets: Shared Levels and Grids and Workset1. The first of these is important — shared levels and grids form the backbone of your model and should generally remain on their own workset so all team members can see them without requesting ownership.
After enabling worksharing, save the file as your central model. Use Save As > Project and ensure the Make this the Central Model after save checkbox is selected in the save options. Store this file on a network location accessible to all team members — either a mapped network drive or a cloud-hosted path via Autodesk Docs (formerly BIM 360).
Naming Conventions for the Central Model
Establish a clear naming convention for your central model before saving. A common format is:
[ProjectNumber]_[Discipline]_[Stage]_CENTRAL.rvt
For example: 2024-0047_ARCH_RIBA3_CENTRAL.rvt. The word CENTRAL in the filename is a visual reminder that this file should never be opened directly for editing. Opening the central model directly and making changes without creating a local copy first is one of the most damaging mistakes a team member can make.
Understanding Worksets
Worksets are the organisational unit of worksharing. Think of them as logical containers for different parts of your model. A well-structured workset configuration makes it easy for team members to claim ownership of the areas they’re working on without locking out the rest of the team.
Default Worksets
Beyond the two defaults Revit creates automatically, you’ll want to create worksets that reflect your project’s organisational structure. Common workset structures include:
- By discipline: Architecture, Structure, MEP, Landscape
- By building area: Core, Wings A/B/C, Basement, Roof
- By element type: Shell & Core, Internal Partitions, Ceilings, Furniture
- Linked models: Each linked Revit or CAD file should live in its own workset
The right structure depends on your project. A single-building residential scheme works differently from a multi-block masterplan. The key principle is that worksets should align with how your team is actually divided — not just with how the building is physically organised.
Workset Visibility
One significant advantage of worksets beyond access control is visibility management. In the Visibility/Graphics dialogue, you can toggle entire worksets on or off for any given view. This means a structural engineer working on the frame can suppress the furniture and finishes worksets entirely, keeping their views clean and the software responsive. On large models with hundreds of thousands of elements, selective workset loading can make a meaningful difference to performance.
Creating and Opening Local Copies
Once the central model is in place, each team member needs to create their own local copy. This is done through Open > Open and navigating to the central model. In the Open dialogue, ensure the Create New Local checkbox is ticked before clicking Open. Revit creates a local copy in the user’s specified local folder (typically Documents or a project-specific local directory) and appends the username to the filename.
Local files should be stored on the user’s local drive, not on the network. This is a common source of confusion — some teams attempt to create local copies on the server itself, which defeats the purpose and causes performance issues. The whole point of the local/central architecture is that you do your day-to-day work locally (fast) and push to the server periodically (slower, but infrequent).
Synchronising with the Central Model
The Synchronise with Central command (Collabourate tab) is the heart of the worksharing workflow. When you synchronise, Revit does two things simultaneously:
- It publishes your local changes to the central model, making them visible to all other team members
- It downloads all changes that other users have made since your last synchronisation, updating your local model
Before synchronising, Revit performs a series of checks. If there are conflicts — for example, two users have both modified the same element — the software will prompt you to resolve them. In practice, a well-configured workset structure minimises conflicts by ensuring team members are working in discrete areas.
The synchronisation dialogue also allows you to relinquish workset ownership. Once you’ve finished working on a particular workset, releasing it allows other team members to claim editing rights. It’s good practice to relinquish worksets you’re not actively modifying, especially at the end of the working day.
Worksharing Across Disciplines: Linked Models
On multidisciplinary projects, it’s rare for all disciplines to work within a single Revit model. More commonly, each discipline maintains its own central model — architecture, structure, and MEP each have separate files — which are then linked together using Revit’s Link Revit functionality.
This approach keeps file sizes manageable and maintains clear ownership boundaries between disciplines. The architectural model might be the host model, with the structural and MEP models linked in. Alternatively, a coordination model might link all disciplines together purely for clash detection and review, without any team member editing it directly.
Managing Linked Model Updates
When the structural engineer publishes updates to their central model, the architectural team needs to reload the link to see those changes. This can be done manually via Manage Links or set to reload automatically on open. Automating this is convenient but can sometimes introduce unexpected changes mid-session, so many teams prefer manual reload at defined intervals — typically at the start of each working day or after a formal issue.
Worksharing Using Autodesk Docs (Cloud Worksharing)
For teams working across multiple offices or with remote members, cloud worksharing via Autodesk Docs (part of the Autodesk Construction Cloud platform) offers significant advantages over traditional network-based worksharing. The central model is hosted in the cloud, and team members access it without needing a VPN or server infrastructure.
Cloud worksharing supports all the same workset and synchronisation workflows as server-based worksharing, but with the added benefits of automatic backup, version history, and integration with the wider Autodesk Docs ecosystem for document management and coordination. The Collabourate tab in Revit includes a specific option to enable cloud collabouration for a project.
Latency is a consideration with cloud worksharing — synchronisation takes longer than a local network, particularly for very large models. However, for geographically distributed teams, the operational simplicity usually outweighs the performance trade-off.
Worksharing Monitor
Revit includes a utility called Worksharing Monitor that runs alongside the main application and provides a real-time view of who is currently connected to the central model and when each user last synchronised. This is invaluable for BIM managers who need to know whether team members are keeping up with their sync obligations.
A good rule of thumb is to synchronise at least every two to three hours on active design days, and always before leaving the office. Team members who go several days without syncing create a large delta of changes that can be difficult to merge and may conflict with work that has happened in the interim.
Common Worksharing Mistakes and How to Avoid Them
Opening the Central Model Directly
This is the most damaging mistake. If someone opens the central model and makes edits — even inadvertently — it can corrupt the worksharing configuration and require significant effort to recover. Always open the central model with Create New Local ticked, and consider making the central model read-only at the file system level to prevent accidental direct opens.
Not Relinquishing Worksets
When a team member holds ownership of a workset and is unavailable — on holiday, off sick, or simply at the end of a busy day — other team members can’t modify those elements. Use the Worksharing Monitor to identify stale ownership and use the Relinquish All Mine command before leaving at the end of the day.
Too Many Elements in One Workset
Creating a single workset for all architectural elements and expecting multiple people to share it leads to constant ownership conflicts. Invest time in creating a granular workset structure at project setup. It’s far easier to merge worksets later than to split them.
Infrequent Synchronisation
The longer the gap between synchronisations, the larger the merge operation and the greater the risk of conflicts. Encourage a culture of frequent, lightweight syncs rather than end-of-day mega-syncs.
Performance Tips for Workshared Models
Large workshared models can become sluggish if not managed carefully. A few practices that meaningfully improve performance:
- Open only the worksets you need: When opening your local copy, use the Worksets dialogue to close worksets that aren’t relevant to your current task. Fewer loaded elements means faster operations throughout.
- Use Revit’s Audit function periodically: Over time, Revit files accumulate unused elements, families, and corrupt data. Running an audit (open the file with the Audit checkbox ticked) cleans these up.
- Purge unused elements: Use Manage > Purge Unused regularly to remove loaded families and materials that are no longer used in the model.
- Keep linked models closed when not needed: If you’re working on a purely architectural task, close the structural and MEP links to reduce memory overhead.
Getting the Most from Revit Worksharing
Worksharing is one of Revit’s most powerful features, but it requires a degree of discipline and planning that single-user workflows don’t demand. The teams that get the most from it are those that invest in a solid setup — clear workset structures, naming conventions, synchronisation protocols, and regular BIM management — rather than treating it as something that just works out of the box.
For BIM managers setting up worksharing on a new project, it’s worth documenting your configuration decisions in a BIM Execution Plan (BEP): workset names and ownership rules, synchronisation frequency, central model location and backup policy, and the process for onboarding new team members to the project.
With the right setup, Revit worksharing genuinely transforms how large teams work together, allowing parallel progress across disciplines without the coordination overhead of serialised access. It’s one of the core reasons BIM-based workflows continue to outperform traditional CAD approaches on complex building projects.
Ready to put worksharing into practice? Autodesk Revit is available from GetRenewedTech for €46.99. If your project involves architects, structural engineers, and MEP consultants all working from the same model, the Autodesk AEC Collection at €174.99 brings Revit together with Civil 3D, Navisworks, and a host of other tools in a single package.
