Curtain Wall Systems in Revit: Modeling and Facade BIM Coordination

Introduction

A curtain wall looks simple in a rendering. Glass, a grid of lines, maybe a shadow box panel where the slab meets the facade. In Revit, that same wall is one of the more demanding elements to model correctly, because it sits at the intersection of three disciplines that rarely share a modeling standard: architectural design intent, facade engineering, and the manufacturer who actually fabricates the system.

Most BIM professionals learn curtain wall modeling by trial and error. They build a grid, load a panel family, get something that looks right in a 3D view, and only discover the gaps when the facade consultant asks for a schedule that doesn’t exist, or when clash detection returns hundreds of false positives because mullions were never modeled with real depth.

This guide covers curtain wall modeling as a coordination discipline, not just a geometry exercise: how curtain wall system families actually work, how to build grids and mullions that hold up under scrutiny, how to structure panel families so they carry real data, and how to coordinate the facade model with structure, MEP, and the facade manufacturer without the usual friction.

How Curtain Wall System Families Actually Work

Curtain wall in Revit is a special category of wall, a system family, which means you cannot load it from an external .rfa file the way you load a door or a light fixture. You define curtain wall types by duplicating an existing type inside the project (Architecture tab > Wall > Curtain Wall) and editing its type properties, or by bringing a pre-built type in through your firm’s project template.

Every curtain wall type has three layers working together:

1. The curtain grid, the layout lines that divide the wall into panels, driven by horizontal and vertical grid pattern settings (fixed distance, fixed number, or maximum spacing).
2. Mullions, the framing members that sit on the grid lines, assigned per grid line or automatically to the whole grid.
3. Panels, the infill at each grid cell, which can be basic system panels (glazed or solid) or loadable curtain panel families for anything more specific than flat glass.

Understanding that these are three separate, editable systems layered on one wall is the single most useful mental model for troubleshooting a curtain wall that “looks wrong.” If a panel isn’t updating, check the grid first. If a mullion won’t join correctly at a corner, that’s a mullion-family and corner-condition issue, not a panel issue.

Setting Up Grids and Mullions That Survive Design Changes

Grid layout should be driven by real dimensions from day one, not eyeballed to look tidy in an early massing study.

Fixed distance grid layout locks panel width or height to a set dimension and lets the last panel take up the remainder, which is realistic for most unitized systems where panel size is fixed by the manufacturer’s module. Fixed number divides the wall into an exact count of panels regardless of overall wall length, useful for symmetric facade bays but risky if the wall length changes during design development, since panel width will silently resize. Maximum spacing caps panel size but lets Revit fit as many equal panels as possible, which is the safest default for early design when the final module hasn’t been locked yet.

Assign mullion types by grid line, not just at the “all grid lines” default, once the design has a distinct perimeter mullion versus interior mullion versus a deeper structural mullion at a defined bay spacing. Real facade systems almost never use one mullion profile everywhere. A curtain wall with identical mullions at every line, including the base and head conditions, is a strong sign the model hasn’t caught up with the actual facade design yet.

Corner mullions deserve their own attention. Revit’s default corner mullion types (L corner, trapezoid corner, quad corner) rarely match a real manufacturer’s corner extrusion, which is one reason experienced modelers build a custom corner mullion family that reflects the actual profile shown in the facade engineer’s shop drawings, rather than accepting the generic default all the way to construction documents.

Panel Families: System Panels Versus Loadable Panels

Basic system panels (Glazed, Solid) live inside the curtain wall type and work fine for early massing and simple facades. They are fast to set up and adequate when the design intent is just “glass here, opaque spandrel there.”

The moment a facade needs anything specific, a vision panel with a defined glazing makeup, a spandrel panel with insulation and a backpan, a louver, an operable vent, a shadow box, it should become a loadable curtain panel family instead. Loadable panel families support nested families, shared parameters, and the type of embedded data a facade schedule actually needs.

A well-built curtain panel family should carry:

