Revit Worksets: Start With 5–8 to Keep Teams in Sync
Enable worksharing and save a central model first, then build a compact set of functional worksets with clear names, favor borrowing elements over claiming entire worksets, and synchronize with central at least once a day. Hide anything you don’t need visible in every view, and run Worksharing Monitor so your team can see who’s editing what before it becomes a collision.
TL;DR:
Store the central model on a shared network drive or Autodesk Docs, and have each teammate create a local copy before editing.
Start with five to eight worksets, group elements by teams that edit them together, and add more only when teams work independently or repeatedly conflict.
Borrow individual elements for routine edits; making a workset editable locks every object in it, so reserve that control for major layout changes.
Synchronize with central at least daily, relinquish finished work, and check Worksharing Monitor before major edits for active users and sync status.
Hide furniture, entourage, and temporary worksets from views that do not need them; linked worksets must be open when the link loads to control visibility.
Table of Contents
Enable Worksharing and Create the Central Model
Setting up worksharing starts with a single file and a few deliberate choices about where it lives and who touches it first.
Open the RVT file you want to share, go to Collaborate → Worksets, and click Yes when Revit asks to enable worksharing.
Save the file using File → Save As, and check Make this a Central Model after save in the save dialog.
Pick a storage location your whole team can reach: a shared network drive or Autodesk Docs for cloud-based projects.
Have every team member create a local copy of the model before opening and editing.
Enabling worksharing automatically creates a couple of default worksets, including Shared Levels and Grids and a generic Workset1. You’ll rename or replace these once you decide how your team wants to divide the model, which is the next decision to make.
Create and Organize Worksets Without Causing Sprawl
Revit worksets typically map to one of three strategies, and most teams blend them depending on project size.
Functional: group elements by what they do, such as furniture, casework, or temporary design options.
Discipline: split by trade, like architecture, structure, HVAC, electrical, and plumbing, which Autodesk lists as common divisions.
Zone-based: separate by physical area, like interior versus exterior or by building wing.
A simple naming template keeps things readable months into a project: discipline-purpose-phase, for example “ARCH-Interior-DD” or “MEP-HVAC-CD.” Guidance on planning worksets recommends structuring worksets around who edits elements together rather than splitting by arbitrary categories like floor number. Too many worksets complicates ownership tracking and slows performance; additional granularity is justified only when a group genuinely works independently from the rest of the team.
Pro Tip: Start with five to eight worksets on a typical building project and add more only when a specific team repeatedly fights over the same elements.
Ownership and Editing: Borrowing vs Making a Workset Editable
Revit gives you two ways to claim editing rights, and the difference matters for how smoothly your team works in parallel.
Borrowing requests temporary permission to edit a single element, letting everyone else keep working on the rest of the workset.
Making a workset editable grants exclusive ownership of every object inside it, locking other users out until you relinquish it.
Autodesk’s guidance on ownership recommends borrowing wherever possible, reserving full workset ownership for situations that genuinely require it, like a major restructure of one discipline’s layout. You can check which workset any element belongs to on the Properties palette, and you relinquish ownership either automatically on synchronize or manually through the Worksets dialog. This borrowing-first habit is one of the clearest benefits worksets bring to architecture teams, since it keeps a model open to everyone instead of gridlocked by whoever edited last.
Visibility and Performance: What to Hide and Why
Workset visibility controls which elements load into memory for a given view, and it’s one of the fastest ways to speed up a heavy model using efficient Revit to CGI workflows.
Clear Visible in all views for worksets that don’t need to appear everywhere, which keeps views lighter without hiding elements permanently.
Furniture, entourage, and temporary design worksets are commonly hidden by default, since hiding unused worksets improves model performance by cutting drawing time for every open view.
Visibility choices on linked models carry over into host views too, so a cluttered link can slow down the host project even when its worksets are organized well.
Pro Tip: Keep a dedicated “coordination” view where every workset is visible, and leave your working views lean.
Synchronize, Relinquish, and Use Worksharing Monitor
Good sync habits are what keep a shared model usable instead of a source of daily frustration.
Save locally throughout the day, then use Synchronize with Central to push changes back to the shared file.
Check the sync dialog’s options before confirming: whether to save local, which comments to include, and whether to relinquish worksets automatically.
Compact the central model occasionally through the sync settings to reduce file size, though expect the save to take longer when you do.
Use Relinquish All Mine once you’re done editing a section, so teammates can borrow or take over without waiting on you.
Best practice is to synchronize with central at least once a day, and many teams set fixed sync windows, say mid-morning and before leaving, to avoid everyone pushing changes at once.
Worksharing Monitor shows active users and sync status in real time, which lets your team spot who’s mid-edit before a conflict happens. Checking it before a large change avoids long waits caused by someone else mid-synchronize.
Linked Models and Controlling Linked Workset Visibility
Linked models bring their own worksets into your project, and those need separate visibility control from the host file’s own worksets.
Open the linked file’s Visibility Graphics dialog, go to the RVT Link Display Settings, and use the Worksets tab to choose which linked worksets appear in each host view.
A linked workset must be open when the link loads for you to control its visibility in the host, so closed worksets simply won’t show up as options.
A common pattern limits MEP or furniture visibility from a linked model to coordination views only, keeping design views focused on the architecture.
Practical Checklist and Common Team Pitfalls
A short pre-start checklist saves far more time than fixing problems after the model is already shared.
Agree on the central model’s file name and storage location before anyone opens a local copy.
Confirm everyone has write access to the shared folder or cloud project.
Write down your agreed workset list and naming convention somewhere the whole team can reference it.
Build a daily routine: save local, synchronize, relinquish what you’re not actively editing, and glance at Worksharing Monitor before a big change.
Three pitfalls come up again and again on real projects: working from an old local file that hasn’t synced in days, keeping unused worksets around “just in case,” and forgetting to relinquish before stepping away, which locks teammates out of elements you’re no longer touching.
Pro Tip: Set a recurring reminder for “sync and relinquish” at the end of each work session, not just the end of the day.
Why Disciplined Workset Setup Pays Off on Larger Projects
Teams that agree on workset structure before modeling starts spend far less time untangling sync conflicts later. The projects that struggle are almost always the ones where worksets grew organically instead of by plan. As an Autodesk Certified Trainer, I’ve found that a few shared rules, agreed on day one, do more for a project’s pace than any amount of after-the-fact cleanup. For a deeper look at how worksharing fits into a project’s foundation, see our guide on what Revit worksharing actually involves.
— Steve
Learn Worksharing Hands-On With Our Worksharing Course
Reading through the setup steps gets you started, but applying them inside a real multi-user project is where the habits actually stick. Our Worksharing Course walks through central model setup, workset organization, and synchronize routines using project files built for team practice, not just theory.
The course includes lifetime access to the materials, so you can revisit the lessons whenever your next project needs a worksharing refresh. If you’re newer to Revit generally and want a broader foundation before diving into collaboration workflows, our Revit Course Only at 79 EUR one-off covers beginner through advanced skills.
Project-based lessons built around real worksharing scenarios, not slide decks.
Direct trainer support if you get stuck on a sync or ownership issue.
A completion certificate once you finish the course.
Enroll in the Worksharing Course and start practicing these habits on a live project file.
FAQ
Can two people work on a Revit file at the same time?
Yes, once worksharing is enabled and the file is saved as a central model, multiple people can open local copies and edit different worksets or elements concurrently. Ownership rules, whether borrowed or fully editable, keep two people from overwriting the same element at once.
How do I create a workset in Revit?
Open your local model, go to the Collaborate tab, select Worksets, click New, and give it a name. You can also check Visible in all views at creation time if you want that workset to show by default everywhere.
How to set up a schedule in Revit?
Go to View → Schedules → Schedule/Quantities, pick the category you want to tabulate, and choose the fields to include. Scheduling runs independently of worksets, though a schedule can still filter or group by workset if that field is added to it.
How to set up a central Revit model?
Enable worksharing on your file, then use Save As and check Make this a Central Model after save in the save dialog. Store it on a shared network drive or in Autodesk Docs, then have each team member create a local copy before editing.
Recommended
Comments