RC
Revit CADmep Guide Professional user guidance for modelling, coordination and production
Documentation • Standards • QA • Delivery

Documentation & Standards

This page brings together the main documentation principles for Revit and CADmep workflows, including model setup standards, drawing issue checks, naming conventions, coordination records, QA expectations, and fabrication-ready outputs. It is designed as a reference page for teams who need consistent delivery standards across BIM, design, coordination, and production workflows.

Model standards Drawing QA Issue control CADmep outputs Coordination records Documentation best practice

1. Overview

Foundation

Good documentation is not just about issuing drawings. It is the controlled process of creating, checking, presenting, and recording information so that models, drawings, schedules, reports, and fabrication outputs are consistent and traceable. In practice, strong documentation reduces confusion, improves coordination, and makes project delivery more dependable.

Model documentation

How the live model is organised, named, structured and checked.

Drawing documentation

How views, sheets, notes, tags and revisions are presented for issue.

Output documentation

How reports, spools, PDFs, DWGs and fabrication outputs are controlled.

2. Model standards

Revit / BIM

A reliable documentation process starts with a reliable model structure. If the model is badly organised, the documentation coming from it will also be weak.

Core model standards
  • Correct project template
  • Correct units and project information
  • Consistent view templates
  • Clean browser organisation
  • Linked-model positioning checked
  • Worksets used only where appropriate
What good looks like
  • Views are easy to find
  • Templates are clearly named
  • Schedules are standardised
  • Duplicate uncontrolled views are minimised
  • Model data supports tags and schedules correctly
Warning: Do not rely on manual drawing workarounds to compensate for a poorly structured model.

3. Views, sheets & issue information

Presentation

Views and sheets should be consistent, readable, and suitable for the intended audience. A sheet is not simply a place to drop views; it is a controlled output for review, approval, construction, coordination, or manufacture.

Views

  • Use the correct view template
  • Check scale and crop region
  • Confirm filters and linked-model display
  • Remove accidental hidden items

Sheets

  • Consistent sheet names and numbers
  • Correct title block
  • Correct revision and status
  • Logical arrangement of views and notes

Issue information

  • Correct revision clouding where needed
  • Correct issue status
  • Correct date and project data
  • No conflicting notes or duplicated dimensions

4. QA checks before issue

Pre-issue review

A drawing or model issue should be the end of a checking process, not the start of one.

Model QA

  • Model content matches the intended issue scope
  • Linked-model positions have been reviewed
  • Known coordination issues are recorded or closed
  • Visibility settings are intentional
  • Parameters and schedule data are complete where required

Drawing QA

  • Correct views placed on correct sheets
  • Dimensions and notes are clear
  • Tags read correctly
  • Sheet number, title and revision are correct
  • PDF / print output reviewed after export
Suggested QA split: model check → view check → sheet check → export check

5. Coordination documentation

Clashes / actions / records

Coordination is not only the act of detecting clashes. It also requires recorded actions, ownership, and documented outcomes.

Useful coordination records
  • Clash reports
  • Meeting action lists
  • Issue trackers
  • Model review comments
  • Builderswork or interface records
What should be recorded
  • The issue
  • The owner
  • The expected action
  • The target date
  • The close-out status

A coordination process becomes much stronger when teams can trace not only what was found, but what was done about it.

6. CADmep documentation & outputs

Fabrication

CADmep documentation is driven by content quality, numbering logic, and output control. Reports, worksheets, spools, and exports must all follow a repeatable standard.

Reports

  • Use controlled report formats
  • Check item consistency before issue
  • Use reports as QA tools as well as deliverables

Spools

  • Only spool stable model content
  • Confirm numbering logic first
  • Avoid early spool issue during unstable coordination

Exports

  • Check PCF scope before export
  • Check content and connectivity
  • Use standard naming and save locations
Important: Poor content control upstream will always weaken reports, numbering, spool output, and export quality downstream.

7. Naming conventions

Consistency

Naming conventions are essential for model management, collaboration, issue control, and retrieval of information. They should be agreed early and followed consistently.

Typical items to standardise

  • Model file names
  • View names
  • Sheet numbers and titles
  • Schedule names
  • CADmep service and report names
  • Export file names

Benefits of good naming

  • Faster navigation
  • Cleaner QA
  • Better searchability
  • Less duplication
  • Stronger audit trail

8. Records, revisions & traceability

Control

Documentation should be traceable. Teams should be able to understand what changed, why it changed, when it changed, and what version or revision is current.

  • Maintain revision discipline across sheets and outputs.
  • Record major changes and issue points clearly.
  • Use controlled shared locations or cloud folders for issued information.
  • Keep superseded information distinguishable from current information.
  • Make sure model issue, sheet issue, and fabrication issue states do not conflict.
Strong traceability means: a reviewer should be able to follow the path from live model → reviewed output → issued information without confusion.

9. Best practice summary

Summary

Start clean

Use the right template, naming, and standards before modelling grows.

Check before issue

Never assume the model, sheet, or export is correct without review.

Keep records

Traceability matters for revisions, actions, and project confidence.

Final takeaway: Good documentation is controlled information, not just generated information. The strongest teams build standards into the model, the sheets, the checks, and the outputs from the beginning.