Parameter	Why it matters
Panel type / manufacturer system name	Ties the Revit element to a real product in the facade schedule
Glazing makeup (IGU description, coating, thickness)	Feeds thermal and visual light transmittance checks, and procurement
U-value / SHGC	Required for energy compliance documentation without re-deriving it manually
Frame/mullion profile reference	Keeps the visual model consistent with the fabricator’s actual extrusion
Fire rating (for spandrel or fire-rated panels)	Needed for code compliance schedules, easy to miss if only tracked in a spec document

Building this data into the family once, at the type level, means every schedule pulled later (quantities, glazing area, U-value compliance) is accurate without a modeler re-entering values by hand for every instance.

Parametric Facade Panels for Repetitive and Complex Geometry

Most facades are not flat. Bay windows, angled panels, twisted towers, and articulated shadow boxes all need panel families that respond to the curtain grid’s actual cell geometry rather than a fixed rectangle.

Build these as adaptive or profile-driven families referencing the grid cell’s corner points, so a single family type can populate a curved or faceted facade without a modeler manually adjusting hundreds of individual panels. This is where a lot of BIM Pro time gets wasted on complex facades: modeling each panel as a unique, manually-edited instance instead of investing in one parametric family that adapts automatically as the grid or massing shifts during design development.

Even on straightforward rectangular facades, a parametric mullion depth and panel thickness driven by type parameters (rather than hard-coded dimensions inside the family geometry) pays off the first time the facade engineer issues a revised profile depth. Change the type parameter once, and every instance across the building updates, instead of a modeler manually swapping hundreds of family instances one at a time.

Coordinating With Facade Engineers and Manufacturers

Curtain wall is almost always a delegated design element: the architect sets design intent (module, sightlines, glazing appearance), and a specialist facade engineer or the manufacturer’s own engineering team develops the actual structural and thermal performance, often after the architectural model is well underway.

This creates a predictable coordination gap if it isn’t managed deliberately:

• Early design (LOD 200-300): the architectural model shows generic system panels and approximate mullion sizes, enough to communicate design intent and run early energy analysis.
• Design development to construction documents (LOD 300-350): the facade engineer or manufacturer issues shop drawings with real mullion profiles, anchor details, and thermal break locations. The BIM team’s job is to update the Revit families to match those profiles closely enough that clash detection and clearance checks mean something.
• Fabrication (LOD 400): the manufacturer typically works in their own detailing software (often not Revit at all), and delivers shop-drawing-level information back for reference, not necessarily as a native Revit model.

A practical coordination checkpoint list:

1. Confirm mullion depth and profile against the facade engineer’s issued drawings before running structural clash detection, not against the architect’s original design-intent dimension.
2. Request anchor and bracket locations from the facade package early, since these are a common clash source with structural steel and slab edges that a generic curtain wall model won’t show.
3. Align panel module and joint locations with the structural grid where the design calls for it, a mismatch here is a common source of rework late in construction documents.
4. Track glazing performance data changes (a spec revision on coating or IGU makeup) back into the Revit family parameters, not just the specification document, so schedules and energy models stay in sync with what’s actually being ordered.

Structural and MEP Coordination Around Curtain Walls

Curtain wall clash detection is not just “does the glass hit the beam.” The clashes that actually matter are usually more specific:

• Mullion versus slab edge or spandrel beam, where a mullion depth increase late in design suddenly conflicts with structure that was locked earlier.
• Anchor and bracket clearance, since these embedded connections need real clearance to structural steel, not just visual proximity in a 3D view.
• MEP penetrations through spandrel zones, where ductwork, conduit, or fire protection piping routed near the perimeter needs to clear the curtain wall’s structural mullions and anchors, a clash type easy to miss if MEP coordination views don’t include the curtain wall’s structural elements at full detail.
• Interior finishes and ceiling returns meeting the curtain wall head condition, particularly on floors with a shadow box or a return air plenum that runs right up to the facade.

Run these checks with curtain wall mullions and panels set to a detail level that actually shows their real geometry, not the simplified representation Revit sometimes defaults to in coordination views. A curtain wall shown as a flat glass plane in a Navisworks clash test will miss every mullion and anchor clash entirely.

LOD and LOI Requirements for Facade BIM by Design Stage

