The decision follows agreed criteria and closed evidence.
Shipment release inspection
PCB and PCBA Final Quality Inspection
APTPCB closes the agreed manufacturing, inspection and test record, checks final product condition, and confirms labels and packaging before an identified PCB or PCBA lot is released.
Coverage, sampling, records and acceptance criteria are confirmed for the project. Final inspection does not replace product safety, reliability or system qualification by the customer-designated authority.
Configuration is fixed before product and records are released.
The inspected population and reaction rule are confirmed per project.
Fields, format, traceability and frequency are agreed in the RFQ.
Primary release owner
Can this PCB or PCBA lot be released?
Connect each decision to an approved source, an observable result and a reaction rule before shipment is authorized.
Configuration release check
- Verify
- Part number, revision, variant, ECO status, quantity and destination.
- Source or criterion
- Approved order, fabrication or assembly drawing, BOM or AVL and manufacturing record.
- Release when
- The physical population and the approved configuration agree.
- If it fails
- Hold affected units and reconcile the configuration before labeling or shipment.
Comparable supplier scope
Are inspection scope and deliverables commercially comparable?
Compare suppliers using the same population, criteria, reporting, traceability, exception and packaging requirements.
Compare the same population
Ask whether each characteristic is checked per unit, per lot or by an agreed sampling plan and what happens after a reject.
Define the required record
Specify report fields, file format, frequency, retention and whether results link to a lot, panel or serial number.
Agree the disposition path
Define shipment hold, notification, sorting, rework, concession authority and reinspection requirements before production.
Expose scope that changes price or schedule
Fixture or program setup, inspection population, sampling depth, special methods, reporting and retention can change the quotation.
Design-to-inspection handoff
Can the critical requirements be inspected or tested?
Make interfaces, critical characteristics, access, firmware and limits explicit before the manufacturing test plan is released.
Freeze the design baseline
Provide the released fabrication data, drawing, BOM or AVL, CPL, assembly drawing, DNP list and approved ECO status.
Identify critical characteristics
Mark dimensions, interfaces, polarity, connectors, mechanical alignment, coating areas, cleanliness and cosmetic criteria that affect acceptance.
Define access and limits
Provide test points, connector access, keep-outs, firmware, stimuli, loads, expected outputs and measurable pass/fail limits.
Separate factory screening from product proof
State which risks are screened in production and which remain covered by design verification, reliability testing or system qualification.
Controlled handoff
What must each team define before release?
Missing inputs become visible before quotation instead of becoming assumptions during inspection.
Quality / NPI
Define acceptance and the reaction path
Tie each release characteristic to a criterion, method, population and authorized disposition.
- Applicable document, revision, class and exceptions
- Critical-to-quality characteristics and suitable method
- Unit, lot or sampling coverage and escalation rule
- Containment, rework, concession and reinspection
Procurement
Make supplier scopes commercially comparable
Ask each supplier to quote the same evidence, traceability, exception and shipping requirements.
- Report fields, format, language, frequency and retention
- Lot, panel or serial traceability depth
- Label, pack quantity, ESD and moisture controls
- Setup, sampling, special-method and reporting drivers
Design engineering
Make critical features inspectable and testable
Provide the technical baseline that turns a broad quality requirement into an observable check.
- Critical dimensions, interfaces and mechanical references
- Test points, connector access, board support and keep-outs
- Firmware, stimuli, loads, expected outputs and limits
- Coating, cleanliness, marking and cosmetic criteria
Method boundary
Which method proves each requirement?
Assign each risk to a method that can observe it, then define the evidence expected at final release.
Final inspection
Configuration, final visible condition, quantity, labels, packaging and record closure.
- Evidence
- Agreed release checklist or summary tied to the defined population.
- Boundary
- It does not replace a specialized inspection or test.
Also review: PCBA test strategy
AOI
Presence, orientation and visible features within program and optical access.
- Evidence
- Program revision, reviewed calls and agreed status.
- Boundary
- It cannot prove complete hidden-joint integrity or product function.
X-ray
Selected hidden-joint geometry in the agreed components, areas and views.
- Evidence
- Inspected areas, views, criteria, sampling and result.
- Boundary
- It does not automatically establish metallurgy, electrical behavior or function.
ICT / flying probe
Nets and components accessible to the released program, fixture and test points.
- Evidence
- Netlist, program or fixture revision, limits and result log.
- Boundary
- Coverage depends on electrical access, isolation and the test model.
Also review: Flying probe testing
FCT
Functions included with approved firmware, power, I/O, loads, sequence and limits.
- Evidence
- Program version, configuration and result tied to the defined unit or lot.
- Boundary
- It covers only the specified functions and does not replace complete product or system qualification.
Order-defined evidence
What can be included in the release package?
The exact fields, format, population and delivery frequency are confirmed per order. The example below helps teams specify evidence without implying a universal report.
Lot release summaryPass / Hold
Part and revisionOrder-defined
Lot or serial rangeAs agreed
Inspection statusPass / Hold
Required test statusClosed / Open
Deviation referenceIf applicable
Label and pack checkVerified / Hold
Illustrative fields only. Exact format, population and frequency are confirmed per order.
Baseline identity
Part, revision, population and release status can be associated with the shipment when included in scope.
Agreed evidence
An inspection summary and selected test results may be included in the format and frequency defined by the order.
Exceptions
Approved deviations, disposition and reinspection status can be referenced when required.
Receiving data
Labels, quantity, packaging and traceability fields follow the approved receiving requirements.
Comparable quotation
What should you send for a final inspection RFQ?
Use the same input package across suppliers to compare the actual release scope, residual risk, evidence and commercial assumptions.
Design package
- Part, revision, variant, ECO status, quantity and destination
- Gerber, ODB++, IPC-2581, drawing, BOM or AVL, CPL, DNP and panelization as applicable
- Critical dimensions, interfaces, polarity, connectors, coating, cleanliness and marking requirements
Control plan
- Customer specification and IPC-A-600 or IPC-A-610 when contractually applicable
- Unit, lot or sampling coverage, ISO 2859-1 plan if selected, and reject reaction
- AOI, X-ray, ICT, flying probe, programming or FCT scope, programs and limits
Release package
- Lot or serial traceability, retention, concession and notification requirements
- Pack quantity, labels, ESD, moisture and physical protection
- Required report fields, language, format and delivery frequency
Contract references must identify the applicable document, revision, class, method and exceptions. Common options include IPC-A-600 for bare-board visual acceptability, IPC-A-610 for assembly acceptability, J-STD-001 for soldering process requirements, IPC-1601 for PCB handling and storage, and ISO 2859-1 when attribute sampling is selected.
Release planning FAQ
PCB and PCBA final inspection questions
Short answers for defining scope, evidence and responsibility before order release.
What is final quality inspection for PCB and PCBA?
Final quality inspection is the release gate after the planned manufacturing, inspection and test operations. It confirms the correct part and revision, required evidence status, visible condition, quantity, labels and packaging before shipment is authorized.
Does final inspection replace AOI, X-ray, ICT or FCT?
No. Final inspection verifies that the required controls were completed and their status permits release. It does not recreate AOI or X-ray visibility, ICT electrical coverage or FCT functional coverage.
Is every board checked during final inspection?
Not automatically. Some characteristics may be checked on each unit, while others are checked by lot or sampling. The order must define the population, inspection level, method, acceptance criteria and reaction rule.
What happens when final inspection finds a nonconformance?
The affected lot or population is identified and held. The deviation and its scope are recorded, then the authorized disposition is applied: sorting, rework, reinspection, approved concession or scrap. Release follows only after the required action is verified.
What records can be supplied with a released lot?
Depending on the contract, the release package may include lot and revision identity, an inspection summary, agreed test results, applicable material or conformity certificates, approved deviations and labeling information.
Which IPC criteria apply to final PCB and PCBA inspection?
IPC-A-600 may be specified for bare-board visual acceptability and IPC-A-610 for electronic assembly acceptability when the document, revision, class and exceptions are defined by contract. J-STD-001 addresses soldering and process requirements; it is not a finished-product performance guarantee.
What should an RFQ include for final inspection and release records?
Provide the part and revision, quantity and packaging, drawings and specifications, applicable class or criteria, critical characteristics, sampling or inspection plan, traceability needs, required tests, nonconformance rules and expected evidence format.
Define the release gate before quotation
Send the revision, acceptance criteria, coverage, required tests, traceability, exception, packaging and evidence requirements.