Manufacturing sample approval: prototype, FAI, and PPAP

TL;DR

• Name the decision first. Axon's current supplier quality manual distinguishes several prototype, validation, FAIR, and PPAP stages inside its customer-specific system. The broader control is useful: write the question and approval scope before the supplier builds the sample.
• Verify production intent. Record the actual site, tooling, line or cavity, material route, subcontractors, process, programs, work instructions, inspection, rework, and packaging. A polished sample from a temporary process is still a development result.
• Record actual evidence. Tie each measurement, test, certificate, photo, or observation to a controlled requirement and sample ID. Use actual values where the requirement is quantitative, not an unsupported “pass.”
• Control every exception. A deviation needs an owner, scope, evidence, disposition, affected quantity, and closure or expiration condition. A sample cannot silently rewrite the drawing or specification.
• Release production separately. Sample acceptance does not automatically qualify the supplier, authorize material purchases, release a purchase order, approve shipment, or waive other requirements.

Choose the evidence gate before ordering samples

Start with the consequence of getting the decision wrong. A sample plan for a replaceable, low-risk bracket should not be copied onto a safety-related assembly, and a full automotive-style submission should not be demanded from every machine shop by habit. Use the product, process, and customer requirements to choose the minimum evidence that can support the next decision.

The requirement and evidence fields should already be visible in the quote-ready manufacturing RFQ. If sampling requirements first appear after the quote, the buyer may be changing scope, price, and lead-time assumptions without noticing.

The boundary between one-item conformance and process capability is statistical as well as procedural. The NIST/SEMATECH process-capability handbook defines capability by comparing the output of an in-control process with specification limits and explains that capability estimates need a sufficiently large set of independent data. One first article can document conformance, but it cannot estimate the process distribution by itself.

Ask ten risk questions instead of adding a generic score

A scoring formula can hide judgment behind a number. Discuss these questions with the accountable engineering, quality, procurement, and compliance owners, then record why the selected evidence lane is enough.

Do not let the sample name decide the evidence

Sample-stage labels vary by industry, customer, and supplier. Define each stage in the purchase documents or validation plan by purpose, build conditions, required evidence, reviewer, and release effect. The same physical item can support more than one decision only when its identity and evidence satisfy each gate.

A golden sample is a reference, not a hidden specification

The term “golden sample” has no single universal scope. One customer may use it for appearance, another for an item retained from a formal submission, and another may avoid the term entirely. Axon's customer-specific supplier quality manual uses master or golden sample for an artifact retained from a FAIR or PPAP production run. That illustrates why the term must be defined in the buyer's own system. Link every physical reference to the controlled drawing, specification, and accepted deviations; never let it silently override measurable requirements.

• Mark the item with a unique sample ID, part number, revision, approval date, and stated comparison purpose.
• Link the item to the drawing, model, BOM, specification, color or finish standard, test plan, and accepted deviations that were used.
• Record whether the buyer, supplier, inspection team, or more than one party retains a matching reference and where each item is stored.
• Protect the reference from production use, unauthorized repair, cleaning, fading, corrosion, damage, or component replacement that would change its meaning.
• Define the replacement and obsolescence rule when the design, material, finish, supplier, or production process changes.

FAI and PPAP are not two names for the same package

SAE's public page for AS9102C says the aerospace standard establishes FAI documentation requirements. It applies when the contract or customer flowdown makes it applicable. The forms and detailed requirements are proprietary, so a generic checklist should not imitate or paraphrase them as a universal rule.

AIAG's official PPAP overview connects production-part approval to an actual production run at production rates and consistent compliance with engineering and specification requirements. The customer still defines the required submission, evidence, disposition, and resubmission triggers. Do not demand a “Level 3 PPAP” or any other package unless the current customer requirement gives that term a controlling meaning.

Make production intent a signed statement, not an assumption

“Pre-production” and “first article” can sound definitive while concealing a different factory, temporary fixture, substitute material, hand-selected unit, unreleased program, or unapproved subcontractor. Require the supplier to declare the actual build configuration before the buyer relies on the result.

PRODUCTION-INTENT DECLARATION [buyer tailors]
Sample / lot ID: ___________________________________
Buyer part number and revision: ____________________
Drawing / model / BOM / specification revisions: ___
Manufacturing legal entity and site: _______________
Process route and operation sequence: ______________
Machine / line / cell / station: ____________________
Tool / fixture / mold / die / cavity IDs: ___________
Material source, grade, heat / batch / lot: _________
Subcontracted and special processes, with sites: ____
Software / firmware / CNC program revision: _________
Work instruction and control-plan revisions: ________
Inspection / test methods and equipment: ____________
Rework, repair, hand finishing, or unit selection: ___
Packaging and labeling revision represented: ________

Differences from intended production:
1. __________________________________________________
2. __________________________________________________

Supplier declaration owner / role / date: ___________
Buyer disposition of each difference: _______________

Cover every source of variation the decision depends on

Axon's current supplier quality manual provides one public industrial example: its production-validation, FAIR, and PPAP sections tie evidence to the intended production configuration. Axon's stage labels, forms, and submission rules are customer-specific, but the underlying control is broadly useful. Evidence has meaning only for the configuration that produced it.

Apply the same control when qualifying a replacement source. The production-intent statement connects the sample to the wider alternative-manufacturer and second-source program. It does not replace identity, capability, commercial, import, or first-order checks.

Build one validation record from requirement to decision

The most useful sample checklist is not a list of vague nouns such as “material, dimensions, finish.” It is a traceable row for every characteristic or evidence requirement that matters to the gate. The row identifies the source requirement, method, acceptance criterion, actual result, evidence, deviation, and disposition.

Copy the sample and evidence register

