Revit Fundamentals
Modelling discipline, view templates, sheet sets — everything a Revit modeller actually needs.
A six-hour, twenty-eight lesson course that gets a new modeller from "I can open Revit" to "I can ship a coordinated set." Optimised for studio onboarding.
- Set up a Revit project with disciplined view templates and sheet sets
- Author parametric content that survives audit
- Read and apply your studio's modelling standards
- Recognise and avoid the 12 most common modelling anti-patterns
- 015 lessons · 60 min
Project setup + worksharing
- 026 lessons · 75 min
View templates that scale
- 035 lessons · 65 min
Sheet sets + scheduling
- 046 lessons · 80 min
Family hygiene basics
- 056 lessons · 80 min
Coordination workflow
Revit Fundamentals is the course we wish existed when our junior modellers joined. It is structured around real workflow problems — what to do when a sheet schedule drifts, why your view template is fighting you, how to bring a junior up to speed.
Who this is for
- Junior modellers in their first month at a studio
- Engineers who use Revit as a downstream consumer
- Studio leads building an onboarding programme
What you build
Across the 28 lessons you build a small mixed-use project from scratch. Every lesson ends with a deliverable; the course concludes with a coordinated set you can show in a portfolio.
Articles from our editorial team
Revit central file corruption recovery: when worksharing breaks at 4 p.m. Friday
A central file that throws "Cannot open" at 16:12 on a Friday with 22 modellers about to clock off. The local-to-central extraction, audit-recover-detach sequence, and prevention playbook.
Revit linked files: Overlay vs Attach, shared coordinates, host visibility trap
The structural link landed 1.2 km away from the architectural model. A nested link reload broke 47 sheets. The Overlay vs Attach decision and shared-coordinate workflow that holds.
Revit performance triage: GPU vs CPU vs RAM bottleneck diagnosis
A new $4,200 RTX workstation that opens a 400 MB model in 8 minutes. The bottleneck is not the GPU. The Task Manager + Journal + Process Explorer workflow that finds the real cause.