Worksharing Basics — Enable worksharing and understand central vs local models (conceptual)

Historical Context & Motivation

Before Building Information Modeling (BIM) became an industry standard, architectural collaboration was an exercise in file management chaos. Designers working on large projects—museums, university buildings, performing arts centers—would divide drawings across dozens of separate CAD files, each maintained by a different team member. When one person updated a floor plan, every other drawing referencing that plan had to be manually synchronized, a process that was both tedious and error-prone. The need for a system in which multiple designers could work simultaneously within a single, unified building model drove the development of what Autodesk Revit calls worksharing.

Worksharing addresses the fundamental tension in collaborative design: you want a single source of truth for your building model, yet you also need to let several people edit it at the same time without overwriting each other's work. This problem is not unique to architecture—software engineering solved a similar challenge with version control systems like Git—but the BIM context adds unique complexities because a building model is not a flat text file but a relational database of three-dimensional, parametric elements.

The central question worksharing answers is deceptively simple: How do you let five, ten, or fifty people edit the same building model at the same time, without losing data or creating conflicting geometry? The answer lies in a carefully designed architecture of central models, local copies, and a protocol for synchronizing changes between them.

Core Principles & Definitions

Understanding worksharing requires internalizing a small set of foundational ideas. These concepts map cleanly onto collaborative workflows you may already know from visual arts practice—think of how a film production keeps a master edit while editors work on individual scenes, or how a printmaking studio manages a single plate from which multiple proofs are pulled. The key distinction in Revit is that the central model is the authoritative record of the project, and every team member works on a local copy that periodically exchanges changes with that central authority.

Visual Explanation — Central vs. Local Architecture

As the diagram illustrates, the central model functions as a hub in a hub-and-spoke topology. Each spoke is a local copy residing on an individual workstation. No direct communication occurs between local copies—all data exchange is mediated through the central model. This architecture ensures that the central file is always the most complete, most up-to-date version of the project, provided all team members synchronize regularly. When Designer A synchronizes, their facade modifications are written to the central model; when Designer B synchronizes moments later, those facade changes are pulled into their local copy alongside their own interior design updates.

How Worksharing Works — The Enabling Process

Enabling worksharing is a one-time setup action performed on a Revit project. Before worksharing is enabled, the project is a standalone file that only one person can open at a time—much like a single sketchbook that must be physically passed between collaborators. The enabling process converts this standalone file into a workshared project by creating the underlying data structures (worksets, element ownership tracking, and version metadata) that allow concurrent access.

Step-by-Step: Enabling Worksharing

1. Open the project file in Revit on a workstation that has network access to the intended central file location.
2. Navigate to Collaborate → Manage Collaboration → Worksets (the exact ribbon location varies slightly by Revit version).
3. Revit will ask whether you want to enable worksharing. Click OK. Two default worksets are created: Workset1 and Shared Levels and Grids.
4. Rename and create additional worksets as appropriate (e.g., Exterior Envelope, Interior Partitions, Furniture and Equipment).
5. Use File → Save As to save the file to the shared network location. This saved file becomes the central model. From this point forward, every team member creates a local copy when opening.

What Happens Behind the Scenes

When worksharing is enabled, Revit embeds a unique identifier (GUID) into the central file's metadata. Every local copy references this GUID to confirm it is derived from the correct central model. Revit also begins tracking element ownership at two levels: workset-level ownership (coarse) and element-level borrowing (fine-grained). Workset-level ownership means a user can 'check out' an entire workset so that only they can modify any element within it. Element-level borrowing is automatic—whenever you edit an element, Revit quietly borrows it, preventing others from editing that specific element until your next synchronization.

Notice in the flowchart that the transition from standalone to workshared is irreversible in practice. While it is technically possible to detach a model from central (creating a standalone copy), the central model itself remains workshared. This is by design: worksharing is a structural commitment to collaborative practice, not a toggle you flip on and off between work sessions.

Worksets, Ownership, and Element Borrowing

Worksets are the organizational backbone of worksharing, and their design merits careful attention—especially in interdisciplinary projects where architects, interior designers, and engineers share a single model. A well-structured workset scheme reduces conflicts and speeds up synchronization, while a poorly structured one creates bottlenecks that frustrate the team. The key is to partition the model by discipline or building system, not by individual user, so that ownership boundaries align with professional responsibilities.

Ownership vs. Borrowing

Revit provides two complementary mechanisms for managing edit access. Workset ownership is a coarse, explicit lock: when you make yourself the owner of the 'Exterior Envelope' workset, no other user can modify any element in that workset until you relinquish ownership (by synchronizing or manually releasing it). This is useful for concentrated, uninterrupted work sessions on a specific building system. Element borrowing, by contrast, is fine-grained and automatic. Even if no one owns the workset explicitly, the moment you move a wall, Revit borrows that specific wall. Other users can still edit other elements in the same workset—they just cannot touch that particular wall until you synchronize. Most day-to-day editing relies on element borrowing rather than full workset ownership, because it maximizes the number of people who can work concurrently.

Worked Example — Setting Up Worksharing for a Gallery Project

Imagine you are part of a four-person team designing a contemporary art gallery. The team includes an architect handling the building envelope, an interior designer managing gallery spaces, a lighting designer focusing on exhibition lighting, and a BIM coordinator overseeing the process. Here is how you would set up worksharing from scratch.

Strengths, Limitations, and Best Practices

Worksharing is a powerful collaboration framework, but like any system, it comes with trade-offs. Understanding both its strengths and limitations is essential for managing expectations and designing effective team workflows. The table below summarizes the key considerations.

Connection to Advanced Collaboration Features

Worksharing is the foundation upon which more sophisticated Revit collaboration strategies are built. Once you are comfortable with the central-local model paradigm, several advanced workflows become available—each extending the core concept for larger teams, distributed offices, or more complex project delivery methods.

A particularly important advanced concept is the linked model approach. On very large projects—a campus, a hospital complex, a museum with multiple wings—it is impractical to keep everything in a single workshared file because the file would become prohibitively large and slow. Instead, each discipline (architecture, structure, MEP) maintains its own workshared central model, and these models are linked together into a coordination model. This nesting of collaboration strategies—worksharing within each discipline's model, linking between disciplines—is how real-world BIM projects at scale are managed. Understanding the basic central-local paradigm is the essential first step toward navigating these more complex arrangements.

Practice Problems

Lesson Summary