Introduction
In the dynamic world of Building Information Modelling (BIM), effective collaboration stands as the cornerstone of successful projects. For teams tackling complex projects in Autodesk Revit, efficient worksharing practices are essential, especially when large teams are involved. As architectural and engineering projects grow in scope — encompassing multiple disciplines, geographically distributed contributors, and increasingly complex programme requirements — the demand for a disciplined, structured approach to concurrent model authoring has never been greater.
This post explores best practices that ensure seamless collaboration within large teams working on a single central model in Revit. Whether your organisation is managing a 10-person design team or coordinating across three disciplines on a major infrastructure project, the principles outlined here will help you reduce conflict, protect model integrity, and keep productivity high throughout every project phase.
Understanding Worksharing in Revit
Worksharing in Revit is an advanced feature that allows multiple users to work on a single model simultaneously, each contributing their part without interfering with others' work. This is facilitated through a central model stored in a shared location, with each user working on a local copy. The heart of successful worksharing lies in regular updates to the central model, ensuring that all team members have access to the most current project data.
It is worth understanding what worksharing is not: it is not simply a file-sharing arrangement. Rather, it is a structured ownership and synchronisation system. When a user opens Revit and creates a local copy, they are creating a personal working environment that remains linked to the central model through a bi-directional sync process. Elements within the model can be "borrowed" by individual team members, and Revit tracks these ownership states in real time. This granular control is what makes true concurrent authoring possible — and it is also why a thoughtful setup is so important before a project begins.
On large-scale projects, particularly those involving complex mixed-use buildings, transport infrastructure, or healthcare facilities, poorly configured worksharing environments often lead to file bloat, element ownership conflicts, and frustrating synchronisation delays. Understanding the underlying mechanics gives teams a practical foundation on which to build robust workflows.
Setting Up a Central Model
Proper Model Setup
Before engaging in worksharing, it is crucial to set up the central model correctly. The model should be prepared and reviewed to be error-free and optimised for performance. The initial setup involves creating a central model on a shared network location with suitable permissions and access rights for all involved team members.
In practice, this means conducting a thorough model audit before inviting additional contributors. Purge unused families, audit the model to resolve any corrupt elements, and review view templates and linked files to ensure they are all properly referenced. A bloated or error-laden central file compounds every problem that arises during worksharing — conflicts take longer to resolve, synchronisation slows, and the risk of file corruption increases.
The file location itself warrants careful consideration. Storing the central model on a reliable, high-speed server with appropriate RAID redundancy and daily backups is non-negotiable for professional projects. Naming conventions for the central file, local copies, and backup archives should be established and communicated to all team members before work begins.
Disciplined Use of Worksets
Worksets allow teams to divide a project into manageable parts. By assigning different parts of the model to specific worksets, teams can streamline workflows, reduce conflicts, and improve model performance. It is recommended to create worksets that align with the team's discipline, such as architecture, structure, and MEP systems.
Beyond discipline-level worksets, consider creating worksets that reflect building zones or phases. For example, on a large mixed-use development, you might create worksets for the basement car park, podium levels, residential tower, and retail frontage separately — even within a single architectural model. This zonal breakdown lets contributors focus on their area without loading geometry from zones they are not actively working on, which has a significant positive impact on Revit's performance when the model grows large.
A common mistake is creating too many granular worksets that become difficult to manage and remember. Aim for a balanced structure: broad enough to be intuitive, yet specific enough to provide meaningful performance and ownership boundaries. Document the workset strategy in a BIM Execution Plan (BEP) so all contributors understand the logic from day one.
Core Practices for Effective Collaboration
Frequent Synchronisation
One of the fundamental aspects of using Revit's worksharing feature is regular synchronisation with the central model. Team members should synchronise frequently — every 30 minutes or after significant changes — to minimise the risk of conflicts and data loss.
This rhythm becomes especially important during intensive design phases when multiple contributors are making rapid changes. A team member who neglects to synchronise for several hours and then attempts a large sync introduces a high probability of conflicts with colleagues' recent work. Establishing a culture where synchronisation is treated as a routine professional habit, rather than an afterthought, pays dividends throughout the project.
It is equally important to "Reload Latest" when synchronisation is not required — this refreshes your view of colleagues' changes without pushing your own, and keeps the local copy current. Many conflicts arise not from malicious intent but from team members working in isolation without refreshing their understanding of what others have changed.
Communication and Coordination
Effective worksharing necessitates open lines of communication and coordination between team members. Implementing a robust system for resolving conflicts and making clear assignments of tasks is vital. Utilising tools such as Revit's built-in messaging system, and integrating project management software, can aid in maintaining clear communication.
On large projects, a daily coordination meeting — even a brief stand-up of 10 to 15 minutes — can dramatically reduce the number of conflicts that arise. Team members can communicate which elements they plan to edit, flag any borrowing requests that are pending, and raise issues that might affect others' work. This human layer of coordination complements Revit's technical ownership system and ensures that no team member is unknowingly blocked from the elements they need.
Integrating Revit worksharing with project management tools such as Autodesk Construction Cloud, Microsoft Teams, or Asana allows task assignments to be tracked alongside model ownership. When a team member knows they are responsible for updating the curtain wall on levels 5 through 8, they can request ownership of those elements in advance, reducing the friction of mid-session borrowing requests.
Managing User Permissions
Assigning proper permissions ensures that each team member has access to the required parts of the model while protecting sensitive or crucial components from accidental changes. Project managers should routinely reassess permissions to match each team member's role and project requirements.
On larger teams, it is common practice to define user roles explicitly — BIM Manager, Discipline Lead, Modeller, and Reviewer — and to align Revit permissions with these roles. A reviewer, for instance, may need read-only access to the model; granting them full editing rights introduces unnecessary risk. Similarly, restricting access to shared parameters and project standards to the BIM Manager prevents accidental corruption of shared data that other team members depend upon.
Permissions should be reviewed at each project milestone. As the project transitions from concept design to technical design, and then to construction documentation, the team composition changes and so do the appropriate access rights. Treating permissions as a living document rather than a one-time setup is a hallmark of mature BIM project management.
Optimising Performance
Worksharing with Revit Server
For large teams or remote collaborations, utilising Revit Server can significantly enhance performance. The Revit Server acts as a proxy to the central model, reducing the load and allowing for efficient data transfer, especially in projects where team members are spread across different locations.
Revit Server is particularly valuable in scenarios where a project team spans multiple offices — for example, an architect in London, structural engineers in Birmingham, and MEP consultants in Manchester all contributing to a shared central model. Without Revit Server, each remote user would be downloading the entire central file over a wide-area network connection every time they synchronise. Revit Server reduces this to incremental delta transfers, dramatically cutting synchronisation times and reducing the network bandwidth required.
For organisations running a Revit Server infrastructure, maintaining the server with regular health checks, monitoring disk usage, and ensuring reliable network connectivity between office locations is the responsibility of the BIM Manager or IT team. A poorly maintained server creates the same performance problems that it was intended to solve.
Implementing Cloud Solutions
With the evolution of cloud technology, services like Autodesk BIM 360 and its successor, Autodesk Construction Cloud (ACC), offer cloud-based worksharing that allows smooth collaboration irrespective of geographic barriers. These platforms provide a central environment to manage, share, and distribute model-related data — and they remove the dependency on a firm's own server infrastructure.
Cloud worksharing is increasingly the default choice for new projects, particularly those involving international teams or clients who require direct access to the model as part of their contractual deliverables. The ability to access the central model from any location, on any approved device, without a VPN or dedicated server connection, greatly simplifies project setup and onboarding for new contributors.
That said, cloud worksharing introduces its own considerations. Licensing requirements, data sovereignty policies, and internet connection stability all need to be assessed before committing to a cloud-based workflow. Organisations working on government or sensitive commercial projects must verify that their cloud storage arrangements comply with relevant data protection regulations before uploading models to third-party platforms.
Model Health and Audit Practices
Maintaining a healthy central model over the life of a long project requires ongoing attention, not just careful setup. Large teams working at pace have a tendency to introduce redundant families, view overrides, and orphaned elements that accumulate over time, degrading performance and increasing file size.
Establishing a regular model audit schedule — ideally weekly on active projects — ensures that issues are caught early. The Revit Audit function (available when opening a file with the Audit checkbox enabled) can identify and repair certain categories of corruption. Beyond the built-in audit tool, BIM Managers should periodically run a purge of unused families and types, review warning lists, and check for any in-place families that could be replaced with more efficient parametric families.
A structured practice of archiving project milestones as a separate, detached copy of the central model provides a safety net should the active central file become corrupted. These milestone archives — created at the end of each design stage or major client submission — allow teams to roll back to a known-good state if necessary, without relying solely on Revit's automated backup mechanism.
Onboarding New Team Members
One of the most overlooked aspects of worksharing on large projects is the process of onboarding new contributors mid-project. As teams scale up during construction documentation or tender stages, new modellers joining an established worksharing environment can inadvertently cause disruption if they are not properly inducted.
A well-prepared onboarding checklist should cover: how to create and save a local copy correctly, the project's synchronisation protocol, the workset structure and which worksets each discipline owns, the naming conventions in use, the shared parameter file location, and the escalation process for resolving element ownership disputes. Pairing each new team member with an experienced contributor for their first session helps to embed these practices quickly and reduces the likelihood of early mistakes.
Providing this information as part of the BIM Execution Plan, rather than relying on verbal handovers, ensures consistency regardless of how rapidly the team grows.
Conclusion
Revit Worksharing, when utilised effectively, can significantly improve collaboration among large teams working on intricate BIM projects. By establishing clear guidelines for worksets, maintaining strict synchronisation regimes, utilising both Revit Server and cloud solutions, and embedding regular model health practices into the project rhythm, teams can achieve high levels of productivity and consistency from project start to handover.
The key to successful worksharing lies not only in the tools themselves but in a disciplined, well-coordinated approach to teamwork. Technology provides the platform; processes and people determine the outcome.
At Adyantrix, we work closely with architecture, engineering, and construction teams to design and implement BIM workflows that scale. From initial central model configuration and workset strategy through to cloud worksharing deployment and team onboarding frameworks, our BIM consulting and Revit expertise helps organisations build the collaborative infrastructure their projects demand. If your team is ready to take Revit worksharing to the next level, we would be glad to help you get there.
Speak with our BIM Consulting team at Adyantrix to find out how we can support your next project.
