View Template Best Practices

View templates are the single most effective way to enforce visual consistency across a project. A well-maintained template library saves hours of manual V/G tweaking and eliminates "why does your plan look different from mine?" conversations.

When to Use View Templates

• Always on sheets. Every view placed on a sheet should have a template applied so printed output is predictable.
• Usually on working views. Assign a template to keep things tidy, but consider leaving some parameters unlocked so users can toggle categories while modeling.
• Optionally on coordination views. Lightweight templates that only set scale and detail level are useful without being restrictive.

If a view is purely temporary (a quick 3D check, a throwaway section), skipping the template is fine - just delete the view when you are done.

Naming Conventions

Name templates so they sort logically in the list:

{Discipline} - {ViewType} - {Purpose}

Prefix with discipline so templates cluster together. Add a Sheet vs Working suffix to distinguish locked sheet templates from flexible working templates.

What to Lock vs. Leave Unlocked

Lock these parameters (they define the standard):

• Scale and Detail Level
• V/G Overrides for categories and filters
• Model Display (coarse/medium/fine)
• Annotation crop and crop region visibility

Leave these unlocked (users need flexibility):

• Crop region size and position
• Phase and Phase Filter (unless project-wide)
• Parts Visibility (if parts are used selectively)
• Temporary hide/isolate (Revit never locks this)

A common mistake is locking everything, which forces users to duplicate the template for every small variation. Lock the visual standard; leave spatial and contextual parameters free.

Management Workflow

1. Create templates in the firm template file, not in live projects. This gives you a single source of truth.
2. Transfer templates into projects using Transfer Project Standards or Pyvoid's Meta View Template Manager sync feature.
3. Audit regularly. Use Meta View Template Manager's diff view to compare project templates against the firm master and catch drift.
4. Version your templates. When a template changes, update the last_updated note in the template's description field so teams know which version they have.

Common Pitfalls

• Too many templates. If you have 40+ templates, consolidate. Most firms need 10-15 well-structured templates.
• Orphan templates. Templates that no view uses are clutter. Audit and purge periodically.
• Unlocked filters. If a filter controls a firm standard (e.g., fire-rating color coding), lock it in the template so users cannot accidentally remove it.

Last updated: 2026-03-20