Worksets — Create and use worksets for model organization and performance

Architectural and design workflows have always struggled with a fundamental tension: a building is a single, unified artifact, yet dozens of people must work on it simultaneously. In the era of hand-drafted blueprints, teams divided labor by assigning separate sheets to individual drafters—each person literally owned a physical piece of vellum. When CAD software arrived in the 1980s, it replicated this sheet-based model through external reference files (XREFs), where each discipline or zone resided in its own file and a master drawing assembled them like transparent overlays. The approach worked, but it also meant that coordination errors—misaligned column grids, clashing ductwork, orphaned dimensions—were discovered only when someone printed and overlaid the sheets.

The emergence of Building Information Modeling (BIM) in the early 2000s changed the paradigm. Rather than many files referencing one another, BIM proposed a single, shared database—a central model—from which every plan, section, and schedule is derived. Autodesk Revit, first released in 2000 and acquired by Autodesk in 2002, championed this single-model philosophy. Yet a single file creates a new problem: if everyone edits the same model at the same time, whose changes take precedence? Worksets were Revit's answer—a way to partition the model into named subsets of elements so that team members can take ownership of portions without locking others out of the entire project.

The core question worksets address is deceptively simple: How do you let an entire design team work inside a single, coordinated model without stepping on each other's work or grinding performance to a halt? Understanding the answer requires grasping both the organizational logic and the technical mechanics that worksets provide.

Before diving into step-by-step procedures, it is essential to internalize the foundational ideas that govern how worksets operate within Revit's worksharing environment. Worksets are not merely folders or layers; they are functional partitions of a shared database that control three things simultaneously: element ownership, visibility management, and memory loading. Each of these dimensions plays a distinct role in keeping a multi-user project running smoothly.

The following diagram illustrates the relationship between the central model, local files, and worksets. Understanding this topology is crucial because every action you take—editing a wall, synchronizing, closing a workset—flows through this architecture.

Several things are worth noting in this topology. First, the central model is never opened directly for editing—it serves exclusively as the repository of truth. Second, each designer's local file can have a different combination of open and closed worksets; Alex might only load the building shell while Jordan focuses on interior elements. Third, the Synchronize with Central (SWC) operation is bidirectional: it pushes your local changes up and pulls everyone else's changes down. This architecture lets teams of five, ten, or even fifty people coexist within a single Revit model, provided the workset strategy is thoughtfully planned.

Enabling Worksharing

Worksharing is not enabled by default. In a new project, you activate it by navigating to the Collaborate tab on the ribbon and clicking Worksets. Revit will prompt you to save the file as a central model. Upon doing so, two default worksets are created: Workset1 and Shared Levels and Grids. The latter is critical—it contains datum elements (levels, grids, reference planes) that every team member needs to see and that should rarely be edited individually. From this point forward, every element you create is assigned to whichever workset is currently active.

Creating and Managing Worksets

To create a new workset, open the Worksets dialog (Collaborate → Worksets, or the workset selector on the status bar). Click New, type a descriptive name, and confirm. Naming conventions matter enormously in practice: a common strategy names worksets by building system (e.g., A-Shell, A-Interiors, A-Site, A-Entourage) or by zone (e.g., Wing-East, Wing-West). Each element can be reassigned to a different workset through its properties panel.

Element Ownership and Borrowing

When you begin editing an element, Revit automatically borrows it—claiming temporary exclusive rights. This happens silently behind the scenes. If another user is already borrowing that element, Revit will notify you that the element is in use. Alternatively, you can take ownership of an entire workset from the Worksets dialog, which locks every element in that workset to your user account. Ownership persists until you either synchronize with central (releasing borrowed elements) or explicitly relinquish ownership in the dialog. This dual system—fine-grained borrowing versus coarse-grained ownership—gives teams flexibility to work at different scales of control.

Choosing how to divide a model into worksets is one of the most consequential decisions a BIM coordinator makes. Too few worksets limit your ability to manage visibility and ownership; too many create administrative overhead and confusion. Industry practice generally recommends between four and twelve user-created worksets per architectural model, depending on project scale. The diagram below illustrates a common organizational scheme for a mid-size building.

Imagine you are part of a four-person studio team designing a university art gallery in Revit. The project has an exterior shell with large curtain walls, interior gallery partitions, a landscaped courtyard, and extensive furniture and sculptural display fixtures. Below is the step-by-step process for setting up and using worksets to divide the labor.

Worksets are a powerful feature, but they are not without limitations. Understanding both sides allows you to deploy them effectively and avoid the mistakes that frequently trip up student teams and even professional firms.

Worksets operate within a single Revit file, but real-world BIM coordination often involves multiple files from different disciplines—architecture, structure, MEP (mechanical, electrical, plumbing), and landscape. Understanding how worksets relate to these broader strategies helps you situate this tool within the full collaboration ecosystem.

In advanced practice, worksets and linked models are used together. The architectural team uses worksets within their own model (Shell, Interiors, Site), while the structural and MEP models are linked in as separate files. Workset visibility can even be applied to linked models—you can selectively show or hide worksets inside a linked file without opening it. This layered approach extends naturally into clash detection and design review workflows in tools like Navisworks Manage, where workset-level filtering allows reviewers to isolate specific building systems for interference analysis. As you advance, you will also encounter Design Options and Phasing—features that address related but distinct organizational needs (exploring alternatives and modeling time sequences, respectively). Worksets remain the backbone of the real-time, multi-user collaboration strategy.