Revit Worksets 101: Setup, Best Practices, and CSV Import

Open worksharing on a fresh project file and Revit hands you exactly two worksets: "Shared Levels and Grids" and "Workset1." That's it. Everything else — how your architectural, structural, and MEP elements get organized, how your team avoids stepping on each other's toes, how a coordinator can isolate a discipline's worked-out geometry — is entirely on you. Get it wrong on day one, and by month three you're untangling a workset structure on a live central model with forty active users. Get it right, and worksets quietly do their job: reducing sync conflicts, speeding up selective opening, and giving your BIM manager a clean way to control visibility per discipline.

Start With Enabling Worksharing the Right Way

Worksharing turns on under Collaborate > Worksets, and the moment you do, Revit prompts you to save as a central model. From there, every team member works off a local copy synced back to that central file. This part is well documented and Autodesk hasn't changed the fundamentals in years — central model, local copies, sync with central. What trips teams up isn't the mechanics, it's the workset plan that gets built on top of it.

Structure by Discipline First, Then by Zone

The most durable approach I've seen on multi-discipline jobs is a two-tier naming convention: discipline first, zone or system second. Something like ARC-Core-Podium, ARC-Tower-Levels1-10, MEP-Ductwork-Basement, STR-Foundations. This isn't arbitrary — it maps directly to how people actually want to open and close visibility. A structural engineer checking foundation clashes doesn't want architectural furniture loaded, and a facade consultant working the tower doesn't need basement MEP in their view.

On a genuinely large project — a 300,000 sq ft hospital, say, or a mixed-use tower with a five-level podium — zone-based subdivision matters more than people expect. If your entire architecture scope sits in one workset called Architecture, every architect on the team is contending for the same lock every time they touch a wall, and every sync pulls the whole discipline's worth of changes. Split it by building zone or by phase and you cut that contention down substantially.

Don't Let "Shared Levels and Grids" Become a Dumping Ground

This is the one I see go wrong most often. Shared Levels and Grids is meant for exactly what its name says — levels, grids, and maybe a handful of shared reference planes that every discipline needs visible and editable in coordination. It is not meant for site elements, not for shared families, not for "stuff nobody assigned to a workset yet." Once random geometry starts landing there by default because nobody set a project default workset, you've got a workset that everyone has to load, that nobody can isolate, and that becomes borrow-request chaos during coordination meetings. Set a sensible default workset in Worksets settings before your team starts modeling, and audit it every few weeks early in the project.

A Few Other Habits Worth Building In

Keep a workset for site and topography separate from building elements — site work often gets touched by civil-adjacent team members who shouldn't need building worksets loaded. Give link files their own logical workset naming (linked structural model, linked MEP model) rather than lumping them under whatever workset happened to be active on import. And resist the urge to create a new workset for every single small scope change; too many worksets is its own management headache, with people unsure which one to pick and borrow requests scattered across a dozen near-duplicate categories.

Where the Manual Approach Falls Apart

All of this is straightforward advice on a new model. It gets genuinely painful on an existing one. Say you've inherited a 60,000-element hospital model that was worked up without any workset discipline, and now you need to reorganize it into a proper discipline-and-zone structure before a coordination push. Selecting elements by category, by level, by room, and reassigning them one selection set at a time is the kind of task that eats an entire week and still leaves gaps, because Revit's native workset assignment only works on what you've currently got selected — there's no built-in way to batch-assign by a rule like "everything in Room 214 to workset MEP-L2-East."

That's the gap Workzet, one of the twelve tools in AecNxt's free Revit add-in suite, is built to close. Instead of clicking through selection after selection, you export your model's element data to a spreadsheet, tag the workset assignments in a CSV using whatever criteria make sense — category, level, room, parameter value — and import it back in. What would be days of manual reassignment becomes an afternoon of spreadsheet work, and because it's CSV-based, you can hand the categorization work to someone who's comfortable in Excel without needing them to be a Revit power user. It's the kind of task Workzet was built for, and like the rest of AecNxt's suite, it's free to use, no credit card, no trial limit, across Revit 2022 through 2027.

Worksets aren't glamorous. Nobody puts "clean workset structure" in a portfolio. But on a large collaborative model, they're the difference between a coordination meeting that runs smoothly and one where half the team is stuck waiting on a sync.