Schematic

Schematic Review Checklist: 12 Checks Before PCB Layout

By Hire PCB Designer engineering team · Updated · 8 min read

A schematic review catches errors while they cost minutes rather than a board spin. Check the power tree and decoupling, voltage levels and pull-ups, reset and boot pins, clock load capacitance, debug access, protection, connector pinouts, ratings, footprints, net naming and BOM status, then pass impedance, current and keep-out notes to layout. Verify against datasheets, ideally with a second reviewer.

Why review the schematic before layout?

A schematic error costs a few minutes to fix on screen and a board spin to fix after fabrication. Layout also locks in decisions that are expensive to unwind, so the schematic is the cheapest place to find mistakes.

The most useful review is a structured one, done by someone other than the author and worked against datasheets rather than memory. The twelve checks below are ordered roughly by how often they cause a dead or misbehaving first prototype.

Power: tree, sequencing and decoupling

Start by drawing the power tree: every source, regulator and load, with the expected voltage and current at each node. Add up the worst-case load on each rail and compare it with the rated output of the regulator, including startup peaks. Then check whether any device needs one rail to come up before another, and whether enable and power-good signals enforce that order.

Decoupling comes next. Each supply pin needs the capacitor value and placement the datasheet recommends, and each regulator needs input and output capacitors that suit its stability requirements. Add bulk capacitance where load steps are large, and remember that ceramic capacitors lose effective capacitance as DC bias increases.

Signals: voltage levels, reset, boot and clocks

Open every datasheet and compare each pin function with what the schematic assumes. A 3.3 V output driving a 1.8 V input can exceed the absolute maximum rating, and 5 V tolerance is a per-pin property, not a family-wide one. Open-drain outputs and buses such as I2C need pull-ups sized for the supply voltage and bus capacitance, and any input that must not float needs a defined state.

Reset, boot-mode and strap pins deserve their own pass because they are sampled at startup and fail in confusing ways. Confirm default states, required pull directions and whether other circuitry shares those pins. For clocks, calculate the crystal load capacitance from the specified load, the two capacitors and an allowance for stray capacitance, then check that the frequency tolerance suits every peripheral that depends on it.

Debug access, test points and protection

Make sure the board can be programmed and debugged before anything else. Check the SWD or JTAG header pinout, the reference voltage pin and the reset connection against the probe you will actually use. Add test points for every power rail, ground, the main clocks and key communication buses.

Then look at protection. Interfaces that leave the board usually need ESD protection close to the connector, supply inputs may need reverse-polarity protection, and power paths may need a fuse, current limit or similar overcurrent protection. Choose each part for the voltage and signal speed of the line it protects, since some ESD devices add capacitance that suits a slow signal but harms a fast one.

Connectors, ratings and footprints

Connector errors are common because pin numbering is viewed from different sides. Verify each pinout against the mating part, confirm pin 1 and the viewing direction, and check that cable-side and board-side connectors are not mirrored. Label power and ground pins clearly so a miswired cable is obvious.

Check ratings with derating in mind. Compare voltage, power dissipation and temperature limits against worst-case conditions and leave margin rather than designing at the limit. Capacitors, resistors, diodes and regulators all have limits that fall with temperature or operating conditions.

Finally, verify every footprint and package against the manufacturer drawing in the datasheet, not against a library name. Check pad pitch, pin 1 position, the pin-to-pad mapping of multi-pin parts and thermal pad requirements. Printing a footprint at full scale and placing the real part on it is a quick sanity check for unusual packages.

Readability, BOM and lifecycle

A schematic that is hard to read hides errors. Use hierarchical sheets organised by function, consistent and descriptive net names, and clear signal direction between sheets. Avoid unnamed nets for anything important and keep power symbols unambiguous.

Review the bill of materials while the schematic is still open. Check each part for lifecycle status and availability, and confirm that an approved alternate exists for passives and key active parts. Flag single-source components early, because a footprint that cannot accept an alternate limits your options later.

What should you hand off to layout?

A good review ends with notes that tell the layout engineer what the schematic cannot show. List the nets that need controlled impedance and the target value, plus differential pairs and any length-matching requirements. Mark nets that carry high current so trace width and copper area are chosen on purpose.

