PCB inspection is easiest to plan when each method has a clear job in the production sequence. Start with the features that matter on your board: paste deposits, visible joints, hidden connections, electrical nets and operating behavior. SPI, AOI, X-ray, ICT, flying probe and functional test address different parts of that picture, so the practical choice is a combination that fits the design and build stage.

Start by separating bare-board inspection from PCBA inspection. Bare-board checks address the fabricated board before parts are fitted: material records, dimensions, surface condition, conductor features and the requirements defined by the fabrication data. PCBA inspection starts once components, solder paste and assembly processes enter the picture; it can address paste deposits, visible placement and solder features, hidden joints, electrical conditions and approved product behavior.

For project-specific planning, connect the inspection discussion to quality control, PCB assembly testing and PCB assembly capabilities. The applicable scope is agreed from the released files and acceptance requirements; it is not implied by a generic service label.

How to choose a PCB inspection method

Frame the decision with five questions. What must be seen? Visible placement and solder features call for a different method than a hidden BGA joint. Where is the build? Paste-control evidence belongs before placement, while functional evidence belongs after the assembly is ready to run. What access exists? ICT and flying probe depend on planned electrical access and an appropriate test strategy. How stable and how many? Fixture investment can be appropriate for a mature repeated build, while a changing prototype may benefit from a more flexible approach. What record is needed? Define the images, measurements, test result or release record that demonstrates the agreed requirement.

AI-generated editorial scene: AOI and X-ray inspection workcells examining populated PCBs
AI-generated illustration: AOI and X-ray inspection workcells examining populated PCBs.

Match PCB defect risks to inspection methods

Inspection methods complement one another; they do not make the same observation. Visual review and AOI can evaluate accessible surface features. X-ray can provide evidence where a joint is hidden from optical view. Electrical testing checks the defined conditions that can be reached through the agreed test design. Functional testing evaluates the approved behavior of the assembled product. A plan should name the condition to be checked, the production stage, the sample or unit scope, the acceptance basis and the record to retain.

SPI: control solder paste before placement

Solder paste inspection (SPI) is a pre-placement PCBA process check. Where paste-control evidence is part of the plan, SPI evaluates the printed deposit before components are placed and reflowed. That timing matters: it can help the team detect a paste-printing issue while corrective action is still close to the process step that created it.

SPI does not replace post-reflow inspection or electrical testing. It does not show whether a component was placed correctly, whether a hidden joint formed after reflow or whether the finished unit performs its intended task. Use it when the paste-printing step and the agreed deposition evidence are relevant to the build.

AOI: inspect visible assembly features

Automated optical inspection (AOI) uses an approved program and imaging system to evaluate visible PCBA features after the applicable assembly stage. Depending on the recipe and project criteria, it can support review of component presence, orientation, polarity markings, placement and visible solder conditions. AOI is particularly useful when the question can be answered from the accessible surface of the assembly.

Automated optical inspection equipment for visible PCBA features
AOI evaluates the visible features defined by the approved inspection recipe.

AOI cannot see through an opaque package or board structure. A BGA joint, bottom-terminated package joint or other hidden feature needs a different evidence method when it is in scope. Optical results also depend on a controlled recipe, reference data and review process; a machine name alone does not define acceptance.

X-ray: evaluate hidden solder joints when they are in scope

X-ray inspection can help evaluate joints and features that cannot be verified from an optical view. It is commonly considered for assemblies with hidden solder joints, such as certain BGA or bottom-terminated packages, when the drawing, customer requirement or risk review calls for that evidence. The project plan should specify what is being reviewed and how the result is assessed.

X-ray inspection equipment for hidden PCB assembly joints
X-ray evidence is selected when hidden solder joints are included in the inspection plan.

X-ray is not a substitute for every other gate. It does not by itself prove accessible-net behavior or the product-level function. Its value is in answering the hidden-joint question with the evidence agreed for that build.

ICT, flying probe and FCT: choose by test access and build stage

ICT for defined electrical conditions on a stable build

