USB-C PCB design review checklist

Specify the intended role

Write down whether the port supplies or consumes power, which data functions are required and whether a controller is involved. Keep unsupported modes outside the product claim. A generic USB connector circuit is not evidence that every USB-C configuration has been implemented.

Verify every relevant connector contact

Compare the footprint and schematic mapping with the exact connector drawing. Check the required control, data, power and shield connections for the intended role. Evaluate orientation-dependent behavior explicitly rather than testing one cable orientation and assuming the other is equivalent.

Review electrical and mechanical context

Use the relevant device and interface documentation for routing and protection requirements. Inspect connector fit, mounting features and board-edge placement. Keep protocol compliance claims distinct from continuity checks and a successful one-off demonstration.

Practical checklist

1. Document power and data roles.
2. Check exact connector mapping.
3. Review orientation-dependent paths.
4. Verify protection and routing requirements.
5. Check board-edge and mounting geometry.

A concrete example

Add a USB-C port to an MCU board.

Evidence to accept

The circuit implements the stated role and the chosen connector is mapped and placed correctly.

Evidence that is insufficient

A successful test in one cable orientation is treated as complete interface validation.

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