Design options as Instance Peramater for revit links

[benwrightM4JKX]

Overview:
We are requesting the ability to assign and control Design Options within linked Revit models via instance parameters in the host model.

Current Limitation:
When a Revit model containing multiple Design Options is linked into another model (such as a site or masterplan), the displayed design option must be manually set per view via Visibility/Graphics (VG). This is view-specific, not instance-specific, and cannot be controlled parametrically or scheduled - making it impractical for large-scale developments.

Real-World Context:

I work for one of the top 10 house builders in the UK, where we regularly deliver large residential masterplans with over 100 housing units per site. Each housetype may have multiple variants (Detached, Semi, End-Terrace), and we need to swap between these variants frequently during feasibility and planning stages.

The lack of instance-level control over Design Options is the sole reason we still produce our early feasibility layouts in AutoCAD.
This missing functionality severely limits the potential for full adoption of Revit in the early design and option testing phases.

I’m confident that enabling this feature would significantly accelerate the transition from AutoCAD to Revit for large residential developers across the UK and beyond.

Proposed Feature:

Introduce a new instance parameter (e.g., "Design Option Override") on Revit Link instances, allowing users to select which Design Option should be displayed per instance, rather than globally or per view.

Benefits:

• Massive time savings on large developments.
• Clean, scalable workflows for residential layouts.
• Avoids bloating the model with multiple linked files for each variant.
• Enables BIM-driven feasibility and planning, rather than 2D CAD workarounds.
• Improves Revit adoption across large design teams and developers.

Optional Enhancements:

• Allow Design Option value to be tagged or scheduled per link instance.
• Support view filters or colour schemes based on the selected Design Option.
• Allow API/Dynamo access to control link instance options programmatically.

[RSomppi]

This could be easier accomplished with Types, rather than Design Options.

[benwrightM4JKX]

@RSomppi how do you create types in a Revit project though? Im not trying to create super detailed families that have all the same information as the Revit housetype project. Plus this isnt practical for new or bespoke types or options.

[RSomppi]

@benwrightM4JKX,It is practical despite your denial. I would suggest that you go over to the Revit Architecture forum and ask about using unit types. 
https://forums.autodesk.com/t5/revit-architecture-forum/bd-p/revit-architecture-forum-en

[benwrightM4JKX]

@RSomppi, im not sure you read my initial question. im not trying to create families where we already have Revit projects with sheets and schedules (Standard Houses). I just want to cycle through the design options within a LINK as a parameter as opposed to going through the V/G settings to override them on a view by view basis. much easier to have parameters on the Revit link.

How would you set out 300 slightly different homes on a site model? And print them all as separate drawing sheets?

[lucadV266P]

@benwrightM4JKX 

I’ve had this same limitation for years.

The issue is that creating separate links for every minor variation isn’t practical. In my case, linked models are apartment types and only have a slight layout change depending on where it sits in the building, orientation, services coordination, or even a purchaser variation. These changes are often too minor to justify creating and managing an entirely separate linked model (unit type), which is where Design Options would be an ideal solution.

It would be extremely beneficial if linked model instances could override or lock a specific Design Option on a per-instance basis, rather than being controlled by link host view settings (very time consuming). 

Thanks

[irshadansari058]

Currently, Revit does not allow individual instances of the same linked model to display different Design Options.

Example: A residential apartment model is linked multiple times into a host model. The apartment contains Design Options for minor layout variations, but every linked instance displays the same Design Option.

The current workaround is to control Design Options through Visibility/Graphics, but this is view-specific, requiring additional view templates, repeated setup, and coordination across multiple disciplines. It is difficult to manage and prone to errors on large projects.

Requested Enhancement:

Allow each linked model instance to have its own Design Option selection in the instance properties. This would:

• Eliminate view-specific overrides.

• Simplify coordination across disciplines.

• Reduce project setup and maintenance.

• Improve workflows for repeated units with localized variations.

This would be a valuable improvement for large residential and mixed-use projects.

Thank you for considering this feature.