Assembly Workmanship & IPC Reference
Turn “IPC required” into a usable acceptance brief: identify the document, edition, product class, applicable addenda and the evidence the order requires.
- Requirements
Which documents and revisions apply?
- Evaluation
Which features and methods are covered?
- Disposition
Who approves deviations and rework?
Process requirements and acceptance criteria have different jobs.
IPC J-STD-001 addresses requirements for soldered electrical and electronic assemblies. IPC-A-610 addresses acceptability of electronic assemblies. IPC describes these as complementary documents; neither should be used as a vague substitute for the full project specification.
Specify the IPC documents, editions, product class and acceptance criteria required for your assembly. Use the applicable licensed standards when agreeing workmanship requirements for your order.
- Document revision
- The edition incorporated into the order; “IPC” alone is incomplete.
- Product class
- The performance/acceptance category selected for the product requirements.
- Addendum
- Additional requirements that must be compatible with the specified base document.
What to resolve before release
Use these review prompts with the actual design, component documentation and agreed manufacturing process.
Name the governing documents
Record full document identifiers, revisions and any applicable addenda. Resolve the precedence of drawings, purchase-order notes and standards in the quality agreement rather than leaving contradictory instructions for inspection.
Select the class deliberately
IPC distinguishes general electronic products, dedicated-service products and high-performance/harsh-environment products through its product classes. The customer should specify the required class from the product’s needs; a market label alone is not a complete acceptance instruction.
Keep addenda compatible
Do not mix a new addendum with an unrelated older base edition by assumption. Verify document compatibility and the required contractual combination in the official register and licensed documents.
Evaluate features with the right method
Consider package geometry and visibility when specifying visual, optical, X-ray and electrical evaluation. Do not infer a hidden joint’s complete condition from a top-side photograph or treat a functional pass as a universal workmanship approval.
Control rework and repair decisions
Record the defect, authorized action and subsequent evaluation. Replacing a dense package can introduce new thermal and mechanical exposure, so define the process and verification before intervention.
Separate credentials from product evidence
A training certificate, a company capability statement and an assembly inspection result answer different questions. Request the evidence relevant to the actual order instead of treating a logo or an unsupported phrase as proof of conformity.
Which reference serves which purpose?
Public document roles are summarized here. The official register reviewed on 28 September 2026 lists revision J for the two core assembly standards below. Your contract may specify a different edition.
On a small screen, scroll the table horizontally to see every column.
| Reference | Role in the review | What to specify |
|---|---|---|
| IPC J-STD-001 — revision J listed | Requirements for soldered electrical and electronic assemblies. | Agreed edition, class and compatible addenda; applicable process requirements. |
| IPC-A-610 — revision J listed | Acceptability of electronic assemblies. | Agreed edition, class, evaluation scope and required inspection records. |
| IPC-7352 | Generic guidance for land-pattern design. | Applicability to the device and design; do not replace the actual package guidance. |
| IPC-7525 | Stencil-design guidance. | The edition used and the process-specific stencil decisions. |
| IPC-7530 | Temperature-profiling guidance for soldering processes. | The applicable process and validated assembly-specific profile. |
| IPC-7711/7721 | Rework, modification and repair guidance for electronic assemblies. | Authorized procedure, operator/process requirements and verification. |
Keep the approved project requirements in control. Record uncertainties, agreed exceptions and the supporting evidence before the affected operation is released.
Avoid “IPC compliant” without a defined scope.
A meaningful acceptance brief ties the required criteria to a specific assembly revision and inspection plan. Identify the features to inspect, evaluation method, sampling or inspection extent, traceability and disposition authority. Do not invent numeric acceptance limits from generic web illustrations.
- Hidden and package-specific features
- Use the applicable criteria and package guidance, not a blanket voiding percentage or universal fillet rule.
- Evidence and exceptions
- Retain the required reports and approved departures from the original requirement.
- Future revisions
- Check the official register again before a new order; do not silently change an existing contract’s edition.
Move from open questions to controlled decisions.
These steps organize a project review. They do not replace your formal release or acceptance process.
Specify
Name the documents, editions and product class.
Align
Agree methods, scope and records before the build.
Evaluate
Inspect against the authorized requirements.
Disposition
Resolve nonconformities and retain evidence.
Record the review.
Keep the evidence.
12 checks for this topic. Record status and notes, then export a text copy for your project discussion. A completed checklist is not certification or production approval.
Session only. Nothing is saved automatically or transmitted. Export before closing or reloading. “Reviewed” records evaluation—not a pass verdict. Explain blocked and not-applicable items in the notes.
Showing 12 of 12 checks. Export always includes all checks.
Governing standards and revisions are written in the order.
Avoid a standalone “IPC required” note.
Product class is explicitly selected.
Record the customer’s requirement.
Addenda are compatible with the base editions.
Verify the exact contractual combination.
Drawing and specification conflicts are resolved.
Document precedence and approvals.
Inspection methods suit the actual package features.
Address hidden and inaccessible joints.
Inspection extent and sampling are agreed.
Do not assume an inspection percentage from the standard name.
Electrical and functional tests have separate scope.
Define limits and known coverage gaps.
Acceptance criteria come from the governing documents.
Do not copy unverified numeric limits from a generic article.
Required inspection and test records are specified.
Link reports to the assembly and relevant revisions.
Rework and repair require authorized procedures.
Define post-action inspection and test.
Deviations have a recorded approval and disposition.
Retain traceability to the affected items.
Any requested credentials are verified independently.
Do not confuse training status with product conformity.
No checks match these filters. Change a filter to view other items.
Export your checklist and resolve outstanding items with your engineering team before production. Confirm any changes through your normal approval process.
Practical answers
before release.
Use these answers to frame the discussion. The approved project requirements remain the authority for the build.
What is the difference between J-STD-001 and IPC-A-610?
They have complementary roles: J-STD-001 addresses soldering requirements, while IPC-A-610 addresses assembly acceptability. The required combination and editions should be stated in the project documentation.
Should every high-reliability project automatically say Class 3?
The responsible customer/design authority should specify the applicable requirements and product class. Class selection is not a substitute for qualification, environmental requirements, component selection or the product test plan.
Does this page reproduce IPC acceptance criteria?
No. It provides public orientation and a preparation checklist. Detailed criteria, exceptions and illustrations must be obtained from the applicable licensed documents; they are not reproduced here.
Can a single voiding limit be used for every package?
Do not assume so. Identify the package, measurement method and governing component or contractual criteria. This page intentionally avoids presenting one percentage as a universal acceptance limit.
Does naming IPC on a website prove certification?
No. Verify the specific credential, its holder, scope and validity when it is required. Product conformity must be evaluated against the actual order and its required evidence, not inferred from general website wording.
Technical references & scope
- IPC Standards — official revision register
Document names, revision history and addendum compatibility; checked 28 September 2026.
- IPC — J revisions of the two assembly standards
Public explanation of the different roles of J-STD-001 and IPC-A-610.
- Keysight — Requirement for Successful Boundary Scan Test Development on i1000D In-Circuit Test System (PDF)
Complementary physical and boundary-scan test access.
- Analog Devices — AN-1448, PBGA rework
Rework planning, thermal characterization and post-rework verification.
- Analog Devices — QFN PCB design and SMT assembly guidance
Package-specific discussion of pads, paste, thermal lands and inspection; not a universal process recipe.
Use these engineering references alongside your component documentation and the standards specified for your order. Share your completed checklist with us to confirm assembly, testing and material requirements.