Company Address
201, Factory 6, Longhui Industrial Park, Fuqiao 3rd District, Xinhe Community, Fuhai Street, Baoan District, Shenzhen, Guangdong, China
PCB Assembly Knowledge

IPC soldering processes and assembly acceptance: agreeing on inspection criteria

For purchasing and quality teams defining PCB assembly inspection criteria, this article distinguishes J-STD-001 process requirements from IPC-A-610 assembly acceptance. It organizes revisions, classes, hidden-joint coverage, deviation approval, and repair/reinspection records to turn standard names into an actionable order inspection plan.

IPC soldering processes and assembly acceptance engineering diagram with Process, Joint, Recheck

PCB assembly acceptance criteria must answer at least two questions: which requirements govern manufacturing processes, and which conditions determine finished-product acceptance? J-STD-001 and IPC-A-610 are often used together, but an order cannot simply say “per IPC standards.” A joint may look acceptable while lacking required process records; one acceptable reflow profile also cannot establish the absence of wrong parts, reversed components, or hidden connection faults.

Distinguish process requirements from assembly acceptability

IPC's public announcement of the J revisions in 2024 identifies J-STD-001J with soldering process/material requirements and IPC-A-610J with post-assembly acceptability. This supports their division of responsibilities without providing complete individual criteria. Obtain the formal controlled revisions required by contract, with both parties confirming product class, applicable supplements, and conflict precedence. Do not derive joint dimensions, void percentages, or sample quantities from a press release.

Issues to ResolveFile and Evidence EntryProject Output
Do soldering materials and process meet requirements?Agreed J-STD-001 revision and process documentsMaterial lots, process qualification, and required monitoring records
Can finished appearance and assembly status be accepted?Agreed IPC-A-610 revision and product drawingsReference designators, photos, conclusions, and judgment basis
Customer requirements exceeding or differing from general requirementsApproved product specifications and deviation documentsScope, applicable lots, and approval responsibility
whether product function meets the application purposetest specifications, programs, and fixturesActual conditions, results, limit sources, and retest records

Turn standard names into specific order requirements

Lock PCB, BOM, assembly drawing, and firmware revisions before specifying standards. The product-responsible party should select class according to use, rather than a supplier choosing a stricter-sounding name. For special environmental, lifetime, or safety requirements, provide product specifications and distinguish manufacturing deliverables from complete-product design verification. Do not change standard revisions mid-lot without records; publication of a new revision does not automatically amend existing contracts.

If drawings conflict with a general standard, list affected objects and clauses for an authorized written decision. Retained deviations must identify reference designators, quantity, lot, reason, use restrictions, and expiry conditions. Leaving verbal engineering approval in chat prevents later repeat orders from establishing continued applicability. Values in decision tables should trace to formal documents, not inspector memory.

Plan separate coverage for visible joints and hidden connections

Optical inspection can identify missing parts, displacement, polarity, and some soldering problems in visible areas. BGA ball connections, QFN center pads, and obscured regions need risk-based checks. X-ray provides structural information, electrical tests examine nets or component electrical states, and functional tests check specified operation. Their sensitivities and blind spots differ for the same defect. Identify inspection objects in the plan, beyond equipment names.

For example, a power board's QFN center pad contributes to cooling and possibly grounding; edge-joint photos cannot assess its center connection. Center-region imaging, loaded temperature rise, and related electrical tests can provide separate evidence. Allowed void limits and temperature-rise criteria come from product/component requirements, not example values from articles about other packages. For more detailed inspection routing, see QFN and SON solder joint verification.

How to handle acceptable appearance with process deviations

If a profile exceeds the approved window, moisture-sensitivity records have gaps, or material lots differ, first contain the affected scope, then evaluate finished products. Acceptable appearance cannot clear a process deviation. Conversely, complete process records cannot justify releasing a solder bridge as “normal parameters.” Link both situations to the same board or lot, preserve the unrepaired condition, and state the additional evidence needed for a decision.

