What does the agent check on a worksharing audit?

On a Revit worksharing audit, the agent checks workset organisation against the firm’s BIM Execution Plan, including naming patterns, scope splits, and active versus closed worksets. It flags ownership anomalies, such as one user owning most editable worksets or large sets of borrowed elements that never release. It also inspects edit-requestable settings, detached-and-saved-as drift, sync history markers for failures, recoveries, and force-saves, central-file path consistency across the team, and file-size growth between runs so you see both structural and performance risks in one pass.

How does it find detached-and-saved-as copies floating around?

The agent walks the directories your firm declares as central locations plus typical user local-cache paths, then reads Revit model identifiers and central-model GUIDs. It cross-references these against the active central model, comparing modification timestamps, file sizes, and saved-as histories. Any file that shares central lineage but no longer points to the current central path is flagged as a detached-and-saved-as copy, with the suspected source central and the user or machine that last touched it.

Does it auto-fix worksharing issues?

The agent proposes scripted fixes for low-risk worksharing issues, but it does not modify the central model without explicit BIM Manager sign-off. Workset re-organisation, ownership rebalancing, and cleanup of stale locals run as previewable operations, so you can see the before-and-after impact on worksets and element counts. Higher-risk items, such as suspected corruption or central-path changes, are output as action lists for the BIM Manager and IT team to handle manually in line with firm policy.

How does this differ from the broader model audit?

The broader Revit model audit checklist focuses on universal model health: views, links, imports, families, and warnings. Revit worksharing hygiene narrows in on the central-model collaboration layer: worksets, ownership, sync history, and central paths. In practice, firms run both: a worksharing pass using the Studio QA/QC Agent for central-model behaviour, and a separate warnings and standards pass using Revit warnings cleanup and Revit standards enforcement.

Who’s in the Beta cohort?

The Beta cohort currently includes 1–3 design partners running multi-team central models on Revit 2023 or later, Windows only. Each partner uses central-model worksharing in active production, with multiple disciplines or offices syncing to the same central. Cohort criteria also require a dedicated BIM Manager available for a short calibration sprint, where worksharing rules, workset patterns, and acceptable ownership distributions are tuned to the firm’s standards before the agent runs on live projects.

Use Case Beta

Revit Worksharing Hygiene

Revit Worksharing Hygiene is the central-model-side health pass for Revit worksharing, covering workset organisation, ownership and edit-requestable settings, detached-and-saved-as drift, sync history, central-file path consistency, file-size growth, and sync-failure patterns. VitruAI’s Studio QA/QC Agent walks the central model and flags collaboration issues that the warnings dialog and standard model audit miss, currently shipping with 1–3 design partners.

Worksharing-specific issues flagged across worksets, ownership, sync history, and central-file path consistency so the BIM Manager stops guessing at root causes.
Detached-and-saved-as copies detected, tied back to their source central model, and surfaced with timestamps and user context.
File-size and sync-time growth trended per central model so the BIM Manager catches degradation before it impacts open, save, or sync cycles.

Apply to the beta See capabilities ↓

How it works

From mysterious central-model performance issues to root-cause flags in minutes.

Workflow today

01

Central model performance degrades

Over a few weeks, the central model starts to feel heavy. Open, save, and sync with central (STC) stretch from seconds to minutes. The cause is rarely obvious: it might be oversized links, bloated worksets, sync failures, or a designer working in a detached copy. The BIM Manager hears complaints but sees no single smoking gun.

Ongoing
02

BIM Manager opens the central

Per investigation, the BIM Manager opens the central model with all worksets visible, checks workset organisation, and notes current file size. They may review the Revit worksharing monitor or journal files to infer sync history. This first pass alone can take ~30 min, especially on Revit 2023+ projects with many active worksets and linked models.

Per investigation · ~30 min
03

Manual sleuth

Next, the BIM Manager hunts for detached copies on the network, looking through project folders, user home drives, and VPN-mounted paths. They manually audit ownership and borrowed elements, scroll sync history for force-saves and recoveries, and try to match timestamps to user reports. A single Revit worksharing audit like this often takes 2–4 hours, and still misses edge cases like renamed central paths.

Per investigation · 2–4 hrs
04

Detached-and-saved-as copies found

Sometimes they find a detached-and-saved-as file that a designer used offline, then later synced back to a different central. Ownership fragments across worksets, borrowed elements behave unpredictably, and users see repeated edit requests. Without the right metadata, it is hard to prove that this detached lineage caused the current central-model health issues.

Sometimes
05

Best-practice talk to the team

After each incident, the BIM Manager runs another best-practice talk on worksharing: how to sync with central, when to detach, how to handle local files, and why not to save-as a central. Behaviour improves for a few weeks, then drifts. There is no persistent, automated Revit central model health view to reinforce the rules between training sessions.

Periodic

Workflow with VitruAI

01

Run the agent

For each Revit worksharing hygiene pass, the BIM Manager runs the Studio QA/QC Agent against the live central model from VitruAI + Revit. The agent reads worksharing metadata, including worksets, element ownership, central path, sync history markers, and file-size snapshots. A typical central-model audit completes in single-digit minutes per model, calibrated per deployment for local network performance.

Per audit · single-digit minutes per typical model
02

Review worksharing flags in Revit

On Day 1, the BIM Manager reviews a structured list of worksharing flags directly against the central model. Each issue carries a severity tag and source: workset organisation that violates the firm’s BIM Execution Plan, ownership anomalies where a single user owns most active worksets, detached-and-saved-as drift, and sync-history patterns that suggest recovery from corruption. Items that belong in a broader Revit model audit checklist are clearly separated from pure collaboration issues.

Day 1
03

Resolve the auto-resolvable, escalate the rest

The agent proposes scripted operations for safe fixes under BIM Manager control: rebalancing workset ownership, renaming or splitting worksets, and cleaning up stale local files tied to old central paths. Central-file path inconsistencies route to IT with a concrete list of affected users and machines. The BIM Manager keeps final say on any central-model change, aligning with firm standards from Revit standards enforcement while avoiding any automated edits that could risk corruption.

Day 1–2
04

Trend file-size and sync-time

Each Revit worksharing audit stores a timestamped record of central-model size, typical sync duration, and the count of worksharing warnings. Over a project’s life, this creates a trend line that highlights degradation before users complain. The BIM Manager can pair this with a Revit warnings cleanup run and the broader Revit model audit checklist to plan interventions at specific milestones instead of waiting for a crisis.

Per project

Common questions