C+
CoreSkills+
Pillar 04 — Revit for Real ProjectsRevit Documenters · Built Environment Professionals
ⓘ
Educational content only
CoreSkills+ shares practical knowledge based on real project experience. This is not a substitute for your firm's own standards, BIM Execution Plan, or IT guidance. Always confirm the current software version, project standards and file locations with your BIM manager or team lead before starting work on a live model.
Revit Onboarding
What every new hire needs to understand before touching a live model
Knowing Revit and being ready to work inside a specific firm's live projects are not the same skill. Every firm's projects carry undocumented assumptions, a naming logic, a sync rhythm, a family library, a way of splitting worksets, that no course teaches, because it isn't Revit's logic, it's this firm's. This topic is for anyone stepping into a new company's Revit environment, graduate or senior documenter, and needing to find the invisible rules before they cost someone else time.
Why this is different from "knowing Revit"
◈
Framing
Knowing Revit isn't knowing the project
Revit fluency and firm-readiness are two different things. Every firm's Revit projects carry undocumented assumptions — a naming logic, a sync rhythm, a family library, a way of splitting worksets — that no course teaches you, because it isn't Revit's logic, it's this firm's.
①
Who this is for
This isn't just a graduate problem
A senior documenter arriving from another firm is fluent in Revit, but fluent in someone else's standards. The risk isn't incompetence, it's confident assumption — using the last firm's habits without checking whether this one does it differently.
⊙
Why it matters
The model is shared the moment you open it
On a live, work-shared project, every click has a blast radius. Locking a workset, working off a stale local file, or grabbing a family from an old job doesn't just affect your work — it costs the rest of the team time, often silently, for days.
≡
Reality check
Most of the real rulebook isn't written down
Larger firms may have a BIM Execution Plan or office standards manual. Plenty of firms run this on memory and habit instead. Either way, your job in week one is the same: find out what the rules actually are before you assume none exist.
The mechanics you need to actually understand
None of this is firm-specific — it's how Revit's collaboration model works everywhere. But it's rarely taught explicitly, and it's where most early mistakes come from.
①
Local copy vs central model
The central model is the single source of truth, stored on a shared drive or in the cloud. You never work in it directly — you work in your own local copy, and sync changes back. Ask where the central model lives and how often a fresh local copy should be created, rather than reusing an old one indefinitely.
②
Worksets aren't optional admin
Worksets divide the model into ownable pieces, usually by discipline, level, or functional area. Making a workset editable and holding it open blocks everyone else from touching those elements. The safer default almost everywhere: leave worksets non-editable and let Revit's automatic element borrowing handle it as you work.
③
Element borrowing happens automatically
The moment you edit something nobody else is using, you become its borrower — no need to manually claim a workset for a single change. Syncing relinquishes what you've borrowed by default, which is exactly why frequent syncing matters: it releases your changes for others, not just backs you up.
④
Sync cadence is a team agreement, not a preference
Syncing too rarely means bigger conflicts and longer waits for everyone reloading latest. Ask what the expected sync rhythm is on this project — some firms expect syncs every hour, others at defined milestones through the day.
⑤
Worksharing display modes show you the truth
Turn on worksharing display to see who owns what, what's been updated since your last sync, and which worksets are active. New users often don't know this view exists — it answers most 'why can't I edit this' questions instantly, without needing to ask.
The firm's invisible rulebook
Five questions worth asking directly, whether or not the firm has these written down anywhere. Tap each one.
Is there a BIM Execution Plan or office standards manual?+
This is the closest thing to a rulebook if one exists — it should define naming conventions for files, views, sheets and elements, and set out the folder structure for models, families and exports. If it exists, read it before you model anything. If it doesn't, treat every answer below as the manual you're building for yourself.
What's the naming convention for files, views and sheets?+
Where does the family library live, and who maintains it?+
Is there an approved project template?+
Who's the go-to person when the standard doesn't cover something?+
Before you touch the model — the checklist
Ten questions worth having answered in your first week on any new firm's Revit project. Tick them off as you go.
0 of 10 answered
Where does the central model live, and how do I create my local copy?
What's the expected sync frequency on this project?
Which workset(s) am I responsible for, and should I ever make one editable?
Is there a BIM Execution Plan or standards manual I should read first?
What's the naming convention for files, views, sheets and elements?
Where's the approved family library, and who maintains it?
Is there a project template I should be starting from?
Who do I ask when the standard doesn't cover my situation?
Are there existing view templates I should be using rather than creating my own?
What Revit version is this project locked to, and can I not assume the latest?
What goes wrong in the first few weeks
Common early mistake — newer to the industry
—Making a workset editable and forgetting to release it, quietly blocking teammates for hours.
—Working off a local file that's days old instead of refreshing it regularly.
—Grabbing a family from an old project because it 'looks right', without checking parameters against the firm's standard.
—Not knowing worksharing display mode exists, and asking a colleague something the model would have answered directly.
Common early mistake — experienced, but new to this firm
—Applying the last firm's naming convention because it was 'better', creating a second system inside one project.
—Assuming the sync rhythm from a previous role applies here without asking.
—Bringing in personal or previous-firm view templates instead of using the ones already set up.
—Not reading the BIM Execution Plan (or asking if one exists) because seniority made it feel unnecessary to check.
Free Checklist
The full first-week Revit onboarding checklist
A printable version of this checklist, plus the mechanics and rulebook questions above, to bring to your first week on any new project.
Seen a different onboarding mistake worth adding?
This topic gets better with real examples from real offices. Contribute one below.
Built with input from Revit users across documentation, BIM management and site-side delivery roles. Want to contribute? Use the form above.
Stay updated
Get notified when new topics publish
Free — no spam. New CoreSkills+ topics straight to your inbox.
Get notified when new topics drop — free, no spam.
Notify me →C+
CoreSkills+Real-world practice knowledge for the built environment, students, graduates, architects, designers, builders and project managers.
Pillars
© 2026 CoreSkills+. All rights reserved.
Privacy PolicyTerms of Use