"Parametric" has become a marketing term applied to almost any facade with a non-rectangular geometry. In practice, it means something specific: a design system in which geometry is governed by parameters and constraints, so that changing one value propagates changes consistently through the model without manual intervention. Understanding the distinction matters because the tools, skills, and workflows required for parametric design are fundamentally different from conventional modeling — and the consequences of getting it wrong compound through every phase of the project.
What Parametric Actually Means in Facade Design
In a conventional (non-parametric) facade model, dimensions are drawn explicitly. If a panel is 1,500 mm wide, that width is entered once as a number. If the width needs to change to 1,400 mm, every instance of that dimension must be found and updated manually. At scale — a curtain wall with dozens of panel types across hundreds of units — this is error-prone and time-consuming.
In a parametric model, dimensions are expressed as parameters — named values that can be referenced, constrained, and driven by formulas. A panel width might be defined as GridSpacing - FrameOffset * 2. When GridSpacing changes, the panel width updates automatically. Constraints ensure that related geometry stays consistent: if the panel width changes, the window within the panel recenters; if the window recenters, the frame clearances recalculate.
This is constraint-based modeling: the geometry is not a set of fixed numbers but a set of relationships. The model responds to changes rather than having to be manually redrawn.
For facade design specifically, parametric modeling means that grid spacing, panel dimensions, window positions, and cladding offsets can all be adjusted by changing a small number of driving parameters — and the entire model updates consistently. This is not just a convenience; it is what makes iterative design feasible at the pace that projects actually move.
Parametric Families in Revit
Revit's family system is the primary vehicle for parametric design within the platform. A Revit family defines geometry through parameters and constraints rather than fixed dimensions. Family parameters can be instance-level (unique to each placed instance) or type-level (shared across all instances of a given type). Parameters can drive dimensions, visibility, material assignments, and calculated values.
For curtain wall design, parametric families can define panel geometry, window positions, spandrel dimensions, and frame profiles — all governed by parameters that respond to changes in the grid or the overall wall configuration. When a grid spacing changes, a well-constructed parametric panel family adjusts its geometry automatically and correctly.
Revit families also support formulas: parameters can be calculated from other parameters using arithmetic expressions, conditional logic, and unit conversions. This is what makes formula-driven design possible within Revit without requiring external scripting.
For information on how Revit schedules connect to parametric family parameters, see Revit facade schedule automation. For context on how the curtain wall system family differs from loadable panel families, see Revit curtain wall system vs. loadable families.
Parametric vs. Scripted: Different Tools, Different Skills
Parametric design is often conflated with scripted design — tools like Dynamo (built into Revit) and Grasshopper (for Rhino) are sometimes called "parametric tools." They are more precisely described as visual programming environments: they use scripts (node-based graphs) to generate or manipulate geometry procedurally. This is a different approach from the constraint-based parametric families native to Revit.
The distinction matters for several reasons:
- Skills required. Native Revit parametric families require understanding of Revit's family editor, parameter types, and formula syntax — skills that most BIM-trained architects and technicians have. Dynamo and Grasshopper require programming logic, graph construction, and debugging skills that are not standard in architecture practice.
- Maintenance burden. A Dynamo graph that generates curtain wall geometry must be maintained alongside the model. If Revit updates or the graph is opened on a different machine without the same node packages, it may fail. Native parametric families are self-contained within the Revit file.
- Integration. Geometry created by Dynamo or Grasshopper must be pushed into Revit as model elements. This push process can introduce inconsistencies, especially when the script is run multiple times as design evolves. Native parametric families are always part of the Revit model and update with it.
- Use cases. Scripted tools are most valuable for complex, non-standard geometry that cannot be achieved with native families — organic forms, non-repeating panel layouts, computational optimization. For standard curtain wall design with repeating panel types, native parametric families are more appropriate and more maintainable.
The question is not which tool is better in the abstract, but which is appropriate for the task. A high-rise commercial curtain wall with repeating unitized panels does not require Dynamo or Grasshopper. A complex double-curved parametric facade might. Using a scripted tool where a native parametric family would suffice adds unnecessary complexity and a skill dependency that most project teams cannot sustain.
What Breaks When Facade Families Are Not Parametric
Non-parametric facade families — families with fixed dimensions rather than driven parameters — are common in practice. Many firms use generic panel families from manufacturer catalogs or from Revit's default content. These families work for visualization and early coordination, but they create specific problems as design develops:
- Manual update burden. Every design change requires manually updating dimensions in every affected family instance. On a large curtain wall project, this can mean hours of manual editing for a single panel dimension change.
- Documentation drift. When models are updated manually, the schedule and the model often diverge. Panel types in the schedule reference dimensions that no longer match the geometry. This inconsistency is a primary source of curtain wall RFIs. See why curtain wall projects generate so many RFIs for the full picture.
- Design iteration friction. Without parametric families, evaluating design alternatives requires rebuilding geometry for each option. This slows iteration and often means design decisions are made with less analysis than they warrant.
- Fabrication misalignment. If panel families are not parametric, the dimensions in the model may not match the fabrication rules of the actual system being specified. A unitized panel that looks correct in the model may be impossible to fabricate as drawn. See design-to-fabrication for facades for context.
Kora Studio: Parametric Without Scripting
Kora Studio is a Revit-native plugin that brings parametric facade design to unitized curtain wall projects without requiring scripting knowledge.
Kora's Grid Editor uses formula-driven dimension fields to define horizontal and vertical grid spacing. This is the same logic as Revit's native curtain grid, but with a more controlled interface and explicit formula support — changes to one dimension propagate consistently through the grid without manual correction. The grid is not drawn; it is calculated.
Panel families in Kora are predefined parametric families that reflect the actual fabrication logic of unitized curtain wall panels: each panel is either opaque or contains a window, and window position and frame clearances are governed by parameters rather than fixed geometry. When grid spacing changes, panels adapt. When a window type changes, the frame recalculates.
The Window Editor applies predefined window profiles within panel families. The profiles are parametric within the constraints of what can actually be fabricated — there is no option to create custom profiles that fall outside the system's manufacturing logic. This constraint is deliberate: it prevents design decisions that produce correct-looking models but incorrect fabrication outputs.
Kora also supports parametric families for Light and Air calculations. Parametric families with embedded formulas populate ventilation and daylight values that feed into Revit schedules automatically — the same schedule logic used throughout the rest of the model, without a separate calculation workflow. See light and air calculations for facades in Revit for detail.
Kora operates at LOD 100 — it is a design-phase tool. The parametric model it produces is not a fabrication model, but it is consistent with fabrication constraints in ways that a generic Revit curtain wall model typically is not. The result is fewer surprises when the project reaches the shop drawing phase.
Kora is built by the team behind Dextall's prefab facade systems. The parametric logic in Kora's families reflects the same assembly rules that govern real unitized panel production. This is not parametric modeling for its own sake — it is parametric modeling constrained by what can actually be built.
If parametric facade design without scripting is relevant to your workflow, book a demo to see how Kora operates within a standard Revit environment. For a broader view of how Kora approaches facade grid design, see facade grid design in Revit.
FAQ
What does "parametric" mean in facade design? Parametric means that facade geometry is governed by named parameters and constraints rather than fixed dimensions. Changing a parameter — such as grid spacing or panel width — propagates changes consistently through the model without manual editing. This is distinct from non-parametric models, where every dimension must be updated individually when design changes.
What is the difference between parametric design and scripting tools like Dynamo or Grasshopper? Parametric design in Revit uses the native family editor with parameters, constraints, and formulas — skills that BIM-trained architects typically have. Dynamo and Grasshopper are visual programming environments that generate or manipulate geometry through scripts. They require programming logic and graph construction skills beyond standard BIM practice. Scripted tools are most useful for complex non-standard geometry; native parametric families are more appropriate and more maintainable for standard repeating curtain wall systems.
Why do non-parametric facade families cause problems? Non-parametric families have fixed dimensions. Every design change requires manual updates to every affected instance. At scale, this creates documentation drift — schedules and models diverge, generating RFIs. It also makes design iteration slow, because each alternative requires rebuilding geometry rather than adjusting parameters.
Does Kora Studio require scripting or programming knowledge? No. Kora's Grid Editor uses formula-driven dimension fields within a standard Revit interface. Panel families are predefined parametric families — architects work with them through Kora's editors, not through Revit's family editor or any scripting environment. The parametric behavior is embedded in the system; users set parameters through the interface.
What LOD does Kora Studio produce? Kora Studio operates at LOD 100. It is a design-phase tool that produces parametric curtain wall models consistent with unitized fabrication constraints, but it is not a fabrication or shop drawing tool. The model output feeds into Revit schedules and supports early-phase coordination and documentation.