Design Stage	Geometric Detail (LOD)	Information Required (LOI)
Concept / Schematic	Massing-level curtain wall, generic panel type	Approximate module size, glazing ratio for area studies
Design Development	Real grid and mullion sizes from facade consultant	Preliminary U-value, panel type differentiation (vision/spandrel)
Construction Documents	Manufacturer-confirmed mullion profiles and anchors	Full glazing makeup, fire ratings, manufacturer system reference
Fabrication / As-Built	Shop-drawing accurate geometry (often manufacturer-modeled)	As-ordered product data for O&M and facade maintenance records

Agreeing this table with the design team and the facade consultant at project kickoff, as part of the BIM Execution Plan, removes a huge amount of back-and-forth later about “how detailed does the curtain wall need to be right now.”

Exporting Facade Data Through IFC

Facade elements export to IFC as IfcCurtainWall, IfcMember (mullions), and IfcPlate or IfcWindow (panels, depending on how they were built). A few checks before export matter more for curtain walls than most other categories:

• Confirm that shared parameters carrying glazing or performance data are mapped to IFC property sets, not left as Revit-only parameters that silently disappear on export.
• Check that nested loadable panel families export as distinct elements rather than collapsing into a single generic curtain wall representation, which happens if the panel family wasn’t built with IFC export in mind.
• Validate a sample IFC export in a viewer (Solibri, BIMcollab, or the free BIMvision) before delivering it, specifically checking that panel type data survived the round trip.

Common Mistakes in Curtain Wall Modeling

• Using default corner mullion types all the way to construction documents, instead of building a custom family that matches the manufacturer’s actual corner extrusion.
• Leaving all grid lines on one mullion type, when the real facade has distinct perimeter, interior, and structural mullion profiles.
• Building panel families as flat rectangles with no embedded data, which looks fine visually and produces useless schedules.
• Not updating mullion depth after the facade engineer issues real profiles, so clash detection runs against dimensions nobody actually intends to build.
• Ignoring anchor and bracket clearance, since visual clash tests on glass and mullions alone miss the connections that most often conflict with structure.
• Skipping detail-level checks before clash detection, running coordination against a simplified curtain wall representation that hides real mullion and anchor geometry.
• Manually editing individual panels on a complex facade, instead of investing in one parametric, grid-driven panel family.

Best Practices for Facade BIM Coordination

1. Agree an LOD/LOI table for the facade package at kickoff, so the architectural model, the facade engineer’s deliverables, and the BIM Execution Plan all target the same detail at each stage.
2. Build custom mullion and corner families early once real profiles are available, rather than carrying Revit defaults into construction documents.
3. Carry manufacturer and performance data at the family type level, not in a separate spreadsheet that drifts out of sync with the model.
4. Set curtain wall detail level to show real mullion and anchor geometry before running any structural or MEP clash detection.
5. Track facade design changes back into the Revit families immediately, since a stale mullion profile is one of the most common causes of clash reports nobody trusts.
6. Use parametric, grid-referenced panel families for non-rectangular facades, so geometry updates propagate instead of requiring manual edits.
7. Validate IFC exports specifically for facade data, checking that panel type and performance parameters survive the round trip.

Where This Fits in a BIM Career

Facade BIM sits in an unusual spot: it needs the same modeling discipline as structural or MEP work, plus the ability to coordinate with a specialist consultant and manufacturer who often work outside Revit entirely. BIM professionals who get comfortable managing that handoff, translating a facade engineer’s shop drawings into families that carry real data and coordinate cleanly, become the person a project turns to whenever the facade package gets complicated.

If you’re building toward a BIM coordinator role, curtain wall and facade coordination is a strong specialization to develop alongside architectural and MEP modeling, since it’s one of the areas where a generic Revit skillset alone isn’t enough. Archgyan’s Revit courses cover facade modeling workflows as part of the broader BIM coordination curriculum, so you can build that cross-discipline fluency in one place. Browse the Archgyan course catalogue to see how facade work fits the wider curriculum.

Conclusion

A curtain wall model earns its keep when it does more than look right in a rendering: when its mullions carry real profiles, its panels carry real performance data, and its geometry survives contact with a structural clash test. Get the grid, mullion, and panel family structure right early, keep it in sync with what the facade engineer and manufacturer are actually issuing, and the facade package stops being the part of the project that surprises everyone in construction documents.