Category • Modelling Practice • Standards

Modeling Standards

This page sets out practical modelling standards for Revit and CADmep workflows. It focuses on consistency, coordination, content control, naming, and buildable information so that models are reliable, clear, and suitable for downstream use.

Revit standards CADmep standards Naming & structure Coordination-ready models QA-minded workflows

1. Overview

Foundation

Good modelling standards exist to make information understandable, consistent, and dependable. They help teams coordinate effectively, issue clearer information, reduce rework, and maintain a reliable link between model content and downstream outputs such as drawings, schedules, reports, fabrication information, and site use.

Consistency

Users should model similar conditions in similar ways across the project.

Clarity

The model should be easy to navigate, review, and understand.

Suitability

The model should support the intended purpose without unnecessary clutter.

2. General modelling principles

Applies to all workflows
Core principles
  • Use approved templates and standards from the start
  • Model with purpose and clarity
  • Avoid unnecessary duplication
  • Keep geometry and information aligned
  • Think about who will use the model next
Good modelling behaviour
  • Consistent content placement
  • Clear naming and browser structure
  • Predictable visibility and documentation
  • Controlled revisions and updates
  • Fewer one-off workarounds
Warning: A model becomes hard to trust when each user applies their own methods without reference to project standards.

3. Revit modelling standards

BIM authoring

Revit modelling should be structured around the correct template, correct relationships, and consistent use of content, views, and parameters.

Template use

  • Start from the approved template
  • Use agreed view templates
  • Maintain browser organisation

Model logic

  • Check levels and grids
  • Link models correctly
  • Use families consistently

Data quality

  • Populate required parameters
  • Support schedules and tags
  • Avoid unused or duplicate content

Revit good practice

  • Use loadable families for repeatable objects rather than unnecessary in-place families.
  • Keep working views clean and purposeful.
  • Use view templates to control consistency, not random manual overrides.
  • Confirm linked models and shared coordinates before major modelling progresses.
  • Keep annotation and model information aligned rather than relying on misleading notes.

4. CADmep modelling standards

Fabrication-focused

CADmep standards depend heavily on content control, service templates, database setup, and output logic. Good modelling in CADmep is not only about geometry — it is about using the correct items in the correct way.

Profile & database

  • Use the correct profile
  • Check the database source
  • Avoid uncontrolled local variations

Services & content

  • Use approved service templates
  • Use controlled ITM content
  • Keep folder structure understandable

Outputs

  • Model with reports in mind
  • Maintain numbering logic
  • Only spool stable content

CADmep good practice

  • Do not let users work around poor service or content setup manually.
  • Keep similar items truly consistent if they are expected to report or number together.
  • Confirm connectivity before running downstream exports such as PCF.
  • Treat content standards as part of model standards, not as a separate afterthought.

5. Naming & structure

Organisation

A model can be technically correct and still be difficult to use if naming and structure are poor.

Standardise these items
  • File names
  • View names
  • Sheet numbers and sheet titles
  • Schedules
  • CADmep services and reports
Why it matters
  • Improves navigation
  • Supports QA
  • Improves searchability
  • Reduces duplication
  • Helps traceability

6. Coordination expectations

Model for coordination

Models should be built in a way that supports coordination rather than making coordination harder. That means predictable geometry, sensible detail, clear interfaces, and consistent ownership assumptions.

Geometry

  • Model at an appropriate level of detail
  • Avoid misleading placeholder geometry
  • Keep interfaces clear

Linked models

  • Check positions properly
  • Understand host vs linked responsibility
  • Review clashes in context

Coordination records

  • Record actions clearly
  • Close issues properly
  • Avoid repeated untracked assumptions

7. QA-minded modelling

Build quality into the model

Good modelling standards should make QA easier. A clean and consistent model reduces the effort needed to review, check, and issue information.

Model with QA in mind
  • Use predictable naming
  • Keep views and outputs controlled
  • Check before issue, not after problems appear
  • Make sure schedules and tags read correctly
Common weak habits
  • Random manual overrides
  • Unapproved content use
  • Over-modelled or messy geometry
  • Relying on memory instead of standards

8. Do / Don’t guidance

Quick reference

Do

  • Use project-approved templates and content
  • Model consistently
  • Keep naming clear
  • Think about downstream users
  • Check outputs before issue

Don’t

  • Invent one-off standards for each user
  • Leave unresolved naming problems
  • Mix approved and unapproved content casually
  • Use geometry to hide uncertainty in information
  • Assume the model is clear just because it looks busy
Final takeaway: Good modelling standards make the model easier to trust, easier to coordinate, and easier to issue. The strongest teams do not only model accurately — they model consistently.