Revit Modelling Basics
This page introduces the core basics of modelling in Revit. It is designed for new users who need to understand how Revit models are structured, how views and content relate to the model, and what good modelling habits look like from the start.
1. What Revit modelling is
Start hereRevit modelling is the process of creating building information inside a single coordinated project model. Plans, sections, elevations, schedules, and sheets all come from the same model rather than existing as separate disconnected drawings.
Model-based
Changes in the model can update multiple views and outputs automatically.
Information-based
Objects are not only geometry. They also carry categories, parameters, and data.
Coordinated
The model supports design, coordination, documentation, and downstream checks.
2. Project setup basics
Before modelling startsGood modelling begins with good setup. It is much easier to start correctly than to fix a badly structured model later.
- Correct project template
- Correct units
- Correct project information
- Correct levels and grids
- Correct linked-model strategy
- Improves consistency
- Reduces rework later
- Makes documentation easier
- Supports better coordination
3. Levels and grids
Project frameworkLevels and grids form the basic framework of many Revit models. They help define floors, vertical relationships, and layout references across the project.
Levels
- Define vertical reference points
- Support floor-based modelling
- Help create consistent views
Grids
- Define structural/layout references
- Help align content across views
- Support coordination and documentation
4. Views and visibility
How you see the modelViews do not create new model geometry. They are ways of looking at the same project model. That means visibility settings, templates, filters, and view range can all affect what you see without changing the model itself.
Plan views
- Use view range
- Can hide or reveal categories differently
- Need consistent templates
3D views
- Useful for checking model condition
- Can use section boxes
- Good for quick diagnostics
Visibility controls
- View templates
- Filters
- Worksets and phases
- Linked-model display
5. Families and categories
Model contentFamilies are reusable components used in Revit projects. Categories are how Revit groups and controls different types of objects for visibility, scheduling, and behaviour.
System families
Examples include walls, floors, roofs, and levels.
Loadable families
Examples include equipment, fixtures, title blocks, and generic components.
In-place families
Useful for special one-off conditions, but should be used carefully.
6. Linked models
Coordination contextLinked models allow you to reference other project files without rebuilding that information in your own model. This is essential for coordination between disciplines.
- To reference architecture, structure, or other disciplines
- To coordinate around another team’s information
- To reduce duplication of work
- Correct positioning
- Correct visibility settings
- Correct linked view logic where used
- Clear understanding of who owns what
7. Good modelling habits
Learn these early- Name views clearly
- Use the correct families
- Keep the browser organised
- Check views before changing model geometry
- Model consistently across similar conditions
- Make QA easier
- Improve coordination
- Reduce confusion for other users
- Support better schedules and drawings
8. Common beginner mistakes
Avoid these early- Starting with the wrong template
- Ignoring levels, grids, or linked-model positions
- Using random content instead of approved families
- Assuming something is deleted when it is only hidden in a view
- Creating too many uncontrolled duplicate views
- Using in-place families for everything
- Not thinking about how the model will schedule or document later
9. Do / Don’t guidance
Quick referenceDo
- Use the approved template
- Check levels, grids, and links early
- Use reusable families where possible
- Keep naming and views clear
- Think about schedules and drawings as you model
Don’t
- Treat Revit like disconnected 2D drafting
- Ignore visibility settings when troubleshooting
- Overcomplicate the model too early
- Use random unapproved content
- Assume a model is good just because it looks busy