Worksets are one of those Revit features everyone touches but few people set up deliberately — and a badly structured workset arrangement is one of the most common causes of "the project file is corrupted again" panic on live jobs. Here's how to set them up properly, and why most corruption issues trace back to workset discipline, not bad luck.
What a workset actually is
A workset is a named subset of a Revit project's elements that can be "checked out" for editing by one user at a time, inside a single shared central file. This is different from a linked model, which is an entirely separate file from another discipline. Worksets solve the "two people editing the same model" problem; links solve the "coordinating between disciplines" problem. Confusing the two is the first mistake I see in junior coordinators.
How to structure worksets sensibly
| Workset | Typically contains |
|---|---|
| Shared Levels and Grids | Levels, grids — rarely edited, kept separate to avoid contention |
| Architecture - Core | Walls, floors, roofs for the core/shell team |
| Architecture - Interiors | Interior partitions, fit-out elements |
| Site | Topography, site elements |
| Linked Models | Structural and MEP links (kept isolated for visibility control) |
The general principle: split worksets by who's editing and how often that part of the model changes, not by discipline naming alone. Two people constantly editing the same workset defeats the purpose — you'll just trade file corruption for constant "element is being edited by..." conflicts. This is exactly the kind of decision worth locking into your office template up front, rather than re-deciding it on every new project.
The habits that actually prevent corruption
- Always work on a local copy, never directly on the central file. Each team member should have their own local file synced regularly.
- Synchronize with Central frequently — every 30-60 minutes during active work, not once at the end of the day. Long gaps between syncs increase the chance of conflicting, hard-to-merge changes.
- Avoid working over unstable network drives or VPNs for the central file location — this is the single most common root cause of corruption I've traced on real projects, far more than "Revit being buggy."
- Run a periodic Audit + Compact on the central file (via File > Save As with the Audit option checked) every few weeks on long projects, especially after major design changes, to clean up orphaned data.
- Relinquish worksets when you're done for the day so others aren't blocked from elements you're no longer actively editing.
What I tell every coordinator on day one
Worksets are a discipline problem before they're a technical problem. A clean workset structure and a synced-often habit prevents 90% of the "corrupted file" emergencies I've been called in to fix over the years. If your team is still treating central file management as an afterthought, that's the first thing to fix — before adding more software to the workflow.
Workset structure and collaboration discipline are covered hands-on inside our Structure plan, alongside Navisworks and BIM 360 — because coordination tools only work if the underlying model collaboration is solid. Details on the Programs page.
Frequently asked questions
What is the difference between a workset and a linked model in Revit?
A workset divides one shared project into editable sections owned by different team members. A linked model is a separate file from another discipline, federated for coordination but not jointly editable.
Why does my Revit central file keep getting corrupted?
Common causes include editing the central file directly, unstable network drives, infrequent syncing, and oversized worksets straining the file during sync.
