First Article Inspection: What Product Teams Should Prepare

First article inspection is a planned review of an initial production-intent part or assembly against agreed requirements. It helps a product team find differences in dimensions, materials, fit, finish, function, and records before those differences spread through a larger run. The useful question is not simply whether the first part looks right. It is whether the team can show what was checked, what was found, and what must happen before production proceeds.

Discuss your production readiness (https://www.jacksonhedden.com/contact)

What should first article inspection confirm?

A first article review checks whether a part made with the intended production process matches the current design definition and acceptance criteria. Depending on the product, that definition may include drawings, a 3D model, a bill of materials, material and finish requirements, assembly details, labeling, packaging, and functional expectations.

It is also a checkpoint on the process, not only the object. The team should know which supplier, equipment, material, tooling, work instructions, and inspection methods produced the sample. If a prototype was made by hand or with a different process, its success does not by itself establish that production parts will be consistent.

First article inspection is sometimes abbreviated FAI. In aerospace, AS9102 establishes requirements for performing and documenting an FAI. The American Society for Quality overview of AS9102 revision activity (https://my.asq.org/events/event-description?CalendarEventKey=90a297c9-109e-48f1-a3b1-01888c136d89&CommunityKey=0a842288-5046-4a9b-9b38-802c0e6c6303&Home=%2Fevents%2Fcalendar) describes the standard in those terms. That standard is specific to its context; do not assume every consumer or commercial product needs the same formal process. Agree on the applicable customer, industry, regulatory, and supplier requirements before setting the inspection plan.

For other products, the review may be shaped by a purchase agreement, the supplier's documented process, or the product team's own acceptance plan. These are not interchangeable requirements. Write down which source governs each check. For example, a drawing may control a mounting-hole dimension, while a separate product specification defines finish or the expected function of a moving part. If two documents appear to conflict, pause and resolve the discrepancy before recording a pass.

How is a first article review different from a prototype review?

A prototype answers questions about an idea. A first article answers whether an initial item from the planned production setup meets the approved definition. A prototype may be hand-finished, built with temporary materials, or assembled with substitute parts to test a concept. Those shortcuts can be valuable during development, but they can hide issues that appear only with final tooling, production materials, fixtures, or assembly sequences.

The name of the milestone matters less than its purpose. Before calling a sample a first article, ask whether it came from the actual or agreed production-intent process and whether its configuration is traceable. If not, treat it as a development sample and record what remains unverified.

- Main question: Does the concept solve the user or product problem? — Does the initial production-intent item meet the approved requirements?

- Typical build: May use temporary methods or substitute components — Uses an agreed production process, material, and configuration

- Evidence: Observations, models, user feedback, and test notes — Recorded requirement checks, actual results, deviations, and disposition

- Decision: What should change in the design? — What must be corrected or approved before the next run?In practice, one sample can serve more than one purpose, but keep the purpose and evidence distinct. A product can be attractive and usable yet still have a production issue. Conversely, a dimensionally conforming part may still need further evaluation for assembly, usability, or performance.

Consider a handheld device housing that looks polished in a prototype review. The early model may have been sanded by hand, while the production-intent housing comes from a mold. The first article review should therefore check not only the overall shape but also the molded features that affect assembly, the finish the customer will see, and whether the housing mates with the intended internal components. The earlier prototype feedback remains useful, but it cannot stand in for these production checks.

How do you prepare before the first article arrives?

Good preparation starts before the supplier ships the sample. The product team, supplier, and any relevant customer or quality representative should agree on the item being reviewed, the version of the design, the inspection method, and the decision authority. This avoids spending the review arguing about which drawing or tolerance is current.

- Freeze the review configuration. Identify the drawing or model revision, parts list, material, finish, and any approved changes. Mark open items clearly rather than treating them as silently resolved.

- Confirm how the sample was made. Record the supplier, production site if relevant, tooling or equipment, process, material batch when available, and any departures from the intended process.

- Translate requirements into checks. List each characteristic or requirement to verify. Include dimensions, interfaces, material, appearance, assembly, labeling, and function where they apply.

- Assign a suitable check method. State how each item will be checked, what equipment or reference is needed, and who will record the result. A visual check, measurement, document review, or functional test may be appropriate for different requirements.

- Set acceptance and escalation rules. Agree what counts as conforming, who can accept a deviation, and what happens if a result is uncertain or outside tolerance.

- Schedule the people and time. Include people who can answer design, production, quality, and business questions. Allow time to inspect the sample and review evidence, not just attend a brief approval meeting.Turn the inspection list into a working plan rather than a collection of vague reminders. A row for a mounting interface might name the drawing callout, the tolerance, the measurement tool, the actual result, and the person who records it. A row for appearance can name the viewing conditions and the surfaces that matter. A functional check can specify the action to perform and the expected response. This level of detail lets different reviewers apply the same criteria and makes missing information visible before the sample is on the table.

For teams still resolving the product definition, the product design overview (https://www.jacksonhedden.com/product-design) is a useful starting point for connecting the product brief and design decisions. If the next question is how to evaluate a physical model before production, review the prototyping services (https://www.jacksonhedden.com/prototyping) page. A prototype can reduce uncertainty, but its limits should be clear before the first production-intent check. Teams aligning production needs with design decisions can also review a design for manufacturing guide (https://www.jacksonhedden.com/iterate/dfm-consulting-firms).

Which evidence should the team collect?

Keep the inspection record practical and traceable. Someone reviewing it later should be able to identify the sample, the requirement, the method, the observed result, and the decision without relying on memory or a string of informal messages.

- Sample identity: product and part name or number, sample quantity, date, supplier, and a way to distinguish the inspected item from later samples.

- Configuration: applicable design revision, material and finish, component versions, and known process or tooling details.

- Check results: each characteristic, requirement or tolerance, check method, measured or observed result, and pass, fail, or unresolved status.

- Visual evidence: photographs of the full item and any relevant details, especially defects, interfaces, cosmetic surfaces, or assembly concerns. Label images so their purpose is clear.

- Supporting records: relevant material declarations, supplier records, process notes, test results, or certificates when the project requires them.

- Issue log: a unique issue reference, evidence, impact, owner, corrective action, due date, and closure evidence.

- Disposition: the decision for each issue and an overall status, with the name or role of the person authorized to approve it.Do not record only “pass” or “looks good” when the requirement calls for a measurable result. If a check cannot be completed, say why and identify the next action. If the result is close to a limit or the method is uncertain, capture that uncertainty and decide whether a more suitable check is needed.

Make sample identification unambiguous. If the team receives several similar pieces, mark or bag them with unique identifiers and connect each identifier to the relevant record and photographs. Note whether a measurement was taken before or after assembly, because assembly can change access to a feature or alter the observed fit. Keep raw results as well as the final status. A later change to a tolerance or method may make the original measurement useful for comparison.

What should the team check on the part?

Start with the agreed requirements, then consider the ways the part will be used and made. A checklist should be specific to the product, not copied blindly from another project. These areas can help structure the discussion:

- Identity and configuration: Is this the intended part, revision, material, and finish? Are included components and labels correct?

- Critical dimensions and interfaces: Do key features meet their stated dimensions and tolerances? Do mating parts align and connect as intended?

- Material and finish: Is the supplied material and surface treatment consistent with the specification? Are there visible defects or changes that could affect use?

- Assembly: Can the item be assembled in the intended sequence? Are fasteners, clearances, access, and joints workable? Does assembly introduce damage or inconsistent fit?

- Function: Does the item perform the functions that are within scope for this review? Use defined test conditions where results depend on load, temperature, timing, or user interaction.

- Use and handling: Are edges, controls, touch points, stability, and access consistent with the intended user experience?

- Packaging and identification: Where included in the review, are protective packaging, product identification, and instructions present and suitable?

- Repeatability clues: Are there signs that a result depends on manual adjustment, unusual handling, or extra rework that may not be sustainable in a run?Not every project needs every check. Prioritize features that affect safety, regulatory obligations, fit, essential function, customer acceptance, and costly rework. Make the rationale visible so a later reviewer understands why certain characteristics received closer attention.

Order the checks to avoid creating misleading results. First confirm the part identity and condition. Then record dimensions and visual observations before any destructive test, adjustment, or assembly step could change the sample. Next, evaluate assembly and function in the agreed sequence. For a product with several components, record whether the checked combination uses the intended versions of each part. If a test requires a specific setup, photograph or describe the setup so the result can be repeated.

Use risk to determine where careful attention is most valuable. A cosmetic mark on a hidden internal surface may not have the same impact as a loose connection at a user interface. A small dimensional deviation can matter greatly if it affects a mating feature, but be of little consequence in a nonfunctional surface where no tolerance is specified. The written criteria and authorized review, not an individual preference, should guide those judgments.

How should findings become production decisions?

Inspection has value only if the findings lead to a clear action. Sort observations into a small number of statuses, such as conforming, nonconforming, and not yet verified. Then decide what each one means for the product and the next build.

For each nonconformance, describe the requirement, the actual finding, and the evidence. Avoid vague notes such as “fit issue.” Instead, identify the interface, show the measured gap or observed condition when possible, and explain the effect on assembly or use. Then assign an owner and a corrective action. Depending on the issue, that action might involve changing the part, adjusting a process, improving a fixture, clarifying a requirement, or repeating a check.

For example, suppose two housing halves do not close evenly. A useful record identifies the relevant interface, the location of the visible gap, the parts and revisions assembled, and whether the fasteners were tightened using the planned sequence. The team can then determine whether the cause is a part dimension, an assembly method, or an unresolved design expectation. Simply writing “housing does not fit” leaves the next person without enough information to reproduce the condition or check whether a correction worked.

Keep correction separate from approval. A proposed deviation is not automatically an accepted change. The authorized decision-maker should document whether the item must be reworked, replaced, retested, accepted under a defined concession, or held for further review. If the design changes, update the controlled documents and communicate the revision to everyone who needs it.

A useful closure check asks: Was the corrective action completed? Was the result rechecked with an appropriate method? Is the record linked to the original issue? Does the revised item match the current definition? If a correction affects other features or parts, have those been considered too?

Keep the original finding visible when closing an issue. Add the corrective action and follow-up result rather than overwriting the initial result with a new pass. This preserves the history and helps the team distinguish between a problem that was never present and one that was found, corrected, and verified. If the corrective action changes a process rather than the part itself, identify the production setup used for the follow-up check.

How do you decide whether to approve a production run?

A first article review is a decision gate, not a ceremonial sign-off. The approval should reflect the evidence and the agreed acceptance rules. Teams commonly choose among these paths:

- Approve: the required checks are complete, results meet the criteria, and the record is adequate for the next planned stage.

- Approve with defined conditions: only where the responsible authority allows it, the remaining items are understood, and limits, owners, and closure dates are written down.

- Correct and resubmit: one or more findings require changes and a new sample or repeat inspection before approval.

- Hold: evidence is incomplete, the configuration is uncertain, or a risk needs further assessment before a decision.Set the next stage explicitly. Approval might allow a controlled pilot or another validation build rather than unrestricted volume production. Define the quantity, configuration, monitoring, and stop conditions for that next step. If the first article has passed but assembly or performance still needs validation, do not let the word “approved” imply that every open question is closed.

A practical decision note says what was reviewed, the applicable revision, which checks remain open, and what the decision permits. For a limited next build, specify how many units or assemblies are included, which configuration is authorized, and what observations must be recorded. Set a clear stop condition too. For instance, repeated fit concerns or a new material variation may require a pause and a fresh review rather than being treated as routine production variation.

For examples of how product decisions connect to real development work, browse Jackson Hedden's project work (https://www.jacksonhedden.com/our-work). The manufacturing page (https://www.jacksonhedden.com/manufacturing) offers a relevant next step for teams considering how product requirements carry into production planning. If a physical trial is still needed, the guide to planning a pilot run (https://www.jacksonhedden.com/iterate/pilot-run-guide) can help frame questions about the next build.

What common mistakes weaken first article inspection?

- Checking against an old revision. Confirm the current approved definition before measuring or judging the sample.

- Confusing a polished prototype with a production sample. Trace how the item was made and which production conditions it represents.

- Using broad visual approval for measurable requirements. Record actual values where dimensions or limits are specified.

- Leaving the inspection scope implicit. List what was checked and identify what was not checked.

- Accepting undocumented changes. Record the decision authority and update the applicable product definition if a change is approved.

- Closing issues without rechecking. Preserve evidence that the action worked, not merely that someone performed it.

- Approving without a next-step boundary. State what the approval permits and what remains conditional.Small process habits help prevent these problems. Use one shared revision reference, a consistent record template, clear photo labels, and a short issue review after inspection. Store the final record where the team can retrieve it when a later sample, supplier question, or product change needs comparison. For a related checklist on transferring design information, see the design handoff guide (https://www.jacksonhedden.com/iterate/design-handoff-guide).

Another common gap is treating the review as a single meeting rather than a sequence. Preparation establishes what to inspect; the hands-on check captures evidence; the decision meeting assigns status and responsibility; follow-up confirms that corrections worked. When those stages are collapsed, findings may be discussed but not recorded, or a verbal agreement may be mistaken for formal approval. A short agenda and one shared issue log can keep the handoffs clear without adding unnecessary paperwork.

Talk through your product readiness (https://www.jacksonhedden.com/contact)

Frequently Asked Questions

Is first article inspection the same as quality control?

No. First article inspection is a focused review of an initial production-intent item and its supporting evidence. Quality control may include ongoing checks and controls across subsequent production. The first article can inform those controls, but it does not replace them.

How many samples should a team inspect?

There is no single quantity that fits every product or requirement. Agree on the sample quantity based on the applicable contract or standard, product risk, process, and the checks being performed. A single sample can reveal useful issues, but it cannot by itself demonstrate every aspect of repeatability.

Does every product need a formal FAI report?

No universal answer applies to every product. Customer agreements, industry standards, regulations, and supplier procedures may set different expectations. Determine what governs the specific project, then create records proportionate to those requirements and the decisions the team needs to make.

Can a first article fail one check and still be approved?

That depends on the acceptance rules and the authority responsible for the decision. A failure should be recorded and assessed, not ignored. The team may require correction and reinspection, or an authorized person may accept a documented deviation when the governing requirements allow it.

What if the first sample was made by hand?

Record it as a development sample unless the team has agreed that the method represents the production process for the purpose being evaluated. Hand-built samples can test form, fit, or function, but they may not provide evidence about tooling, process variation, or production assembly.

When should inspection happen?

Plan it after the product definition and inspection criteria are sufficiently clear, and after an initial item can be made with the intended production setup. Schedule it early enough that findings can be corrected before the next planned build or production commitment.

What is the most useful first step?

Write down the exact product configuration and acceptance criteria for the sample. That short alignment step helps the supplier and review team use the same reference, select appropriate checks, and make a decision based on evidence.

How can you make the review useful?

Prepare the product definition, inspection plan, sample identity, and decision roles before the item arrives. During the review, record observable results, capture unresolved points, and assign every corrective action. Afterward, document what is approved, what remains open, and what the approval allows next. That discipline makes first article inspection a practical bridge between product development and a controlled production run.