First Article Inspection: Verify the Part and Revision Before Reusing the Claim

*By Daoyu Guan. Official sources reviewed November 9, 2026.*

A supplier's English website says it can provide first article inspection. A buyer receives an impressive report package with measurements, document references and approval fields. Before using that package to qualify a new order, the buyer needs to identify exactly what it covers.

The part number, design revision, configuration, production context and customer requirements matter. An accepted record for one defined item should not quietly become evidence that every product, changed process or later shipment has already been accepted.

For manufacturers publishing technical capability content, the useful claim is specific: which first article process can be supported, under which applicable requirements, with what records and review authority? That is more informative than a broad first-article certification label.

Establish which requirements apply to the order

The public scope of SAE AS9102C describes requirements for performing and documenting first article inspection. It also states that those requirements complement customer and applicable statutory and regulatory requirements.

That public scope does not give a buyer the complete paid standard, settle the terms of an order or establish that every industrial part is subject to an identical process. Confirm the applicable edition, purchase-order conditions and customer instructions before treating a generic checklist as sufficient.

A public supplier guide offers a concrete illustration of this boundary. L3Harris's QA-01.1.1 guide, effective February 20, 2024, defines its applicability by the purchase order and specified product categories. It is a customer's own procedure, not a universal rule for every manufacturer's products. A supplier dealing with that customer must validate the applicable controlled requirements rather than assume a downloaded copy is current for its order.

Tie the report to a product identity

Start by matching the report to the item being offered. Similar product names are insufficient. A commercial family can contain several drawings, material options, manufacturing routes or assembly configurations.

Record the identities together:

This table is an editorial review aid. It is not a reproduction of all mandatory AS9102 fields. The applicable standard and customer process determine the actual required package.

A document can be genuine and still be outside the scope of the current purchase. The buyer needs the relationship between the record and the offered configuration, rather than a large folder whose contents happen to concern the same supplier.

Distinguish three quality questions

First article evidence, process capability evidence and shipment acceptance evidence can inform related decisions, but their scopes differ.

A first article package concerns the specified article and the applicable verification process. A capability analysis concerns a defined process and characteristic under its statistical assumptions. A lot-acceptance decision concerns a defined population of items and an agreed inspection or acceptance arrangement.

NIST's acceptance-sampling introduction describes sampling used to decide whether to accept or reject a lot. Its process-capability guidance addresses a different analysis of process performance relative to specifications. Neither description turns a first article report into a blanket claim about every future unit.

Ask which decision each submitted document supports. A supplier may provide all three kinds of evidence where required. The receiving team should still avoid substituting one for another without an approved basis.

Use a revision change to expose the gap

Consider a fictional bracket, part H-170, manufactured to revision C. The retained first article record refers to that revision and an identified manufacturing context. A later inquiry requests revision D, with a changed hole pattern.

The website should not present the revision C record as automatic acceptance of revision D. The correct next step is to identify the changed requirements and obtain the applicable engineering and quality review.

That review may lead to additional evidence, a partial or full activity, or another disposition under the actual requirements. This article does not prescribe which outcome applies. A public brochure cannot make the decision merely by calling both versions the H-170 series.

The same discipline applies when another condition changes. A new manufacturing location, process route, supplier operation or material condition can be relevant to the approved scope. Determine what the governing requirements say and preserve the decision, rather than inventing a universal trigger rule from an online summary.

The fictional example demonstrates traceability. It is not a failed inspection, a customer dispute or an engineering ruling about a real part.

Preserve the link from a requirement to its result

A reviewer should be able to follow a requirement from the released design definition into the applicable record and its disposition. A headline saying all dimensions passed can hide unresolved conditions if the record does not identify which characteristics and revisions were assessed.

For the handoff, ask how referenced specifications, externally performed operations and supporting documents are connected. A certificate for a finishing operation, for example, needs an appropriate relationship to the item and condition under review. Its existence does not establish that the assembly's other requirements have been addressed.

Keep unresolved items visible. If a requirement awaits clarification or an authorized disposition, the summary should preserve that state. A content editor should not simplify a pending technical matter into an unconditional approval claim.

Useful receiving questions include: can the reviewer identify the governing requirement; can the result be traced to the relevant item; is the measurement or other evidence appropriate to that requirement; and who is authorized to accept or resolve the issue? The actual quality process supplies the detailed rules.

Decide what may be public

A supplier can describe its ability to support an agreed first article process without publishing a customer's drawing or complete inspection package. The public page should explain the scope, the document-request route and the approvals needed for a specific engagement.

If a redacted example is authorized, label its status. A fictional specimen should be called fictional. An actual customer record needs appropriate permission and enough context to explain its limits. Removing identifying information should not turn a narrow result into a company-wide performance claim.

Similarly, distinguish having a quality-management certificate from having an accepted first article record for a particular item. Publish each claim with its own evidence and scope. A certificate number or report cover is not a substitute for explaining that relationship.

This helps overseas buyers ask a useful follow-up: can this supplier support the evidence package required for this drawing and order? It avoids forcing them to interpret a vague badge or a broad statement about aerospace quality.

Write the English capability statement with its condition intact

A source statement might mean that first article documentation can be prepared when required and agreed. The English version should retain those conditions. Editing it into “all products are first-article approved” changes the meaning.

A practical proposed statement identifies the applicable work and directs the buyer to a review: “First article documentation can be scoped for the specified part and released design requirements. Submit the drawing revision and applicable customer requirements for confirmation.” A real manufacturer should publish such wording only after its responsible team confirms it.

If the supplier supports one customer's defined process, name that context only where disclosure is permitted. Do not automatically claim compliance with every other customer's requirements or an unreviewed edition of a standard.

For content production, retain the original source statement, proposed English wording, technical reviewer and release decision together. Later revisions can then change the appropriate claim rather than leaving an old catalog statement in circulation.

An acceptance exercise for the website and document route

Choose one authorized product example. Ask a reviewer who did not write the page to find the relevant capability statement, identify its conditions and request the appropriate document through the agreed route.

The exercise should establish whether the public information and handoff preserve the item identity, revision and intended review. It does not perform the first article inspection or accept a shipment.

Xindar publishes this article and provides manufacturing-focused English website and GEO work. Its role can include organizing approved technical material into a usable buyer explanation. Manufacturing facts, inspection requirements and acceptance decisions remain with the responsible manufacturer and customer authorities. The B2B export-marketing scope supplies context for the page and inquiry-path work; it is not a claim of laboratory accreditation or engineering approval.

Questions buyers ask

Does one accepted first article report establish acceptance of all later shipments?

The report's actual scope and the applicable order requirements must be checked. Do not infer a blanket future-shipment decision from a record for one identified item and production context.

Does every manufacturer need to advertise AS9102C?

Determine the requirements relevant to the products and customers served. The public aerospace standard scope is not a reason to add an unsupported universal capability claim to an industrial website.

Does a design change always require the same new inspection activity?

Do not apply a universal rule from this article. Identify the change and follow the applicable standard, customer instructions and authorized disposition process. Preserve that decision with the product records.

Can a content provider approve the technical claim?

It can organize sources and propose wording within its agreed role. The authorized technical or quality owner must decide whether the evidence supports the published claim and the offered scope.

Sources and method

This article uses SAE's public AS9102C scope, selected relevant pages of the public L3Harris supplier guide and NIST's descriptions of lot acceptance and process capability. The complete paid standard was not reviewed. The identity table, revision-C/revision-D example and publication exercise are editorial proposals, not a reproduced customer procedure, a complete FAI audit or a supplier approval.