Add keep-out and placement notes too: antenna clearance, crystal and sensitive analogue areas, connector positions, mechanical height limits and thermal concerns. Call out decoupling capacitors that must sit close to specific pins. These notes turn the schematic into a specification the layout can be checked against.

The 12 checks in one pass

Use this list as a sign-off sheet. Each item should be checked against datasheets and initialled before layout starts.

  1. Power tree and sequencing: sources, loads, worst-case current, enable and power-good order.
  2. Decoupling and bulk capacitance: datasheet values, regulator stability, DC-bias loss.
  3. Pin function and voltage-level compatibility: 3.3 V against 1.8 V, 5 V tolerance, open-drain pull-ups.
  4. Reset, boot and strap pins: default states, pull directions and shared use.
  5. Clock and crystal: load capacitance, frequency tolerance and startup margin.
  6. Programming and debug: SWD or JTAG header pinout, reset line and test points.
  7. Protection: ESD, reverse polarity and overcurrent where the design needs them.
  8. Connector pinouts and orientation: pin 1, mating side and mirrored cables.
  9. Ratings and derating: voltage, power and temperature at worst case.
  10. Footprints and packages: verified against the datasheet drawing.
  11. Net names and readability: hierarchy, consistent labels and no stray unnamed nets.
  12. BOM, lifecycle and second sources, plus layout hand-off notes for impedance, current and keep-outs.

Where do schematic errors show up later?

Most schematic mistakes do not announce themselves at the desk. They appear at assembly, at first power-up, during firmware bring-up or, in the worst case, in the field. The table shows typical examples and the stage at which each is usually caught.

Where schematic errors usually show up later
MistakeSymptomWhen it is caught
Footprint does not match the datasheet packagePart does not fit, or pins land on the wrong padsPrototype assembly
Missing pull-up on an open-drain line or I2C busBus stuck low, unreliable communication or false interruptsFirmware bring-up
Floating or wrongly pulled boot or strap pinBoard starts in the wrong mode, sometimes only intermittentlyFirst power-up or bring-up
Wrong crystal load capacitorsOscillator off frequency, slow to start or not startingBring-up, or later across temperature
Voltage-level mismatch between devicesDead interface, excess current or a damaged pinBring-up, sometimes as a later reliability failure
No debug header or test pointsBoard cannot be programmed or probed easilyFirst power-up
Mirrored or mis-numbered connectorCable fits but nothing works, or supply is reversedSystem integration
Capacitor or part operated near its ratingRail droop, overheating or an unexpected failureEnvironmental test or field use
No reverse-polarity or ESD protectionDamage when the wrong supply is connected or a connector is touchedField use or compliance testing
Obsolete or single-source partCost jump, long lead time or a build that cannot proceedProduction planning

This guide is general educational information. Requirements vary by project, fabricator and applicable standards, so confirm specifics with your manufacturer and test lab.

Frequently asked questions

Who should review a schematic?

Ideally someone who did not draw it, because authors tend to read what they meant rather than what is on the page. A second engineer, working through datasheets pin by pin, finds different problems from the original designer. If no colleague is available, review again after a break, using a printed checklist and the datasheets open.

Can electrical rule checks replace a manual schematic review?

No. Electrical rule checks in an EDA tool find unconnected pins, duplicate designators and conflicting pin types, which is useful, but they do not know your design intent. They cannot tell that a pull-up is missing, a crystal capacitor is wrong, or a footprint disagrees with the datasheet. Run the checks first, then review manually.

How long does a schematic review take?

It depends on board complexity, so there is no fixed figure. A simple board may need a focused sitting, while a design with a large processor, several power rails and high-speed interfaces needs a review per sheet over several sessions. Budget the time before layout starts, because it is far cheaper than finding the same problems on a prototype.

Should the BOM be reviewed at schematic stage or later?

At schematic stage, at least for lifecycle and availability. Once the board is laid out, swapping a part that is obsolete or hard to source may mean changing footprints and re-routing. Checking status, alternates and package options now keeps those choices open, and you can refine pricing and quantities later with your assembler.

What should I do if I find an error after layout has started?

Fix the schematic first, then update the layout from it so the two stay consistent, rather than patching the board alone. Re-run the relevant checks on the affected sheet, since one change often touches related nets. If a fix would alter many routes, it may be worth pausing layout until the schematic is stable.

Have a hardware project in mind?

Send us your requirements through the contact form. We review the scope and reply with questions or a proposed approach.