Revit mistakes fall into predictable patterns — the same errors appear on project after project, usually because no one explained the underlying concept clearly. Here are the ten most common mistakes beginners make, and exactly how to fix each one.
1. Modelling in the Wrong View
Placing walls or floors while in a 3D view or the wrong level plan creates elements at unexpected heights. Always model in the view that corresponds to the level you are working on. Structural columns go in a structural plan; walls go in an architectural plan at the correct level. If something looks wrong in 3D, check which view you were in when you placed it.
2. Not Setting Levels Before Modelling
Levels define the vertical reference for every element. Starting to model before levels are set up correctly means every floor, wall, and roof will need to be adjusted later. Set up all project levels — with correct elevations and meaningful names — before placing a single element.
3. Using Generic Families Instead of the Right Category
Placing a structural column as a generic model, or a door as a wall-hosted generic family, breaks schedules, tags, and phase tracking. Always use the correct Revit category family for each element type. If you cannot find the right family, load one from the Autodesk library or create one in the Family Editor with the correct category.
4. Ignoring Warnings
The Revit warnings dialog is not decoration. Warnings about overlapping elements, room separation lines not forming closed loops, and structural elements not meeting gridlines indicate real problems that will cause issues in schedules, exports, and coordination. Review and resolve warnings regularly rather than accumulating thousands of them.
5. Not Using Worksets Correctly
In workshared projects, placing all elements on the default workset means no one else can check out any part of the model without locking everyone else out. Organise elements into meaningful worksets by discipline or zone from the start, and borrow elements rather than checking out entire worksets for small edits.
6. Copy-Pasting Geometry Instead of Using Groups or Arrays
Copy-pasting a typical unit layout dozens of times creates independent copies with no relationship to each other. Changing one requires changing all of them manually. Use Groups for repeated spatial arrangements that need to stay synchronised, or Revit’s Array tool for structural grids and repetitive elements.
7. Overriding Graphics Manually Instead of Using View Templates
Right-clicking elements and manually overriding their colour or line weight in one view means the same override will not appear in other views and must be repeated manually every time. Use View Templates to apply consistent graphic overrides to all views of the same type. When standards change, update the template once and every view updates automatically.
8. Placing Dimensions Without Reference to Locked Constraints
Dimension strings that float freely in a view do not constrain the model — they just report the current value. To lock a constraint, place a dimension and then click the padlock icon to lock it. Locked dimensions prevent accidental movement and document the intended dimension as a design intent.
9. Not Purging Unused Families and Types
Revit project files grow quickly when families are loaded, used once, and then replaced with better alternatives without removing the originals. Use Manage — Purge Unused regularly to remove unused families, types, and line patterns. On large projects this can reduce file size by hundreds of megabytes.
10. Exporting to DWG Without Configuring Layer Mapping
Exporting DWG without a configured export setup produces layers named after Revit’s internal categories, which rarely match the layer convention expected by collaborators. Configure and save a DWG export setup with the correct layer mapping before your first export issue, and every subsequent export will be clean and consistent.
Conclusion
Most Revit mistakes come from working around the software instead of understanding how it is designed to work. The underlying concepts — levels, categories, worksets, view templates, families — are consistent throughout the application. Understanding one well makes the others easier to grasp, and these ten fixes cover the majority of what goes wrong on real projects.