ERC vs DRC: what each PCB check proves

Different artifacts, different questions

ERC operates on the schematic's electrical representation. DRC evaluates the PCB and its rule configuration. A schematic can be logically connected while the board has an unrouted net; a physically clean board can implement the wrong circuit.

A clean report depends on configuration

Record severity settings, net classes, custom rules and exclusions. Compare results under the same settings. Changing a rule to eliminate a finding changes the test, not necessarily the underlying design.

Build a release sequence

Check the schematic, synchronize the board, refill zones, check board parity and DRC, then inspect the exports from that revision. Add device-specific and functional checks for requirements outside either rule system.

Practical checklist

1. ERC: review pin and power connectivity.
2. DRC: review board geometry and intended connections.
3. Preserve configurations and exceptions.
4. Check schematic-board parity.
5. Verify behavior independently.

A concrete example

An ERC-clean circuit is routed onto a PCB.

Evidence to accept

Both representations agree and the final board passes the chosen physical rules.

Evidence that is insufficient

ERC alone is described as proof that all PCB connections were routed.

Common questions

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.

• KiCad schematic editor documentation
• KiCad PCB editor documentation
• KiCad command-line interface documentation