First Article Inspection in PCB Assembly Outsourcing

 

The first assembled board is where assumptions become physical.

A BOM may look complete until the purchased component turns out to have the wrong package. A pick-and-place file may import correctly until an IC rotates 90 degrees because the CAD and placement-machine conventions were interpreted differently. A connector may appear correct on the assembly drawing but interfere with the enclosure, cable path, or mating hardware once the board is actually built.

That is why first article inspection (FAI) matters in outsourced PCB assembly.

FAI is not simply a visual inspection of the first board off the line. It is a controlled comparison between the released manufacturing package and the first physical assembly produced from it. The purpose is to catch interpretation, documentation, setup, and product-integration problems before they are repeated across the rest of the build.

FAI also has limits. Passing the first article does not prove that every subsequent board will be defect-free, and it does not replace process control, electrical testing, workmanship requirements, or final acceptance inspection.

Its job is narrower: confirm that the customer and contract manufacturer are building from the same requirements and interpreting them the same way before production continues.

It is also worth distinguishing a practical PCBA first article review from a formally defined aerospace FAI. SAE AS9102C establishes formal first article inspection requirements for aviation, space, and defense products. The International Aerospace Quality Group's 9102 guidance notes that the framework can also be used in other industries where a standardized FAI process is needed. For most commercial and industrial PCB assembly programs, however, the exact FAI scope is defined by the customer, contract manufacturer, quality requirements, and purchase agreement rather than automatically by AS9102.

What Should a PCBA First Article Inspection Prove?

At the simplest level, FAI asks one question:

Does the first assembled PCBA match the released design and manufacturing requirements closely enough for the build to continue?

The answer may depend on information from several sources:

• Bill of materials (BOM)

• Approved vendor list (AVL)

• PCB revision

• Assembly drawing

• Pick-and-place or centroid data

• Approved component substitutions

• DNP/DNI instructions

• Polarity and orientation notes

• Programming requirements

• Test specifications

• Customer drawings

• Mechanical requirements

• Labeling and serialization requirements

• Product-specific acceptance criteria

The first article is therefore more than a sample board. It is evidence that the manufacturing interpretation is aligned with the released product definition.

If a connector faces the wrong direction, a DNP component is installed, an alternate part does not match the intended footprint, or the functional-test fixture cannot reach a required test point, FAI provides a controlled opportunity to stop the build and determine why.

That distinction matters in outsourced manufacturing. A contract manufacturer may know how to assemble the board correctly but cannot always know which design details are negotiable and which are functionally critical unless those requirements are documented.

Start With the Released Build Package

A good FAI does not begin with an inspector looking at a board and deciding whether it "looks right."

It begins with the released build package.

IPC's IPC-2611, Generic Requirements for Electronic Product Documentation describes electronic product documentation as potentially including assembly descriptions, printed-board fabrication data, BOM information, diagrams, and other manufacturing information. That is the right mindset for FAI: the physical board should be checked against a controlled product definition, not against memory or an engineer's informal expectation.

For an outsourced PCBA build, the release package may include:

Build Package Item	What FAI Should Verify	Typical Mismatch
BOM and AVL	Manufacturer part number, package, value, quantity, substitute status, sourcing rule	Purchased part does not match the footprint or approved alternate
Pick-and-place data	Reference designator, X/Y coordinates, rotation, board side	Component rotated, placed on the wrong side, or programmed from the wrong revision
Assembly drawing	Orientation, DNP status, hardware, labels, connector direction, special notes	Drawing requirement was missed or conflicts with another file
PCB fabrication data	Board revision, outline, finish, drill information, key fabrication requirements	PCB revision does not align with BOM or assembly revision
Programming instructions	Device, firmware file, revision, programming sequence	Wrong firmware or undefined programming requirement
Test specification	Test method, limits, fixture requirements, power conditions	Test cannot run because limits, access, or firmware are missing
Customer requirements	Product-specific requirements beyond general workmanship standards	General inspection criteria conflict with a customer-specific requirement

Revision control is critical here. A first article inspected against an obsolete drawing or BOM is not meaningful evidence.

This is also where a quality management system matters. ISO 9001 addresses controlled documented information and operational controls, while ISO's guidance specifically identifies work instructions, specifications, approved supplier lists, test instructions, inspection plans, and quality plans as examples of useful controlled information.

Verify Component Identity Before Judging Workmanship

A perfect solder joint is irrelevant if the wrong component is soldered into it.

Before focusing on workmanship, the first article should answer the more fundamental question:

