IPC-A-610 is one of the first standards buyers mention when discussing outsourced PCB assembly. That makes sense. It gives inspectors, engineers, assemblers, and customers a common language for evaluating the acceptability of completed electronic assemblies.
The problem is that many RFQs reduce that requirement to a single line:
“Build to IPC-A-610.”
That is rarely specific enough.
IPC-A-610 does not tell the contract manufacturer which BOM revision to build, which component alternatives are approved, what firmware to load, how hidden solder joints should be inspected, what functional limits the product must meet, or who has authority to approve a deviation.
For outsourced PCBA, the useful question is not simply whether a supplier “follows IPC.” It is:
Which IPC-A-610 revision and product class apply, which customer documents take precedence, what inspection evidence is required, and how will exceptions be handled?
Those decisions should be made before production starts—not during first-article review or after a shipment is already on hold.
IPC-A-610 is primarily an acceptability standard for completed electronic assemblies.
It is used to evaluate workmanship conditions such as component installation, soldering, terminals, connectors, and other assembly features according to the applicable product class.
That makes it extremely useful, but its scope has limits.
A contract manufacturer still needs a complete build package that may include:
BOM
Gerber, ODB++, or other fabrication data
Pick-and-place data
Assembly drawings
Polarity and pin-1 information
DNP / no-pop instructions
Approved component alternates
Programming requirements
Functional-test requirements
Packaging specifications
Customer-specific workmanship requirements
Approved deviations or waivers
IPC-A-610 can help determine whether many finished assembly conditions are acceptable. It cannot determine what product variant the customer intended to build.
This distinction becomes especially important in pcb assembly outsourcing, where engineering intent must be transferred from one organization to another through controlled documentation.
Standards change.
At the time of writing, IPC lists IPC-A-610J, released in 2024, as the current revision. IPC announced the J revisions of both IPC-A-610 and J-STD-001 in April 2024.
The current document status should still be checked before a new program is released using IPC's official Document Revision Table.
An RFQ should therefore avoid wording such as:
IPC-A-610 required.
A better requirement identifies:
The standard
The revision
The product class
The document hierarchy
Customer-specific exceptions
Required inspection evidence
For example:
Workmanship acceptance shall be evaluated to IPC-A-610J, Class 2, unless otherwise specified by the approved customer drawing, purchase order, or formally approved deviation.
That single sentence removes several common sources of ambiguity.
Procurement, engineering, quality, and the contract manufacturer should all be working from the same revision.
If the assembly drawing specifies Revision H while the purchase order specifies Revision J, the disagreement should be resolved before the build begins.
IPC-A-610 defines three product classes with different expectations.
In simplified terms:
Class 1 applies to general electronic products where basic functionality is the primary requirement.
Class 2 applies to dedicated-service products where continued performance and extended life are expected.
Class 3 applies to high-performance or harsh-environment products where continued operation is critical.
The exact definitions should always come from the applicable IPC document rather than from shorthand descriptions.
Class selection is not a marketing decision.
Choosing Class 3 simply because it sounds more rigorous can affect:
PCB design
Solder acceptance
Inspection effort
Documentation
Supplier capability
Rework decisions
Cost
Instead, the product class should reflect the actual application, contractual requirements, customer expectations, and risk.
Before release, the customer should answer several questions:
What environment will the product operate in?
Does the customer contract require a specific class?
Do drawings or regulatory requirements introduce stricter criteria?
Can the design and manufacturing process support the selected class?
Who has authority to approve exceptions?
A product class chosen after production has started is already too late.
IPC-A-610 cannot know the unique requirements of every electronic product.
Customer drawings may define details such as:
Connector orientation
Special polarity markings
Component substitutions
DNP variants
Label position
Conformal-coating keepouts
Hand-soldered wires
Mechanical hardware
Torque requirements
Firmware revision
Product-specific inspection points
For outsourced PCBA, the customer and supplier should agree on an order of precedence before the first build.
A practical hierarchy might be:
Purchase order and contract requirements
Approved customer drawings and specifications
Approved deviations or waivers
Specified IPC standard, revision, and class
Supplier work instructions
The exact hierarchy can vary.
What matters is that both parties know which document controls when two requirements appear to conflict.
Without that hierarchy, acceptance disputes tend to occur precisely when schedule pressure is highest.
These two documents are frequently mentioned together, but they serve different purposes.
IPC J-STD-001 addresses requirements for soldered electrical and electronic assemblies, including materials and manufacturing processes.
IPC-A-610 focuses more directly on the acceptability of the completed assembly.
A simple way to think about the difference is:
J-STD-001 → process and materials requirements for soldered assemblies
IPC-A-610 → acceptance criteria for the finished electronic assembly
IPC itself describes the two standards as closely related and released their J revisions together.
For outsourced production, many customers may need both.
Simply writing “IPC compliant” therefore leaves too much unanswered.
A supplier saying that it inspects to IPC-A-610 is only the beginning of the conversation.
The next question should be:
What evidence will be available?
Depending on the product, useful records may include:
First-article inspection records
AOI results
X-ray images
Inspector signoff
Rework records
Defect images
Approved deviations
Functional-test results
Customer sample approval
The amount of evidence should be proportional to the product risk.
A simple assembly with visible gull-wing solder joints may not need the same inspection package as a board containing:
Fine-pitch BGAs
QFNs
Large thermal pads
High-mass connectors
Hand-soldered wiring
Conformal coating
Safety-critical components
More inspection is not automatically better.
The inspection method has to answer a real quality question.
Automated Optical Inspection is particularly effective for visible assembly features.
Depending on the equipment and program, AOI can help identify:
Missing components
Position errors
Polarity errors
Certain visible solder bridges
Some solder-fillet defects
Component orientation problems
But standard AOI cannot directly inspect solder joints hidden beneath a BGA.
For BGA assemblies, IPC publishes IPC-7095, which addresses design and assembly-process considerations for BGA technologies.
Where hidden solder joints create meaningful risk, X-ray inspection may be appropriate.
The important point is that IPC-A-610 acceptance requirements and inspection technology are separate decisions.
A requirement may define what is acceptable, while the manufacturing team still has to determine how that feature can actually be inspected.
X-ray is valuable because it provides information that optical inspection cannot.
It can be useful for:
BGA solder balls
Hidden bridges
QFN / BTC thermal pads
Certain void structures
Internal solder distribution
Some THT conditions
But an X-ray image does not prove electrical functionality.
This is why a robust quality plan may combine several evidence layers:
AOI for visible workmanship
X-Ray for hidden structural features
ICT or Flying Probe for selected electrical properties
FCT for actual product behavior
No single inspection system answers every question.
NASA's Electronics Workmanship resources also illustrate why inspection methods should be selected according to the failure mechanism rather than treated as interchangeable quality checks.
A PCB assembly can look perfect and still fail electrically.
Examples include:
Wrong resistor value
Damaged IC
Incorrect firmware
Missing programming
Open internal PCB connection
Incorrect calibration
Failed communication interface
IPC-A-610 is not intended to define these product-level functional limits.
A proper outsourced PCBA package should separately define:
Test fixture
Test sequence
Power-up conditions
Input conditions
Measurement limits
Firmware state
Pass/fail criteria
Test-record requirements
If a buyer requires functional test but only writes “IPC-A-610 Class 2,” the functional requirement is still undefined.
Many PCB assembly projects eventually include wiring.
That may involve:
Wire-to-board connections
Crimped terminals
Cable assemblies
Harnesses
Hand-soldered wires
These activities are not simply extensions of ordinary PCB workmanship.
For cable and wire harness assembly, the industry commonly uses IPC/WHMA-A-620.
If a contract manufacturer is expected to provide both PCBA and harness assembly, the RFQ should separate the relevant requirements rather than assuming IPC-A-610 covers both.
When a defect is found, the next question is often whether the assembly can be reworked.
Rework and repair introduce their own process risks:
Additional thermal cycles
Pad damage
Component damage
Contamination
Trace repair
Mechanical stress
IPC publishes IPC-7711/7721 for rework, modification, and repair of electronic assemblies.
The customer should define:
Whether rework is permitted
Whether repair is permitted
Whether customer approval is required
Whether particular components may not be reworked
Whether follow-up inspection is required
Whether follow-up functional testing is required
This should be agreed before the first nonconformance occurs.
Otherwise, production personnel may be forced to make release decisions while a shipment is already waiting.
Conformal coating is another area where IPC-A-610 alone is insufficient.
Coating projects may require controls for:
Material type
Masking
Thickness
Cure
Coverage
Bubbles
Voids
Keepout areas
Adhesion
IPC publishes IPC-CC-830 for qualification and performance of electrical insulating compounds for printed wiring assemblies.
If conformal coating is part of the outsourced PCBA scope, coating requirements should appear explicitly in the manufacturing package.
The same principle applies to:
Potting
Encapsulation
Adhesives
Mechanical assembly
Programming
Calibration
Box build
Each process needs its own defined acceptance basis.
The first article is where several assumptions become physical reality.
It is an opportunity to verify:
BOM correctness
Component orientation
Assembly drawing accuracy
DNP configuration
Mechanical fit
Solder workmanship
Labeling
Programming
Test setup
Customer-specific requirements
A useful first-article package might include photographs, AOI results, X-ray evidence where relevant, deviation records, and functional-test results.
However, first-article approval does not replace production process control.
A technician can manually correct one prototype and make it look perfect.
That does not prove that the next 5,000 assemblies will be produced consistently.
The purpose of first-article review should therefore be both:
Is this assembly correct?
and
Can this process reproduce it?
IPC-A-610 should not be treated as a simple checkbox on a supplier questionnaire.
A more useful supplier discussion includes several practical questions.
The answer should be specific.
Training does not automatically guarantee product quality, but it helps establish a common inspection language.
A supplier assembling BGAs should be able to explain its X-ray capability or alternative verification strategy.
The answer should go beyond:
We repair it.
A stronger process explains how the defect is:
Identified
Contained
Reworked if permitted
Reinspected
Tested
Trended if recurring
Fed back into process improvement
For higher-value or regulated products, traceability may be as important as the inspection itself.
A mature supplier should be able to explain how drawings, BOM revisions, deviations, test specifications, and workmanship requirements flow into production.
The RFQ does not need to become a standards manual.
It simply needs to remove ambiguity.
At minimum, consider defining:
Acceptance standard: IPC-A-610 revision and class
Process standard: J-STD-001 revision/class if required
Drawing precedence: Which customer documents override general criteria
First article: Required records and approval process
AOI: Whether required and what records are expected
X-Ray: Packages or conditions requiring inspection
Rework: Permitted methods and approval authority
Electrical test: ICT, Flying Probe, or other requirements
Functional test: Procedure and pass/fail limits
Cable / harness: IPC/WHMA-A-620 if applicable
Coating: Material and inspection requirements
Traceability: Required lot, serial-number, and component records
Deviation handling: Who can approve use-as-is or alternative disposition
This helps both sides.
The buyer receives a clearly defined acceptance basis.
The assembler can identify additional cost, equipment, fixtures, documentation, and inspection requirements before quoting.
This does not identify the applicable standard, revision, or class.
Different revisions may contain different requirements and interpretations.
“IPC-A-610 workmanship” is incomplete without the applicable class.
The class should reflect actual product requirements and contractual risk, not marketing preference.
It does not.
Electrical and functional testing need separate documentation.
It cannot directly inspect hidden BGA solder joints or verify electrical operation.
Cable and harness requirements generally belong under IPC/WHMA-A-620.
Rework and repair need their own controlled procedures and approval path.
Qualified inspectors are important, but they cannot compensate for incomplete drawings, conflicting revisions, or undefined acceptance criteria.
Late quality requirements often become late cost increases.
The correct time to define them is before supplier selection and production release.
IPC-A-610 is extremely useful in outsourced PCB assembly because it creates a shared language for evaluating workmanship.
But it works only when the customer uses it precisely.
A robust RFQ should identify the revision, product class, customer-document priority, inspection evidence, and deviation process. Related requirements such as J-STD-001, IPC/WHMA-A-620, IPC-7711/7721, conformal coating, functional test, programming, and product-specific acceptance criteria should be defined separately where applicable.
The goal is not to fill a purchase order with as many standard numbers as possible.
The goal is to make sure engineering, sourcing, quality, the contract manufacturer, and the end customer are judging the same product against the same requirements.
That is where IPC-A-610 provides its greatest value: not as a substitute for a complete manufacturing specification, but as one well-defined part of it.
IPC-A-610 defines acceptance criteria for completed electronic assemblies and is widely used by inspectors, assemblers, engineers, and customers.
The current revision should always be verified through IPC's Document Revision Table.
No.
The RFQ still needs the BOM, placement data, drawings, revision control, approved component alternatives, test requirements, programming requirements, packaging instructions, and other product-specific criteria.
IPC currently lists IPC-A-610J, released in 2024.
Projects should nevertheless verify the current revision when releasing new documentation.
IPC-A-610 primarily addresses the acceptability of completed electronic assemblies.
J-STD-001 addresses requirements for soldered electrical and electronic assemblies, including materials and process-related requirements.
They are frequently used together.
No.
Functional testing requires its own test procedure, conditions, limits, firmware state, fixture requirements, and records.
Not as the primary cable-and-wire-harness acceptance standard.
For those assemblies, IPC/WHMA-A-620 is commonly used.
IPC-7711/7721 provides procedures and guidance for rework, modification, and repair of electronic assemblies.
The customer or design authority should determine the class based on product use, risk, contractual requirements, and customer expectations.
The contract manufacturer can provide manufacturing and inspection input, but the required acceptance level should not be left undefined.