Elecrow PCBA First Article Inspection: What Teams Should Verify

First article inspection, often called FAI, is the disciplined review of the first completed PCBA before a team treats a build as repeatable. It is not just a cosmetic check of solder joints. A useful Elecrow PCBA first article inspection confirms that the released design files, components, assembly process, programming steps, and test plan produce the intended hardware. It catches systemic errors while the build quantity is small and the correction cost is still manageable.

For prototypes, FAI may be a rapid engineering review performed on one or several boards. For production, it may include documented dimensional, material, process, and functional records. In both cases, its purpose is the same: prove that the actual board matches the approved configuration before more units are committed. Teams that skip this step often discover a library, polarity, sourcing, or test problem only after it has been replicated across an entire panel or order.

Set the inspection scope before assembly begins

FAI works best when its acceptance criteria are defined during release, not after reflow. Identify which checks are visual, which require measurement, which require X-ray or automated optical inspection, and which require functional test. Tie every check to a controlled source: schematic, BOM, assembly drawing, fabrication drawing, CAD data, firmware release, or test specification.

Start by assigning a build identifier. It should capture PCB revision, BOM revision, placement revision, firmware version, and any approved component substitutions. If the first article is later found to be good, that identifier tells the team exactly what configuration was proven. Without it, a board may pass testing while its source files remain ambiguous.

Create a risk-based checklist

Not every reference designator needs the same level of attention. Prioritize components and features that can create hidden or high-impact defects: polarized parts, BGAs, bottom-terminated packages, fine-pitch ICs, RF modules, switching power stages, high-current connectors, programmed devices, and safety-related clearances. Include any item changed since the previous revision. A focused checklist is more effective than a long generic form that inspectors rush through.

• Verify board identity, revision marking, finished dimensions, surface finish, and panel breakaway features.
• Verify the BOM against fitted components, including manufacturer part numbers for critical items.
• Verify reference designators, polarity, pin-one orientation, package selection, and placement rotation.
• Verify solder joints, thermal-pad behavior, through-hole fill, and cleanliness.
• Verify firmware programming, serial-number handling, calibration, and functional test results.

Confirm the right materials were built

Begin with traceability rather than appearance. Compare the physical PCB marking and manufacturing record with the released fabrication data. Check board thickness, copper finish, controlled-impedance notes, and special construction features where relevant. Confirm that the PCBA was assembled to the intended revision, especially if a prior revision is still present in the factory or laboratory.

Next, check components against the BOM. Critical ICs, oscillators, power devices, connectors, and safety components should be verified by marking, label, or incoming inspection record. For passive parts, verify values and package families using the approved component records and measurement when practical. A visually similar component may have a different tolerance, voltage rating, pinout, or temperature class. The component sourcing process described in Elecrow’s PCBA component sourcing guide provides a useful foundation for this verification.

Check approved substitutions explicitly

Substitution is not automatically a defect, but undocumented substitution is a configuration-control failure. Compare every alternate used in the build with the engineering approval. Check electrical equivalence, package compatibility, orientation, programming needs, and any changes to test limits. Record the lot and quantity affected. A first article is the right point to validate an approved alternate before it becomes the default in later purchases.

Inspect placement, polarity, and solder quality

Use the assembly drawing, component overlays, and board render to review component placement. Inspect both sides of the board under adequate magnification. Look for missing components, wrong positions, rotated polarized parts, incorrect connectors, lifted leads, skew, insufficient fillets, solder bridges, tombstones, and paste balls. Compare pin-one marks with the drawing rather than assuming a package notch has been interpreted correctly.

Pay close attention to components whose orientation is electrically meaningful but visually subtle. Diodes, electrolytic and tantalum capacitors, LEDs, crystals with asymmetric pads, QFNs, regulators, MOSFETs, and sensors are frequent candidates. Confirm connector keying and pin numbering at the system level; a connector can be placed correctly on the PCB yet have a mirrored cable-facing pinout in the product.

