Revit Worksets Per Person Is Why Your Model Still Has Ghost Owners

Every firm with a workshared model over a year old has a ghost in it. An "Owned by departed_user" warning that nobody has permission to relinquish. A workset named after a person who left in 2023. A 620 MB central file that takes 14 minutes to sync because nobody purges it and nobody wants to be the one who breaks the project.

Worksharing does not fail because Revit is bad at it. It fails because teams treat worksets as an ownership system, skip sync cadence when deadlines tighten, and never schedule the cleanup that keeps the central file alive. The fix is not a new tool. It is a hygiene cadence. This article is that cadence.

Workset hygiene is one of the five dimensions in Revit model health; see the pillar guide for how it sits with warning hygiene, parameter integrity, view templates, and file performance.

What Are Revit Worksets?

Revit worksets are a hygiene framework that separates visibility from ownership in workshared models, paired with a 30-60 minute sync rhythm and a monthly audit cadence that keeps Revit central files under 300 MB across years of edits. Worksets are not the ownership system - element borrowing is. Use worksets for what they're good at (coarse visibility), let Revit borrow elements automatically, and the ghost-owner problem disappears.

Worksets Do Two Jobs, Not One

Worksets serve two functions, and mixing them is the source of most workset misuse.

The first job is visibility control. A workset can be shown or hidden in a view, giving you a coarse layer of visibility above categories and filters. That is a useful layer when you want to turn all the furniture off in a coordination view without editing every Visibility/Graphics override.

The second job is ownership management. When a user edits an element, Revit borrows it. Borrowing means Revit puts your name on the element for the duration of your edit, and releases the name when you sync. If the specific element cannot be borrowed (for example, because another user already has it), Revit falls back to trying to borrow the whole workset the element sits on. That fallback is why workset setup matters for ownership at all.

Most firms that struggle with worksharing are trying to use worksets as the primary ownership system. They create a workset per person, or per zone, then assign people to them. Revit's element-level borrowing already handles the ownership job. You do not need worksets to do it, and you make element ownership confusing when you try. Use worksets for visibility. Let Revit borrow elements. That separation is the first fix.

The Workset Structure That Actually Holds

A workset structure that holds up across multi-discipline projects looks like this:

The rules behind it:

• Prefix with a discipline letter so the list sorts by discipline
• Separate by editing frequency, not by person - shell elements change less often than interior
• Keep Shared Levels and Grids under BIM Manager control so nobody accidentally moves a grid
• Isolate linked content on a Links workset so it can be unloaded when it slows the session

What not to do, in order of how often we see it:

1. Worksets per person. This is the source of the ghost owner problem. When somebody leaves, their workset stays, and every element on it is stuck behind an ownership barrier that nobody can cleanly release.
2. Worksets per floor. Floors belong in levels and view range. Using worksets for floors collapses the visibility job and the ownership job into the same bad scheme.
3. Thirty-plus worksets. Eight to fifteen covers nearly every project. Past that, you are paying a cognitive tax for no additional control.

Assignments Drift. Catch the Drift.

Here is the failure pattern: a wall is created on A-Shell. Somebody copies it. The copy lands on A-Furniture because that was the active workset when the copy was made. A week later, a keynote disappears from a plan and nobody knows why. The keynote is on A-Furniture, which is hidden in that view.

This is workset drift. It is the most common worksharing hygiene problem, and it compounds silently.

Conform Worksets is a Pyvoid tool that scans Revit elements against a category-to-workset rule set, previews misplaced assignments, and bulk-corrects drift for BIM Managers running multi-discipline workshared models. You define a category-to-workset mapping, scan for misplaced elements, review the proposed moves, and apply. Run it:

• Weekly during active production
• Before every Sync to Central when you are the BIM lead on the session
• After loading families or linking models, because those operations drop elements on whatever workset happened to be active

ReViewer catches the same drift at a higher altitude. Its audit includes workset-related checks, and if you run it monthly you get a trend line. A rising number of workset violations is not a model problem. It is a training problem. Somebody on the team is creating elements with the wrong workset active and needs to know.

Sync Like You Mean It

Sync to Central is not a ceremony. It is the mechanism that keeps your work on disk and clears the borrows you are holding.

The cadence that actually works:

• Every 30 to 60 minutes during active editing
• Minimum every two hours, even on quiet stretches
• Always before lunch, meetings, calls, or end of day

Long sync gaps produce two costs. Conflicts get more likely, because other users are editing adjacent elements and the reconciliation window widens. And the sync itself gets slower, because more changes need to merge into central. In our experience, teams who sync every 40 minutes rarely wait more than a minute for sync to complete. Teams who sync once in the morning and once before they leave often sit through three or four minutes each time, and that time compounds across a team of six.

The cadence also acts as a release valve on borrowing. Every sync relinquishes elements you are not actively editing. If three architects are all working in the same corner of the building, a 30-minute sync rhythm means none of them sits on a borrowed wall for more than thirty minutes. A two-hour rhythm means somebody is blocked for two hours while somebody else has lunch with their model checked out.

When Revit reports "Element owned by another user," the hierarchy is:

1. Revit tries to borrow the specific element
2. If the element is borrowed by somebody else, the borrow fails
3. The current borrower must relinquish ownership by syncing or running Relinquish All Mine

