Hardware Design Reviews: What to Check Before You Order Boards

Ordering boards turns every remaining error into a cost: a bodge wire if you are lucky, a new revision if you are not. A design review is the last inexpensive chance to find those errors. It works best when it follows a written checklist and is carried out by someone who did not draw the design. This article covers what to check in the schematic, the layout and the release package.

At a glance

Schematic
Pin functions, power domains, pull-ups and every datasheet application note.
Footprints
Pad sizes, pin 1 and pin numbering checked against the datasheet drawing.
Layout
Placement, return paths, clearances and the routes that carry current or fast edges.
Release
Gerbers, drill data, BOM and assembly drawings checked as a set before they go out.

The problem

Many respins come from small, checkable mistakes: a swapped transmit and receive pair, a footprint drawn from the wrong package variant, an enable pin left floating, or a regulator feedback divider set for the wrong voltage.

Designers rarely catch their own errors, because they read what they meant to draw. A fresh reviewer with a checklist reads what is actually there.

Review the design you are about to pay for, not the one you remember drawing.

Checks that pay off

In the schematic, compare every IC against its datasheet: pin functions, absolute maximum ratings, required decoupling, strapping pins and power sequencing. Check every net that leaves the board for protection and correct levels, and confirm that unused inputs are tied off as the datasheet recommends.

In the layout, print the footprints at one-to-one scale and lay real parts on them where you can. Check connector orientation against the mating part, mounting holes against the enclosure, and that test points and the debug header are reachable once the board is installed.

What good looks like

Freeze the design and generate the release files before the review, so that the review covers exactly what will be ordered.

Work through a written checklist for schematic, layout and release data, recording every finding with its location.

Resolve or formally accept each finding, regenerate the files and check that the fixes did not introduce new problems.

What to check, and where
AreaCheckError it catches
PowerRegulator settings, sequencing, rail ratingsFeedback divider set for the wrong output
InterfacesSignal direction and logic levelsTransmit wired to transmit
FootprintsPads, pin 1, package variantMirrored or wrong-pitch footprint
MechanicalConnectors, holes, keep-outsConnector facing into the enclosure wall
TestabilityTest points, debug accessDebug header blocked by a component
Release dataGerbers, drill, BOM, drawingsBOM revision out of step with the layout
Examples of the errors each area of review is designed to catch.

A review sequence

  1. Freeze: Generate the release files
  2. Schematic: Datasheet-by-datasheet check
  3. Layout: Footprints, placement, routing
  4. Release data: Files checked as a set
  5. Close out: Fix, regenerate, recheck
Reviewing the release files last confirms that what is ordered is what was reviewed.

What it changes

Fewer Respins

Checkable errors are found before they are built into copper.

Faster Bring-Up

Boards arrive with fewer surprises, so testing starts sooner.

Shared Knowledge

A second engineer understands the design and its decisions.

Better Checklists

Each review adds the mistakes it found, so the next one is stronger.

Where to go next

Run the fabricator’s and assembler’s own design checks as well. They catch manufacturing issues that a functional review may miss.

Keep the review findings with the design files. They explain later why particular choices were made.

Problems this prevents

  • A respin caused by a swapped pin pair
  • Footprints drawn from the wrong package
  • Connectors that do not mate with their cables
  • Release files that do not match the reviewed design

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.