TL;DR
A parametric family is built in a fixed order: pick the right template (it cannot be changed later), draw the skeleton of reference planes, dimension the planes and label those dimensions as parameters, draw geometry and lock it to the planes, add formulas so dependent values calculate themselves, then flex the family at extreme values before loading it into a project. Skipping a step — especially the skeleton or the flex test — is where broken families come from.
Key Takeaways
- ✓The build order is fixed: template → reference planes → labeled dimensions → geometry → formulas → flex.
- ✓The template decides category and hosting behavior and cannot be swapped later.
- ✓Reference planes are the skeleton — geometry never gets dimensioned directly.
- ✓A dimension becomes a parameter the moment you label it.
- ✓Formulas turn many manual inputs into a few drivers plus calculated followers.
- ✓Flex at minimum, typical, and maximum values before the family ever meets a project.
Every clean, resizable, schedule-friendly family you have ever admired was built in the same six steps, in the same order. The order is the method: each step creates what the next one needs. Here is the complete walkthrough, using a simple wall cabinet as the running example.
Step 1 — Choose the Template (Carefully)
File → New → Family presents dozens of .rft templates. The choice sets two things you cannot change later without rebuilding: the category (which controls scheduling and visibility behavior) and the hosting (wall-hosted, ceiling-hosted, face-based, or standalone).
Rule of thumb: match how the element attaches on site. A wall cabinet that always mounts to a wall → Casework wall based. If the same component might land on walls, ceilings, or reference planes → face-based is the flexible choice.
Step 2 — Draw the Skeleton: Reference Planes
Before any geometry: reference planes. They are the bones the whole family hangs on. For the cabinet, in plan view: left face, right face, back face, front face. In elevation: bottom and top.
The habit that separates pros from beginners: geometry is never dimensioned directly. Planes get dimensioned; geometry gets locked to planes. Skip this and the family fights you forever.
Step 3 — Dimension the Planes, Label the Dimensions
Dimension between the reference planes, then select each dimension and use Label Dimension → Add parameter. Name it, choose type or instance scope, done — the dimension is now a parameter:
The type-vs-instance decision matters more than it looks — the scope of control chapter gives you the 30-second test. Add an equality (EQ) constraint where symmetry should hold, so the family stays centered as it flexes.
Step 4 — Draw Geometry and Lock It
Now extrusions, sweeps, and blends — drawn snapped to the reference planes, then locked with the padlocks (or Align → lock). The chain of control becomes:
Test immediately: change Width in Family Types. If a face doesn't follow, its lock is missing. Fix it now, while the family is four rectangles — not after it has 40 pieces of geometry.
Step 5 — Add Formulas: Drivers and Followers
This is where the family becomes genuinely parametric. Decide which parameters the user controls (drivers) and calculate everything else (followers):
Four formulas, four chapters of technique: arithmetic proportions (Chapter 1), fit counts via rounding (Chapter 4), and visibility automation with Yes/No logic (Chapter 7). The complete function reference is in the Revit formulas guide.
Step 6 — Flex Before You Ship
In Family Types, drag every driver to its extremes: narrowest plausible cabinet, widest, shortest, tallest — and ugly combinations of all four. Watch for geometry that breaks, dimensions that go negative, and formulas that error. Every combination you don't test is one a user will eventually type; the debugging chapter covers what to do when the flex test finds something.
The Six-Step Checklist
Key Takeaways
- ✓Template matches the element's real hosting behavior and category.
- ✓Reference planes exist for every face that will ever move.
- ✓Every dimension that should be controllable is labeled as a parameter, with deliberate type/instance scope.
- ✓All geometry is locked to planes — verified by flexing after each addition.
- ✓Drivers are few and obvious; everything else is a formula.
- ✓The family survives extreme value combinations before it is loaded into a project.
Frequently Asked Questions
Go deeper
Step 5 is a whole discipline — master it
All 10 formula chapters with worked examples, HD Video Vault, and the Formula Cheat Sheet. 40% off at $18.
