Revit Tip: Tokenized, Sortable Revit Naming Standard

Consistent, human- and machine-readable naming is the fastest way to make your Revit projects easy to archive, search, automate, and audit.

Adopt a tokenized pattern across models, views, sheets, links, exports, and folders. Keep it concise, sortable, and enforced from day one.

Core pattern (recommended order)

• Discipline: A | S | M | E | P | C
• ProjectCode: short, unique alphanumeric (no spaces)
• Site/Building: S01 | B01 | TWR-N
• ContentType: MODEL | LINK | VIEW | SHT | FAM | NWC | IFC | PDF | DWG
• Detail: Level/ViewType/Package (use underscores for subparts)
• Status: WIP | SHARED | PUBLISHED | IFC | ASBUILT
• Revision/Version: R2 | v015 (use leading zeros)
• Date: YYYYMMDD (ISO 8601 for sorting)

Separators: hyphen “-” between tokens; underscore “_” inside a token detail. Avoid spaces, slashes, and special characters.

Revit-specific guidance

• Project Information: Create parameters that mirror your tokens (ProjectCode, Building, Status). Map to shared parameters in the title block to auto-populate sheets and transmittals.
• Views: Name with Discipline-ProjectCode-Building-ViewType_Level-Descriptor-Status (e.g., A-PJT123-B01-PLAN_L02-Unit-Typ-WIP). Use Browser Organization rules that group by View Type, Level, and Phase so names sort naturally.
• Sheets: Keep sheet numbers standard (A101), and use sheet names that begin with key tokens for fast filtering (e.g., A-PJT123-B01-SHT-A101-GA-L02-PUBLISHED_R2).
• Worksharing: Central model as A-PJT123-B01-MODEL-WIP_v015_20260622.rvt; local files as A-PJT123-UserInitials_20260622.rvt. Consistent naming prevents cross-project mix-ups.
• Linked models: Mirror the same convention with Discipline and Status tokens (e.g., S-PJT123-B01-LINK-STRUCT-SHARED_v010_20260615.rvt). This keeps Manage Links readable and archivable.
• Exports: Set print and export naming to use Sheet Number + Sheet Name or your token pattern. Apply to PDFs, NWC, IFC, and DWG so archives remain uniform.
• Families: Prefix office-standard families with Org and Category (e.g., ACME-A_Doors-Single-Flush_v003.rfa) and control with a type catalog for consistency.

Archiving workflow (repeatable and auditable)

• Foldering: 06_Archive/20260622_PUBLISHED_R2 (date + status). Keep each milestone in a sealed folder.
• Model prep: Detach from Central, Audit, Purge (judiciously), and Compact. Save with final version/date tokens.
• Bundle: Include all linked models, the Shared Coordinates file, key schedules, and the keynote file. Use eTransmit for completeness.
• Naming control: Maintain a README and a Token Dictionary (CSV) describing each token and allowed values.
• Validation: Use Dynamo or a simple script with a regex pattern to flag nonconforming names before issue.

Quick wins

• Define conventions in your Revit template and office BIM manual.
• Enforce via View Templates, Browser Organization, and shared parameters.
• Train teams and set up a pre-issue checklist to catch violations.
• Apply the same pattern to cloud containers and transmittal ZIPs.

Need Revit licenses, training, or add-ons to support standardization? Explore NOVEDGE for tailored solutions.

For procurement and expert advice on Autodesk workflows, connect with NOVEDGE and streamline your BIM standards from template to archive.