First-Piece Approval: Record the Production Release Boundary

First-piece approval should identify the setup, measured sample and exact production conditions being released. The quality decision must say what may run, what remains on hold and which changes require another check.

Use this workflow after a setup or other change that your control plan identifies as requiring first-piece inspection. The operator presents the sample and setup evidence, quality evaluates the required characteristics, and the supervisor releases only the authorised scope.

Define the release before measuring the sample

Collect the work order, item and drawing revision, operation, machine, tooling identity, applicable program or setup revision, material identity, inspection method and gauge status. The inspection plan determines which characteristics need evidence. Avoid turning an old sample sheet into the specification for a different job.

A routine setup approval and a formal first article inspection have different scopes. NIST's study of first article inspection reports describes comparing sample characteristics with specified requirements. The practical release record here does not replace a customer's required FAI package.

Separate the sample decision from the batch decision

Illustrative scenario: a supervisor plans a 240-piece operation. The first-piece plan requires three measurements and a fit check. Two measurements are recorded, but the third gauge is unavailable. The sample remains pending; there is no complete release decision to apply to the 240-piece run.

Once the required checks are complete, quality records the approved setup and applicable control-plan interval. Suppose a fixture is then replaced after 60 pieces. If fixture replacement is a defined reapproval trigger, the previous decision no longer covers production under that changed setup. Identify the last accepted boundary and hold any affected output pending the prescribed review.

Do not infer process capability from one conforming piece. First-piece approval establishes that the checked setup produced the inspected sample under the recorded conditions. Continued production still follows its inspection and process-control plan.

Handle a failed or incomplete inspection

Record the failed characteristic and actual result, identify the sample and affected pieces, and assign the correction to an authorised owner. After adjustment, retain the original result and link the new inspection to it. Replacing the failure with a passing value destroys the sequence needed to explain the decision.

If the inspector is unavailable, use the approved escalation route. A queue delay does not authorise a supervisor to sign for a competence or permission they do not hold. If a customer concession is required, identify the exact scope and controlling approval before treating it as permission to proceed.

Record the decision in Optiwise

Our quality workflows support configurable inspection forms, parameters and role-based quality queues. You can connect a release form to the production job and use required fields for setup identity, sample evidence and the decision owner. Our no-code configuration lets the form reflect your released control plan.

Check a pilot across ten setup events: every released run should have traceable sample results, an authorised decision and a stated release boundary. Review any output produced while approval was pending and every setup change lacking its required recheck. These are record acceptance checks, not a claim that ten inspections prove long-term capability.

First-piece approval questions

Must every first-piece check use the same sample size?

No. The applicable product requirements, control plan and inspection method determine the evidence needed. Do not copy a sample size from an unrelated job.

Can the operator inspect their own first piece?

Follow the site's competence and authorisation rules and any customer requirements. Record who performed the check and who has authority to release the run.

Bring a redacted setup sheet and inspection plan to an Optiwise demo to map the release fields and recheck triggers.