Worksets Naming Convention for MEP Coordination

Our MEP model setup checklist flags unnamed worksets as a common failure. Here’s the actual convention to replace Workset1 with.

The pattern

[Discipline]-[System]-[Zone or Phase]

Examples: MEP-HVAC-Supply, MEP-HVAC-Return, MEP-PLM-Sanitary, MEP-ELE-Power, MEP-ELE-CableTray, MEP-FP-Sprinkler.

Checklist

1. Prefix every workset with the discipline code — MEP, STR, ARC. In a federated model with links from every discipline, this is the first thing a coordinator scans for.
2. Second segment is the system, not the equipment type — HVAC, PLM (plumbing), ELE, FP (fire protection). Don’t create a workset per equipment family (AHU, Diffusers) — that’s schedule-level granularity, not workset-level.
3. Split Supply/Return/Exhaust for HVAC ductwork — visibility toggling by direction is one of the most common coordination-meeting requests; if it’s all one workset, you can’t isolate it without a view filter workaround.
4. Zone or phase only if the project is large enough to need it — a 3-storey building doesn’t need per-zone worksets; a 40-storey tower with 4 MEP zones does. Don’t add this segment speculatively (YAGNI) — it adds worksets to manage without adding clarity until the project is actually that size.
5. No worksets named after people — John's stuff, Temp — these accumulate elements nobody can categorize later and never get renamed once real work starts.
6. Delete Workset1 after moving its contents — Revit creates this by default; leaving it in the model with orphaned elements is the single most common “what is this” question in a coordination review.
7. Document the convention once, in the BEP or a project wiki — not just in your head. The naming pattern only pays off if every team member (including a new hire six months in) uses it consistently.

Why this order

Discipline and system prefixes (items 1-2) are what a coordinator scans a federated model for during a clash review — get those right first. Zone/phase (item 4) is the one item to skip on smaller projects; adding it prematurely is over-engineering a naming scheme nobody needs yet.

Common mistake

Naming worksets after the equipment instead of the system — e.g. AHU-1, AHU-2, FCU-Zone-A as separate worksets. This looks organized but actually fragments a single system’s visibility control across a dozen worksets, making “hide all HVAC” in a coordination view a multi-click chore instead of one toggle.