Templates & Standards — Use templates and standards (view templates, line styles, object styles) (conceptual)

Long before digital modeling existed, architects and designers relied on carefully maintained sets of drafting conventions — standardized line weights, title block formats, hatch patterns, and dimensioning styles — to ensure that any professional reading a drawing could interpret it unambiguously. These conventions were codified in national standards such as the AIA CAD Layer Guidelines and the National CAD Standard (NCS), which prescribed everything from layer naming to pen thicknesses. When the profession transitioned from hand-drafting to CAD and eventually to Building Information Modeling (BIM), the need for graphic consistency did not disappear — it migrated into software-based templates and style definitions that could be shared, versioned, and enforced automatically.

The central question that templates and standards answer is deceptively simple: How do we guarantee that a model created by dozens of collaborators looks, reads, and behaves as though a single mind produced it? In Revit, the answer lies in three interlocking systems — view templates, line styles, and object styles — each operating at a different level of graphic control.

Understanding Revit's standards ecosystem begins with recognizing that graphic representation in BIM is fundamentally different from CAD. In CAD, you draw lines that happen to represent walls; in Revit, you place intelligent objects whose appearance is governed by a cascading hierarchy of style rules. This hierarchy — from global project template down to individual view overrides — ensures consistency while still allowing targeted customization when design intent demands it.

The diagram above reveals the key architectural insight behind Revit's approach: graphic control cascades downward. Settings defined higher in the hierarchy propagate automatically to everything below unless explicitly overridden. This cascade is analogous to CSS inheritance in web design — a body-level font declaration applies everywhere until a more specific selector intervenes. In practice, this means a well-crafted project template can control the appearance of hundreds of views simultaneously, and a single edit to an object style or view template ripples through the entire document set without requiring anyone to touch individual sheets.

For Visual Arts students accustomed to thinking about brand systems and design guidelines, this hierarchy should feel familiar. Just as a museum's identity system specifies typefaces, color palettes, and spacing rules at various levels of granularity — from institution-wide to exhibition-specific — Revit's standards system operates at graduated scopes. The discipline lies not in memorizing every setting, but in understanding where in the cascade a particular graphic decision lives, and why it was placed there.

A view template in Revit is essentially a named snapshot of every view property that affects display. When you assign a view template to a view, each property can be individually toggled to 'include' or 'exclude.' An included property is locked — the template dictates its value, and users cannot change it from the view's property palette. An excluded property reverts to whatever the view had before the template was assigned, allowing selective flexibility. This include/exclude mechanism is what distinguishes Revit view templates from simpler 'preset' systems in other software.

Properties Controlled by View Templates

A critical distinction exists between applying a view template and assigning one. Applying a template copies its settings into the view once — future template edits will not propagate. Assigning a template creates a live link: when you modify the template, every assigned view updates automatically. For standards enforcement, assignment is almost always preferred because it maintains a single source of truth.

Object Styles: The Category Baseline

Every Revit element belongs to a category — Walls, Doors, Furniture, Structural Columns, and so on. The Object Styles dialog (accessed from the Manage tab) lists every category and subcategory in three tabs: Model Objects, Annotation Objects, and Imported Objects. For each entry you control four properties: line weight (a pen number from 1 to 16), line color (RGB value), line pattern (solid, dash, center, hidden, or custom), and material. Projection and cut representations are set independently, because a wall's visible face and its cut section require different visual weights.

Line Weights: The Pen Number System

Revit uses a pen number system (1 through 16) rather than absolute millimeter widths. Each pen number maps to a printed thickness that varies by view scale — a deliberate design decision inherited from traditional drafting, where finer detail at larger scales demanded proportionally thinner lines. You configure these mappings in the Line Weights dialog (Manage → Additional Settings → Line Weights). Pen 1 is always the thinnest, typically 0.1 mm at 1:100, and pen 16 the thickest, perhaps 2.0 mm. The scale-dependent mapping table ensures that a wall drawn with Pen 5 looks proportionally correct whether printed at 1:50 or 1:200.

Line Patterns & Custom Definitions

A line pattern defines the repeating dash-gap sequence of a line. Revit ships with standard patterns — Solid, Dash, Hidden, Center, Dot — but firms routinely create custom patterns to represent site boundaries, setback lines, fire separation ratings, or phasing distinctions. Each pattern is defined as an alternating sequence of dash lengths and gap lengths in real-world units (e.g., 6 mm dash, 2 mm gap, 1 mm dot, 2 mm gap). These patterns combine with pen numbers and colors to produce fully specified line styles that users select from a dropdown when drawing detail or model lines.

Imagine you are a BIM coordinator at a mid-size architecture firm about to start a new mixed-use project. Your firm's standard requires that all 1:100 floor plans show walls with a heavy cut line, furniture in halftone, and structural grids visible but in a light gray. The following walkthrough shows how you would create and assign a view template to enforce these rules.

The template and standards concepts discussed so far represent the foundational layer of BIM quality control. In advanced practice, these concepts connect to broader frameworks that automate enforcement and extend consistency beyond a single project file. Understanding where basic templates end and enterprise-level standards management begins prepares you for the workflows you will encounter in large firms, public-sector projects, and international collaborations.

As you advance in your BIM education, you will find that templates and standards are not static artifacts but dynamic components of an evolving quality ecosystem. The ISO 19650 series, adopted internationally for information management in construction, formalizes the idea that every digital deliverable must be produced according to agreed-upon standards — and your Revit project template is the tangible embodiment of that agreement. Mastering the conceptual foundations covered in this lesson positions you to engage meaningfully with these professional-grade workflows.