Revit Worksharing for Small MEP Teams, a Practical Setup

Revit worksharing is documented as if every team has a BIM manager, a dedicated server, and a written standard. Most small MEP shops have none of those – they have two to five people, a project deadline, and a model that needs to not corrupt. This is a practical worksharing setup for teams that size, focused on the few decisions that actually prevent pain.

Central file: get the location right once

The single most important decision is where the central file lives and how people open it. A central file on a desktop sync service folder that is actively syncing while Revit writes to it is the most common cause of corruption on small teams. You have three reasonable options: a proper BIM 360 / Autodesk Construction Cloud workshared model, a dedicated on-premise file server, or – if you must use a consumer sync service – a discipline of pausing sync during work hours and only letting it run overnight as a backup, never as the live host.

Pick one and write it down. The failure mode is not a wrong choice; it is three people each assuming a different one.

Worksets that match how you actually divide work

Worksets are not folders and they are not a substitute for view filters. Their job is to let two people edit the same model without stepping on each other and to let you unload parts of the model you do not need loaded. For a small MEP team, a workset scheme that maps to discipline and ownership works better than an elaborate one:

• One workset per major system you actively coordinate: HVAC, Plumbing, Piping, Electrical, Fire Protection.
• A workset for shared levels and grids that nobody edits casually.
• A workset for linked models so you can unload links to speed up a slow session.

Resist the urge to make twenty worksets. On a small team, a worksets list that nobody can hold in their head defeats the purpose. The goal is “I can tell at a glance who owns what and unload what I do not need,” not a taxonomy.

Sync discipline is the whole game

On a small team, the difference between a healthy model and a daily fight is sync habits, not software. A few rules carry most of the weight:

• Sync with relinquish, frequently. Every 30 to 60 minutes, and always before lunch and before leaving. Holding borrowed elements overnight blocks your teammates and grows the local file out of step.
• Never sync on top of an error you do not understand. If Revit warns about something during sync, read it. Syncing through warnings is how a small problem becomes a corrupt central.
• Stagger syncs. If two people hit sync at the same instant on a small server, one waits. Agree on a rhythm or just call it out in the room.
• Create local files, never open central directly. Always open the central as a new local. Editing the central file in place is asking for trouble.

Maintenance that prevents the bad day

Small teams skip model maintenance until something breaks. Two cheap habits prevent most breakage. First, audit on open once a week – the “Audit” checkbox when opening the central catches small inconsistencies before they compound. Second, compact the central periodically; workshared files bloat over time, and a compact-on-sync once a week keeps file size and sync time down. Both take seconds and both are insurance against the day the model will not open.

The coordination layer

Worksharing keeps your own team out of each other’s way; it does nothing for clashes against the architectural or structural models. That is a separate workflow – linked models, a clash routine, and a coordination cadence. See coordination without an expensive Navisworks seat for the tooling side. The point here is to keep the two concerns distinct: worksharing is internal hygiene, coordination is cross-discipline.

If the model is already a mess

If you have inherited a workshared model that is slow, bloated, or throwing sync errors, a one-time cleanup pass often costs less than limping through the job: audit, purge unused, resolve warnings, rationalize worksets, and re-establish sync standards with the team. Small shops without in-house BIM capacity sometimes outsource that pass as fixed-scope model QA rather than staffing it internally.

Bottom line

Worksharing on a small MEP team is not about mastering every feature. It is about choosing where the central lives, dividing worksets the way you actually divide work, and syncing with relinquish often and cleanly. Get those three right and a five-person model will run for the length of a project without drama.