Is the correct part installed in the correct location and configuration?

At minimum, check:

• Manufacturer part number where verification is practical

• Package

• Value

• Reference designator

• Board side

• Polarity

• Orientation

• DNP/DNI status

• Approved substitution status

For critical components, the inspection may go further and verify package markings, lot or date-code information, programmed-device status, firmware revision, or customer-approved alternates when those items are part of the project requirements.

This becomes particularly important when component sourcing is outsourced.

In a consigned build, the customer supplies most or all components. In a turnkey build, the contract manufacturer handles procurement within the agreed sourcing rules. A hybrid build divides purchasing responsibility between the customer and manufacturer.

The first article should reflect those responsibilities. If substitutions are allowed, the installed part should match the approved substitution process rather than simply being electrically similar.

For programs requiring deeper production traceability, IPC-1782, Standard for Manufacturing and Supply Chain Traceability of Electronic Products provides a risk-based framework covering materials and manufacturing processes for printed-board assemblies and related products.

Polarity, Orientation, and Product Variants Deserve Formal Review

A large share of first-article problems are not soldering defects at all.

They are interpretation problems.

Examples include:

• Reversed diode

• Reversed LED

• IC rotated 90 or 180 degrees

• Polarized capacitor installed backward

• Sensor facing the wrong direction

• Connector pointing toward the wrong board edge

• DNP component installed

• Required option resistor omitted

• Wrong product variant assembled

• Wrong BOM revision used

When one of these appears, stopping at "operator error" is usually too shallow.

The real question is what allowed the error to happen.

FAI Finding	Source to Investigate	Corrective Action
Reversed diode, LED, IC, or sensor	Silkscreen, pin-1 callout, assembly drawing, package marking, placement rotation	Correct source documentation or placement setup and verify another sample
Wrong connector orientation	Assembly drawing, 3D model, cable path, mating direction	Correct drawing or work instruction before continuing
DNP component installed	BOM variant, pick-and-place file, assembly drawing	Align variant status across released files
Required jumper or option part missing	BOM configuration, work instruction, product variant definition	Define requirement explicitly and update controlled documentation
Wrong PCB or BOM revision	ERP/MES record, traveler, purchase order, released package	Quarantine affected material and restart from the controlled revision

The purpose is not to decide whether engineering or manufacturing deserves blame.

The purpose is to remove the ambiguity that allowed the mismatch.

Workmanship Needs an Agreed Acceptance Standard

Once component identity and configuration are confirmed, workmanship becomes the next question.

But workmanship should not be judged using criteria invented at the inspection bench.

For most contract electronics manufacturing, the acceptance basis should be agreed before production and may include:

• IPC-A-610 revision and class

• Customer drawings

• Approved deviations

• Product-specific requirements

• Supplier inspection procedures

• Contract or purchase-order requirements

The current IPC-A-610J and IPC J-STD-001J are complementary but serve different purposes: IPC-A-610 addresses post-assembly acceptance criteria, while J-STD-001 addresses soldering processes and materials used to produce electronic assemblies.

A first article workmanship review may include:

• Solder bridges

• Insufficient solder

• Excess solder

• Tombstoning

• Lifted leads

• Component alignment

• Missing or damaged components

• Visible contamination

• Handling damage

• Board scratches

• Connector seating

• Hardware installation

• Label condition

• Customer-defined special features

The applicable IPC class should also be stated rather than assumed. A contract manufacturer should not have to guess whether the customer expects Class 2, Class 3, or additional product-specific criteria.

Hidden interconnections require another inspection method. BGA, LGA, QFN, and other bottom-terminated components cannot be fully evaluated by ordinary optical inspection. Depending on product risk and the agreed quality plan, X-ray, electrical test, process evidence, or a combination of methods may be required.

The key point is that FAI verifies the agreed acceptance basis; it does not create that basis.

Check Test Readiness on the First Article

A PCBA can look correct and still be impossible to test efficiently.

For an outsourced build, this is one of the most valuable things to discover before ten, one hundred, or one thousand more boards are assembled.

A useful first article review should therefore ask whether the intended programming and test process can actually run.

Check questions such as:

• Are the required test pads accessible?

• Can the fixture make reliable contact?

• Is the programming connector installed and reachable?

• Is the correct firmware package available?

• Is the firmware revision controlled?

• Are power-up voltage and current limits defined?

• Does the fixture match the board outline?

• Can all required connectors be accessed?

• Are functional pass/fail limits documented?