On-Site ConditionsWhat to Hold FirstNext Judgment
Profile-record anomaly without obvious visual defectsOriginal profile, board identification, oven run, and component limitsDetermine affected components and reliability-verification scope
AOI alarm, manually deemed acceptableOriginal images, part numbers, and verification photosRe-evaluate and record reasons based on controlled clauses
Functional failure but normal solder joint imagesFailure logs, supply state, and firmware revisionDistinguish circuit, software, and connectivity issues
First Test Pass After ReworkRepair designators, thermal profiles, and material change batchesRe-verify affected areas and final configuration

what first article inspection requires delivery of

A first article verifies that files and processes work together on the actual product; it is more than photographing a good-looking board. Link its identification to the BOM revision, stencil, pick-and-place files, reflow program, inspection program, and test program. Distinguish tested, untested, and not-applicable items, with reasons for uncovered items. Continue planned lot inspections after first-article approval; its results do not establish verification of every connection in the lot.

  1. Check complete files and resolve conflicts among polarity, DNP, and substitute materials
  2. Retain key printing and placement results; confirm inspection-program coverage of actual board sides and reference designators
  3. Add hidden-joint and electrical checks according to package risk; identify each image's board and location
  4. Run functional tests under specified loads and interface combinations, retaining program and fixture identifiers
  5. Close first-article issues and document the decision to continue production, limit the pilot run, or pause

Example acceptance record for a mixed-assembly board

This is a method example, not a Historical Production Example. Suppose a control board contains QFP, QFN, and through-hole connectors, with formal standard revisions and product class agreed in the order. A visible first-article QFP bridge requires repair and reinspection by reference designator. An anomaly in QFN imaging must be judged against center-pad requirements, not QFP visual rules. The connector enters final functional testing only after secondary soldering. One board identification thus has three evidence chains, combined for the final release status.

If connector repair reheats a nearby QFN, reinspection scope must consider thermal and removal/reinstallation effects. Rechecking connector continuity alone may miss changes to previously completed components. Retain original failures and final passes instead of overwriting defect history with the last passing report. For actual inspection items, also compare Test Scope and Factory Records Formulate.

common questions in acceptance agreements

Must an order state standard revisions if inspectors have training certificates?

Yes. Training history and the current order's document requirements are different matters. A certificate does not identify the contractual revision or class, replace customer supplements, or provide project authorization.

Can photos serve as complete proof of shipment

Photos establish visible conditions at specific locations and times. Link them to board identification, reference designators, and imaging conditions; they still do not cover underside connections, firmware content, or function under every load.

How sampling and re-evaluation are applied to specific scopes

An inspection plan must identify its unit: complete board, component category, joint, or lot. Sample quantities and allowable outcomes come from the approved contract or plan; this page provides no universal sample count. Define responsibility for expanded inspection, work-in-progress holds, and evaluation of delivered products after sample failures. Otherwise, “sampling passed” may mean very different scopes to different people. Retain original decisions and reassessment conclusions; do not erase alarms by overwriting records. For disputed photos, verify suitable magnification, lighting, and viewing angle. Before destructive analysis, identify samples and boards and agree that analyzed items cannot be normal deliverables. Separate temporary customer release from long-term process approval; the next lot cannot automatically inherit a previous concession. When interpretations differ on the production floor, incorporate the approved interpretation into process and inspection documents and confirm personnel actually use it. Meeting minutes that never reach execution do not resolve recurring issues.

Source material and applicable scope

  1. IPC, “IPC Releases ‘J’ Revisions to Two Leading Standards for Electronics Assembly”; public news dated 2024-04-08; checked on 2026-10-17; sections on standard responsibilities and revisions. Supports the distinction between J-STD-001J and IPC-A-610J purposes, without the complete criteria in the paid standards.

cross-check assembly route based on board type

Back to PCB Assembly Knowledge
PCB / PCBA · PROJECT ENQUIRY

Does Your Project Need PCB Fabrication, Assembly, or Box Build?

Tell us the product use and which files are available. We can define the next engineering step even when the data package is not complete.

Call UsWhatsAppRequest a Quote