You move a wall, change a family type or nudge a grid, and Revit stops you with a red error: "Constraints are not satisfied." It is one of the most common and most confusing messages in Revit, because it rarely tells you which lock, alignment or parameter is to blame. The good news is that the cause is almost always one of a handful of things. This guide explains what the error means and walks you through a reliable way to find and fix it, both in project models and in families.
What the Error Actually Means
Revit lets you add rules about how elements relate to each other. A padlocked dimension keeps a distance fixed, a locked alignment keeps two edges on the same line, and an EQ (equality) constraint keeps spacing even. Families add another layer: parameters, formulas and reference planes that drive geometry. "Constraints are not satisfied" appears when your change would force Revit to break one of those rules, or when two rules contradict each other and cannot both be true at once.
Because it is an error rather than a warning, Revit will not let the change go through as is. On the Autodesk forums, users report that the dialog can offer a Remove Constraints option alongside Cancel, and in some situations Delete Element(s). Before clicking anything that removes rules, it is worth understanding which constraint is involved.
The Most Common Causes
- Locked dimensions or alignments: You are moving or resizing something that is padlocked to another element.
- Equality constraints: An EQ dimension string cannot keep segments equal after your change.
- Groups: An Autodesk specialist on the forums points to constraints between elements inside a group and elements outside it as a frequent culprit.
- Family parameters that clash: Changing several driving values at once (for example height and angle together) can produce geometry Revit cannot solve.
- Impossible geometry: A sweep profile too large for a tight radius, or a value that makes a reference plane cross another one.
- Lost references: Forum users also mention dimensions tied to linked elements that were later deleted, and out-of-date local copies in worksharing.
Step-by-Step Fix in a Project Model
Start with the safest option and only remove rules once you know which one is in the way.
- Cancel the change first. Click Cancel rather than Remove Constraints so the model stays as it was while you investigate.
- Turn on Reveal Constraints. On the View Control Bar at the bottom of the view, click the Reveal Constraints icon. A colored border appears, constraints are shown in color and model elements turn gray half-tone.
- Select a constraint to see what it controls. Revit highlights the walls, windows or other elements tied to it, which quickly reveals the conflict.
- Unlock or remove the culprit. Select the dimension and click the padlock to unlock it, or click the EQ symbol to turn off equality (it shows a slash when off). You can also delete the dimension; Revit then warns you, and choosing Delete Element(s) removes the constraint too.
- Check sketches. Constraints created in sketch mode appear half-toned. Double-click the element (a floor or roof, for example) to edit its sketch and fix them there.
- Exit Reveal Constraints from the View Control Bar and repeat your original edit.
If the element is in a group, edit the group and look for locks to things outside it. Locking group members to external elements is a classic trigger, so it is usually better to avoid those locks altogether.
Fixing It Inside a Family
When the error appears while switching family types or flexing a family, the problem is usually in the family logic rather than the project.
- Open the family and flex it in the Family Types dialog, changing one parameter at a time to see which value breaks it.
- Test extreme values. A sweep or blend may only work above a certain radius or below a certain depth. One forum user found their profile failed at small radii until they repositioned it inside the path.
- Guard formulas. If a value has a minimum below which geometry fails, a conditional formula such as
if(r > 120, r, 120)can clamp it to a safe range. - Simplify the constraint chain. Remove redundant locks and duplicate dimensions to the same reference planes. For complex motion such as rotating and sliding parts, forum experts recommend splitting the behaviour into nested families.
When to Use "Remove Constraints"
Remove Constraints is not evil, but it is blunt. It deletes the rule standing in the way, and you may not notice which one until something else stops behaving later. Use it when you already know the lock is unnecessary, such as an old alignment someone added by accident. In shared or worksharing models, also make sure your local copy is synchronized before blaming the constraint. If you like automating checks like this, our list of top Dynamo nodes is a good starting point.
Conclusion
"Constraints are not satisfied" is Revit protecting a rule you or a colleague set earlier. Cancel first, use Reveal Constraints to see what is locked, and then unlock only what you need. In families, flex one parameter at a time and keep your constraint logic lean. Follow that routine and this error goes from a mystery to a two-minute fix.