Revit project setup checklist
A usable project file needs version, template, levels, grids, views and organisation before modelling ramps up. That is file setup — not BIM management.
Published 24 August 2026 · 3 min read
A Revit project that is messy on day one stays expensive. Levels in the wrong place, views with no naming convention, and a Project Browser nobody can navigate all show up later as wasted production time. Setup is the work of making the file usable before modelling or documentation ramps up.
Project setup checklist
- Revit version the office will keep using
- Practice template, if you have one
- Units and any shared coordinates the job actually needs
- Project information filled in so sheets can read it
- Levels and grids
- Browser organisation and naming
- Starting views and view types
- View templates the office intends to keep
- Sheets and titleblock
- Basic schedules, if they belong in this package
- Linked models, if they are part of the starting file
- Office standards that must be followed — and anything that is out of this setup
A practical sequence
Agree the year first. Place levels and grids before modelling. Set browser organisation and view names before dozens of views exist. Apply view templates once the view types are known. Sheets come after the views they will hold. Linked models should be loaded with a known origin strategy, not dropped in and left for later.
Browser organisation
The Project Browser is how the team finds the work. Consistent view names, grouping by type or level, and sheet numbering that matches the office drawing system save more time than any decorative start view. Inconsistent names are a production problem, not a taste problem. Decide the grouping before dozens of views exist. Changing browser organisation later is possible; it is also how people lose views they thought they had issued.
View templates
Autodesk describes a view template as a collection of view properties — scale, discipline, detail level, visibility — that can be applied so views look consistent. They can be assigned so later template edits update linked views, or applied once. Too many templates, or templates that fight the office standard, create the same chaos they were meant to prevent. A small set that the office actually uses is more valuable than a library nobody remembers.
Why setup saves production time
A wrong level elevation is cheaper to fix before walls exist. A missing view template is cheaper to apply before twenty plans have been graphically overridden by hand. A titleblock that does not match the office is cheaper to swap before sheets are numbered. Setup is not a luxury at the start of a job. It is the work of not paying for the same organisation twice.
Production setup, not BIM consultancy
Organising a Revit file is not the same as running an ISO 19650 appointment. Clash detection, COBie and digital twins need their own scope if they are required at all. RVTForm’s project setup is for production: a file the design team can actually work in.
Questions
No. Setup organises a Revit file so production can start. Information-management appointments and ISO 19650 consultancy are separate scopes.
A practice template is useful when the file should match in-house standards. If none is supplied, the quotation should state what organisation will be used.