In-circuit test (ICT) uses a dedicated fixture to contact defined test points and evaluate the electrical conditions included in the test program. It can be a strong fit where test access, fixture development and repeat production justify that approach. It is not a generic promise of full coverage: the electrical conditions tested are determined by the design, access, program and agreed plan.

Flying probe for flexible electrical test access

Flying probe testing uses movable probes instead of a dedicated bed-of-nails fixture. It can be useful where design changes, lower quantities or fixture timing make flexibility important. The test conditions and reachable points still need to be defined from the released data; flexibility does not remove the need for a testability review.

FCT for approved product behavior

Functional circuit test (FCT) checks the behavior that the project has defined for the assembled product under the agreed setup. It may exercise power-up, interfaces, signals, firmware interactions or other product functions that are relevant to the release. FCT is complementary to inspection and electrical checks because a unit can appear correct while still failing an approved functional requirement.

SPI, AOI, X-ray, ICT and FCT compared

MethodProduction stageEvidence it can provideKey boundaryPlanning input
SPIAfter paste print, before placementAgreed solder-paste deposit conditionsDoes not verify placed components or reflowed jointsStencil, paste process and deposit criteria
AOIAt the agreed visible-inspection gateVisible placement, polarity and solder features defined by the recipeCannot evaluate hidden jointsApproved program, reference data and acceptance criteria
X-rayAfter the relevant soldering stageEvidence for hidden solder joints or features in scopeDoes not establish product functionPackage risks and agreed evaluation criteria
ICTAfter assembly is accessible to the fixtureDefined electrical nets and conditionsNeeds planned test access and fixture/program investmentTest pads, coverage goals and stable released design
Flying probeAfter assembly is accessible to probesDefined electrical nets and conditionsTest time and reachable points depend on the designTest points, quantity and change cadence
FCTWhen the assembled product is ready for the approved setupSpecified product behaviorDoes not replace manufacturing-stage inspectionFunctional requirements, fixture and result record

Build the inspection plan from incoming material to final test

For a PCBA project, a practical plan connects each gate to the information available at that point in the build. Incoming material checks and documentation review precede the assembly process. DFM, DFA and testability review establish what can be inspected or contacted. SPI, AOI, X-ray, electrical test and functional test are then selected only where they answer an agreed question. Final inspection and shipment records close the loop with the documentation the project requires.

AI-generated editorial scene: In-circuit and functional test fixtures for PCB assemblies
AI-generated illustration: In-circuit and functional test fixtures for PCB assemblies.

PCB inspection checklist for your next build

  • Provide the released Gerber or ODB++, BOM, Pick & Place data, drawings and revision control.
  • Identify bare-board requirements separately from PCBA workmanship and test requirements.
  • Flag hidden-joint packages, critical interfaces, test points and any required traceability records.
  • State whether the build is a prototype, pilot or repeat production run, and what change cadence is expected.
  • Define the acceptance class, applicable customer requirements and the evidence required at each selected gate.
  • Confirm the final functional setup, firmware or fixtures needed when functional testing is in scope.

These inputs make the selection discussion more actionable before a project review. They also help align the inspection plan with the chosen PCB assembly service rather than treating testing as an afterthought.

Standards and acceptance language

Standards provide a shared vocabulary, but they do not replace the build-specific plan. IPC-9716 addresses test methods and qualification guidance in the reliability context; it should be applied only where the project calls for it and with the current applicable document confirmed. IPC J-STD-001 provides requirements for soldered electrical and electronic assemblies. The applicable revision, customer drawings, class, acceptance criteria and documentation scope should be agreed before release.

For production planning, review the current IPC document revision information alongside the released project requirements. PCBArise can use those inputs to discuss the appropriate manufacturing and test pathway; the final scope is confirmed for the specific build package.

How PCBArise can help

PCBArise supports PCB fabrication and PCBA work from prototype through repeat production. A project review can connect bare-board requirements, assembly risks, component sourcing, DFM review, inspection, test and documentation needs to the actual released files. Explore quality control and production planning considerations, then share the package and acceptance requirements for a project-specific review.