勛圖tv

Quality Assurance / Quality planning

勛圖tv 繚 Inspection and test planning

PCB final quality inspection: make the release decision traceable

Reconcile the finished product, sample observations, required records and shipment. Keep unresolved evidence visible before an authorized release.

Share your current requirements and open questions. Tool use is optional.

Quality inspection workstation
Quality inspection workstation. Published 勛圖tv process photograph; the image does not establish the scope or result of your order.

What is FQC for a PCB order?

FQC means final quality control: the review of the finished product and its supporting evidence before the agreed release point. For a PCB order, it connects final inspection, completed test records, quantity, identity, approved dispositions and packaging requirements. A meaningful release identifies exactly what is being accepted and the requirements used to make that decision.

The term is sometimes used alongside outgoing quality control, or OQC. Companies may assign these names to different steps. Define the responsibility and the release point in the project agreement instead of relying on the abbreviation alone. This page covers the final review and handover; earlier manufacturing controls belong in PCB quality control or PCBA quality control.

FQC is not a replacement for controls that should have happened during production. A final visual check cannot recover a missing internal-layer observation or create a functional-test result. Its value is to ensure that required evidence is present, findings have an authorized disposition and the actual shipment matches the approved product and quantity.

Final release brings the evidence and the shipment together
FQC reconciles the finished product, required evidence, exceptions and physical handover. A checklist is not release authorization.

Separate bare-board and assembled-board release

Start by identifying the object being released. A bare board has fabrication, dimensional, connectivity and finish requirements. A populated assembly adds component identity, soldering, programming and any specified functional requirements. The final reviewer should not use the same generic checklist without considering those differences.

Release subjectBare PCB examplePCBA example
Product identityFabrication part number and revisionAssembly part number, BOM variant and firmware
Physical conditionOutline, holes, mask, finish and handling damageWorkmanship, connectors, labels and handling condition
Test statusRequired netlist and special-characteristic evidenceRequired inspection, ICT/FCT or other agreed records
Exception handlingApproved fabrication deviationApproved assembly deviation, rework and retest
HandoverLot, quantities, requested reports and packingSerial/lot relationships, reports and protective packing

Check the order acceptance checklist before ordering if these requirements are not yet agreed. That resource defines the acceptance agreement; FQC applies the agreement to the actual finished lot. Keeping those tasks separate avoids changing the rules only after inspection finds a problem.

Review finished condition against the right reference

Use the released drawing and the required acceptance documents, with revisions visible to the inspector. Identify the datums and inspection methods for dimensions. For an assembly, use the intended variant and applicable workmanship criteria. A familiar-looking product is not sufficient evidence that the correct revision is in the shipment.

Final review may include condition, labeling, quantity and the characteristics specified for that stage. It should also reconcile the status of checks performed elsewhere. A missing report is different from a failing measurement, but both can leave the release unresolved. Record which situation exists rather than using an undifferentiated ���not OK��� note.

The helps identify the correct document family and edition. Product-specific limits, class and customer requirements must be part of the agreed acceptance basis. This page supplies a planning framework, not substitute acceptance criteria or a universal IPC sampling table.

Sampling supports a defined lot decision

If sampling is agreed, define the lot, sample selection, characteristics, defect classification and decision rule before inspecting the sample. A small convenient handful from the top of a box may not represent the lot. Separate inspections may require different populations or methods, especially where a check is destructive or a feature has special significance.

The explains sampling as a basis for a lot decision. It should not be mistaken for a precise estimate of the quality of every unit. AQL is not permission to knowingly ship a stated percentage of defective boards, and an accepted sample does not prove that no defects exist outside it.

A sample result is only one part of the release decision
Illustrative user-entered single-sample rule, not a recommended sampling plan. Satisfying the count rule cannot resolve missing records or open product issues.

Use the applicable, agreed sampling procedure to choose the sample size and decision numbers. The tool below does not derive a plan from an AQL value and does not reproduce a standards table. It only compares your observations with a simple single-sample rule that you enter, then keeps the other release obligations visible.

Review an agreed sample rule and the release evidence

Enter the lot size, inspected quantity and number of nonconforming units. Count each inspected unit once, even if it has several findings; this tool models a nonconforming-unit count, not a count of defects per opportunity. For a sample plan, enter the approved acceptance number and identify the plan reference. For full inspection, the tool uses a zero-nonconforming candidate condition and still requires disposition review.

勛圖tv ENGINEERING

FQC Count Rule and Release Evidence

Quality Planning
Loading FQC Count Rule and Release Evidence…
Using this tool & sharing results

Use the stated units, input limits and model assumptions. Results support an engineering discussion; they do not approve a design, process or production order.

After changing inputs, update the result before using it. Where a download or copy action is available, review that brief and attach or paste it into your enquiry. Opening Contact does not transfer these inputs or send a request.

How to use and share tool results

