How to Model Curtain Wall in Revit: A Step-by-Step Guide

Revit's curtain wall tools give architects control over grid layout, panel types, and embedded elements — but the workflow is more fragile than it looks. This guide covers the full standard process from type creation to panel assignment and explains why iteration often means rebuilding from scratch. It also explains how Kora Studio's Grid Editor and Panel Editor address the most common pain points for unitized facade work at LOD 100.

Table of contents

Subscribe to our newsletter

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Design to Fabrication
Revit Curtain Wall: Complete Reference for BIM Teams (2026)
The definitive reference for curtain wall in Revit — covering system families, grid setup, panel types, documentation, and the coordination failures that generate the most RFIs in facade projects.
Design to Fabrication
Unitized vs Stick-Built Curtain Wall: How to Choose the Right System for Your Project
The choice between unitized and stick-built curtain wall isn't about which system is better — it's about which one fits the project. Building height, facade geometry, volume, and schedule all drive the decision. And whichever you choose, the LOD sequence follows.

Modeling a curtain wall in Revit looks straightforward until you start iterating. The basic steps — draw the wall, set the grid, assign panels — are familiar to most architects and BIM managers. But the standard workflow has structural weaknesses that appear quickly on real projects: grids that don't flex when dimensions change, panel assignments that reset during edits, and embedded elements that behave unpredictably when the wall host moves.

This guide walks through the standard Revit curtain wall process step by step, names the specific points where it breaks down, and explains how Kora Studio addresses those gaps for unitized curtain wall design at LOD 100.

Step 1: Create or Duplicate a Curtain Wall Type

Every curtain wall in Revit starts with a wall type. In the Properties panel, select an existing curtain wall family and use "Duplicate" to create a project-specific type. Rename it with a convention that will make sense in schedules and views — type names carry through to every schedule that references the wall.

In the Type Properties dialog, you'll set the base grid spacing: vertical and horizontal grid patterns (Fixed Distance, Fixed Number, Maximum Spacing, or None), mullion types for interior and border conditions, and panel family assignments. These settings define the default behavior of every instance of this type in the project.

One immediate limitation: the grid settings here are type-level, not instance-level. Any change to vertical spacing in the type properties will update every wall instance of that type across the project. If you need different grid layouts on different facades, you need different types — or you override at the instance level, which creates its own management overhead.

For a deeper comparison of curtain wall family approaches, see Revit curtain wall system vs. loadable families.

Step 2: Draw the Curtain Wall

With a type selected, draw the curtain wall like any wall: pick the start point, trace the line, set the height. Curtain walls can be placed on a level with a top constraint, or given an unconnected height. For facades that span multiple floors, you typically draw one tall wall per bay and manage the grid internally rather than stacking walls per floor as you would with stick-built construction.

Immediately after placement, check that the wall is face-hosted or level-hosted correctly and that the base offset, top offset, and orientation are set. Curtain walls are more sensitive to base/top constraint changes than basic walls — adjusting these after grid lines and panels are assigned can cascade into broken panel assignments.

The difference between unitized and stick-built logic matters here. For unitized systems, each grid cell will eventually correspond to a factory-assembled panel unit. Revit doesn't enforce this distinction — it will let you model any configuration regardless of constructability. Understanding what you're representing is necessary context before you start. For background on the distinction, see unitized vs. stick curtain wall.

Step 3: Set the Grid

Once the wall is placed, open it in plan or elevation and use the Curtain Grid tool (Architecture tab) to add grid lines. Revit gives you three placement options for each grid line: All Segments (runs the full width or height), One Segment (hits only the cell you click), and All Except Picked (adds to all cells except one). This flexibility is powerful but requires care — partial grid lines create irregular panel configurations that are easy to create accidentally and hard to read in elevation.

Grid line spacing can be set by typing a dimension while placing, or by moving the line after placement and editing the temporary dimension. Neither method is driven by a formula. If your facade layout is based on a modular system — say, 1,500 mm panels with 50 mm joints — you're typing those numbers manually on every grid line. There is no input field where you define the module once and let Revit distribute it.

Grids can also be set automatically at the type level using Fixed Distance or Maximum Spacing. These auto-patterns work for regular, repetitive facades, but they remove your ability to position individual grid lines precisely when the facade deviates from the pattern — which it almost always does at corners, openings, and level transitions.

For more on how facade grids behave and break, see How to Create a Facade Grid in Revit.

Step 4: Assign Panels

With the grid in place, each cell contains a default panel from the type properties. To change individual panels, click on the cell boundary (not the center) until the panel highlights, then change its type in Properties. Revit supports vision panels (glazed), spandrel panels, and system panels in this workflow.

Panel assignment is done cell by cell unless the entire wall uses one panel type. There is no built-in tool for assigning panels by row, column, or zone — each cell is addressed individually. On a wall with 80 cells, that means up to 80 separate selections if you're mixing types.

Spandrel panels and vision panels are the two main categories. For the distinction between them in terms of code compliance and design documentation, see spandrel panel vs. vision glass.

One common source of confusion: Revit's curtain panel families are not the same as loadable component families. They behave differently in terms of hosting, nested elements, and schedule visibility. If a panel needs to carry schedule parameters — area, type mark, fire rating — those parameters must be explicitly built into the panel family.

Step 5: Add Embedded Doors and Windows