• Is the retest procedure defined after rework?

A test without defined limits is not an acceptance test. It is simply an observation.

For prototypes, some limits may still be under development. That is acceptable if the uncertainty is documented. What matters is that the team understands which parts of the test process are released and which are still engineering work in progress.

Do Not Ignore Mechanical Fit and Product Interfaces

FAI should not stop at the solder joints.

For a PCBA-only project, the first article may also need to verify:

• Board outline

• Mounting holes

• Edge connectors

• Connector direction

• Component height

• Heat sinks

• Shields

• Switches

• Displays

• Mechanical keepouts

If the manufacturing scope extends into box build, additional checks can include:

• Enclosure fit

• Cable routing

• Wire-harness length

• Fastener type

• Torque requirements

• Strain relief

• Gasket clearance

• Display alignment

• Button actuation

• Label placement

• Serial-number format

For cable and harness workmanship, IPC/WHMA-A-620E is the IPC/WHMA standard covering manufacturing and acceptance requirements for cable and wire-harness assemblies.

These mechanical checks matter because an electrically functional PCBA can still fail at the product level. A USB connector can be perfectly soldered but sit too far from the enclosure opening. A tall capacitor can interfere with a housing rib. A cable can bend correctly on the bench but collide with another module during final assembly.

Those are much cheaper problems to find on the first article than after the rest of the build is complete.

Labels and Serialization Are Part of the Product

Labels often receive less attention than they deserve.

A poorly placed label can:

• Cover a test point

• Block a vent

• Hide a component marking

• Interfere with an enclosure

• Sit outside a barcode scanner's usable area

• Carry the wrong revision

• Break traceability between assembly and test records

If the product uses serialization, the first article should verify how serial numbers are generated, applied, scanned, recorded, and associated with test or production data.

For products requiring manufacturing traceability, this is part of the same broader control problem addressed by IPC-1782 rather than a cosmetic afterthought.

Record Causes and Corrective Actions, Not Just Defects

A weak FAI report is a list of things that look wrong.

A useful report explains what was found, where it came from, what will change, and how the correction will be verified.

For example:

Weak record:
"D12 reversed."

Useful record:
"D12 installed with polarity opposite assembly drawing. Pick-and-place rotation and package pin-1 convention to be reviewed. Placement program to be corrected and polarity verified on the next assembly before lot release."

The second record creates a path to closure.

A practical FAI record should identify:

Record Field	Why It Matters
Finding	States the physical condition clearly
Reference designator or location	Lets engineering identify the issue quickly
Requirement or source document	Connects the finding to the BOM, drawing, placement file, test plan, or work instruction
Risk to current build	Separates stop-build issues from minor corrections
Corrective-action owner	Establishes responsibility
Required document/process update	Prevents the same error from returning
Verification method	Defines how closure will be confirmed
Approval status	Records whether production may continue

This is where controlled documentation becomes essential. ISO 10013:2021 provides guidance on developing and maintaining documented information that supports an effective quality management system.

If rework is required, it should also follow an approved process rather than an improvised bench fix. IPC identifies IPC-7711/21D as its guidance for rework, repair, and modification of electronic assemblies.

Classify Open Issues Before Releasing the Rest of the Build

Not every first-article finding requires the entire order to stop.

Every finding does, however, need a disposition.

A practical classification system is:

Build Stop

Use this when continuing would knowingly reproduce a significant problem.

Examples include:

• Wrong component

• Wrong PCB revision

• Critical polarity or orientation error

• Unsafe power-up condition

• Product variant mismatch

• Test method cannot be executed

• Customer-controlled characteristic is incorrect

Correct and Continue

Use this when the problem can be corrected before subsequent assemblies are produced.

Examples include:

• Placement-program correction

• Label-position adjustment

• Work-instruction update

• Fixture adjustment

• Missing manufacturing note

The correction should still be verified before normal production resumes.

Accept for Prototype Only

Engineering may intentionally accept a noncritical issue to keep a prototype program moving.

That does not mean the issue has disappeared.

The acceptance should be documented, limited to the current scope, and accompanied by an action for the next revision or build.

Track for the Next Revision

Some findings identify improvements rather than current build failures.

Examples include better test access, clearer silkscreen, improved fixture access, or a mechanical adjustment that is not required to satisfy the current release.

The important point is that the decision is written down.

A prototype waiver should not quietly turn into production approval.

Define FAI Responsibilities Before Outsourcing the Build

FAI works best when its scope is agreed before the first board reaches the inspection bench.