Do not force-borrow unless you have coordinated with the current owner in chat or in person. Force-borrowing overwrites their unsaved work. This is the single most common way teams destroy a morning of somebody's edits. The one-minute coordination cost is always cheaper than the recovery.

Maintenance on a Cadence

Central files do not bloat in a day. They bloat across months of edit history, unused families, and accumulated backups. The fix is a calendar, not a project. Build it into the BIM governance loop and the maintenance becomes part of the recurring cycle, not a Friday emergency.

Compact Central reduces file size by purging edit history. Revit does not do this automatically. You have to open Save As, enable Compact in Options, and save. That step is how central files stay under 300 MB.

Wipe Hub handles the deeper cleanup. Run it before compacting so that compact has less to carry forward. The Cache Wipe cleaner specifically targets stale local copies from closed projects, backup files with numeric suffixes, and collaboration cache that is no longer needed. Disk space on BIM workstations fills up with local copies faster than any other source, and the user almost never cleans them manually.

For heavily bloated files in the 500 MB range or higher, there is a more disruptive option: detach a local copy, run full cleanup, and create a new central from that cleaned detach. This breaks every user's local file, so coordinate it for a Friday evening and have the team create fresh locals on Monday morning. It is the last tool in the kit, not the first. Reach for Wipe Hub and Compact before you rebuild the central.

The quarterly cadence looks disruptive on paper and is not. Fifteen minutes weekly, one hour monthly, one half-day quarterly. A BIM Manager running ten workshared projects budgets less than two days per quarter for the whole portfolio, assuming they batch the work on Fridays when project load is lighter.

When Things Go Wrong

Three failure modes come up often enough to list.

Elements missing from views. If an element disappears from a view in a workshared model, the cause is usually workset visibility, not deletion. Check View > Visibility/Graphics > Worksets tab to see if the element's workset is open in that view. A common trap is that the element got moved to a different workset by another user, and that workset happens to be closed in your view. X-Ray is the systematic answer. It walks all 53 visibility conditions that can hide an element in Revit, including workset state, view filters, category overrides, crop regions, and design option visibility. Use it before you assume the element was deleted.

Slow Sync to Central. If sync takes longer than a minute, the two suspects are file size and warning count. Files over 300 MB or warning counts over 1,000 both slow sync, and the two often travel together because warnings accumulate as the file grows. Check both in File > File Info, then run ReViewer to quantify the warning breakdown. Wipe Hub addresses the underlying load by purging unused families, imports, and views. Compact Central after you purge, not before - Compact is far more effective on a leaner model.

Frequent ownership conflicts. If your team is colliding on ownership multiple times a day, the cause is one of three things. Users are working on overlapping geometry with no coordination, which is a scope problem that chat can solve. Elements are on the wrong worksets and Revit is grabbing whole worksets instead of single elements, which Conform Worksets solves. Or somebody is syncing once a day and sitting on borrowed elements for hours, which only cadence discipline solves.

Frequently Asked Questions

How many Revit worksets should a project have?

Eight to fifteen worksets covers nearly every multi-discipline project. Structure them by editing frequency (shell, interior, furniture) with discipline-letter prefixes (A-, S-, M-, P-, E-). Past fifteen, you're paying a cognitive tax for no additional control. Past thirty, the team can no longer hold the structure in their heads.

How often should I Sync to Central in Revit?

Sync every 30 to 60 minutes during active editing, minimum every two hours on quiet stretches, always before lunch, meetings, calls, or end of day. Teams that sync every 40 minutes rarely wait more than a minute. Teams that sync once a day sit through three or four minutes each time, and the cost compounds.

Why does my Revit central file keep growing?

Central files bloat from accumulated edit history, unused families, and backup files. Compact Central (File > Save As > Options > Compact) reduces file size by purging edit history; Revit does not do this automatically. Run Wipe Hub first to purge unused content, then Compact. Files over 300 MB show measurable sync degradation.

What is workset drift in Revit?

Workset drift is when elements end up on the wrong worksets because the active workset wasn't switched before an operation. The result is invisible until a coordination meeting or QA check surfaces an element that disappeared from a view because its workset was hidden there. Conform Worksets is the fix.

Why are worksets per person a bad idea?

Worksets per person create the ghost owner problem. When somebody leaves the firm, their workset stays in the model, and every element on it is stuck behind an ownership barrier no remaining user can cleanly release. Revit's element-level borrowing already handles ownership. Use worksets for visibility.

What's the safest way to fix a heavily bloated central file?

For files over 500 MB: detach a local copy, run full cleanup with Wipe Hub, Compact Central, and create a new central from the cleaned detach. This breaks every user's local file, so coordinate it for a Friday evening and have the team create fresh locals on Monday. It's the last tool in the kit, not the first.

The Cadence Is the Product

Healthy workshared models are not built in a project kickoff. They are maintained across a year of small, regular habits. Eight to fifteen worksets. Thirty-minute sync intervals. Weekly conform. Monthly audit and compact. Quarterly cleanup.

The tools in Pyvoid exist because the cadence is the hard part, not the clicks. Conform Worksets is a fifteen-minute weekly task. ReViewer runs unattended. Wipe Hub does in an hour what would take a BIM manager a full day of manual purging. None of it is exciting. All of it compounds.

Ghost owners are not a Revit problem. They are a hygiene problem. Fix the hygiene and the ghosts never appear.