Four Revit Habits That Only Break When Someone Else Opens the File
Most Revit problems we inherit are not modelling errors. They are worksharing errors. A model can look correct in a single view and still be built in a way that falls apart the moment a second person opens it. These habits survive because they never get tested. One modeller working alone in a file never feels the cost. A coordinated team feels it on day one.
Here are the four we correct most often when a model lands on our side, whether it comes from a client on intake or from a junior on our own team.
Worksets used as Photoshop layers
A new client once sent us a model where the worksets were organised like layers in an image editor. Not by discipline, not by linked file, just convenient containers for hiding parts of the model while working. Furniture sat next to walls. A chunk of MEP lived in a workset named temp.
While one person works in that file, it holds together. The problems start when someone else opens it. Selective open becomes useless, because you cannot predict what sits where. Visibility in linked files gets configured blind. Any filter built on worksets returns noise.
Worksets exist to control what loads into memory and what a team member can edit without stepping on someone else. Organised by discipline or by linked model, they do that job. Organised as personal scratch space, they quietly transfer a cost to whoever opens the file next. After that project we added a permanent item to our pre-delivery checklist: audit workset assignment on every model, including the ones clients send us.
Align used by eye
Elements nudged into position manually, almost straight, look fine on screen at the working zoom level. They stop looking fine once the model is coordinated against other disciplines, because nothing shares a real reference. Grids, levels and the Align tool exist so geometry locks to something. Skip them, and everything floats in coordinates. The drift only becomes visible when a duct misses a wall opening by the amount nobody measured.
Disallow Join skipped at junctions
Walls that merge at their junctions into an unreadable mass are almost always a sign that the person modelling them does not know Disallow Join exists. The command is one click. Without it, joined walls fight each other in plan, material takeoffs get confused about where one element ends and the next begins, and cleaning it up later takes far longer than doing it right the first time.
Synchronisation treated as an occasional event
Rare, large synchronisations packed with conflicts, instead of frequent small ones, are a habit from tutorial-scale models where you are the only author. On a live shared model the pattern costs real time. One lost evening untangling a sync conflict usually cures a person forever, but it is an avoidable evening. Sync often, sync small, and treat every sync as the moment your work becomes visible to the rest of the team.
Why these matter for the model you are paying for
None of these functions is difficult. That is the point. Tutorials teach people to model, not to work in a shared file next to other people, so these gaps show up specifically in production, where they are most expensive. A model can pass a casual visual review and still carry every one of them.
This is why we treat a model as a database, not a picture. A clean render says nothing about whether the worksets are sane, the geometry is referenced, or the quantities can be trusted. If you are taking over a model from a previous team, or you are not sure what was actually delivered to you, a model audit is the fastest way to find these issues before they reach the site. You can ask us for a model audit and we will tell you plainly what state the file is in.