To add a door or window inside a curtain wall cell, select the panel in that cell and replace it with a curtain panel door or curtain panel window family. These are specialized family types hosted by curtain wall panels. Standard door and window families cannot be placed directly into curtain wall cells.

Curtain panel doors and windows must be modeled or sourced as curtain panel families. If you have a specific sill, head, or jamb profile requirement, it must be built into the family or achieved through a nested component. Revit's native curtain wall tools do not expose profile editing at the individual embedded window level.

Sizing embedded elements is also constrained: the element fills the panel cell it replaces, and the cell size is determined by the surrounding grid lines. To change the size of an embedded window, you change the grid lines — which may ripple to adjacent cells and affect their panel assignments.

Where the Standard Workflow Breaks Down

The standard Revit curtain wall workflow is functional for initial modeling but fragile under iteration. These are the most common failure points:

Grid lines don't have formula-driven positioning. Dimension values are typed manually. When a grid module changes — because the structural bay shifted or the client revised the facade rhythm — every affected grid line must be repositioned individually. There is no field where you redefine the module and have Revit recalculate.

Panel assignments don't survive certain edits. Moving grid lines, changing wall height, or swapping the wall type can reset panel assignments in the affected cells. After a geometry edit, you may need to re-assign panels across large sections of the facade.

No panel-level window editing. Changing the window profile within a panel requires modifying the family, not just the instance. This makes facade-level window editing slow and dependent on the family library.

Schedules don't update automatically. Panel counts, areas, and window-to-wall ratios must be scheduled manually, and schedule parameters must be mapped correctly to the families in use. When the model changes, schedules need to be verified against the current geometry. For more on this, see How to Automate Facade Schedules in Revit.

Iteration means rebuilding. On many projects, curtain wall iteration is handled by deleting and remodeling the wall rather than editing it — because accumulated edits and panel assignments are easier to start over than to untangle. This is the clearest sign that the workflow doesn't scale to iterative design.

Does Kora Studio Help with Curtain Wall Modeling?

Yes — for unitized curtain wall at LOD 100, Kora Studio addresses the two main breakdown points in the standard workflow: grid rigidity and panel assignment.

Kora's Grid Editor uses the same grid logic as Revit but adds formula-driven dimension fields. You define the grid module once using a formula, and Kora distributes the cells accordingly. When the module changes, you update the formula — not every grid line individually. The interface is more direct than Revit's native grid tools for this kind of repetitive, modular facade work.

Kora's Panel Editor lets you assign opaque panels or panels with a window across the grid without hunting individual cells in elevation. Windows within panels are defined using predefined profiles — no custom mullion profile creation is available, but the predefined set covers standard unitized window configurations.

Important constraints to understand: Kora works at LOD 100 only. It is designed for unitized curtain wall — it does not model stick-built systems. There are no mullions in Kora's structure: the system is Grid → Panels → Claddings and Windows, which reflects how unitized panels are actually manufactured. Corner panels are supported using the same system.

If you're evaluating Kora for a project, see the full feature list or book a demo.

FAQ

What is the difference between a curtain wall system and a basic wall in Revit? A curtain wall system uses a grid-and-panel structure rather than a solid layer assembly. Panels are placed inside grid cells and can be assigned different families (vision, spandrel, door). Basic walls use compound layer assemblies and don't support this cell-based panel logic. For a detailed comparison, see Revit curtain wall system vs. loadable families.

Can I place a regular window family inside a Revit curtain wall? No. Standard window families are hosted by basic walls. Inside a curtain wall, you must use curtain panel door or curtain panel window families, which are a distinct family category. Replacing a panel cell with one of these families is the correct method.

Why do my panel assignments reset when I edit the curtain wall? Revit rebuilds the grid cell structure when certain geometry changes occur — grid line moves, wall height changes, type swaps. This rebuild can orphan or reset panel assignments in the affected area. It's a known limitation of the system and is one reason curtain wall editing is often handled by full redraw rather than incremental edit.

Does Kora Studio replace Revit for curtain wall modeling? No. Kora Studio is a Revit-native plugin. It runs inside Revit and outputs to Revit. It adds a structured editor for unitized curtain wall grids and panels at LOD 100, but the result lives in the Revit model. You are not working in a separate application.

Is LOD 100 sufficient for design development? LOD 100 represents schematic-level geometry — overall form, approximate dimensions, basic panel arrangement. It is appropriate for early design stages, facade system comparisons, and preliminary area calculations. For detailed connection geometry, shop drawing coordination, or fabrication, higher LOD levels are required. See what LOD do architects need for guidance on when each level applies.

Book a Demo

See how Kora Studio transforms façade design into build-ready deliverables in minutes.

Latest Insights

Design to Fabrication

AGACAD vs Kora Studio: Which Revit Facade Plugin Do You Need?

AGACAD and Kora Studio both work inside Revit, both handle curtain walls — but they serve completely different project phases. AGACAD produces LOD 400 fabrication documentation. Kora Studio accelerates LOD 100–300 design iteration. Choosing the wrong one costs weeks.
Revit Workflows

Best Revit Add-ins for Architects: Productivity Tools vs Façade Workflow Systems

Not all add-ins solve the same problem. Here’s why façades need a workflow layer like Kora.
Design to Fabrication

Best Revit Plugins for Facade Design in 2026: An Architect's Comparison

Five Revit plugins for facade design compared — what each tool does, which project phase it covers, and how to choose based on your workflow. No one plugin fits every project type.