View Template Strategy for Multi-Discipline Projects

View templates control what users see in every Revit view. In multi-discipline projects with architectural, structural, MEP, and interior views, template strategy determines whether coordination works or falls apart. A bad template strategy means views that show the wrong elements, filters that override the wrong categories, and teams that cannot trust what they see on sheets.

This article covers how to build a template strategy that scales across disciplines and projects, and how to use Pyvoid's template management tools to enforce it.

The Template Problem

A typical mid-size project accumulates 40-80 view templates over its lifecycle. Without a strategy:

• Templates are created ad-hoc ("Floor Plan - Copy 3")
• Nobody knows which templates are active vs. abandoned
• Filter assignments drift between similar templates
• Different disciplines create overlapping templates instead of sharing
• Template changes to fix one view break others

The root cause is that Revit provides no tools for managing templates at scale. The "Edit View Template" dialog shows one template at a time with no comparison, no audit, and no bulk operations.

Naming Convention

A consistent naming scheme makes templates self-documenting and sortable. The pattern that works across firms:

{Discipline} - {ViewType} - {Purpose} [{Phase}]

Examples:

• A - Floor Plan - Working
• A - Floor Plan - Presentation [CD]
• S - Floor Plan - Framing
• M - Floor Plan - Piping
• E - Floor Plan - Lighting
• I - RCP - Finish Ceiling
• A - Section - Wall Detail
• A - 3D - Design Review

Rules:

• Discipline prefix sorts templates by team in the dialog
• ViewType matches Revit's view type (Floor Plan, Section, Elevation, 3D, etc.)
• Purpose describes the intent, not the content
• Phase suffix (optional) distinguishes SD, DD, CD variants
• No spaces in prefix, hyphen-separated segments

Conform Names can enforce this naming pattern automatically. Configure the naming rules once and run Conform Names to rename non-compliant templates.

Template Hierarchy

Structure templates in three tiers:

Base Templates

Define the common settings shared across a discipline. Every view in a discipline starts from its base template.

• A - Floor Plan - Working (the default architectural plan)
• S - Floor Plan - Working (the default structural plan)
• M - Floor Plan - Working (the default mechanical plan)

Base templates control: scale, detail level, model categories visibility, annotation categories visibility, and V/G override rules.

Purpose Templates

Specialize the base for specific deliverables. Created by duplicating the base and modifying only what changes.

• A - Floor Plan - Presentation [CD] (adds rendering overrides)
• A - Floor Plan - Demo (turns on phasing filters, hides new construction)
• S - Floor Plan - Foundation (hides upper structure)

Purpose templates should override only what is necessary. If a purpose template changes 30 parameters while the base template controls 50, something is wrong - the purpose template is probably a fork, not a specialization.

Sheet Templates

Configure views for final sheet production. These add title block formatting, sheet-specific scale adjustments, and print-specific overrides.

Most firms can skip this tier and handle sheet-specific settings at the view level rather than adding more templates.

Filter Strategy

View filters are the second half of the template equation. Templates define which categories are visible; filters define how specific elements within those categories appear.

Filter Naming

Match the template naming convention:

{Discipline} - {Purpose} - {What}

Examples:

• A - Highlight - Non-Compliant Names
• S - Hide - Architectural Walls
• M - Color - Pipe System Type

Filter Assignment Rules

1. Shared filters go on base templates. If a filter applies to all views of a discipline, assign it at the base level.
2. Purpose-specific filters go on purpose templates. If a filter only applies to demolition views, assign it to the demo template.
3. Never assign filters to individual views. If you need a one-off filter, create a purpose template for it. Otherwise the filter assignment is invisible to anyone managing templates.
4. Document filter-to-template mapping. Use Find Used View Templates Filters to generate this mapping automatically.

Managing Templates with Pyvoid

Meta View Template Manager

Meta View Template Manager replaces the one-at-a-time workflow with a dashboard:

• Browse all templates with filter counts and usage statistics
• Diff any two templates to see exactly which parameters differ
• Bulk rename to enforce your naming convention
• Copy filters between templates by drag-and-drop
• Sync groups to keep related templates aligned (e.g., floor plan and reflected ceiling plan variants that should share the same category visibility)

Template Audit

Run Template Audit monthly to catch drift:

• Unused templates (zero view assignments) that should be purged
• Orphaned filter references (filters assigned to templates but deleted from the project)
• Naming violations (templates that do not match your convention)
• Incomplete templates (missing parameter overrides compared to the base)

Template Diff

Use Template Diff when two views look different but you cannot figure out why:

1. Select the two templates to compare
2. Review the side-by-side parameter comparison
3. Differences are color-coded - matching values are dimmed
4. Copy specific values from one template to the other

This is also useful when creating a new purpose template. Diff it against the base to verify that only the intended parameters changed.

Multi-Office Considerations

When a firm has multiple offices sharing templates:

1. Maintain a single master template file. Each office pulls templates from this file using Transfer Manager.
2. Use Sync Groups in Meta View Template Manager to define which templates must stay identical across offices.
3. Run Template Audit after transfers to verify the received templates match the master.
4. Version the master file. Store it in a shared location with date-stamped copies so offices can compare what changed.

Common Problems and Fixes

See Also

• View Template Best Practices - fundamentals of template creation and naming
• Views Panel - full reference for all template and view management tools
• Standards Enforcement - naming and conformance workflow

Last updated: 2026-04-16