The core idea
Constraint Manager (Setup > Constraints > Constraint Manager) is a rules spreadsheet tied to the board database. Instead of remembering widths and distances, you declare them once and online DRC warns you the moment something is violated.
The main domains
Physical
Minimum and maximum trace width, neck width (narrowing allowed in tight areas), vias allowed per net, and whether the net may use blind/buried vias.
Spacing
Distances between trace, pad, via, shape and hole, organized in sets. There are also same-net spacing rules, useful to keep vias away from pads.
Electrical
Propagation delays, maximum length, match groups, topology and differential-pair rules: coupled spacing, phase tolerance and maximum uncoupled length.
A structure that scales
- Start with DEFAULT set to the fabricator's standard capability (e.g., 0.10 mm / 0.10 mm).
- Create physical and spacing constraint sets (for example
PWR_1A,DIFF_90R,HV_SPACING). - Group nets into net classes and assign the sets to classes, not to individual nets.
- Use class-to-class rules to keep, for example, high voltage away from logic signals.
- Create constraint regions under fine-pitch BGAs, allowing smaller widths and spacings only there.

Differential pairs in practice
- Define the pair (manually or by name pattern, such as
_P/_N). - Use the width and spacing indicated by the stackup impedance calculation.
- Limit the uncoupled length (pad and via breakouts) and set the phase tolerance.
- Keep the pair over a continuous plane; do not cross plane splits.
Tip: Constraint Manager's actual and margin columns show where you are close to the limit. Use them as a routing status dashboard.
References and further reading
Original text for educational purposes. Menus and commands may vary between Allegro X versions; check the Cadence documentation for your version.