Separate Sample Acceptance from Repeat-Production Readiness

Ask what the sample was intended to evaluate

A sample may be requested to review geometry, fit, a selected manufacturing step or a proposed production route. Identify that purpose in the order and acceptance record. Record the part revision, sample identity, route used and characteristics actually evaluated; distinguish a dimensional record from an assembly or application evaluation.

If a prototype is machined from a different starting form than the planned production blank, approval of that prototype does not demonstrate the unperformed blank process. Likewise, a selected feature check does not establish that every characteristic or every later part meets its requirements.

Keep the customer's disposition specific: accepted for which purpose, under which definition and with which unresolved items? A verbal statement that a sample looks acceptable should not be expanded into a technical release for unstated requirements.

Compare the repeat order with the accepted scope

Review the proposed order against the accepted sample and its supporting records. Confirm the drawing revision and applicable specifications, then identify changes in the starting material or blank, treatment condition, route, tooling, required reports or packaging.

An unchanged part number alone is not a complete comparison. A changed source or process condition can require review even when the visible profile is similar. Conversely, do not require every record to be recreated without a reason: identify the affected requirements and agree the necessary review scope.

• Product definition: revision, material, finish and acceptance requirements.
• Starting point: blank specification, proposed source and supplied condition.
• Route: sample route versus the proposed repeat-production route.
• Deliverables: agreed reports, certificates, identification and packaging.
• Commercial scope: order quantity and requested delivery conditions.

Decide which additional evidence is needed

Connect the requested evidence to the change or risk being evaluated. If a feature definition changed, identify the relevant check. If the proposed route differs from the sample route, identify what remains to be demonstrated. Keep a request for a report separate from an available record and from an approved result.

Customer-specific first-article or production-approval submissions should be specified in the inquiry when applicable. Agree the required scope and responsible approval authority rather than assuming that every order includes the same submission package. A sample inspection report is not automatically a completed PPAP or an approval of serial-production capability.

Do not interpret a few accepted measurements as a process-capability study, a full-lot acceptance result or evidence of stable output over time. Those conclusions require their own defined evaluation and supporting data.

Record the release scope and the open items

A compact handoff record can connect the accepted sample to the proposed repeat order without becoming a new quality framework. Use the customer's existing forms where required. The example below is a discussion aid, not a claim about an implemented Jinhua approval system.

• Accepted sample reference, revision and evaluation purpose.
• Proposed order reference and revision.
• Differences in blank, material condition, route or deliverables.
• Evidence available and its exact scope.
• Required decision, responsible authority and decision reference.
• Remaining open items and the conditions to resolve them.

Use a change decision rather than an automatic restart

Describe the difference, the affected requirement, the evidence already available and the additional confirmation requested. Identify who can approve the revised scope. Until that decision is available, keep the changed item open rather than claiming that a familiar drawing makes it approved.

For example, a repeat order may request a different report format while keeping the part definition unchanged. Review the reporting commitment without pretending that this alone establishes a changed machining route. A different blank condition may instead require route and inspection review. These are illustrative distinctions, not Jinhua customer histories.

Keep delivery requirements visible without turning them into guarantees

Agree identification, reporting, protection and packaging requirements for the repeat order. These requirements support receiving and traceability, but a requested record or delivery date is not proof that it has been completed or promised.

Use the existing RFQ checklist to prepare the basic quotation package and the Quality Inspection page to discuss reporting scope. This guide addresses acceptance scope and changes between orders; it does not replace the released drawing, purchase order or an authorized technical decision.