The result says whether the recorded count is within the entered rule. It does not authorize shipment. Required documents, unresolved nonconformities, traceability and packaging are reviewed separately. If any are open or not reviewed, the brief preserves those items and identifies the need for the authorized reviewer to decide what happens next.

Example: a sample is within its rule, but the lot is held

Consider an illustrative lot of 500 boards with an independently approved plan to inspect 50 and accept no nonconforming units for the characteristic in question. The observed count is zero. Numerically, that sample satisfies the entered rule. This is arithmetic using a stated plan, not a recommendation that those numbers are appropriate for a real order.

Now suppose the shipment requires a test report that has not been reconciled to the lot. The sample observation does not resolve the missing evidence. The release remains open until the required record is found, reviewed or addressed through an authorized disposition. The useful output is two separate statements: sample result within rule; required evidence unresolved.

If one nonconforming unit had been observed, the sample would exceed the entered acceptance number. Do not remove that unit, take another convenient sample and erase the original result. Apply the agreed reaction procedure, contain the affected product and record any sorting, reinspection or other authorized action with its relationship to the original lot.

Assemble a release package that can be checked

The requested package should be proportionate to the product and agreement. It might include a conformity statement, inspection results, specified electrical or functional records, traceability references, approved deviations and packing information. Agree the required format and retrieval method before shipment, particularly when customers need machine-readable serial-level records.

RecordQuestion it should answerCommon ambiguity to resolve
Product and revisionWhich released build is represented?Board revision and assembly revision are mixed
Lot/serial rangeWhich units are covered?Report identifies an order but not the shipped split lot
Inspection/test referenceWhat was checked and against which limits?A pass label has no program or specification revision
DispositionWhat happened to failures or deviations?Retest pass replaces the original failure history
Quantity reconciliationWhat is accepted, held, rejected and shipped?Packed count differs from the authorized release
AuthorizationWho approved this specific release?A preliminary review is mistaken for final approval
The release record must agree with the physical quantities
Example quantity reconciliation. The counts do not establish approval; held and rejected units remain controlled outside the shipment.

The traceability guide helps define record relationships and retention. A customer requesting lot evidence should not receive an unrelated demonstration report. Clearly mark sample report formats as examples and provide actual shipment evidence through the agreed project channel.

Functional test workstation
Functional test workstation. Published 勛圖tv process photograph; the image does not establish the scope or result of your order.

Make packaging part of the handover

Packaging protects the accepted condition during storage and transport. Define protection appropriate to the product, including mechanical support, separation, identification and applicable moisture or electrostatic handling needs. Avoid a universal instruction that every board must be baked, vacuum packed or treated identically regardless of construction and assembly state.

For moisture-sensitive assembled devices, verify the relevant component and process instructions. The provides a starting point for device-specific handling data. A bare PCB���s storage and solderability requirements need their own agreement; they should not be inferred directly from a component moisture-sensitivity label.

Check that labels survive the chosen packing arrangement and that opening one package does not break the required unit-to-record association. Define split shipments, handling instructions and carton contents explicitly. The packing list should identify what was actually released, while held or rejected units remain controlled and outside the shipment.

Resolve exceptions without rewriting history

Keep unresolved product, record and quantity issues visible until an authorized decision is made. Distinguish rework to meet the original requirement from a concession accepting a deviation. The latter requires the relevant authority and cannot be created by a calculator, an inspector���s convenience or an informal statement that the product probably works.

For returned or damaged goods, preserve the link to the original shipment and record the condition on receipt. Do not automatically treat a previously passed lot as currently acceptable after uncontrolled storage, transport damage or additional processing. Identify what changed and which checks are necessary to establish the new disposition.

The quality assurance page provides the supplier-level context. For a project enquiry, send the required release evidence, lot or serial scope, inspection expectations and packaging conditions. That discussion allows quality work to be included in the quotation instead of becoming an unplanned request at dispatch.

Final PCB inspection questions

Is FQC the same as final electrical testing? No. Electrical testing can contribute evidence, but final release also reconciles identity, condition, required records, exceptions, quantity and packaging.
Can the tool choose the right AQL plan? No. Sample size and decision rules must come from the applicable agreed procedure. The tool checks only the simple entered count rule and keeps other release issues separate.
Does a passing sample mean every board is good? No. Sampling has defined risks and scope. It does not prove defect-free production or replace required full-population checks.
Can a missing record be treated as a pass? No. Identify whether the requirement is unmet, the evidence is missing or a review is pending. An authorized disposition is needed; the absence of a recorded failure is not evidence of conformity.

Discuss final inspection and delivery records

Send the product revision, quantity, required standards and expected records. Identify unresolved limits, methods or responsibilities so the engineering review can address them before quotation or release.

Attach a downloaded tool brief manually. Contact does not automatically receive these inputs. References reviewed September 2026. Diagrams explain methods; published equipment photographs do not establish project results, certification or included test coverage.