Click Copy sample register, then paste into cell A1 in Excel or Google Sheets. The 26 fields become columns; add one row for each sample characteristic or evidence requirement.

Keep the supplier's original report attached, but map the values into the buyer's controlled register. If a field does not apply, use N/A with a reason where needed. A blank field should not be interpreted as conforming, not required, or approved.

Record numbers as numbers

When a drawing gives a measurable limit, the report should normally show the actual result, unit, method, and sample or feature location. “Pass” alone hides the measurement's distance from the limit, makes transcription errors harder to find, and prevents comparison across sample rounds. Attribute checks can use a clear conforming or nonconforming result when that is how the requirement is defined.

A first-article record should also account for the applicable design characteristics and purchase requirements, including material, special processes, functional tests, and traceability where required. Northrop Grumman's public AS9102 report guide is a useful customer-specific example of characteristic accountability and released-engineering traceability. Use its form instructions only when they apply to the contract.

Keep deviations narrower than design changes

SAMPLE DEVIATION DISPOSITION
Deviation ID: ______________________________________
Requirement ID and revision: _______________________
Sample / lot IDs and affected quantity: ____________
Required condition: ________________________________
Actual condition: __________________________________
Evidence and risk review: __________________________

Disposition [choose one]:
[ ] Accept for this stated evaluation only
[ ] Accept for identified units / lot only
[ ] Approve a permanent requirement change separately
[ ] Rework and reinspect
[ ] Revise and resubmit
[ ] Reject

Production remains blocked? [ ] Yes [ ] No
Expiration / closure condition: ____________________
Authorized buyer owner / role / date: ______________

Write what the approval releases, in plain language

“Sample approved” is too broad. The supplier may read it as permission to buy material, start tooling, schedule production, or ship. Replace it with a bounded disposition that states the item, evidence, purpose, allowed next action, open holds, and authorized buyer owner.

Give every approval a change trigger

Approval applies to an identified configuration. Decide in advance how the supplier must report changes and who selects the revalidation scope. Depending on the applicable customer system, the response may be a selected recheck, new reference sample, partial FAI, full FAI, PPAP resubmission, or another pilot.

• Part number, drawing, model, BOM, software, material, finish, or specification revision
• Manufacturing legal entity, site, building, line, cell, equipment, fixture, die, mold, cavity, or program
• Material manufacturer, approved source, grade, route, formulation, or critical component
• Special-process provider, subcontractor, inspection method, test method, gage, or laboratory
• Rework, repair, corrective action, process sequence, control plan, work instruction, or packaging method
• Production interruption or transfer when the current customer requirement treats it as a resubmission event

Axon's current Supplier Quality Manual is a useful public example of customer-specific development stages, FAIR and PPAP evidence, retained master samples, and resubmission triggers. Its labels and requirements belong to Axon's system. Your own contract and customer documents control your program.

Move from technical acceptance to first-order readiness

Even a fully accepted validation package does not confirm the supplier's contracting entity, bank controls, tooling ownership, capacity reservation, payment authority, Incoterm and named place, packaging, inspection plan, shipping documents, escalation path, or purchase-order terms. Carry the approved sample IDs, revisions, deviations, and open holds into the supplier first-order readiness checklist before releasing a deposit or first production order.

Worked example: a manifold moves through three bounded gates

A US equipment manufacturer is developing fictional machined manifold MAN-204 with a prospective overseas supplier. The buyer separates design learning, first-article conformance, and pilot readiness instead of sending one “approved” email.

The characteristic rows carry the decision

The example avoids a common fiction: no sample “proves the supplier.” Each gate closes only the question it was designed to answer. The buyer can stop, revise, narrow, or advance the project without losing the evidence trail.

Twelve approval shortcuts that create the next problem

Glossary

Prototype

A development item used to answer a design, fit, function, appearance, material, or feasibility question. It is not production intent unless the build conditions establish that scope.

Production-intent sample

An item made under a declared set of conditions intended to represent the planned production configuration. The buyer defines which site, tooling, process, material, subtiers, controls, and pack must match.

Golden sample or reference sample

A uniquely identified physical artifact retained for a stated comparison purpose. The term has no universal scope and the item does not replace controlled requirements.

Master sample

A customer-defined retained sample, sometimes associated with a formal approval package. Confirm the applicable customer definition rather than assuming it means the same thing as golden sample.

Limit sample

A controlled example used to illustrate an acceptance boundary, often for an attribute that is difficult to express in words. It needs identification, condition control, and a linked written rule.

First article

An initial item selected from the declared manufacturing configuration for documented evaluation against applicable design and purchase requirements.

First article inspection (FAI)

The documented evaluation and characteristic-accountability process for a first article. The required format and triggers depend on the contract, customer, and applicable industry standard.

Partial FAI

A customer-authorized first-article scope limited to characteristics affected by a change, while retaining traceability to the accepted prior baseline. The applicable customer rules decide when it is allowed.

PPAP

Production Part Approval Process, a customer-defined system for product and manufacturing-process evidence. The current manual, contract, and customer-specific requirements control the package.

Pilot run

A controlled run used to evaluate how the intended process, controls, traceability, inspection, handling, packaging, and handoffs work together under defined conditions.

Characteristic accountability

The mapping of each applicable design or purchase requirement to an inspection, test, or evidence result and disposition.

Deviation or concession

Documented authorization for a specific departure from a requirement, with a defined item, quantity, duration, purpose, and approval scope. Terminology varies by quality system.

Rework

Action taken to bring a nonconforming item back into conformance. Disclose it when the sample's representativeness or evidence could otherwise be misunderstood.

Production release

A separate buyer authorization to produce the stated quantity, revision, supplier, site, and configuration under the named purchase conditions.

Frequently asked questions