Design options in Revit: accept, promote, delete, show them

Design options in Revit let you carry several competing versions of a design inside one model: 2 roof forms, 3 entry configurations, a brick facade against a timber one. One file, no parallel models, no folder of copies with dates in the filename. Revit design options are useful, but their rules confuse people, and the alternatives can be hard to show.

You need to know how the options behave in the model and how you will present them when the client has to choose.

How design options in Revit actually work

Your model has a main model, everything common to every version, plus option sets, each holding alternatives. One option per set is the primary. That is what schedules, exports and views show unless you tell them otherwise.

The workflow:

1. Manage tab → Design Options → New option set. Name it for the decision: "Entry configuration" tells you more than "Option A".
2. Create the options inside the set. "Canopy entry", "Recessed entry". Explicit names pay off in every dialog after this one.
3. Move existing elements into an option. Select the geometry that varies, use Add to Set, choose which options it belongs to. Everything you leave alone stays in the main model.
4. Edit inside the option. Activate an option, model its version, finish. Elements you create while an option is active belong to that option.
5. Control visibility per view. Each view's Visibility/Graphics → Design Options tab picks which option that view displays. Duplicate a view per option and you have parallel presentations of the same building.
6. Accept the winner. Make the chosen option primary, then use Accept Primary to merge it into the main model and delete the rest of the set. Do this when the decision is made. Option sets kept "just in case" become more model to maintain.

The rules that trip everyone

• An element lives in one option set at most. Geometry cannot belong to 2 sets. If a wall participates in 2 independent decisions, restructure the sets.
• References across the boundary are restricted. Elements in the main model cannot host or be hosted by option elements in ways that would break the other options. Revit will block or warn, and the fix is usually moving the host into the option too.
• Tags and dimensions bind to visible options. Annotate in the option-specific duplicated views. In shared views, the annotations can vanish when the option switches.
• Schedules follow the primary. Quantity comparisons between options need per-option schedule views with the right Design Options setting. Check that setting before presenting the numbers.
• Worksharing interacts. On multi-user projects, agree who edits inside which option. Simultaneous edits in one option can collide.

The shared geometry stays in the main model. Each option holds the part you are still deciding. Keep that boundary clear as you work.

Accepting, promoting and deleting Revit design options

Make Primary and Accept Primary do different jobs. Both live in the Design Options dialog (Manage tab → Design Options). Menu positions and wording shift a little between Revit versions.

1. Make Primary promotes a secondary option inside its set. Select the option, click Make Primary, and it becomes the version views, schedules and exports show by default. Nothing is merged and nothing is deleted. You can still compare the alternatives.
2. Accept Primary ends the decision. It merges the primary option into the main model, deletes the other options in that set, and removes the set. The accepted option's elements become ordinary main-model elements. To move a design option to the main model, make that option primary first, then accept.
3. Save a copy before you accept. The copy preserves the alternatives you are about to discard. Once you have saved over the working file, those alternatives are no longer in it.
4. Deleting an option removes its elements. You can delete a single option or a whole set from the same dialog. Elements inside a deleted option are deleted with it; they do not fall back into the main model. Views set to display that option are affected too, and Revit warns you first.
5. Duplicate a view per option and name it. "Street view, canopy entry" tells you which alternative you are looking at. "3D View 7 Copy 2" does not. Those names also help when you clean up after the decision.

Why design options in Revit are cheap to build and expensive to show

Revit lets you maintain 3 alternatives in one model. Showing those 3 alternatives convincingly adds a separate cost: every option needs its own imagery, and imagery has traditionally been priced per image. 3 options, times 2 views, times a revision round. At hours per render, or hundreds per outsourced image, a practice may only be able to afford to put 1 alternative in front of a client.

The imaging budget can narrow the presentation before the client sees it. You develop one direction, present it and defend it, even when the design process produced several answers. The client then reacts to the only image they were shown. They have to imagine the alternatives from your description.

