Final inspection is the last quality check before a product ships: a verification that the finished item meets every release requirement, performed against defined acceptance criteria and closed by a signed, dated release authorization from someone with the authority to accept the product for the customer. It is the gate where product either earns its way out the door or gets held.
Everything upstream feeds this moment. Incoming inspection cleared the raw material, in-process checks caught problems on the line, but final inspection is the plant's last chance to stop a defect before the customer finds it. Get it wrong and the escape becomes a complaint, a return, or a recall. This guide covers what final inspection verifies, how it differs from in-process checks and first article inspection, the release decision itself, who is allowed to make it, and the records that prove it happened.
What is final inspection?
Final inspection is the acceptance activity performed on finished product, after all manufacturing and packaging steps are complete, to confirm it conforms to specification before release. It is not one more sample check on the line. It is a decision point: pass, and the product is released to the customer or to finished-goods stock; fail, and it goes on hold for disposition. The whole quality system exists to make that decision correct.
Two ideas sit at the center. The first is acceptance criteria: the specific, written requirements a unit or lot must meet to pass, drawn from the drawing, the specification, the customer contract, and any regulatory limits. Criteria that live in someone's head are not criteria. The second is authority: the product is not released until a designated person with defined authority signs and dates the release. Final inspection turns "it looks fine" into a documented, accountable decision.
What does final inspection actually verify?
It confirms the finished product meets the requirements that matter to the customer, checking the things routine line checks may not cover on every unit:
- Critical and key characteristics. The dimensions, functions, and features flagged as critical to quality get verified against their limits, usually on every unit for high-risk items and by sampling plan for the rest.
- Workmanship and cosmetic requirements. Surface finish, marking, and visible defects checked against a workmanship standard or boundary samples, not personal taste.
- Completeness and configuration. The right revision, the right options, the right count, the right accessories. A perfect part shipped as the wrong revision is still a defect.
- Labeling, packaging, and identification. Correct label, lot code, quantity, and packaging integrity. In regulated industries this is a release requirement, not an afterthought.
- Documentation and records. The certificates, test results, and traceability that must accompany the product exist and match the physical goods before release.
How is final inspection different from in-process inspection and FAI?
They answer different questions. In-process inspection asks "is the line making good product right now?" and runs continuously during the build. First article inspection asks "can this process, run as planned, make a conforming part at all?" and runs once at launch or after a change. Final inspection asks "can this specific finished lot be released to the customer?" and runs at the end, every time. The three overlap in tooling and technique but sit at different points in the timeline and carry different decisions.
| Check | Question it answers | When | Decision |
|---|---|---|---|
| First article inspection | Can the process make a conforming part? | Once, at launch or after a change | Approve the process |
| In-process inspection | Is the line making good product now? | Continuously, during the run | Keep running or stop and adjust |
| Final inspection | Can this finished lot ship? | At the end, every lot | Release or hold |
How do you run final inspection and release a product?
Final inspection is a procedure, not a vibe. The sequence below turns a finished lot into a released lot with a record behind every step.
- Confirm the acceptance criteria and revision. Pull the current drawing, specification, and customer requirements at the correct revision. Releasing against the wrong revision is one of the most common and most expensive escapes.
- Verify the lot is complete and traceable. Confirm the quantity, the lot or serial identification, and that in-process records for this lot exist and are signed. A missing record is an open question, and open questions do not ship.
- Inspect against the plan. Measure critical characteristics per the inspection plan or sampling plan check workmanship against boundary samples, and verify labeling and packaging. Record actual results, not just pass or fail.
- Check the accompanying documentation. Certificates of conformance, test reports, and material or process certs must exist, match the goods, and be at the right revision before the product is eligible for release.
- Disposition any nonconformance. If anything fails, raise a nonconformance report quarantine the lot, and route it through review. Product on hold does not ship on a promise to fix it later.
- Authorize the release. A person with defined release authority reviews the evidence, then signs and dates the release. The signature is the point of the whole exercise: an accountable decision by someone allowed to make it.
- File the acceptance record. Store the results, the signature, the equipment used, and the date so the release can be reconstructed later during an audit, a return, or a recall investigation.
Who has the authority to release product?
Release is an authorized act, not a default. Product should not leave the plant until a named person with defined release authority reviews the acceptance evidence and signs. That person is usually quality, not production, precisely because the two roles have different pressures: production is measured on shipping, quality is measured on conformance, and separating the release decision from the shipping pressure is what keeps a late lot from going out unchecked.
For higher-risk work, the authority is often layered. Critical lots, customer-designated parts, and first articles commonly require a second review or countersignature from a quality engineer or quality manager before disposition is final. And when product must ship outside its normal specification, that is not a release, it is a concession or deviation, which requires explicit authorization, often from the customer, and a record explaining why the departure is acceptable. Nobody on the floor gets to decide, on their own, that out-of-spec is good enough.
What records does product release require?
The release record is the proof the decision was made correctly, and it is what an auditor, a returning customer, or a recall investigation will ask for first. A complete acceptance record captures the acceptance activities performed, the dates they were performed, the actual results, the signature of the people who performed and authorized them, and the equipment used. If you cannot reconstruct who released what, when, against which revision, and on what evidence, you have shipped product but not really released it.
What the standards require at release
- ISO 9001:2015 clause 8.6, Release of products and services, requires that product not be released until planned arrangements have been completed, and that the organization retain documented information on release, including traceability to the person authorizing it (ISO 9001:2015).
- The U.S. FDA device regulation on acceptance activities, 21 CFR 820.80, requires that finished product not be released for distribution until the required activities are completed, the data reviewed, and the release authorized by the signature of a designated individual, and dated (FDA 21 CFR Part 820).
- The same regulation requires acceptance records that include the activities performed, the dates, the results, the signatures of those performing them, and where appropriate the equipment used, the elements that make a release reconstructable years later (FDA).
How does final inspection fit the rest of the quality system?
Final inspection is a gate, and a gate is a weak place to put all your trust. Catching a defect at final means the plant already spent the full cost of making it, so the goal is always to need final inspection less by building quality upstream. That is why final results feed straight back into statistical process control and process capability work: a defect type that keeps showing up at final is a signal that a process is drifting and should be caught on the line, not at the door. Final inspection is also where the cost of quality becomes visible, because every hold, rework, and scrap disposition at this stage is failure cost you can count. It leans on the broader split between quality control and quality assurance inspection finds the defect, the system prevents the next one, and it hands nonconforming lots to the quality management system that governs their disposition.
The quiet failure mode of final inspection is not the missed defect; it is the release that cannot be reconstructed. When results, signatures, and revisions live on loose travelers and clipboards, a customer return three weeks later turns into an afternoon of hunting for paper, and nobody can say for certain what was checked or who released it. When that acceptance data is captured at the point of inspection, tied to the lot, the revision, and the person, the release record assembles itself and a recall question becomes a search instead of an excavation. That live capture is what Harmony gives a plant, working alongside the existing QMS rather than replacing it, no rip-and-replace. The processor in our CLS case study made exactly that shift, from quality records found the next morning to quality records visible as the work happens, which is the difference between a release you can prove and one you can only hope was right. See how the capture works on the features overview.