Season 1 in preparation.Rankings will be published after measured runs are complete. The pilot snapshot is available with its caveats.Pilot results
Skip to content
PCBBench

Layout

KiCad DRC checklist before PCB fabrication

PCBBench editorial · Published October 14, 2026 · Editorial policy

Run DRC against the manufacturing and electrical rules intended for the actual board. A clean report is meaningful only when the checked artifact, rule deck, exclusions and connectivity expectations are known.

Start from the correct fabrication profile

Record the layer stack and the board manufacturer's capabilities used by the project. Check net classes and custom rules as well as global defaults. Do not substitute a convenient default profile merely because it produces fewer errors.

Check the final board state

Refill copper zones before the final check and verify that schematic and board connectivity agree. Review remaining unconnected items explicitly. Exporting Gerbers from an older revision after checking a newer board breaks the chain of evidence.

Resolve exceptions one by one

Keep a reason for each exclusion and separate inherited input findings from changes introduced by a tool. Mechanical fit, thermal behavior and signal integrity may need checks beyond the configured DRC rules, so preserve those as separate release criteria.

Practical checklist

  1. Verify stackup and fabrication rules.
  2. Refill zones.
  3. Check schematic-to-board parity.
  4. Resolve unconnected items and exclusions.
  5. Export only from the checked revision.

A concrete example

Release a two-layer board for manufacturing.

Evidence to accept
The report and exports come from the same revision with the chosen fabrication profile.
Evidence that is insufficient
The board passes after the clearance rule is relaxed without approval or documentation.

Common questions

Does zero DRC mean fabrication-ready?

It is one release gate. Assembly data, footprints, mechanical details and the export package still need validation.

Can old violations be ignored in a routing test?

Only with an explicit baseline policy. Preserve the baseline report and reject unexplained regressions.

Primary references and further reading

Use the matching device documentation and project configuration when applying this checklist. These references explain the underlying tools and evaluation approaches.

How this fits PCBBench

The AI PCB placement and routing benchmark describes the proposed inputs, outputs and checks for this capability. The pilot snapshot contains partial measured attempts; it is not a finished ranking.

Related reading