Upload BOM & Gerber
-
Mobile: +86 13312967631
-
Email: sales@suga-pcba.com
PCB & PCBA Quality Inspection Services
How Inspection Evidence Moves from Plan to Release
SUGA helps OEM teams in quality control, sourcing, and project development plan PCB and PCB Assembly (PCBA) inspections according to the manufacturing stage, PCB and PCBA design complexity, and submitted project specifications. The inspection plan covers surface inspection, hidden-joint inspection, first article inspection, visual inspection, and complete document records without relying on a single method as the only check.
SUGA combines inspection methods to connect findings to closure within the agreed inspection criteria and prepare inspection documents before pricing questions become late-stage holds.
Available Gerber files, BOM information, design drawings, and inspection requirements can be reviewed during planning.
Inspection Coverage at Key Build Stages
- Paste
- Optical
- X-Ray
- First Article
- Visual
- Records
Build Quality Should Be Clear Before Testing Starts
A board can pass its testing phases even though the board still has a quality issue, such as solder, placement, polarity, or hidden-joint conditions that have not been addressed early enough.
Inspection helps verify that the quality of the build matches the approved project design, inspection class, and project requirements within the limits of the agreed inspection scope before electrical testing starts. During the review, the inspector checks the condition of the assembled board and factors related to submitted specifications and assembly risk areas.
Defects Become Costlier After They Move Downstream
Correction of defects typically becomes more complex as the build progresses through print inspection, placement, post-reflow inspection, final assembly, and shipment. If inspection identifies a paste print risk during print inspection, it can likely be resolved using process control before placement proceeds. If the same risk is identified after reflow inspection, the risk would most likely require the board to be reworked and re-inspected at the board level. Once the board reaches final assembly or shipment, the response grows to include lot control, containment, corrective action, or replacement planning.
The purpose is not to check all possible conditions, but rather to place the appropriate checks at the point in production where they can provide the earliest possible intervention to eliminate preventable failures.
Inspection planning should be done in accordance with the build sequence rather than the inspection method name.
Build Issues and Test Failures Are Not the Same
The inspection plan includes assembly and solder conditions like solder shape, positioning, polarity, physical damage, marking accuracy, first article consistency, solder under packages, and record alignment.
Functional testing checks electrical or functional performance against the predetermined submission requirements.
When an observable assembly issue such as a solder concern, missing part, or shifted component is identified, it should be documented in the inspection plan. If those same observable assembly issues are only found through functional testing, it creates the possibility of ambiguity between circuit performance and build quality.
One common mistake is treating solder appearance issues as functional testing issues. Another is assuming that if a functional test fails, it indicates a design issue when in reality it was a result of placement, polarity, or solder condition.
Solder problems that exist under a package would create ambiguity if the inspection method was not specified earlier in production and there was no substantial evidence available to identify the solder condition.
Put the Right Check at the Right Build Stage
When considering inspections on PCBs, the useful question is not just which inspection method is available, but where in the build sequence it will occur and what conditions it can identify.
Paste condition, placement accuracy, surface solder shape, hidden solder areas, and first panel acceptance are all unique inspection points.
Sensitivity and coverage of the measurement device will be considered during inspection planning. The inspection on the completed assembly is determined by the selection of inspection equipment, complexity of PCBs, submitted files, and class of inspection.
When layout and packages are reviewed by SUGA, the project input documents will be used to review at least each of the following: visible checks, hidden-joint review, and requirements for first-run confirmation and release records.
Build-Stage Inspection Planning
| Inspection Point | Build Stage | Review Question | Review Result | Coverage Limit |
|---|---|---|---|---|
| Print Review | Before placement | Is the print condition stable enough to continue? | Hold, adjust process, or proceed | Paste-level print condition depends on the selected SPI setup. |
| Surface Review | After placement or reflow | Are the accessible components, solder, polarity, and markings acceptable? | Accept, verify flag, or rework decision | Surface coverage depends on AOI and visual access. |
| Hidden-Joint Review | After reflow | Are all non-visible solder joints specified in the plan? | Evidence of non-visible solder areas | Subsurface evidence depends on X-Ray inspection coverage. |
| First Article Review | First production run or revision change | Does the first article match the drawing, BOM revision, and required supporting documentation? | First-run confirmation or open discrepancy record | The depth of review is based on FAI requirements. |
| Final Record Review | Before release | Are open findings, rework, deviations, and reports closed? | Basis for release or unresolved hold | Record package depends on project requirements. |
The result of each checkpoint provides answers to what corrective actions can still be taken at that stage of production, what evidence can be created, and what decision is needed at that point before proceeding. Method-specific details are covered under SPI, AOI, X-Ray, FAI, and Visual Inspection.
Classify Findings Before They Drive Rework
Inspection can distinguish between process signals, acceptable conditions, and findings that require closure. A finding is acceptable or unacceptable based on the relevant criteria rather than the process alone. The severity of a finding will affect the type of response required as well as its classification.
Finding Severity and Review Basis
An inspection review typically uses four levels to classify findings: 1) Process indicators do not affect acceptance but may indicate future trends and may be monitored for trend purposes. 2) Minor findings meet the acceptance criteria but are worth recording. 3) Major findings require rework, deviation review, or approval before the unit can continue. 4) Critical findings are unacceptable, and the unit may need to be reworked or scrapped.
For solder and fillet conditions, the same physical configuration can create a different level of response based on the relevant class or project requirement. An inspector may accept the same condition under a Class 2 basis, while another inspector may hold that condition under Class 3 expectations. By determining the class and project requirement before inspection, a final decision regarding acceptance can be established, limiting the potential for disputes.
Inspection Decision Inputs by Risk Type
| Risk Type | Decision Basis | Needed Input | If Unclear | Better Handled In |
|---|---|---|---|---|
| Solder Condition | IPC-A-610 and project requirements based on the agreed-upon class; bridging rules when relevant | package pitch, pad geometry, soldering process notes, class, or project criteria | each solder shape may be acceptable based on one set of criteria while unacceptable based on another, which can lead to late rework or approval questions | AOI or Visual Inspection |
| Placement & Polarity | drawings, placement data, BOM status, revision, orientation marks, and acceptance criteria | footprint, centroid or placement data, MPN status, polarity marking, and revision status | improperly placed components may cause a test failure and make it difficult to determine the root cause of the issue | 3D AOI or Visual Inspection |
| Bare-Board / Panel Condition | IPC-A-600, relevant project-specific notes, PCB class, material stackup, and project criteria | PCB material, stackup, copper balance, warp or bow requirement, and handling limits | material or surface issues may shift into lot containment or incoming material follow-up | PCB quality or visual review |
| Contamination & Cleanliness | project-defined cleanliness limit, visible residue rule, or test method if required | flux chemistry, cleaning method, critical areas, residue limit, or ionic test requirement | when methods and limits are not provided, inspections may be delayed or remain open before release | Visual Inspection or cleanliness-specific review |
| Hidden Solder Area | marked BGA, bottom-terminated component, shielded or covered solder locations, and evidence requirement | package map, marked locations, sample quantity, image format, and acceptance basis | adding review later can reopen the inspection plan, report scope, and quote basis | X-Ray Inspection |
| First-Build / Revision Confirmation | FAI context, controlled release criteria, or revision approval requirement | drawings, BOM, revision, characteristic list, and required record format | the initial build may lack structured evidence for approval or release | First Article Inspection |
Placement and Polarity Errors
Placement defect patterns often appear due to the accumulated effect from the process, equipment, material used, or a combination of these factors. Placement defects from incorrect assembly data or setup can often be present throughout an entire batch.
When errors are noted during the placement process, placement issues should be identified as soon as possible. Identifying placement or polarity issues before beginning subsequent checks on the assembly allows the inspection team to better separate component processing issues from errors noted during inspection.
To maintain records that indicate where defects occurred and which assembly data was used to review components, the inspection record should note whether the condition appears repeatedly across multiple boards at the same position. In such cases, the condition is likely related to the process or input data rather than chance, and corrective action should take place at the process level rather than by board-level rework.
When One Method Is Not Enough
When evaluating the full range of a PCB or PCBA project's quality, typically no one method will adequately demonstrate the complete quality. The various methods answer different questions: what is visible, what remains covered, and how the outcome will be decided. Relying on a single methodology risks insufficient or inconclusive data due to its limitations, so one method may cover a specific risk area while leaving another open.
Single-Method Review Leaves Blind Spots
Single-method reviews may leave gaps in quality coverage. Surface inspection will cover accessible placements, polarity, markings, and visible solder conditions. The inspector may need additional reviews to obtain data on hidden joints, areas that remain covered, or cosmetic items subject to aesthetic judgment.
Combined Methods Need Clear Review Criteria
While combining inspection methods does not automatically eliminate every gap, the combination of inspection methods is valuable when clear review criteria define which inspection results require an additional review, what supporting evidence is transferred between methods, and how the combined result supports the disposition decision. Without clear criteria, inspectors may repeat effort on low-risk areas while leaving high-risk areas unresolved.
When Additional Review Is Needed
When additional review conditions include BGA, bottom-terminated packages, concealed solder areas, shielding, or another condition that may need X-Ray review, define which marked areas require X-Ray review and what images are needed.
When FAI records will be prepared due to a first build, revision change, or controlled release, establish what format will be followed for the preparation of those records. If the project contains cosmetic items, labeling, or markings that are visible to the inspector, the identification of those areas along with criteria for visual acceptance should be established before planning for product release. Where appropriate, AOI or surface inspection may serve as the baseline layer of a PCB assembly inspection. Each layer should follow its own review method and result criteria.
From Machine Flag to Quality Decision
A machine flag does not necessarily indicate a final defect. An inspection flag means further validation or assessment is needed, or that process adjustment, rework, or approval may be required before proceeding or release.
There are typically three types of flags: false calls, borderline findings, and confirmed defects. Properly categorizing these different types of flags will minimize unnecessary rework and ensure that unresolved quality issues do not pass to the next step of the manufacturing process.
For borderline findings, the flag should remain open until the acceptance basis, rework option, deviation review, or approval requirement is confirmed.
Pre-Reflow Flags: Process Adjustment or Hold
The resolution approach for an inspection flag raised before reflow will differ from one that is raised after reflow. At that stage, the options for correcting the issue will likely include process adjustment, tool cleaning, support adjustment, or holding the product before the next processing step. The product is not yet locked into the manufacturing process, so the decision to continue processing can be based on whether the current process appears capable of producing an acceptable result.
The framework for determining how to proceed for inspection flags raised before reflow is: 1. Product is acceptable within tolerances; 2. Process can be adjusted before continuing; or 3. The product or process should not continue until further adjustment has been made. If a pattern emerges across consecutive units at the same position, then the approach will transition from board-specific evaluation to process-specific correction.
Post-Reflow Flags: Verification, Classification, and Closure
Post-reflow flags should be verified before they become defect decisions. They can fall within three classification categories: false calls are flags from the system that were determined by manual review to be acceptable; borderline findings have a condition on or very near the acceptance threshold; and confirmed defects are findings that clearly fail to meet the acceptance standard.
Each of these classifications produces a unique closure action; recurring false calls may require program changes to reduce future occurrences, borderline findings require review against the acceptance standard, and confirmed defects require rework or deviation processing. The condition remains open until it is accepted or a deviation is approved.
The final determination of a finding is based on the acceptance criteria that were in place at the time the finding was made, not solely on the detection of the condition by the machine.
Final Review Closes Open Inspection Points
Open inspection items relating to an assembly should either be resolved or have a fully documented quality decision before shipping the finished assembly. The final review process for an assembly may include FAI records, inspection reports, accepted deviations, verification of rework, final alignment to the approved inspection requirements, and any other required documentation.
Release for delivery requires completion of the confirmed project records, the requirements specified in the inspection documents, and any other documentation needed to support release.
Inspection Flag Closure Actions
| Flag Category | Typical Trigger | Closure Action | Required Information | Closure Requirement |
|---|---|---|---|---|
| False Call | The system flagged a condition that manual review confirmed as acceptable | Verify, confirm acceptable, adjust program if recurring | Acceptance criteria, reference images, program settings | Verification record and program update if needed |
| Borderline Finding | Condition is near the acceptance limit, or project-specific criteria are needed | Compare against the acceptance standard, request approval input if necessary | IPC class, drawings, deviation procedure | Confirmation or deviation approval |
| Confirmed Defect – Reworkable | Condition is outside the acceptance standard and rework is possible | Rework, re-inspect, record | Rework instruction and re-inspection criteria | Rework verification passed; record closed |
| Confirmed Defect – Non-reworkable | Condition is outside the acceptance standard and repair is not possible or not allowed | Scrap review or deviation request | Scrap or deviation procedure and authorization | Scrap record or deviation approval |
The final inspection report for an assembly should document that all open flags have had a closure action recorded, all rework has been verified, deviation requests have been approved or withdrawn, FAI records have been completed if applicable, and the final report aligns with the approved inspection plan.
Keep Quality Decisions Repeatable
For inspections to be repeatable, the solder, placement, or cosmetic condition should be judged consistently regardless of operator, shift, equipment, or production lot. For example, if one inspector classifies the same condition as acceptable while a second inspector holds it for further review, the lack of consistency creates unnecessary rework or undetected risk.
Some of the variables that control consistency in this area include clarity of inspection criteria, alignment of inspector training, calibration of inspection equipment, and traceability of inspection records. All of these variables can support repeatable inspection when quality record documentation is necessary.
To evaluate how well an inspection setup can consistently and reliably identify acceptable versus defective conditions, measurement system analysis (MSA) is used. In addition, gauge repeatability and reproducibility (GR&R) is used to evaluate whether the same inspector obtains the same result on two different occasions and whether different inspectors agree on their classification of the same inspection item. Manufacturing execution system (MES) records provide a means to link inspection results to the specific panel, lot, or serial number in production. Corrective and preventive action (CAPA) is used to investigate and help prevent recurrence of documented defect patterns that require formal follow-up.
Measurement Assurance and Feedback Controls
| Inspection Item | Acceptance Basis | Check Method | Required Project Input | Review Value |
|---|---|---|---|---|
| Operator GR&R | GR&R study or operator qualification record when required; IPC-A-610 training records where applicable | Scheduled MSA; trainer or supervisor review | lighting, standard checklist, sample set, and acceptance criteria | supports false-call control and rework decision consistency |
| Defect Coding and Feedback | Defined defect codes; MES or DfM feedback loop if in place | Digital upload; Pareto review where used | code-to-Gerber or assembly-data review when needed | supports closed-loop yield review where defect data is available |
| Equipment Calibration | AOI, SPI, and X-Ray calibrated per equipment OEM schedule; calibration records maintained per project requirements | Calibration log; scheduled audit | equipment selection per board complexity | supports measurement drift monitoring |
| Escape Tracking & CAPA | Reported escapes recorded according to the required response window | MES escape log; periodic review | alert threshold per agreement | supports closed-loop improvement tracking |
Shared Criteria Improve Repeatability
Sharing common judging criteria among multiple inspectors improves repeatability and enables the inspector to assess findings against project input documents or project-defined criteria. The way inspectors share the same common criteria will be different based on project risk; this may be done by providing a written workmanship standard, reference images for borderline accept/reject conditions, a physical reference sample, or a digital criteria library accessed by the inspector.
Additionally, documentation depth changes with board risk, release expectations, and future release evidence. A low-risk surface inspection and an audit package documentation set will not require the same level of records.
Calibration Records Help Stabilize Review
To maintain the stability of inspection tools such as AOI, SPI, X-Ray, microscopes, and gauges, calibration records should be maintained. Maintaining calibration logs, equipment schedules, and measurement checks provides ongoing monitoring of inspection drift. These records also serve as audit or delivery evidence when needed.
The required records confirm which documents support inspection and audit. Calibration records are often requested during supplier qualification or audit review, so maintaining the documentation standard helps avoid late gaps in documentation requirements.
Defect Coding Turns Findings into Follow-Up
The defect coding system converts findings into engineering feedback for follow-up. Examples include repeated solder bridges, polarity issues, offset trends, or covered-joint findings, which can be combined into one documented list of findings supporting engineering follow-up action.
Using digital links established between MES, Pareto reviews, escape tracking, or CAPA records provides direct connections between inspection findings and future investigation. Each individual inspection flag is a data point, but the same code seen on the same reference designator across multiple boards becomes a pattern. That pattern points to a process input, not a random event.
Acceptance Starts with the Project Files
An acceptance basis needs to exist before making inspection decisions; otherwise, a finding may cause release delay, rework dispute, or approval questions after assembly completion.
Generally, the basis for acceptance will be established within drawings, assembly notes, BOM status, required revisions, inspection class, and project criteria. IPC references can be used to help make an acceptance determination, but they should not replace the project files or project criteria stated in the purchase order.
Drawings and Assembly Notes Set the Baseline
Supplied drawings and assembly notes define what the assembly should match. These include component orientation, polarity, mechanical limits, labeling, areas that require coating, and required inspections.
When inputs for the inspection decision are not available or are not clear, the classification of findings becomes more complicated. Missing or unclear information could include assembly drawings lacking polarity or orientation markings, BOMs without manufacturer part numbers, outdated revision status, and purchase orders without a confirmed inspection class. These gaps will push the decision away from inspection review and toward clarification or dispute resolution.
IPC Standards Support the Decision
IPC-A-610, IPC-A-600, and IPC-7095 support different parts of the printed circuit board quality review process. IPC-A-610 covers assembled boards, including solder, placement, marking, cleanliness, and board condition according to product class. IPC-A-600 covers bare PCB quality, including layer alignment, plating, surface condition, and dimensional accuracy.
IPC-7095 covers BGA inspection and process considerations. The acceptance basis still needs to be derived from the order requirements, from IPC-A-610 when relevant, and from specified criteria.
Class and Project Requirements Shape the Final Call
Acceptance decisions related to workmanship and reliability can be affected by Class 2 and Class 3 designation, especially for specified inspection items and soldered connections. Cosmetic criteria should still follow either the project files or the project-specific criteria.
AS9102 and PPAP are separate project contexts. When AS9102 is specified, it requires a first article report, including balloon drawings, characteristic accountability, design records, and process traceability. PPAP focuses on production part approval evidence and process documentation, but follows a separate review and approval process.
Signals That Need Earlier Inspection Planning
When inspection details are necessary before producing a quote or planning production for PCBs and PCBAs, the layout complexity, package type, visual inspection limits, solder-joint inspection risks, and required documentation level should be considered.
Defining how to perform the inspection will allow separation of areas that will be routinely inspected from areas that require additional inspection, as well as clarification of what level of documentation will be needed before release approval.
Board Complexity Signals
Certain board characteristics may expand the inspection plan from standard checks to include hidden-joint, dimensional, or evidence-intensive methods. Signals that commonly trigger earlier planning include the following:
- Area-array or bottom-terminated packages where it is not possible to see the joint condition on the surface
- Fine-pitch components that have very little tolerance for placement or solder
- RF shielding or mechanical covers that obstruct access after assembly has taken place
- High-density layouts that do not permit optical or manual access due to close component proximity
- Mixed-technology boards that utilize through-hole, surface-mount, or press-fit features in combination
When any of the above signals are present, SUGA performs an evaluation of the layout and package map and confirms which areas need extended inspection. If there are areas where hidden-joint evidence is expected, the critical areas should be identified during quote review rather than added after production starts.
When using BGAs or bottom-terminated packages, early identification of X-Ray locations will assist in verifying sample size, coverage, image evidence, and quote assumptions before production release. If the additional request happens after assembly is already underway, the production plan may need to be reopened to confirm part locations, acceptance criteria, image formats, and whether the production stage can accommodate the extra review.
Record and Evidence Expectations
Inspection planning can be changed by requirements for evidence of inspection coverage regardless of the inspection method. Some projects require a simple pass/fail summary, while others require retained images, X-Ray evidence for specific package locations, FAI documentation based on AS9102 or PPAP requirements, defect classification reports, and lot or serial number traceability.
Changes to evidence requirements affect review time, report preparation, and data handling. When documentation requirements and expectations are confirmed at the time of quote, routine output can be separated from specific project-based outputs.
Review Effort, Records, and Finding Closure Shape the Quote
For inspection quotes, inspection fees are not based solely on the method name. For example, the same request for AOI or X-Ray inspection could require very different effort depending on how many hidden solder joints exist, what the placement density looks like, the sampling level definition, report depth, and the type of records required.
The factors below clarify covered areas and the quote basis.
Quotation Factors and Inspection Impact
| Factor | What It Clarifies | Inspection / Quote Impact |
|---|---|---|
| Layout Complexity | Layout density, layer structure, and inspection area mapping | Confirms inspection points and method planning |
| Component Package Profile | Package type, MPN status, and critical components | Identifies component-level review needs |
| Assembly Details | Polarity, orientation, dimensions, labels, and FAI items | Supports acceptance review and report preparation |
| Inspection Class | Class 2 / Class 3 expectations and borderline criteria | Affects review strictness and closure requirements |
| Hidden-Joint Areas | BGA, bottom-terminated, or covered solder locations | Confirms X-Ray workload and image evidence |
| Record Need | Pass/fail summary, images, FAI, deviation, traceability records | Affects documentation preparation to support release |
| Sampling | 100%, lot sample, specified panels, or critical-location review | Affects inspection quantity and per-lot review time |
If a factor is unavailable during quote review, SUGA can list it for clarification and note how it may affect the final inspection plan.
Review Depth Changes the Workload
The review depth for validating and documenting results could take longer for a BGA or very fine-pitch component than for a manually placed part, first article checks, or deeper image reviews. Cycle times to validate and document results may be extended based on the factors mentioned above.
During quote review, it is useful to clarify reviewed locations, acceptance standard, release evidence requirements, and all required documentation.
Records and Finding Closure Affect the Quote
New preparation of records such as FAI documentation, X-Ray images, defect summaries, rework verification, traceability support, or issue-containment notes increases the preparation work before release.
Missing Inputs Delay the Quote
Inspection quotes usually need clarification because of missing inputs, such as misidentified revisions, unclear critical components or locations, unidentified hidden zones, and undefined report requirements.
Business-day submissions can receive a SUGA response within 12 hours when enough information is available for review.
Upload BOM & Gerber
FAQ
PCB inspection is the process of checking the quality of PCB or PCBA manufacturing. It ensures that the bare PCB or assembled PCBA meets the submitted design and project criteria and that suitable records support the project's specified scope. PCB inspection serves as a basis for testing and shipping PCBAs by identifying concerns related to soldering, component placement, component polarity, PCB assembly marking, first-run acceptance, and hidden-area conditions before release.
The PCB checklist should include revision, BOM match, component orientation, component polarity, solder condition, critical component packages, visual inspection items, inspection class based on IPC-A-610, open PCB inspection results, rework verification, and records. The PCB inspection checklist should define the project scope and should not rely on a universal template.
PCB inspection planning is beneficial if the PCB contains BGA packages or bottom-terminated component technology, fine-pitch components with limited visual access, first-run approval needs, special records, or specific acceptance criteria. Information about the PCB inspection will impact the review time, required evidence, and quote assumptions.
Typically, one of the main reasons for needing X-Ray review is that BGA, bottom-terminated components, shielding, and other solder areas may not be visible. PCBAs may require X-Ray review when a project requires documentation support for hidden solder joints. SUGA can review the package map and marked critical areas to determine which locations need X-Ray review or evidence documentation.
A standard inspection report documents required checks and findings for release from inspection. FAI verifies the first or new build by comparing it against drawings, BOM, dimensions, polarity, revision status, and required record format.
Yes. A preliminary inspection review can be performed based on available layout and package data. Final determination is based on pending information such as revision status, inspection class, and critical areas before completing the review.
Class 2 and Class 3 classifications can affect workmanship and reliability acceptance decisions, particularly for soldered connections and specified inspection items. Classifications should be confirmed before inspection to prevent late decision-making on borderline conditions.
Typical inspection reports include inspected items, findings, closure status, images required for rework verification, deviations from the standard, and release records. The extent of the report follows the required coverage and evidence requirements.
Related Services
For method-specific inspection requirements, the following related services support established build and release requirements.