|  Created: October 25, 2021
 | 
Updated: July 18, 2025
At the various companies and organizations I've worked for, there have been a wide variety of procedures for reviewing and approving a PCB design for production. It has been more of a quick look over the board at some of the smaller companies to see if there are any glaringly obvious mistakes, and maybe, if the reviewer remembers, running a design rule check report. Even at larger organizations, there has been a distinct lack of procedure and consistency involved, often because there was simply never enough time to create a procedure with the pace of work and the workload levels of all the relevant staff.
We all know how important it is to check a board for issues before proceeding to production or prototyping. No matter how much effort you put into the design, inevitably, something slips through the gaps. If you do not have a robust list of items to look at before sending off your design files, those issues might still slip through to the board fabricator or assembler.
As we're always operating under such high workloads and pressures to get things done, it can be hard to find the time to generate a procedure or process for reviewing your board's design, as I mentioned above. So, rather than talking in this article about the evils of not checking board designs over, instead, I'm going to make your life easier by providing an extensive PCB checklist you can either adapt or use directly for reviewing each board design. Depending on your board and the technologies used on it, some items on this list may not be relevant - or there may be items missing. While this list is relatively extensive, it's not exhaustive as I've intended it to be the starting point for your own process. Hopefully, saving you from taking hours to come up with your own PCB quality checklist from scratch to needing just a few minutes to add any items as you think of them when you read through my list. Note that some items are repeated with different wording in multiple categories because they are important. Each phase of your PCB design for manufacturing review may have different considerations applied to a particular PCB design checklist item during any discussions.
I'm also not going to detail all the items on the list. If the items are relevant to your product/board, I will hope you either understand the PCB checklist item's implications - or are willing to do some research to aid your understanding. Many of the list items have relevant articles associated with them on this blog, written both by myself and some other industry experts.
Ensure the design rule report passes with no errors
Ensure there is a design rule to catch nets with only 1 pin
Ensure you have the board outline on a mechanical layer that will go to the board fabricator
Fiducials are present for the assembly and meet these criteria:
Three board-level fiducials are included as a minimum
Two fiducials are diagonally opposing each other across all extremely fine-pitch components
Mounting points have sufficient clearance for the chosen washer and screw head
If an enclosure model is available, it has been tested against the board to ensure there will be no interference between the enclosure and components
All components (including mechanical items) have accurate 3D models
Your board should be fully production-ready, as far as you are concerned, before sending it to colleagues for a design review checklist to avoid any nugatory effort on their part.
Your PCB layout should have all the required markings finished, as well as the mounting hole and fiducials shown here. Can you spot the silkscreen error in this image?
Check the layer stack and substrate heights meet the fabricator's specifications (or that the fabricator can meet your specifications)
Check the copper thickness on all layers matches the target fabricator's specifications (or that there is a callout on the documentation layer for the required copper thickness)
Ensure there is at least one continuous, unbroken ground plane
If your board has controlled impedance nets, they are correctly set up both on the layer stack and in the design rules
Check if any keep-out track matches the board shape
Check any board cutouts or slots used for a keep-out barrier to prevent nets from crossing milled areas
A PCB stackup table that was created as part of your front-end engineering specifications can be helpful here as it gives a visual comparison with the data in your PCB editor. A table provided by your fabrication house or manufacturer is the best resource, such as the example shown below.
Example stackup table for comparison in a PCB design review. Image provided by Zach Peterson/TTM.
Ensure that the ground plane has sufficient current-carrying vias near connectors, and voltage/return sinks
If required/relevant, ensure voltage planes and areas have sufficient connection vias for current requirements
Ensure tracks to reference planes are sufficiently wide for current requirements
Check there are sufficient quantities of vias for the current-carrying capacity of traces
Check the minimum track widths for all current-carrying nets are sufficient. Consider if a design rule is required
Check all ground pins have a via to the ground plane
Check there is a continuous ground plane within one signal layer of any signal trace
Check any controlled impedance traces have the correct net rules and impedance profile
Check differential pair tracks are as close together as possible
Check differential pair tracks lengths are matched
Check all high-speed signals are length matched, specifically including:
DDR
PCIe
Ethernet
LVDS
HDMI
USB3+
MIPI
Check every signal trace has a constant impedance along its length. If the trace changes layer, its impedance should stay the same
Check traces longer than 1/6th of the rise or fall time of the signal have been simulated:
Check termination resistors, or another termination is present to prevent ringing or overshoots
Check termination resistors are in the relevant locations
Check long traces that hug other traces that have been simulated for crosstalk
Check all high-speed traces run over a continuous ground pour
Ensure that no sensitive nets run under noisy components
Check that the vias for decoupling capacitors are not shared
Each decoupling capacitor requires its own via for VCC and for GND direct to reference planes
The xSignals package has features in it that can help automate many of these checks after the PCB layout is finished, but before a more rigorous manual review by the engineering team.
Return path violation highlighted in xSignals. You can choose to ignore this or re-do portions of the routing to eliminate it.
Check that test pads are sufficiently far from the edge of the board to allow fixturing
Check test pads do not create stubs/impedance mismatch on high-speed nets
Check that component do not obstruct access to test pads for manual testing (e.g., using an oscilloscope probe) or automated testing (e.g., using a bed of nails)
Check test pads are clearly labeled for prototypes
Check any signal needed for testing or inspection has a test point
Check test points are all located on the same side of the board, ideally:
The bottom of the board for access using a bed of nails fixtures
The top of the board for manual access with test equipment (e.g., oscilloscope probes)
Testpoints sometimes get placed on inconvenient locations, such as too close to other pads or near board edges. When placed near other pads, there is a risk of creating an unintentional short when probing. When placed near a board edge, they might interfere with the enclosure or mechanical mounting. Because testpoints don't often have a placement spec, it's a good idea to consider moving them and identify alternative locations during a design review.
These Keystone testpoints are placed very close to the board edge, and their silkscreen markings are placed very close to other through-hole pads for wire soldering. If there is no spec that requires these testpoints to be here, a new location could be identified in a PCB design review.
Check appropriate creepage and clearance rules are set for all high-voltage nets
Check if separate earth tracks/paths are necessary for ESD
Check there are decoupling capacitors next to connectors and vias that may require them
Check TVS diodes or other ESD mitigation component pads are in series with the track to the component (i.e., any ESD event must pass through the component pad before getting to a sensitive device)
Ensure there are no track stubs/net antennas going to test points or unused connector pins
Ensure high-speed signals are routed as directly as possible—no scenic routes
Check any track carrying over 100mA has its width calculated to ensure it is of sufficient size for the current
If the board will be fitted within an enclosure with little or no airflow, calculate or simulate the width for an internal layer instead of an external layer
Check if an RF shield is required anywhere on the board and if it has a sufficient footprint
If you are using a two-layer board:
Are there any ground loops?
Is there a ground track of sufficient size for the return current of every device?
Is there an unbroken ground pour under every high-speed trace?
If you have multiple grounds, ensure that they are tied together at a single point only
If you are running through this PCB checklist or your own derivative created from it and using it in a PCB design review meeting, then it is best to consider each item as a discussion point rather than merely as a box to tick off. This can be really important to ensure the design meets the product's intent, rather than just ticking boxes. A review before production should be more than just ensuring that all the technical issues with the board you can consider having been addressed. It should also ensure the functionality meets the requirements. It's much more efficient to make any schematic changes and shift the electrical design to meet the design intent and requirements that may have been re-evaluated during the meeting than it is to just order the boards and then find out that you should have had that discussion before spending any money and needing to wait for the boards to arrive.
Mark Harris is an engineer's engineer, with over 16 years of diverse experience within the electronics industry, varying from aerospace and defense contracts to small product startups, hobbies and everything in between. Before moving to the United Kingdom, Mark was employed by one of the largest research organizations in Canada; every day brought a different project or challenge involving electronics, mechanics, and software. He also publishes the most extensive open source database library of components for Altium Designer called the Celestial Database Library. Mark has an affinity for open-source hardware and software and the innovative problem-solving required for the day-to-day challenges such projects offer. Electronics are passion; watching a product go from an idea to reality and start interacting with the world is a never-ending source of enjoyment.
Altium is transforming the electronics industry so thoroughly that our web pages need a minute to catch up. For a short time, some information on this page may be outdated.
We appreciate your patience. It will be worth the wait!