Capstone: PCB Review Checklist

This capstone turns the PCB design handbook into a repeatable review process. The goal is not to find every possible imperfection. The goal is to decide whether the board is ready for fabrication, what risks remain, and what must be fixed before release.

Learning Objectives

By the end of this lesson, you should be able to run a structured PCB design review, record findings by severity, verify fabrication outputs, plan bring-up tests, and explain release risk clearly.

Prerequisites

You should already understand requirements, stackup, schematic capture, footprints, placement, routing, decoupling, return paths, signal integrity, mixed-signal layout, EMC/ESD, DFM, and board bring-up.

Concrete Task

Review a small embedded controller board package. The package contains:

• product requirements;
• schematic PDF;
• PCB layout screenshots or CAD view;
• BOM;
• Gerber and drill outputs;
• assembly drawing;
• proposed bring-up checklist.

Create a review report with pass, fail, or action-required status for each checklist section.

Review Implementation

Use this report structure as the review artifact. It is written as normal Markdown so it wraps cleanly on small screens.

PCB Review Report Fields

• Board:
• Revision:
• Reviewer:
• Date:

Release Decision

• Status: PASS, ACTION REQUIRED, or DO NOT BUILD
• Top risks:
• Required fixes before fabrication:
• Bring-up risks to watch:

Requirements and Architecture

• Input voltage range documented:
• Power budget complete:
• Interfaces documented:
• Mechanical constraints included:
• Test method defined:

Schematic

• Connector pinouts checked:
• Protection devices placed:
• Regulator ratings checked:
• Decoupling present:
• Programming/debug access:
• Reset/boot configuration:

Layout

• Placement follows signal and power flow:
• Return paths continuous:
• High-current loops compact:
• Sensitive analog routed away from noise:
• High-speed constraints met:
• Thermal copper adequate:

Manufacturing Outputs

• ERC/DRC clean or justified:
• Gerbers inspected:
• Drill and outline present:
• BOM complete:
• Pick-place file present:
• Polarity and pin 1 visible:

Bring-Up Plan

• Current limits listed:
• Rail checks listed:
• Clock/reset checks listed:
• Firmware programming path:
• Interface tests:
• Known risks:

Findings Record

• F1, high, power: example finding. Required action: fix before fabrication. Owner: hardware.

Expected Behavior

A good review report should:

• identify build-blocking issues separately from minor improvements;
• connect each finding to a real risk;
• include exact page, sheet, component, or net references;
• avoid vague comments such as "check layout";
• produce a clear release decision.

Verification Steps

1. Confirm every requirement has a schematic or layout response.
2. Cross-check connector pinouts against the mechanical or cable drawing.
3. Run ERC and DRC or inspect their reports.
4. Open Gerbers in an independent viewer.
5. Verify BOM, centroid, and assembly drawings agree on reference designators.
6. Check that the bring-up plan can be followed with available lab equipment.

Common Failure Symptoms

• Board cannot be programmed because debug pins are missing or swapped.
• Regulator overheats because the power budget ignored input voltage.
• ADC readings are noisy because reference return shares load current.
• Fabricator asks for clarification because outline, slots, or stackup are missing.
• First power-up trips current limit because no rail resistance check was done.

Debugging Guidance

When a review uncovers a problem, isolate the decision:

• If it can damage hardware, fix before fabrication.
• If it affects manufacturing data, regenerate and reinspect outputs.
• If it only affects convenience, decide whether a documented bring-up workaround is acceptable.
• If evidence is missing, request the exact artifact rather than guessing.

Extension Challenge

Create a severity rubric for your team:

• Blocker: likely board respin, unsafe, or unbuildable.
• High: likely bring-up failure or unreliable product.
• Medium: measurable risk with workaround.
• Low: clarity, documentation, or future improvement.

Apply the rubric to five real findings from a previous board or open-source hardware project.

Concise Explained Solution

A strong capstone answer is a filled review report with a release decision. For example, a board with missing TVS at an external connector, no current limit in the bring-up plan, and uninspected Gerbers should be ACTION REQUIRED, not PASS. The required actions should name the exact fixes: add or justify connector protection, define first-power current limits, inspect Gerbers independently, and update the release package before fabrication.

Summary

A PCB review is a disciplined risk filter. It checks that requirements, schematic, layout, manufacturing outputs, and bring-up plans agree before money and time are spent on boards.

Further Reading

• IPC-2221 printed board design guidance.
• IPC-A-610 acceptability of electronic assemblies.
• Fabricator DFM checklists from the selected PCB vendor.

Mind Map