First article inspection is well established as a quality practice. A supplier produces an initial part using production tooling, processes and personnel, verifies every characteristic on the drawing, and submits the results for approval before series production is released. The discipline is mature and the formats, whether an aerospace style report or a production part approval package, are standardized.
What is less mature is the contractual side. The requirement usually lives in a quality plan or a purchase order note, and its recurrence is governed by trigger events, a design change, a process change, a tooling move, a site transfer, a lapse in production, that originate with the supplier and may never be reported. The result is a control that works well at program launch and degrades steadily afterwards.
This datasheet sets out what a supplier agreement should say about first article inspection, the trigger events worth naming explicitly, and how to hold the resulting duties as tracked records so that the question of who currently owes a submission has an answer. None of this is new practice in mature programs; what changes is where the requirement lives and whether anyone can report on it.
What the agreement should specify
A first article requirement that says only that the supplier shall perform first article inspection leaves five important questions open. Each of them becomes a dispute at some point in a long program.
- Scope by part and characteristic, which part numbers require full inspection, which require key characteristics only, and how the characteristic list is controlled between the parties.
- Trigger events, the specific changes that require a new or partial submission, including design revision, process change, tooling change, site relocation, subcontractor change and extended production lapse.
- Submission format and content, the report format, the required supporting records such as material certifications and measurement system data, and the medium of submission.
- Timing and approval, how many days before first delivery the submission is due, the buyer’s review turnaround, and what constitutes approval as distinct from receipt.
- Consequences pending approval, whether shipment is permitted under deviation while approval is outstanding, on what terms, and who bears the cost of rework if approval is refused.
The fifth point is the one that determines whether the obligation has teeth. If deliveries continue regardless of approval status, the submission becomes paperwork. If shipment is conditional, the supplier has a direct operational reason to submit on time, and the buyer has a defensible position when it refuses receipt. It also changes the conversation with the supplier, because a conditional shipment term makes the submission deadline a commercial matter rather than a quality request.
A launch first article is a project task with an end date. The trigger events are what make first article inspection an ongoing contractual obligation, and they are invisible to the buyer unless the supplier reports them. That makes change notification the dependency: a first article requirement without a matching notification duty relies on the supplier volunteering the news that it moved a process.
Where the obligation degrades
Programs rarely fail at launch. They drift, and the drift follows a familiar sequence across the supplier base.
- The requirement sits in the purchase order only. Purchase orders are transactional and get superseded. A requirement that lives only there disappears when the order does.
- Trigger events are undefined. Without a named list, the supplier applies its own judgment about what constitutes a significant change, which is usually narrower than the buyer’s.
- Change notices do not reach quality. The supplier notifies a buyer contact, the notice is treated as commercial correspondence, and the first article implication is never assessed.
- Partial submissions have no defined scope. For a change affecting a handful of characteristics, neither party knows whether a full resubmission is required, so the decision is renegotiated each time.
- Approval status is not visible to receiving. Goods arrive and are accepted because nobody at the dock can see that the approval is outstanding.
Five steps to a durable first article control
Step 1, Put the requirement in the agreement, not the order
Move the first article obligation into the supplier quality agreement or the master supply agreement so that it survives individual purchase orders. Reference it from the order rather than restating it, which avoids the two documents drifting apart across revisions.
Step 2, Name the trigger events explicitly
List the changes that require a submission and pair each with the notification duty that surfaces it. Ambiguity here is expensive, because the supplier and buyer each have an incentive to read an undefined trigger in their own favor when a change has already happened.
Step 3, Extract the duties into tracked records
Convert the submission requirement, the notification duty and the approval turnaround into obligations with owners, linked to the part number, the supplier and the program. The buyer’s own review turnaround should be tracked too, since late approvals are a common cause of disputed shipment holds.
Step 4, Route change notices into assessment
Establish a single intake for supplier change notifications with a mandatory assessment step determining whether a full or partial first article is required. Record the determination, including a decision that no submission is needed, because documented negative decisions are what make the control auditable.
Step 5, Make approval status visible at receipt
Expose the approval state to receiving and to the planning system so that unapproved parts are flagged before they enter inventory. A control that only exists in the quality function cannot prevent acceptance at the dock.
See first article duties tracked to approval
Watch how submission deadlines and change triggers become monitored records with named owners.
Where this sits in the wider supplier control set
First article inspection is one member of a family of supplier commitments that share the same structure: a trigger, a deadline, a deliverable and an evidence record. Production part approval duties, change notification and corrective action deadlines behave identically, and they are catalogued in Supplier quality agreement and PPAP commitment tracking. Running one register across all of them, rather than a separate tracker per requirement type, is what makes the supplier picture coherent, and it is the model described in Obligation Management for Manufacturing. A single register also makes supplier performance comparable, which is difficult when each requirement type is tracked in its own spreadsheet.
Trigger, submission scope and evidence
Different triggers justify different submission scopes, and agreeing that mapping in advance removes most of the argument.
| Trigger event | Typical scope | Notification duty | Evidence retained |
|---|---|---|---|
| Initial production release | Full first article | Not applicable | Full report and approval record |
| Design revision | Affected characteristics | Advance written notice | Partial report and revision reference |
| Process or tooling change | Affected characteristics | Advance written notice | Partial report and process description |
| Site or subcontractor change | Full first article | Advance written notice | Full report and site qualification |
| Production lapse beyond term | Full or partial, by agreement | Supplier declaration | Report and lapse duration record |
First article inspection is a control that works precisely as well as its trigger management. The inspection itself is a solved problem; the open question in most programs is whether anyone knows that a trigger fired. Writing the trigger list into the agreement, pairing it with a notification duty, tracking both as dated obligations and making approval status visible where parts are received turns a launch gate into a control that holds for the life of the program. The cost of doing this is a few fields and an intake process, set against the cost of discovering an unapproved process change in a warranty investigation.
For related guidance, see Price adjustment clauses in direct material contracts, ESG and supply chain due diligence clause tracking and Capacity reservation clauses in semiconductor supply deals.
