■ MEP BIM INSIGHTS — TOOLS & SOFTWARE
A single MEP discipline model is rarely built by a single person. Mechanical, electrical, plumbing, and fire protection modelers often work in the same Revit file at the same time — and without a proper worksharing setup, that means overwritten work, locked elements, and corrupted files. Revit worksharing is the mechanism that lets a team collaborate in one model without stepping on each other.
This article explains how worksharing works, what worksets are for, and the practices that keep a shared MEP model healthy.
Worksharing is built on one central model and multiple local copies. The central model is the single source of truth — stored on a server or, more commonly now, in BIM 360 / Autodesk Construction Cloud. Each team member works in their own local copy on their machine.
The cycle is straightforward: a modeler makes changes in their local copy, then synchronizes with central — pushing their changes up and pulling everyone else’s down. Between syncs, each person works independently. Frequent syncing keeps everyone current.
The golden rule of worksharing: sync often, and always sync before you leave. A local copy that hasn’t synced in three days is three days of divergence waiting to become a conflict.
A workset is a named collection of elements that can be owned by one user at a time. Worksets are how Revit prevents two people from editing the same elements simultaneously. When you make a workset editable, you take ownership of everything in it — no one else can change those elements until you release them.
For an MEP model, worksets are typically organized by system or discipline:
You do not have to take an entire workset to edit one element. Revit lets you borrow individual elements: when you edit something owned by a workset you don’t control, Revit requests permission to borrow just that element. If no one else has it, the borrow is granted automatically. This is the everyday mechanism that keeps a team moving without constantly claiming whole worksets.
| File | Role | Rule |
|---|---|---|
| Central model | Single source of truth for the whole team | Never open and work in it directly |
| Local copy | Your personal working copy | Always work here; sync to central |
| Backup folder | Revit-managed recovery data | Never delete or edit manually |
A frequent and damaging mistake is opening the central model directly and working in it. This bypasses the worksharing system and can corrupt the central file. Everyone works in a local copy, always.
Cloud worksharing through BIM 360 or Autodesk Construction Cloud has become the standard for distributed teams. The central model lives in the cloud, and team members in different locations — or different countries — sync to the same central file over the internet.
For an offshore MEP team working with a US-based client, cloud worksharing is what makes real-time collaboration practical. The model is one model, wherever the people are. This is a significant change from the older approach of exchanging files by email or FTP, where every handoff risked working from an outdated copy.
Most “Revit is slow” and “the model is corrupted” complaints trace back to worksharing discipline, not the software. A well-managed central model with clear worksets and frequent syncing stays fast and stable.
Our MEP teams work in worksharing-enabled Revit models with worksets organized by system, syncing to a central model on Autodesk Construction Cloud so distributed modelers collaborate in real time. Workset structure and sync protocols are defined at project setup — part of the same discipline that keeps a model coordinated is what keeps it healthy to work in.
Have a project in mind?
moc.s-yrtemoeg%40olleh | © 2026 GEOMETRY-S | MEP Engineering Firm
moc.s-yrtemoeg%40olleh | © 2026 GEOMETRY-S | MEP Engineering Firm