← Insights

Design review

A design review checklist

Every experienced designer works to a checklist — memory is no method. But a checklist is a prompt for a review, not a record of one.

2026-07-24 · 8 min · Guide

A checklist turns “did we remember?” into “did we check?”. It only works when it’s applied consistently, by people who can see the design, with the results written down. It’s a prompt for a review, not a record of one.

Before the schematic

Is there a written spec, and does the design’s scope match it? Is every external interface defined — levels, protocol, connector, pinout, mating part? Are the constraints captured: size, cost, thermal, regulatory and mandated parts?

Power

Power problems show up at bring-up. Are the rails identified with voltage, tolerance and worst-case current, and the sources sized with margin? Is power-up and power-down sequencing enforced with enables and supervisors where needed? Are capacitors, inductors and regulators within derating, with values stated in the BOM? Is bulk and local decoupling there per the datasheet, with short return paths?

Connectivity

A clean rule check lulls you to sleep. Does the pin assignment match intent, and are swappable pins chosen deliberately? Are the net names consistent and meaningful — no auto-names on critical nets? Signal direction: one driver per net, no floating inputs, pull-ups and pull-downs in place. More on why a clean ERC/DRC doesn’t cover this in What a review finds that DRC misses.

Components

A design is only as good as your ability to buy it over the product’s life. Are the parts available today, and is there a second source for critical or long-lead parts? Do voltage, current, power and temperature meet the worst case, with the right package and temperature grade? Check for NRND or end-of-life, and plan for likely obsolescence.

Layout

The schematic says what’s connected; the layout decides whether it works. Do high-speed nets run over continuous reference planes, without crossed splits? Are creepage and clearance sensible for the voltages, and fab clearances and keepouts respected? Do critical nets hold length and impedance to spec, are differential pairs matched, and are sensitive nets kept away from noisy ones?

Manufacturing

Are footprints verified against the datasheet, and pin 1 and polarity clear? Are there fiducials and sensible panelisation? Testability: test points on rails and key nets, programming and boundary-scan access, and a production test plan.

Documentation

Is the material revision-controlled and legible — schematic, complete BOM with values and sources, current fab package and ODB++? Are non-obvious choices and exceptions written down?

What a checklist can’t do

It verifies nothing. A ticked “decoupling — checked” is still just a claim, and it can’t tell “checked and OK” from “skipped under pressure”. It only catches what’s already on it — new spin faults have to be added. And a clean ERC or DRC proves legality, not correctness, so it doesn’t tick the connectivity items off for you.

How modern teams handle the findings

Note findings against the design object — net, component, position — with their evidence, not in a separate document. Give every reviewer access to the design without hanging it on a CAD seat (review without a CAD licence). And keep the findings with the design, so the checklist accumulates the team’s knowledge across boards.

How Probe does it

Probe opens the real design to every reviewer without a CAD licence and takes ODB++, or schematic and BOM before layout. It turns checks into findings tied to design evidence — netlisted, layout position, datasheet page — that carry over to the next revision. It runs some of the checks itself (connectivity plus several power and lifecycle items) and distinguishes three modes per item: checked and clean, couldn’t be checked (missing data, named), and not yet reviewed. Rules without enough data abstain rather than pass.

The checklist is worth keeping. But verification still needs a human looking at the real design — with the findings noted where they hold. See Probe on your design.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se