Building Your BIM Standards: Essential Elements for Revit Workflows

Why BIM Standards?

Some questions to consider

BIM Standards System






General Topics



  • Purpose — Tell the user what you hope to achieve with this system and why. Align this with the organizational mission, goals, and/or objectives.
  • Scope — Indicate the limits of standards scope. Is it used only for specific project phases (design development, construction documents)? Is it excluded in others (schematic design)?
  • Background — Give some history if appropriate and helpful. This might help the user understand why you have arrived at some of the components of this system.
  • Glossary — A tedious section but necessary. Use it to clarify semantics.
  • Policy — This usually occurs in conjunction with IT management but at the very least ensure the following is documented: 1) where files are stored; 2) how files are accessed; 3) how files are backed up and how frequently.
  • Roles and responsibilities — Define what is typical for your projects. It is recommended to have a model manager for every project. This role is the single point of contact for all things related to the administration of the model.


  • Execution Plan — BIM Implementation, Management, Execution, and Project Execution Plans are commonplace. Regardless of which flavor you prefer (BIP, BMP, BEP, PxP), the important factor is that you have one for all projects (even those that don’t require BIM). If it is not a contract requirement, use a company version to get everyone aligned as to how you will execute BIM. The company version can be simpler than what is often part of contract requirements. Perhaps a 5-page version is more applicable to your projects than a 30-page version.
  • BIM uses — Have a common definition of which BIM uses your organization employs. This can be a predefined list or one that you create on your own.
  • LOD — Provide definitions of Level of Development (LOD) and/or variations of LOD if applicable to you (Level of Detail, Level of Reliability). Again, if you can reference standards already in the industry, which will save a lot of effort. Just ensure your organization is using the same definition.


  • Graphical standards — This encompasses all the printed (or PDF) graphics that come from model elements.
  • Drafting standards — What symbols do you use? How do you want the details to look?
  • Sheet set organization — How do you want the sheet set organized?

Revit Topics

File Setup

  • Establishing model coordinates
  • Naming conventions — File, view, sheet, families and types, materials, and parameters
  • Central and local files — Work-sharing or cloud collaboration?
  • How/when will projects be divided into multiple models?


  • Define frequencies for the following:
  • Browser organization
  • View specificsView templates standardized; export views
  • Protocol for collaborating with others outside of your organization
  • Phasing and design options setup and use


  • What elements to constrain or pin and when
  • Define the use of detail components versus drafting lines
  • When can detail lines be used?
  • When can model lines can be used?
  • When should your users create drafting views versus detail views?
  • Do you use classification systems?
  • When/how will you use grouping?

Additional Workflows

  • How to start a project?
  • What is the protocol for when something goes wrong?
  • How to prepare CAD data (or other formats) for insertion?
  • What are the steps a user should take to ensure consistency for export to CAD or Navisworks?

Creating the System

System Development Tips





Entrepreneuring | curious thinker | technology advisor | photographer at stories by AMG | CTO of paradigm IT |

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium


First Public Test is Imminent!

Automatic Persisted Queries and why you should use them

Journey of a mechanical engineer to open-source contribution

Flash Stock Rom on Itel IT1508 plus

Flash Stock Rom on Itel


What to consider when picking a library or plugin

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Aashish Mathew George

Aashish Mathew George

Entrepreneuring | curious thinker | technology advisor | photographer at stories by AMG | CTO of paradigm IT |

More from Medium

Accessing One Oracle APEX Application from another

Conduct a Quality Control Analysis on Soil Samples — Global S

Own server part 5 — SMTP mail server

Behavior Driven Development, Cucumber, BDD with Cucumber.