When a rendered image takes about 30 seconds from a viewport screenshot, showing each option becomes easier to justify. Screenshot each option view and render it. You can put 3 realistic versions of the building on the table in the same meeting, while the decision is still open.

Render-driven exploration: using renders to compare alternatives and make a design decision while the options are still open.

I build SecondRender, which is one way to do this. AI-generated imagery varies between runs, so treat the per-option renders as convincing representations of each direction, not as pixel-final documents. Carrying one option's exact detailing into a second perspective is still a real challenge. That is a property of the whole category of AI image models rather than a bug in one product.

Fidelity mode keeps your geometry authoritative. A saved style keeps the look consistent across the options, so differences in lighting do not become the basis of the comparison. For pixel-final deliverables the traditional pipeline still applies, and the people who run it are doing a different job than this one.

The workflow, end to end: duplicate a camera view per option, set each duplicated view to its own option, screenshot each, render each with the same style, present the set.

That gives the client something concrete to compare. It also leaves you with a presentation decision: which alternatives belong in this round, and what are you asking the client to choose?

What happens when the options reach the client

More images can mean more indecision. An architect on Reddit, asked about hardware: "rendering blows our project budget every time because it creates client indecision." Another, on contract scope: "Unbounded on-call turns into unpaid redesign very quickly." A wider set of images widens the conversation. The fee needs an agreed limit on that work.

Polished images can also bring feedback you cannot act on. A visualization freelancer on Reddit:

Comments like "I'm not sure about this" or "something feels off" come up a lot.

From the project management side, a comment on r/Architects: "“WOW” isnt a measurable metric and has no actionable feedback."

There is also a legitimate worry that a client will read a photoreal image as a finished design. The image can look settled while the design is still open. Say out loud what stage each image represents and which decision you are asking the client to make.

Before presenting the set:

• Keep it to 2 or 3 options per decision. Showing 6 branches gives the client a much wider comparison. Keep the round focused on the choice you need.
• Name the decision. "Entry configuration: canopy or recessed" tells the client what they are being asked to choose. "Option A, B, C" leaves that work to the presentation.
• Put the round in the fee. Agree how many options, how many views, how many revision rounds, and what a new direction costs. Do this before the images exist, while the scope of the round is clear.
• Check every image against the view it came from before anyone else sees it. An AI-assisted image can move a window or invent a detail you then have to defend. I ran that check in detail for Nano Banana and architecture.

When Revit design options are the wrong tool

Whole-building variants, different footprints or different massing strategies, are better as separate files. Design options are for bounded alternatives inside a shared design.

Use phasing for phases. Keeping options alive after a decision leaves more model to maintain, so make the winner primary and accept it when you are ready to discard the alternatives.

Try render-driven exploration on the next set you build: 2 options, one camera view each, screenshots into a render. Present them with a specific decision attached. You can judge whether the comparison helps your next client meeting from that small test.

Design options in Revit: common questions

How do you accept design options in Revit?

In the Design Options dialog (Manage tab → Design Options), make the option you want primary, then use Accept Primary. Revit merges it into the main model and deletes the other options in that set. Save a copy of the file first: once you have saved over it, the discarded options are gone.

How do I move a design option to the main model?

There is no separate move command. Make the option primary inside its set and run Accept Primary. Its elements become ordinary main-model elements. Revit deletes the other options in that set, so save a copy if those alternatives still matter.

How do I get rid of design options in Revit?

Accept Primary keeps the primary option's geometry and ends the set. Use it when you have chosen the design you want to keep. Deleting an option, or a whole set, removes the elements inside it. Use that route when you want to discard the alternative and its geometry.

Can I render each design option?

Yes. Duplicate a camera view per option, set each view's Visibility/Graphics → Design Options to one option, then render or screenshot each in turn. Any renderer that reads a Revit view handles it: how to render in Revit walks the paths, and the rendering software for Revit comparison sorts them by phase and cost.

Related reading: how to render in Revit covers the full rendering workflow for Revit users, and the complete guide to architectural rendering covers the economics of presenting multiple options.