What Is PCB Routing, and How Do You Route a Board Well?

Detailed Explanation

Routing draws the actual copper that carries every signal defined in the netlist between the components placement has already positioned. It's constrained from multiple directions at once: the netlist dictates what must connect, the stack-up dictates which layers are available to route on, and the design rules dictate how — minimum trace width and spacing, via sizes, and any impedance targets for specific nets.

Most routing follows a rough priority order: critical nets first (clocks, high-speed buses, anything with a controlled-impedance or length-matching requirement), then power and ground connections, then general-purpose signal nets last, since they tolerate the most flexibility in routing path. Routing power and ground through planes rather than discrete traces wherever the stack-up allows is standard practice for anything beyond the simplest two-layer board — it gives a much lower-impedance return path than a routed trace ever could.

Practical Examples

A microcontroller's crystal oscillator traces are typically routed first and kept short, direct, and clear of other signals, because the crystal circuit is sensitive to parasitic capacitance and noise coupling — a beginner mistake is to route it last, by which point the only remaining path is long and runs alongside several other signals.

On a board with a high-speed differential pair (USB, for instance), routing has to maintain consistent trace width and spacing for the controlled impedance the protocol requires, keep the two traces length-matched, and avoid routing vias or layer changes that would introduce impedance discontinuities — none of which an autorouter handles well without significant manual rule configuration first.

Design Considerations

• Route critical and constrained nets before general-purpose ones — clocks, high-speed buses, and anything length- or impedance-sensitive should get first claim on the cleanest, most direct paths.
• Keep return paths in mind, not just the forward signal path — a signal routed over a split or gap in its reference plane has a degraded return path even though the forward trace looks fine. See signal integrity in PCB design for how return-path breaks connect to reflections, crosstalk, and EMI.
• Use vias deliberately, not just where convenient — every layer change adds inductance and a potential impedance discontinuity, which matters far more on a high-speed net than a low-speed one. See types of PCB vias for how via choice affects this.
• Size traces for their actual current, not by habit — a trace that's too narrow for its load current will overheat under sustained load; see how to calculate PCB trace width for current capacity.
• Dense or high-speed routing: Complex routing challenges — mixed signals, controlled-impedance differential pairs, tight pitch BGAs — are where professional PCB layout brings the most leverage over a self-taught approach.

Common Mistakes

• Routing power and ground as thin traces instead of planes on boards with more than two layers, creating unnecessary voltage drop and a poor return path for every signal referenced to that net.
• Leaving the most sensitive nets (oscillators, high-speed differential pairs) for last, by which point the cleanest routing paths have already been used by less-critical signals.
• Adding vias freely on high-speed nets without considering the impedance discontinuity and added inductance each one introduces.
• Treating autorouter output as finished rather than as a starting point — autorouted boards almost always need manual cleanup on critical nets before they're production-ready.