PCBA First Article Release: Define What Stops the Build

Author : HUANG Micky | Published On : 09 Nov 2026

A first article is useful when it changes what happens next. If the remaining production quantity can continue before anyone reviews the evidence, the first unit has become a sample rather than a release gate. Before a PCB assembly build starts, agree on the hold point, the checks required, and who can authorize continuation.

Start with the configuration that the sample represents. Record the PCB revision, BOM revision, placement file, assembly drawing, and applicable firmware or test procedure. Check fitted and do-not-populate positions against that same configuration. A sample assembled from one revision cannot establish acceptance for a different variant merely because the boards look similar.

Define the hold point before production consumes the whole kit. Depending on the process and agreed plan, an inspection may be useful after placement, after reflow, or after later assembly operations. Some checks must happen before features become inaccessible. Choose the sequence with the manufacturing team; a single final photograph does not establish that every required intermediate check occurred.

Make the evidence match the question. Component identity, location, orientation, visible joint condition, and agreed workmanship criteria address different issues. An AOI result only covers the features included in the inspection program and visible to the equipment. Hidden connections may need another agreed inspection method. Programming and functional checks need their own defined inputs, operating conditions, and pass/fail limits. Do not turn a visual inspection sign-off into an unsupported statement that the complete product works.

Write down what stops the build. A wrong component, unresolved polarity, inconsistent revision, or failed agreed test needs a clear disposition. Identify who investigates, who approves any deviation, and how the approved decision reaches the controlled production documents. A verbal instruction beside the line is difficult to trace and can disappear at a shift change. Keep a proposed substitution separate from permission to fit it.

Separate product corrections from process adjustments. If a misplaced part is corrected on the sample, establish why it happened and whether the same error could affect subsequent units. Where the approved placement program, stencil setup, inspection recipe, or assembly instruction changes, confirm which checks must be repeated. Passing one repaired board does not by itself show that the unmodified process is ready for the remaining quantity.

Close the release gate with a record that another person can follow. Include the sample or lot identity, configuration, inspection and test results, open issues, dispositions, approver, and release time. State which quantity or variant the approval covers. Retain failed results with their resolution instead of replacing them with a clean pass record that hides the sequence of events.

For scope context when dividing assembly, inspection, and test responsibilities, the PCB assembly overview at https://printedcircuitboardassy.com/pcb-assembly/ is a useful reference. The actual first-article checklist and acceptance limits still need to come from the released design and the agreed project requirements.

A practical final question is: could the next operator tell, from the record alone, exactly what was approved and what remains on hold? If the answer is unclear, the release decision needs more definition before the rest of the build proceeds.