What first article inspection should prove
A first article is not simply the first board that powers on. It is the first assembly used to prove that the released product data, materials, process setup, workmanship criteria, firmware, inspection program, and test package agree with one another before the rest of the pilot lot is released.
The exact scope should match product risk, customer requirements, production quantity, and the agreed workmanship class. This guide is an engineering workflow, not a substitute for a contract, product-specific acceptance specification, or applicable industry standard.
Why first article inspection fails in practice
Most first-article problems are not caused by a missing inspection step. They happen because the inspected board cannot be traced back to one controlled set of inputs.
For example, the assembly drawing may be revision B while the placement program was generated from revision A. A substitute component may be electrically acceptable but use a different marking, height, moisture-sensitivity level, or reflow limit. The functional test may show a pass while the operator used an unrecorded firmware image or a golden unit with no numeric limits.
The first article should answer one question clearly:
If the remaining pilot units are built using the same released inputs and controlled setup, what evidence supports releasing them?
1. Freeze the document baseline before inspecting the board
Start with the manufacturing release package, not with the assembled board. Record the exact revision or checksum for:
- fabrication data such as Gerber or ODB++ and drill files;
- BOM and approved manufacturer list;
- centroid or placement data;
- assembly drawing and polarity instructions;
- stencil data and any local aperture decisions;
- firmware, configuration data, and programming instructions;
- inspection and functional-test procedures;
- labeling, serialization, and packaging requirements.
Avoid filenames such as final, latest, or new. A release identifier should connect the first article, work order, material issue, setup record, inspection results, and approval decision.
2. Confirm that the material identity matches the released decision
The first article is also a material-control gate. Check the PCB lot, critical component manufacturer part numbers, package and marking, date or lot codes where required, and approved-alternate status.
An alternate part should not be accepted only because it fits the footprint. The review may need to cover electrical limits, tolerance, temperature rating, package dimensions, pin compatibility, moisture sensitivity, lifecycle status, firmware interaction, and product-specific validation.
Record temporary substitutions as a lot-specific deviation unless they have completed the approved-alternate process. This distinction prevents a one-time shortage decision from silently becoming the default BOM. Use the PCBA BOM alternate-part qualification workflow to define evidence, approval scope, and lot controls before release.
3. Verify setup evidence before relying on visual appearance
Before judging the finished assembly, confirm the setup that produced it:
- stencil identification and revision;
- solder-paste type, lot, storage, and time-out record;
- placement program revision and feeder setup;
- component moisture-handling status;
- reflow recipe and measured profile reference;
- wave, selective-solder, press-fit, cleaning, coating, or manual processes in scope.
A visually acceptable board can still come from the wrong program or an uncontrolled setup. Setup records are therefore part of the release evidence, not background paperwork.
4. Inspect polarity, placement, soldering, and hidden joints against stated criteria
The inspection plan should identify which conditions are checked by SPI, AOI, visual inspection, X-ray, or another method. It should also state the sampling rule, program revision, acceptance criteria, and disposition process.
Give additional attention to:
- polarized capacitors, diodes, LEDs, connectors, and IC pin-one orientation;
- fine-pitch parts, bottom-terminated components, BGA, QFN, and LGA packages;
- high-mass or thermally imbalanced joints;
- press-fit and through-hole insertion depth;
- hand-soldered wires, shields, jumpers, and mechanical hardware;
- components close to depanelization routes or mechanical keep-out zones.
IPC identifies J-STD-001 as addressing soldering processes and materials, while IPC-A-610 addresses post-assembly acceptance. These documents are often used together, but the product still needs its own inspection scope, class, customer exceptions, and functional requirements. IPC release note
5. Prove programming and test configuration, not only the pass result
A green test screen is weak evidence if nobody can reproduce the setup. Record:
- firmware filename, version, and checksum;
- programmer model and configuration where relevant;
- test-fixture identification and revision;
- test-software version;
- instrument configuration or calibration reference;
- power sequence, delays, loads, and safe current limits;
- numeric pass/fail limits and units;
- serial-number or result-file association.
Separate structural inspection from functional proof. AOI may detect missing or misaligned components but cannot prove communications, current draw, sensor response, calibration, or product behavior. Functional test proves only the functions and limits that the released test actually exercises.
6. Close deviations before releasing the remaining lot
The first article often exposes issues that are repairable but not yet resolved at the process level. A reworked first board should not automatically release the rest of the lot.
For every nonconformance, decide whether the response is:
- correct the released data;
- correct the machine or process setup;
- replace or requalify material;
- approve a documented one-lot deviation;
- rework the first article and repeat affected checks;
- stop the build for design or customer review.
The disposition should identify who approved it, which units or lot it covers, and whether a new first article is required after the change.
7. Use a release record that another team can audit
The approval record should connect the evidence rather than repeat every detail. At minimum, record:
| Release field | Minimum useful evidence |
|---|---|
| Product baseline | Assembly part number and revision |
| Manufacturing data | PCB, BOM, placement, drawing, firmware, and test revisions |
| Material identity | PCB lot plus defined critical component lots or approved alternates |
| Process setup | Stencil, paste, placement, reflow, and special-process record references |
| Inspection | SPI/AOI/visual/X-ray results and program revisions where applicable |
| Test | Programming and electrical/functional test-log reference |
| Traceability | Work order, batch, panel, or unit identifier |
| Deviations | Open/closed status, disposition, scope, and approver |
| Release decision | Named approval roles and date |
Download the editable checklist: PCBA First Article Inspection Checklist.
When should the first article be repeated?
The trigger should be defined before production. Common reasons include:
- a PCB, BOM, placement, drawing, firmware, or test revision;
- a new or materially changed alternate component;
- a stencil, fixture, program, or process change that affects acceptance;
- a line transfer or long production interruption;
- replacement of critical tooling;
- a significant defect escape, repair pattern, or customer requirement.
Not every change requires repeating every check. The change review should identify which evidence is affected and whether partial or full revalidation is appropriate.
Final release questions
Before releasing the pilot lot, confirm:
- Can the first article be traced to one released data package?
- Were all substitutions approved for the stated scope?
- Do setup, inspection, programming, and test records identify their revisions?
- Are numeric limits used where operator judgment would otherwise vary?
- Are deviations closed or explicitly approved for the affected lot?
- Is the approval decision linked to the work order, batch, or unit identity?
The purpose of first article inspection is not to create a perfect-looking report. It is to prevent the remaining pilot units from reproducing an unknown or uncontrolled first build.
For coated assemblies, use the dedicated conformal coating process validation guide to link cleanliness release, masking, material lot, thickness, cure, inspection, repair, and serial/lot evidence to the first-article gate.