Worksharing Best Practices

Worksharing lets multiple users work on the same Revit model simultaneously. When it works well, teams collaborate on large projects without stepping on each other's work. When it breaks down, users see "Element owned by another user" warnings, sync conflicts slow production, and the central file grows to unwieldy sizes.

This article covers workset strategy, collaboration hygiene, and how Pyvoid tools help maintain workshared model health.

Workset Strategy

Purpose of Worksets

Worksets serve two functions in Revit:

1. Visibility control. Worksets can be shown or hidden in views, providing a coarse layer of visibility management above categories and filters.
2. Ownership management. When a user edits an element, Revit borrows that element's workset (or the element itself). This prevents conflicting edits.

In practice, most firms use worksets primarily for visibility control and accept Revit's element-level borrowing for ownership.

Recommended Workset Structure

A workset structure that works for most multi-discipline projects:

Rules:

• Prefix with discipline letter for consistent sorting
• Separate architectural elements by editing frequency (shell changes less often than interior)
• Keep Shared Levels and Grids under BIM Manager control to prevent accidental moves
• Create a Links workset to isolate linked content and allow it to be unloaded

What Not to Do

• Do not create worksets per person. This makes element ownership confusing and creates "owned by departed_user" problems when people leave.
• Do not create worksets per floor. Use levels and view range for floor-based visibility, not worksets.
• Do not create excessive worksets. 8-15 worksets covers most projects. 30+ worksets is a sign the strategy is being misused.

Enforcing Workset Assignments

Elements end up on wrong worksets when users create elements while the wrong workset is active. This is the most common worksharing hygiene problem.

Using Conform Worksets

Conform Worksets automates workset enforcement:

1. Define the category-to-workset mapping (which categories belong on which worksets)
2. Run a scan to identify misplaced elements
3. Review the list of proposed moves
4. Apply to relocate elements to their correct worksets

When to run:

• Weekly during active production phases
• Before every Sync to Central
• After loading families or linking models (these operations often create elements on the active workset rather than the correct one)

Tracking Workset Drift

Workset assignments drift over time. A wall created on A-Shell gets copied, and the copy lands on A-Furniture because that was the active workset when the copy was made.

ReViewer includes workset-related checks in its audit. Run ReViewer monthly to track the trend - if workset violations increase, it signals a training issue with the team.

Collaboration Hygiene

Sync Frequency

Sync to Central at regular intervals:

• Minimum: Every 2 hours during active editing
• Recommended: Every 30-60 minutes
• Before breaks: Always sync before lunch, meetings, or end of day

Long sync gaps increase the chance of conflicts and make the eventual sync slower because more changes need to be reconciled.

Element Borrowing

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

1. Revit first tries to borrow the specific element
2. If borrowing fails, it reports the owner
3. The owner must relinquish ownership (save to central or use Relinquish All Mine)

Do not force-borrow unless you have coordinated with the current owner. Force-borrowing overwrites their unsaved work.

Central File Maintenance

Central files grow over time as edit history accumulates. Periodic maintenance keeps them manageable:

1. Compact Central: Revit's File > Save As > Options > Compact reduces file size by purging edit history. Schedule this monthly.
2. Purge unused content: Use Wipe Hub to remove unused families, views, and imports before compacting.
3. Detach and recreate: For heavily bloated files, detach a local copy, run cleanup, and create a new central. This is disruptive - coordinate with all users.

Local File Hygiene

Local files (collaboration cache) accumulate and consume disk space. The Cache Wipe cleaner in Wipe Hub specifically targets:

• Stale local copies from projects you no longer work on
• Backup files (.0001, .0002, etc.) that are no longer needed
• Collaboration cache from closed projects

Run Cache Wipe quarterly or when disk space is low.

Diagnosing Worksharing Problems

Elements Missing from Views

If elements disappear from views in workshared models, the cause is often workset visibility:

1. Check if the element's workset is open in the view (View > Visibility/Graphics > Worksets tab)
2. Use X-Ray to systematically check all 53 visibility conditions, including workset state
3. Check if the element was moved to a different workset by another user

Slow Sync Performance

If Sync to Central takes longer than expected:

• Check file size (File > File Info). Files over 300MB need cleanup.
• Check warning count. Files with 1000+ warnings sync slower.
• Run ReViewer to quantify the problem, then Wipe Hub to address it.

"Element Owned" Conflicts

Frequent ownership conflicts indicate:

• Users working on overlapping areas (coordinate scope)
• Elements placed on incorrect worksets (run Conform Worksets)
• Infrequent syncing (enforce sync cadence)

Quick Reference

See Also

• The BIM Governance Loop - how worksharing maintenance fits into the governance cycle
• The Deep Cleanup - pre-milestone cleanup including worksharing hygiene
• Health Panel - full reference for audit, conformance, and cleanup tools

Last updated: 2026-04-16