A useful PCB assembly inspection report format connects the boards being reviewed to their configuration, acceptance criteria, inspection and test results, exceptions, and release decision. The report can be a summary with referenced records rather than a single file. The blank template below provides a starting point; adapt it to the agreement, applicable obligations and inspection plan.
For choosing inspection methods, see PCB inspection. This report format focuses on documenting the selected checks and reviewing their evidence.
1. Blank PCB assembly inspection report template
Complete the header once, then repeat the inspection record for each method, stage or separately identified scope. Add an exception record for each finding that needs investigation or disposition. Use the final section to identify exactly what is authorized for release.
Report header
| Field | Entry |
|---|---|
| Report ID, revision and status | ____________ |
| Order, customer and assembly part number | ____________ |
| Build lot, quantity and unit or panel mapping reference | ____________ |
| PCB, assembly and BOM revisions | ____________ |
| Firmware and test-plan revisions, if applicable | ____________ |
| Drawings, specifications and standards, including revision and class where applicable | ____________ |
| Document precedence and approved deviation references | ____________ |
| Inspection location and reporting period | ____________ |
| Inspector name or ID and date | ____________ |
| Reviewer name or ID and date | ____________ |
| Proposed shipment or ship-list reference | ____________ |
Inspection or test record — repeat as needed
| Field | Entry |
|---|---|
| Record ID; method and process stage | ____________ |
| Units or sample inspected; selection plan and lot size | ____________ |
| Side, features, reference designators and exclusions | ____________ |
| Equipment or fixture ID; relevant calibration/status reference | ____________ |
| Program, recipe or procedure ID and revision | ____________ |
| Inspector or operator; date and location | ____________ |
| Applicable criterion and acceptance limit | ____________ |
| Actual result, measurement definition and units where applicable | ____________ |
| Original call or attempt; reviewed result and reviewer | ____________ |
| Result status and supporting image, data or record references | ____________ |
Exception and retest record — repeat as needed
| Field | Entry |
|---|---|
| Nonconformance ID; affected units and features | ____________ |
| Original finding or failure and record reference | ____________ |
| Containment and investigation | ____________ |
| Disposition, authorized action and approving authority | ____________ |
| Work performed and verification record | ____________ |
| Retest attempt numbers, results and final status | ____________ |
Release decision
| Field | Entry |
|---|---|
| Quantity reconciliation and ship-list reference | ____________ |
| Units eligible, held and scrapped; exclusions | ____________ |
| Open issues or approved concessions and conditions | ____________ |
| Release authority, decision, signature or approval record, and date | ____________ |
| Attachments, record locations and retention reference | ____________ |
Use additional rows or linked records where one check has several results or several boards share a lot-level record. Mark a field not applicable with a reason when appropriate; a blank field is not evidence that a required check passed. Record a check that was not performed as such, rather than entering a pass.
2. Method-specific reporting checklist
Apply the common fields above to every selected method. The following board assembly inspection checklist adds details that make each type of result interpretable. Use only the methods and coverage required by the agreed plan.
Visual inspection
Record the process stage, board side and accessible features examined, along with the applicable workmanship criteria. Identify the inspector, date, location, lighting and magnification conditions, and any personnel qualification required by the plan. For each finding, identify the unit and feature, the observed condition, review outcome and supporting record. A visual result does not establish the condition of concealed joints or electrical function.
Solder paste inspection (SPI)
Solder paste inspection evaluates the printed deposit before component placement.
Record the pre-placement stage, equipment and recipe revision, sampled units and programmed pads or features. For measurements required by the plan, retain the actual result, units, applicable limit and measurement definition—for example, paste volume where supported. Link original calls to their reviews and any correction or repeat check. A paste result is not post-reflow joint acceptance.
Automated optical inspection (AOI)
Automated optical inspection examines visible features according to the programmed inspection coverage.
Record the inspection stage, sides, equipment, program revision and the component or solder features covered. Identify exclusions and preserve the original machine calls, affected unit and reference designator, reviewer, review outcome and any specified image or record reference. Separate acceptable indications from confirmed defects. An AOI report covers its programmed optical evaluation; it is not an electrical test.
X-ray inspection
Record the imaging method, equipment and recipe, selected units, packages or joints, and any coverage exclusions. Identify the criteria and image references. If a measurement is required, record its value, units, limit and how the feature or measurement was defined. Do not substitute an assumed void limit for an agreed criterion. An X-ray image can provide evidence about selected hidden geometry, but it does not by itself prove electrical continuity or service life.
ICT and flying probe
For selecting electrical test methods, see the circuit board testing guide.
Record whether the check uses in-circuit test (ICT) or flying probe, the equipment and fixture or probe setup, program revision and relevant equipment status. Identify the tested units, achieved net or component coverage and exclusions. Retain required electrical measurements, units, limits, original failures and repeat attempts. Coverage depends on access and the programmed test; optical or powered functions, if used, should be identified separately.
Functional test (FCT)
Record the test procedure and program, firmware, fixture, power, stimuli, loads, environment and sequence applicable to the result. Identify tested units, required actual values and units, limits, failures, investigations and retests. An FCT pass applies to the stated conditions; it does not replace workmanship acceptance or establish performance outside those conditions. Routine production inspection and test passes do not, by themselves, establish product or system reliability qualification or service life; those require a product- and use-condition-specific qualification plan.
For imaging-method selection and its limitations, see X-ray PCB inspection. Keep that method decision separate from documenting the agreed coverage and results.
3. How to fill the inspection report fields
Identify the population and configuration
Start with the order, assembly part number, lot and proposed ship list. State whether results apply to individual serial numbers, mapped panels, a sample or an agreed lot-level population. If panel identifiers are used, retain the mapping needed to identify the affected boards.
Record the released PCB, assembly and BOM revisions, plus applicable firmware, test-plan and program revisions. A valid result against one configuration should not be silently applied to another. When a record covers only part of a lot, identify that part and explain how the remaining units are covered.
Specify the acceptance basis
Name the applicable drawings, customer specifications, standards, revisions and class where relevant. Include approved deviations and their effectivity. If documents conflict, use the precedence established by the agreement or obtain an authorized interpretation; do not assume that the newest document automatically governs.
For example, IPC-A-610J's public scope addresses visual acceptability of electronic assemblies. It excludes X-ray and cross-section criteria, and its criteria do not themselves authorize repair or modification. If A-610 is invoked, record the agreed revision and class and use a separate applicable basis for other required checks.
Describe both dimensions of coverage
Coverage means which units were checked and which features were checked on those units. Record the lot size, selection method, sample identities, stage, sides, feature boundaries, exclusions and agreed escalation rule. A sample can support a lot decision when the agreed plan permits it, but the report should describe that decision as sample-based—not as direct inspection of every board.
Similarly, checking two named packages on every board is full unit coverage for those packages, not inspection of every hidden joint. Method names alone do not communicate the achieved scope.
Make results comparable
For each required measurement, give the actual value, units, limit and measurement definition, together with the relevant procedure or record reference. A pass/fail summary may be useful, but it cannot replace actual values when those values are required. Identify where images or raw records can be retrieved if the agreement calls for them.
4. Record calls, dispositions and retests
A machine call is an indication for review, not automatically a confirmed defect. Preserve the original call and record whether the reviewer classified it as an acceptable condition, a confirmed defect or unresolved. Count findings separately from affected boards: several findings can occur on one board. A call count is neither a board failure count nor a measure of defects that escaped inspection.
Link a confirmed finding to its unit, feature, nonconformance record, authorized action and verification. Rework aims to restore the original requirements; repair may need a separate disposition if those requirements are not restored. The applicable agreement determines who can authorize the work and what verification is required.
A retest repeats a check; it is not the same thing as rework. Record the initial attempt, investigation, any intervention, each repeat result and the final status. A later pass without physical intervention does not automatically prove the first failure was a false call. If an attempt is judged invalid because of a setup or procedure issue, retain the record and identify the reason and the person who made that determination.
Do not overwrite an earlier result when a report is corrected or criteria change. Link the revised record to the original, identify the change and retain the acceptance basis used at the time.
5. Review the report before release
Match the report to the proposed ship list, not just to the quantity originally built. Reconcile prior shipments, proposed units, holds and scrap without counting a board twice. An eligible unit can proceed to the release decision; it is not authorized to ship until the designated authority approves it.
| Review question | If evidence is missing or conflicting |
|---|---|
| Do identities and quantities match the proposed shipment? | Hold unmatched units and resolve the mapping or quantity difference. |
| Do revisions and criteria apply to the configuration? | Hold affected units until the basis or an authorized change is documented. |
| Is required unit and feature coverage demonstrated? | Retrieve the plan and records; contain the population dependent on missing evidence. |
| Are original calls, findings and required actions closed? | Review unresolved indications and verify authorized work before release. |
| Are required test attempts and results valid and traceable? | Investigate missing, invalid or failed results and retain the attempt history. |
| Does the approval cover the exact shipment population? | Keep excluded units segregated and obtain the appropriate authorization. |
A missing required record establishes neither a pass nor a defective board. First look for the correctly identified record. If it cannot be recovered, an authorized resolution might include a new check permitted by the agreement. Identify it as a new check; it does not recreate the earlier observation. Expand containment if the issue may affect units beyond those initially identified.
6. Worked example: reconciling 100 boards
This hypothetical example illustrates report arithmetic, not production performance or an acceptance threshold. A lot contains 100 uniquely identified boards, each with one valid first attempt at the defined FCT gate.
AOI produces 10 reviewed calls: four acceptable indications and six distinct confirmed defects on four boards. The six defects are corrected and verified under the agreed plan. They are six findings, not six failed boards; the four affected boards are already included in the lot of 100.
At FCT, 92 boards pass on the first attempt and eight fail. Six of the eight are subsequently repaired under an authorized plan and pass FCT; one is scrapped and one remains unresolved on hold. Assume the six also complete required post-repair workmanship checks, other affected verification and disposition. Their original failures and subsequent actions remain in the records.
There are 92 + 6 = 98 boards with a currently recorded FCT pass. One of those 98, assumed to be a first-attempt passer, lacks a required identified X-ray record and is held. That is a different board from the unresolved FCT failure.
Assume all other requirements are complete, the holds are traceably limited to those two boards, wider common-cause exposure has been resolved and partial shipment is permitted:
| Current status | Boards | Basis |
|---|---|---|
| Eligible for release | 97 | Required evidence and dispositions are complete under the assumptions. |
| Held | 2 | One unresolved FCT failure and one missing required X-ray record. |
| Scrap | 1 | Not eligible for shipment. |
| Total accounted for | 100 | Each board appears in only one status. |
The gate-specific FCT first-pass yield is 92 / 100 = 92%. The provisional recorded FCT-pass proportion is 98 / 100 = 98%, while the shipment-eligible proportion is 97 / 100 = 97%. These answer different questions. The first figure is not a whole-line first-pass yield, and eligibility still requires the actual release authorization. No final accepted yield is available while the holds remain open.
7. Request the report format at RFQ and NPI
Agree the inspection report fields before production so that the necessary records can be generated and retrieved. An RFQ or new-product-introduction request should identify:
- Population and traceability: lot boundaries, unit or panel mapping, shipment splits and required serial-level linkage.
- Criteria and coverage: released revisions, document precedence, methods, stages, samples, features, exclusions and escalation rules.
- Test inputs: program and fixture ownership, firmware, conditions, limits and the actual values to retain.
- Evidence delivery: report format, original calls and attempts, images or measurements where specified, record references, delivery timing and retention.
- Exceptions and authority: containment, action and retest records, concession approval, partial-shipment rules and the named release authority.
- Cost assumptions: setup, execution, review, correction, retest, special evidence and retention, distinguished where needed for comparison.
The designer or product owner supplies the released configuration, test objectives and limits and owns product qualification. The assembler executes the agreed activities and records results and exceptions. The named customer or quality authority, or an authorized delegate, decides release and concessions within the agreement. First-article approval addresses its defined initial-build gate; it does not automatically authorize a later shipment. See PCB first article inspection for that separate scope.
For PCB assembly, HILPCB selects inspection and test against package risk, product criticality and the customer test plan. A route can combine 3D SPI, AOI, visual review and electrical or functional testing; X-ray, flying probe or ICT can be selected when the design and criteria call for them. A release package can include inspection, test, traceability, revision and disposition records. Agree the exact methods, coverage, evidence, format and delivery during quotation and NPI. Send the requirements with a quote request, or contact our team to discuss report fields and delivery requirements.
Frequently Asked Questions
What should a PCB assembly inspection report format include?
Include identity and configuration, applicable criteria, method and coverage, actual results and units where required, record references, exceptions and retests, and the authorized release population.
Can I use the blank template for every assembly?
Use it as a starting point, then adapt the fields and attachments to the order, inspection plan and applicable obligations. A template does not determine which methods or acceptance limits apply.
What belongs on a board assembly inspection checklist?
List the selected methods and their stages, units and features, criteria, equipment or program references, required results, exclusions and evidence. Add review and disposition checks for findings and retests.
How should sampled inspection appear in the report?
Identify the lot size, selection plan, sampled units, features examined, results and escalation rule. If the agreed plan supports a lot decision, label it as sample-based rather than claiming every unit was inspected.
Does a completed report authorize shipment?
Not by itself. The reviewer must reconcile the report with the proposed units and close or authorize applicable exceptions. The designated release authority must then approve the exact shipment population.