Set constraints before running the router
An autorouter works with the connectivity, geometry and rules supplied to it. Define layer usage, clearances, widths, via choices and critical signal requirements first. A high completion percentage does not demonstrate signal integrity, thermal performance or assembly readiness.
Separate requirements that the tool can check from requirements needing engineering review. Identify sensitive analog, RF, high-current and timing-critical paths. Decide which routes should be placed manually or protected from later automated changes.
Improve placement and routing access
Review component orientation, pin escape, connector locations and routing channels. Congestion can originate in placement or layer allocation rather than in an inadequate routing algorithm. Moving a component may solve a problem more cleanly than adding many vias.
Keep the intended reference paths and power distribution visible during this review. A short connection that crosses a reference discontinuity may be inferior to a slightly longer route with a controlled return path.
Inspect the automated result
Review unrouted connections, layer changes, bottlenecks and unnecessary detours. Check critical channels against their actual timing and impedance requirements. Inspect power and ground connectivity after copper areas are regenerated.
Run the configured rules and examine exceptions individually. Do not weaken a clearance rule merely to obtain a completed route. If rules change for a valid manufacturing reason, record the agreement and repeat the affected checks.
Release the reviewed design
Compare the final board with the schematic and mechanical definition. Export manufacturing data from the approved revision and inspect the result. Automation should leave a reviewable design, not a collection of unexplained exceptions.
Keep the routing constraints with the native project. Later component or stackup changes can invalidate an earlier routing result even when the board still looks similar.