Type vs. Instance Parameters
Revit's two-tier parameter scheme — type parameters apply to all instances of a type; instance parameters apply to one placement at a time.
Definition
Every element in Revit has a Type (the named definition: Single-Flush 36" x 84") and one or more Instances (each placement). Parameters live at one of these two scopes. Changing a type parameter (e.g., overall width) updates every instance of that type; changing an instance parameter (e.g., head height) updates only the selected instance.
Family authors choose type vs. instance per parameter at creation time. Project parameters also have this scope.
Why it matters
Scope confusion is the single most common Revit modelling mistake. A door height set as instance when it should be type produces inconsistent doors across a project; a type parameter where instance was needed forces 200 type variants to model.
Technical Deep Dive & Core Mechanics
At the database tier, Type vs. Instance Parameters within the Revit ecosystem relies on a structured, relational object graph rather than simple visual vectors. Each instance is tracked by a unique Global Unique Identifier (GUID), linking its geometry to semantic parameters in the project database. When rendering or scheduling, the engine performs real-time queries to resolve parameter values and apply visibility graphic overrides.
In highly federated BIM models, this data structure guarantees that changes in Type vs. Instance Parameters are instantly propagated to structural, MEP, and quantity-takeoff schedules. The coordinate registration uses a double-precision float space, preventing floating-point rounding errors during multi-mile coordinate transformations relative to the project base point.
Step-by-Step Professional Implementation
Deploying Type vs. Instance Parameters in a commercial design production pipeline requires a standardized, structured workflow to minimize model regression and file corruption:
- Parametric Alignment & Parenting: When initializing Type vs. Instance Parameters, reference it strictly to stable datum planes or shared project levels. Avoid referencing ephemeral lines or sketches that may undergo topological naming changes.
Advanced Troubleshooting & Error Diagnostics
When working with Type vs. Instance Parameters in complex multi-user BIM environments, designers frequently encounter specialized coordination anomalies. Use this checklist to diagnose and resolve typical errors:
- Topological Reference Orphaned (Revit Warn 102-A): Occurs when a sketch or parameter reference is lost due to a parent wall/slab deletion. Resolution: Edit the sketch plane and re-associate the broken constraints to active levels.
- Worksharing Permission Locks: Multiple designers locked out of modifying Type vs. Instance Parameters. Resolution: Have the active borrower perform a "Synchronize with Central" and check "Relinquish All Mine" in their collaboration panel.
Cross-Discipline Collaboration & Handoff
In global multi-office projects, Type vs. Instance Parameters is a high-frequency handoff node between diverse software packages. During cross-platform export (for example, exporting Revit drawings to IFC for coordination in Navisworks or Solibri, or converting mechanical STEP files into BIM detail families):
- Class Preservation: Ensure that Type vs. Instance Parameters is mapped to its correct IFC class classification (e.g., `IfcWallStandardCase` for walls, `IfcBuildingElementProxy` for generic parts). Unmapped components default to generic containers, losing their smart structural parameters.
- Visual Overlap Verification: Run spatial clash checks regularly in a federated viewer to verify that no geometric overlaps or clearance violations occur between Type vs. Instance Parameters and structural frameworks.
Common pitfalls
- Authoring a family with too many instance parameters — every placement requires manual setting.
- Reading a project parameter as type-scope when it was created instance-scope — schedules look wrong.
- Migrating an existing family from instance to type parameters mid-project — instance data is lost.
This concept is a core structural element of the Revit drafting and engineering environment developed by Autodesk. Autodesk's flagship BIM authoring tool — the building model becomes the single source of truth for plans, sections, schedules, and clash detection.
Relevant Revit FAQs
❓ Is Revit available on macOS?
No. Revit is Windows-only. Mac users typically run Revit inside Parallels, VMware Fusion, or Boot Camp (Intel Macs). On Apple Silicon, virtualisation requires Windows-on-ARM and is officially unsupported by Autodesk. The closest cross-platform alternative is ArchiCAD.
❓ Can Revit open RVT files from older versions?
Yes — Revit can open any older RVT, upgrading it on open. Once upgraded, the file cannot be saved back to the older version. For cross-version coordination, export to IFC or DWG, or maintain a parallel older file.
❓ Why is my Revit project so slow?
Most common causes: too many in-place families, oversized linked DWG CAD files, raster image imports, links not workset-isolated, unused worksets visible in all views, view templates not used (so views render with unique graphics settings), and too many parameters in mass schedules. Use Manage > Purge Unused and Audit on open.
⚡ Concept Self-Test
🎓 Recommended Practice Lessons
Step-by-step practical exercises and certification-aligned paths chosen by our editors to master this concept:
Revit Professional Design & Engineering Specialization
The Complete Revit 2026 Masterclass: From Beginner to Pro
Autodesk Certified Professional (ACP) - Revit Exam Study Guide & Mock Practice
🌳 Semantic Crossroads & Navigation Pathways
Trunk-Branch-Leaf ModelCore glossary, interactive graph, and domain-wide concept index.
Parent design environments and platforms implementing this method natively.