SMT first article inspection is a release decision made on the first representative board or panel built with the intended product data, materials, programs, equipment, route, and acceptance rules. It should answer one practical question: does the evidence justify allowing this configuration to continue into the authorized production quantity?
A photographed board, a completed checklist, or a green AOI screen cannot answer that question alone. The team must prove that the inspected unit represents what was ordered, that the line used the correct setup, that applicable process and product characteristics were checked, that every exception is controlled, and that the approval remains traceable to the delivered units.
This guide focuses on that buyer-side release gate. The GNS article on moving from PCBA prototype to mass production covers the wider transfer. Here the scope is narrower: how an OEM and EMS provider define, execute, approve, and repeat SMT first-article evidence without allowing an unverified setup to become a batch problem.
Define what the first article must authorize
The first-article plan should be written before setup begins. It must identify the decision, the product boundary, and the authority that can release or stop the build.
Separate a production gate from a sample review
A sample review asks whether a board appears suitable for engineering learning. A production first article asks whether the intended manufacturing configuration has generated acceptable objective evidence. Those are different decisions. An EVT board built with temporary components, hand placement, a provisional stencil, or a laboratory test can be useful without qualifying the production route.
State what approval authorizes: printing the remaining panels, completing placement, entering reflow, starting the lot, proceeding to downstream assembly, shipping samples, or releasing repeat production. If approval is split into stages, name each hold point. For example, the team may verify paste and placement before reflow, then inspect soldering and hidden joints, then complete electrical and functional evidence before releasing the balance.
Do not allow “first article passed” to hide these boundaries. The record should say what quantity, revision, route, date, line, and customer order are covered.
Contract the applicable inspection basis
Identify the customer specification, drawing, product class, standard and revision, approved deviations, inspection population, test requirements, and documentation format. The Global Electronics Association explains that J-STD-001J and IPC-A-610J address soldering process and material requirements and post-assembly acceptance, respectively. They are not substitutes for the product drawing, component instructions, customer requirements, or functional validation.
Some regulated or aerospace contracts explicitly require formal FAI. SAE AS9102C establishes requirements for performing and documenting aerospace first article inspection and states that those requirements complement customer and regulatory obligations. Do not present AS9102 as a universal rule for every commercial PCBA. If it is contractually invoked, use the licensed standard and required forms.
For other projects, build a product-specific release record with equivalent clarity: characteristic, requirement, result, source revision, unit identity, disposition, and approval.
Assign ownership and stop authority
Name who releases the manufacturing data, material substitutions, stencil, placement library, feeder setup, oven recipe, AOI or X-ray program, electrical test, functional test, rework instruction, and final first article. Also name who can stop the line when evidence conflicts.
Manufacturing engineering normally owns the route and process setup. Quality owns inspection planning, evidence review, and nonconformance control. Test engineering owns test access, program, limits, fixtures, and result interpretation. Supply chain controls approved sources and lot status. The OEM owns design intent, customer requirements, approved deviations, and product validation.
Independence should match risk and contract. A trained operator may perform a defined verification, while a quality representative or customer may hold approval. The JPL supplier clause for first article records is a useful high-assurance example: it calls for production equipment and processes, recorded characteristics and test results, quality acceptance, and repetition after specified changes. Apply it only when contractually relevant; use it as a model for evidence quality, not as a claim about ordinary builds.
Freeze the configuration before the build
Approved component identity, lot status and feeder assignment must match the released product configuration. The inspected unit is meaningful only if it is connected to one reconciled configuration. Revision ambiguity must be resolved before the first panel enters the line.
Reconcile product and manufacturing data
Collect the purchase order, approved quote assumptions, PCB fabrication and panel data, BOM and approved manufacturer list, placement file, centroid and polarity data, assembly drawings, schematics needed for test, variants, do-not-fit rules, stencil data, programming files, labels, inspection criteria, test requirements, packaging, and approved deviations.
Run the same cross-checks described in the GNS BOM and Gerber checklist for PCBA manufacturing . Resolve reference-designator count, package and footprint, polarity, side, coordinates, rotations, variant population, panel origin, tooling holes, fiducials, board thickness, finish, and special handling. A coherent file set is more important than a recent timestamp.
The IPC-2581C scope describes an intelligent data format capable of carrying printed board assembly, tooling, manufacturing, and inspection information. Whether the project uses IPC-2581, ODB++, Gerber plus auxiliary files, or another controlled package, the first-article record must identify the exact imported and generated revisions.
Verify materials and line setup
Reconcile each loaded component to the approved manufacturer part number, package, value, rating, marking method, moisture status, date or lot requirement, and applicable substitution approval. Link reel, tray, tube, or kit identity to feeder position and reference designators. Confirm PCB lot and panel revision, solder paste or adhesive, stencil identity, support tooling, cleaning material, labels, and other consumables.
Verify line and equipment identity, preventive-maintenance and calibration status where applicable, rail width, board support, fiducials, conveyor direction, feeder map, nozzle selection, package library, pickup and vision parameters, placement program, print program, inspection program, profile or oven recipe, and test programs. A machine file named for the correct customer part can still contain an obsolete library or coordinate transform.
Retain the independent setup checks and any scan or barcode result. Avoid using a manually retyped list as the sole proof when machine, material, and program records can be linked directly.
Define the first-article evidence matrix
Create the matrix before production. Each row should connect one risk or characteristic to the controlled source, verification method, sample or location, result format, acceptance rule, owner, and release consequence. Use full or targeted checks according to the product and process, not a generic one-page template.
Release area
Minimum evidence to define before the build
Configuration
Effective PCB, panel, BOM, AVL, placement, assembly, variant, test and deviation revisions
Materials
PCB lot, component source and lot, feeder or location, moisture state, paste and consumable identity
Programs
Print, placement, library, profile, AOI, X-ray, electrical, functional and programming revisions
Process
Line, equipment, tooling, support, settings, measurements, alarms and authorized adjustment window
Product
Population, polarity, orientation, solder features, hidden joints, dimensions, programming and required behavior
Decision
Hold points, acceptance logic, exception response, covered quantity, approvers and customer notification rule
The matrix prevents two common failures: checking visible workmanship while missing a setup error, and collecting large amounts of data that are not connected to an approval decision.
Build the first article under intended conditions
Print program, stencil, paste, support and measured deposit evidence should be verified before placement continues. The first article should represent the production route. Record temporary conditions and do not silently treat them as released conditions.
Preserve the route and unit identity
Assign a panel, board, lot, traveler, or serial identity before processing. Record the line, equipment, operator or system login, start time, material lots, program revisions, tooling, and route step. For double-sided or mixed-technology assemblies, distinguish each side and each thermal or soldering pass.
Do not replace a failed first unit and call the next one “the first article” without retaining the failed evidence. The first failure may reveal a feeder, program, print, support, handling, profile, or design issue that can affect the same setup. Preserve the failed unit’s configuration, stop time, affected work in process, investigation, correction, and reinspection.
If engineering must use a temporary component, hand operation, offline program, or alternate equipment, mark the unit and decision accordingly. It may support learning or partial verification, but it does not automatically release the intended production condition.
Verify print and placement before value is added
Use appropriate hold points before reflow makes correction expensive. Check PCB orientation, stencil and paste identity, support, print alignment, aperture condition, deposit evidence, fiducial recognition, feeder map, loaded material, polarity, package, placement coordinates, rotation, and do-not-fit locations.
The IPC-hosted technical paper on first article inspection strategies documents the practical complexity of reconciling customer BOM, internal BOM, loading drawing, feeder list, and placement data in high-mix SMT. The paper is an industry example rather than a contractual standard, but its central lesson remains useful: inspect the data-to-machine-to-board relationship as well as the finished appearance.
Record authorized adjustments. If print pressure, separation, support, feeder pickup, vision threshold, placement correction, or another parameter changes, identify the before and after state and decide whether previously processed material remains valid.
Capture process conditions without inventing proof
Retain the evidence required by the control plan: paste exposure and material condition, stencil cleaning or inspection, print or SPI results, placement verification, oven recipe and applicable product-profile release, line alarms, manual interventions, and environmental or ESD checks when relevant.
The first article is not a substitute for process qualification. A single conforming board cannot establish capability, long-term variation, equipment matching, or reliability. Conversely, a capable historical process cannot prove that today’s feeder, component source, program, and product revision are correct.
Separate direct evidence from inference. A recipe ID proves which recipe was selected only when access control and revision management are reliable. An AOI pass proves only the features and conditions the validated program can evaluate. A photograph can identify a condition but not establish an unmeasured dimension or hidden joint.
Inspect product evidence and resolve exceptions
AOI evidence is useful only within the released program, views, thresholds and acceptance boundary. The release package must combine inspection and test methods according to feature risk. No single method should be described as complete coverage.
Match each method to observable features
Manual visual inspection can confirm overall population, marking, polarity, orientation, contamination, mechanical damage, connector seating, labels, and features that are accessible with adequate magnification and lighting. AOI can provide repeatable programmed checks for visible features within its views and validated thresholds. X-ray can support hidden-joint or internal-feature decisions when the acceptance plan names views, measurements, criteria, and limitations.
The current IPC-9716 AOI process-control description includes program setup, inspection parameters, lighting, calibration, detectability, resolution, thresholds, measurement-system analysis, maintenance, and verification. A stored result is useful only when the effective program and its validation boundary are known.
The GNS guide to AOI, X-ray, ICT, and FCT for OEM buyers explains the wider division of labor among methods. The first-article matrix must name which specific references, nets, functions, and risks each method covers.
Verify electrical and functional evidence
Electrical evidence may include continuity, shorts, resistance, device presence, orientation, value, programming, boundary scan, flying probe, ICT, or other defined checks. Functional evidence should state input conditions, fixture and software revision, power limits, interfaces, loads, sequence, measured outputs, limits, pass or fail result, and any excluded behavior.
Do not accept “ICT passed” or “FCT passed” without the program, fixture, limit set, coverage boundary, unit identity, and result record. A functional test may demonstrate selected behaviors without isolating every manufacturing defect. ICT may diagnose accessible structural faults without proving the complete system function.
When test is unavailable at the first-article stage, state what remains open, which interim evidence is accepted, who accepts the risk, and what hold point prevents shipment or volume release before the missing test is complete.
Contain and disposition every discrepancy
Define a discrepancy as any conflict among the controlled data, actual setup, material, measured product, program, result, or record; broader than an IPC workmanship defect. Examples include an unapproved manufacturer part number, ambiguous marking, wrong feeder location, obsolete library, unexpected polarity, print trend, profile mismatch, false-call suppression, inaccessible test point, intermittent result, undocumented hand touch, or missing serial link.
First-article outcome
Required control before production continues
Accept
All required evidence complete, configuration identified, no open discrepancy, approval and covered quantity recorded
Conditional accept
Named open item, bounded risk, interim control, owner, due date, restricted quantity and final hold point approved
Correct and reinspect
Affected unit and work in process contained; correction authorized; impacted evidence repeated and accepted
Deviation review
Requirement conflict documented; design or customer authority decides use-as-is, repair, rework or rejection
Stop and reset
Setup or configuration invalid; scope contained; root condition corrected; new representative first article built
Reject
Nonconforming material segregated; disposition, records, inventory effect and recurrence action completed
Retain the original observation and the final result. Do not overwrite a failed record with a passing retest. If rework occurs, identify procedure, operator qualification where required, thermal or mechanical exposure, post-rework inspection and test, and whether the sample still represents the production route.
Release production and control repeat triggers
The approved first article should link the effective setup to the authorized production lot and repeat triggers. Approval is complete only when it connects the accepted first article to the production units and defines when that approval becomes invalid.
Assemble the release record
The release package should contain the effective product and order references, first-article unit identity, material and lot links, line and equipment, tooling and program revisions, setup verification, process measurements, inspection and test results, photos or data files where required, discrepancy and rework history, deviations, approvals, date, and covered quantity.
The record should also identify what was not checked. This prevents later readers from treating a selective result as full product validation. Use clear decisions such as accepted for the remaining lot, accepted for a limited quantity, awaiting customer approval, targeted evidence required, or not released.
Link the accepted configuration to the traveler, MES, lot, serial, or shipment record. The GNS article on verifying PCBA traceability before placing a PO provides the procurement context. The first-article record is one controlled node in that chain.
Define changes that reopen the gate
Build a trigger matrix for PCB or panel revision, BOM or source change, package or marking change, stencil, solder paste, component moisture condition, feeder type, placement library, program revision, line transfer, equipment or tooling change, profile, inspection program, test fixture or software, repair method, long interruption, customer requirement, and quality degradation.
For each trigger, define the scope of review and evidence to repeat. The response can be document comparison, material verification, targeted setup check, selected measurement, partial first article, full first article, functional validation, reliability work, or customer approval. Risk determines scope; convenience does not.
Do not rely on filename continuity. Record the effective revision, change reason, affected inventory, implementation date or serial boundary, approver, and evidence that the new condition was released before use.
Audit recurrence and production drift
First-article acceptance is a gate, not permanent immunity. Monitor defects, escapes, false calls, test failures, rework, line alarms, material substitutions, program edits, and repeat-order setup. Compare recurring issues with the assumptions in the original matrix.
IPC-1782B establishes risk-based manufacturing and supply-chain traceability requirements covering products, processes, assemblies, parts, components, and equipment. Select the contractual traceability level and fields for the product; do not claim that merely storing a lot number satisfies every level.
Audit samples should prove that delivered units point to the approved configuration and that exceptions were not detached from the release. If the same defect returns, reopen containment and change review. A first article that passed months ago cannot justify a current line condition that no longer matches its evidence.
Conclusion
An SMT first article is ready to release only when one representative unit connects the ordered configuration to the actual production setup and to complete, reviewable evidence. Freeze the PCB, BOM, approved sources, placement and assembly data; verify materials, feeders, libraries, programs, tooling and process conditions; then inspect and test the features each method can genuinely observe.
Preserve failed attempts, adjustments, rework, deviations, open risks and the exact approval boundary. Link the accepted record to the remaining lot and define which product, material, program, equipment, test or quality changes reopen review. This turns first article inspection from a photographed sample into a controlled decision that can stop a setup error before it becomes a batch defect.
Send the released PCB and panel data, BOM and AVL, placement and assembly files, acceptance and test requirements, and change rules for a controlled SMT first-article review.
Request an SMT First Article Review
FAQ
Is an SMT first article the first board off the line?
It can be the first conforming board or panel built under the intended production configuration, but sequence alone does not make it acceptable. The record should identify the effective product data, material lots, line setup, programs, process conditions, inspection and test results, deviations, rework state, and named approval that authorize the next production step.
Does a passing AOI result release an SMT first article?
Not by itself. AOI can provide evidence for visible features within a validated program and defined acceptance logic. The release may also require material and feeder verification, paste or SPI evidence, profile confirmation, X-ray for hidden features, electrical or functional test, dimensional checks, customer-specific records, and resolution of every exception.
Who should approve an SMT first article?
Approval authority should be defined before the build. Manufacturing engineering normally owns the released route and setup, quality owns inspection and acceptance evidence, test engineering owns test method and program evidence, and the OEM owns product requirements and customer decisions. The contract should state when customer approval is also required.
When must SMT first article inspection be repeated?
Repeat the affected evidence after changes that could invalidate the original release, including PCB or BOM revision, component source or package, stencil, paste, feeder or placement library, program, line or equipment, profile, panel support, inspection or test program, long production interruption, repair route, quality degradation, or customer requirement. The response can be targeted or full based on documented risk.
