Type vs. Instance Parameters

🔗 Related Concepts

Deepen your understanding with these related topics:

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

Type vs. Instance Parameters interacts with the model's phasing system, which assigns every element a "created in phase" and optionally a "demolished in phase" attribute. Views filter elements through phase filters that combine these phase assignments with graphic override rules (show as new, show as existing, show as demolished, or hide). This mechanism allows a single model to represent the building at multiple points in its lifecycle—existing conditions, demolition, new construction—without duplicating geometry.

The workset mechanism controls editing access to Type vs. Instance Parameters in multi-user environments. When a team member takes ownership of a workset, the elements within it become editable only on that user's local copy until synchronized back to the central model. Conflicts arise when Type vs. Instance Parameters references elements owned by different users—for example, a wall in one workset hosting a door in another—requiring careful workset organization to minimize synchronization conflicts and reduce the frequency of failed-to-save errors.

Step-by-Step Professional Implementation

Deploying Type vs. Instance Parameters in a BIM production environment requires careful coordination of model integrity and data standards:

1. Initialize from the BIM Execution Plan (BEP): Bind the model to the project template that defines levels, grids, shared coordinates, and workset structure. Confirm that the BEP's LOD requirements match the current design phase.
2. Model Element Placement with Proper Classification: When configuring Type vs. Instance Parameters, assign correct IFC classifications (e.g., IfcWall, IfcSlab, IfcBeam) and ensure that type/instance parameters carry the required COBie or Uniclass data for downstream handoff.
3. Coordination and Clash Resolution: Federate the model regularly with structural, MEP, and architectural disciplines. Run interference checks to identify spatial conflicts, and log resolution actions in a BCF-compatible issue tracker.
4. Model Health Validation: Run model audit tools to detect warnings such as duplicate instances, room-bounding errors, or unjoined elements. Verify that schedules and quantity takeoffs reflect accurate, current model data before milestone submissions.

Advanced Troubleshooting & Error Diagnostics

Troubleshooting Type vs. Instance Parameters in multi-user BIM coordination workflows:

• Synchronization failures with central model: Attempting to sync Type vs. Instance Parameters changes produces "Can't find central model" or element ownership conflicts. Resolution: Verify network connectivity to the central file location. Check if another user holds editing permission on the affected workset. If the file server is unreachable, save the local changes as a backup before attempting to reconnect.
• IFC export produces generic proxy objects: Type vs. Instance Parameters elements export to IFC as IfcBuildingElementProxy instead of their correct IFC class. Resolution: Review the IFC export mapping table and verify that Type vs. Instance Parameters's category maps to the appropriate IFC entity. Custom families may need their IFC Class parameter explicitly set in the family editor. Re-run the export after correcting the mapping.
• Linked model positions shift after reload: After updating a linked model, Type vs. Instance Parameters elements in the link appear offset from their expected positions. Resolution: Verify that both the host and linked models use the same shared coordinate system. Check the link's positioning method (Auto - Origin to Origin vs. Auto - By Shared Coordinates). If coordinates were recently acquired or published, the link may need to be removed and reloaded with the updated coordinates.

Cross-Discipline Collaboration & Handoff

In federated BIM projects, Type vs. Instance Parameters is an active element in multi-discipline model exchanges. During inter-platform handoff (for example, exporting to IFC for clash detection or converting native models for coordination):

• IFC Classification Mapping: Verify that Type vs. Instance Parameters elements export with the correct IFC entity type and property sets. Unmapped or generic proxy exports lose their semantic identity, reducing the value of coordination reviews and quantity takeoffs.
• Shared Coordinates and Georeferencing: Confirm that all discipline models share the same project base point, survey point, and true north orientation. Misaligned shared coordinates produce multi-meter offsets in the federated environment, creating false clash results.
• Version and Phase Management: Stamp model exchanges with phase, revision, and LOD metadata. Coordinate on a common data environment (CDE) platform with clear status codes (work-in-progress, shared, published) to prevent teams from basing decisions on superseded model snapshots.

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.

Relevant Revit FAQs

Direct answers from our technical editorial desk concerning related workflows.

🎓 Recommended Practice Lessons

Step-by-step practical exercises and certification-aligned paths chosen by our editors to master this concept:

Practical Workflow Tips

Lessons from BIM production workflows involving Type vs. Instance Parameters:

• Establish view templates before modeling begins: Create and assign view templates for plan, section, elevation, and 3D views at the project start. When working with Type vs. Instance Parameters, consistent view settings prevent confusion in review meetings.
• Address warnings as they appear: Each warning related to Type vs. Instance Parameters (overlapping walls, duplicate instances, room boundary gaps) should be resolved promptly—warnings compound over time and degrade model performance.
• Use worksets strategically: Organize worksets around editing ownership rather than element categories. This minimizes synchronization conflicts when multiple team members work with Type vs. Instance Parameters.
• Test IFC export early in the project: Run a trial IFC export and validate the output in an IFC viewer during the first project week. Catching mapping issues with Type vs. Instance Parameters early is far easier than correcting them after months of modeling.

Sources & further reading

• Autodesk Help & Technical Documentation portal · Autodesk Inc.
• Revit Product Support Portal · Autodesk Inc.