Map First-Article PCB Characteristics to Specific Inspection Evidence

A first-article package can contain many pages while leaving some requirements unverified. Build a characteristic-to-evidence map that lets a reviewer follow each agreed requirement to its result. This is particularly useful when dimensions, materials, assembly identity, and functional checks are documented in different places.

SAE’s AS9102 publication information identifies first-article inspection documentation as a formal subject in aerospace. The workflow below is a general evidence-mapping approach; apply the actual customer requirements and applicable standard revision when a formal report is required.

Freeze the requirement baseline

Identify the drawing, BOM, fabrication specification, assembly variant, and test requirements being reviewed. Record their revisions. A report cannot demonstrate coverage coherently if measurements refer to one drawing while material records refer to another.

Assign a clear identifier to each characteristic or requirement in the agreed scope. Keep the source location and requirement text or precise reference. Avoid using a drawing balloon number without preserving the drawing on which that numbering was defined. Include notes and referenced specifications in the scope review, because not every requirement appears as a dimension beside the board outline.

Make each evidence link reviewable

Link results to the inspected article or appropriate supporting sample. A generic supplier capability statement is not a measurement of the article. Likewise, an unrelated material certificate should not be attached solely because its description resembles the requested material.

Check coverage in both directions

1. Confirm every in-scope requirement has a disposition.
2. Confirm every cited result belongs to the intended article or process evidence.
3. Investigate missing, conflicting, or ambiguous records.
4. Track any nonconformance through its own disposition.
5. Release a coherent package with the reviewed baseline.

Use actual measured values where the requirement and method call for them, rather than replacing all results with “pass.” For qualitative requirements, state the observation or referenced evidence that supports the decision. The record should remain interpretable after the inspector is no longer available.

Do not treat completion of this map as proof that every future board will conform. It documents the defined article and review scope. Preserve ordinary production controls, inspection, and change review as separate activities. A concise map with complete links is more useful than a large package whose requirement coverage cannot be reconstructed.