Use the right inspection method for hidden joints

AOI is useful for missing parts, polarity marks, visible bridges, and lead alignment, but it cannot see joints beneath BGAs, QFNs, or large thermal pads. Use X-ray where hidden solder-joint integrity matters. Review BGA ball collapse, bridging, voiding, and QFN thermal-pad coverage according to the component and product requirements. If X-ray is not available for an early prototype, identify that risk explicitly and increase functional coverage rather than pretending visual inspection is sufficient.

For through-hole connectors and power parts, inspect barrel fill, lead protrusion, wetting on both sides, and solder bridges. Confirm that selective solder, wave solder, or hand-soldered areas match the intended process. Residue, flux splatter, or uncleaned no-clean flux may be acceptable only when consistent with the process specification and product environment.

Measure electrical safety and basic power behavior

Before loading firmware or attaching expensive equipment, perform safe power-up checks. Measure resistance from each power rail to ground and compare it with known-good expectations. Use a current-limited supply for the first energization. Confirm input protection, regulator output voltages, sequencing, quiescent current, and thermal behavior. Monitor current while enabling subsystems so a shorted rail or incorrect assembly does not damage downstream components.

Verify high-current paths, isolation barriers, and protective earth connections according to the product’s applicable standards. Check fuse orientation and value, creepage and clearance around high voltage, and connector polarity. This is especially important after a PCB or component substitution, because a layout change can preserve functionality while reducing safety margin.

Exercise interfaces and timing-sensitive circuits

Run a repeatable bring-up sequence covering clocks, reset, programming interfaces, boot configuration, communication ports, and peripheral functions. Measure oscillator frequency and supply ripple where relevant. Test USB, Ethernet, CAN, UART, SPI, I2C, RF, display, and sensor interfaces using the actual cables and devices planned for the product. For high-speed interfaces, confirm link training, error counters, eye-quality indicators, or protocol diagnostics as available.

Do not accept a board merely because it “boots.” Test the failure cases that the product must handle: brownout, unplugged peripherals, boundary inputs, repeated reset, thermal soak, and power cycling. If calibration or manufacturing test firmware is used, lock its version in the FAI record. A board that passes with a developer image may fail with the production configuration.

Review process feedback with the assembler

FAI should include manufacturing feedback, not just laboratory results. Ask whether the Elecrow assembly team observed feeder issues, placement offsets, stencil-release problems, reflow concerns, board warpage, inspection flags, or unusual rework. These details can reveal a design-for-manufacturing weakness before it becomes a yield problem. The Elecrow PCBA manufacturing process explains the stages where that feedback originates.

If a defect is found, separate containment from root cause. Containment may be to stop the lot, sort affected boards, or apply a documented rework instruction. Root cause may be a wrong BOM line, footprint error, paste aperture, placement rotation, profile setting, or component-lot issue. Record the evidence and decide whether the fix requires a manufacturing instruction, a controlled BOM change, or a new PCB revision.

Document acceptance and release the build deliberately

A useful FAI record includes the unit serial number, build configuration, inspection results, photographs of critical areas, measurements, test logs, nonconformances, and approvals. Mark any deviations as accepted only with explicit engineering authority. If the first article is not representative—for example, it was manually reworked—do not use it as proof that the normal process is ready.

• Record pass, fail, and conditional-acceptance results against each defined requirement.
• Attach evidence for critical measurements and hidden-joint inspection.
• Capture the exact firmware, test script, and calibration data used.
• Close or formally defer every discrepancy before scaling the build.
• Update the controlled package so the next order uses the proven configuration.

Once FAI is accepted, keep the result linked to future Elecrow PCBA orders. Use the Elecrow shop for standard assembly requests and contact support for build-specific quality requirements. A clear first article inspection is not bureaucracy: it is the evidence that a PCB assembly team can move from an engineering sample to a controlled, repeatable product build with confidence.