When preparing an outsourced PCBA project, define:

• Who creates the released manufacturing package

• Who controls revisions

• Who approves component substitutions

• Whether the assembler may continue after the first article

• Which findings require customer approval

• What inspection standard applies

• Whether first-article photos are required

• Which components require X-ray

• What programming records are required

• What electrical or functional testing is required

• How rework is documented

• How deviations are approved

• What evidence closes an FAI finding

These responsibilities are part of the larger supplier/customer handoff. If you are deciding how much sourcing, manufacturing, testing, and quality responsibility to transfer to a contract manufacturer, our guide to pcb assembly outsourcing discusses that broader decision.

The more responsibility the contract manufacturer assumes, the more important it becomes to define what constitutes an approved first article and who has authority to release the remainder of the build.

Common FAI Mistakes in PCB Assembly Outsourcing

Skipping FAI Because the Build Is Small

A ten-board prototype can still contain the same interpretation error on all ten boards.

Small quantity does not eliminate the value of checking the first assembled unit before repeating the same setup.

Treating FAI as Visual Inspection Only

Workmanship is only one part of the review.

Component identity, revision alignment, variants, orientation, programming, test readiness, mechanical interfaces, labels, and documentation may be just as important.

Inspecting Against the Wrong Revision

A detailed inspection is useless if the inspector is comparing the assembly with an obsolete BOM or drawing.

Revision status should be established before inspection starts.

Closing the Report Without Closing the Cause

Photographing a defect is not corrective action.

A finding should lead to a controlled document change, process correction, approved deviation, or other defined disposition.

Letting Schedule Pressure Become Production Approval

"Accept for prototype" and "approved for production" are not equivalent statements.

The release decision should clearly state what the approval covers.

Assuming Every Problem Began on the Assembly Line

The production operator may be the final person who touched the part, but the original cause may be an incorrect BOM, ambiguous drawing, bad footprint convention, outdated placement file, undocumented ECO, or incomplete test specification.

FAI should trace the problem back far enough to prevent recurrence.

Conclusion

First article inspection is one of the most useful control points in outsourced PCB assembly because it sits between digital product definition and repeated physical production.

A good FAI verifies more than whether the first board looks acceptable. It checks whether the correct components, revision, orientation, product variant, workmanship requirements, programming process, test method, mechanical interfaces, labels, and manufacturing records all agree with the released build package.

More importantly, it creates a closure loop.

A finding should lead to a cause. The cause should lead to an owner and corrective action. The correction should update the controlled manufacturing information or process, and the result should be verified before the build moves forward.

That is what makes first article inspection valuable: not the first board itself, but the opportunity to correct one misunderstanding before it becomes an entire production lot.

FAQ

What is first article inspection in PCB assembly?

First article inspection is a structured review of the first assembled PCBA against the released manufacturing package. It typically verifies component identity, placement, polarity, product variant, workmanship, programming, test readiness, mechanical requirements, and other customer-defined requirements before the remaining build proceeds.

Is PCBA first article inspection the same as AS9102?

Not necessarily. AS9102C is an aerospace first article inspection standard developed for aviation, space, and defense products. Commercial and industrial PCBA projects may use similar principles without being contractually subject to AS9102. The applicable requirement should be defined by the customer, contract, quality system, or industry-specific standard.

Is first article inspection the same as final inspection?

No. FAI examines an initial production sample so setup, documentation, and interpretation problems can be corrected before they are repeated. Final inspection evaluates completed assemblies against the applicable release requirements.

What should be included in a PCBA first article checklist?

A practical checklist should cover BOM and revision verification, component identity, polarity and orientation, DNP/DNI status, approved substitutions, workmanship, programming, test readiness, mechanical fit, labels, serialization, open findings, corrective actions, and release status.

Does passing FAI guarantee the rest of the lot will pass?

No. FAI can identify setup and documentation problems early, but subsequent assemblies still depend on process control, inspection, testing, traceability, change control, and final acceptance.

Who should approve a first article?

Approval authority should be established before production. Depending on the project, it may belong to the customer's design authority, quality engineer, manufacturing engineer, program owner, or another formally designated representative. The contract manufacturer may provide inspection results and corrective-action recommendations, but customer-controlled design and acceptance decisions need clear ownership.

Should prototypes receive first article inspection?

Usually, yes, although the process may be lighter than for production. Prototype FAI is particularly useful for identifying BOM, placement, polarity, mechanical, programming, and test problems before they are duplicated across the remaining prototype quantity.