Planning a Pilot Production Run for Automotive Plastic Parts

Pilot production run sequence from molding setup through inspection, testing, packaging and retained samples

Pilot runs often begin with a round quantity — "make 300 parts" — without deciding who needs the samples or what each group must prove. Parts are then double-booked for assembly and destructive testing, cavities lose traceability, revisions are mixed, and the build consumes time without closing the decision that justified it.

Plan a pilot from decisions backward. Define product, process, assembly, test, packaging, and release objectives; run under intended serial conditions; allocate uniquely identified samples by cavity, lot, and destination; and give every objective an owner, method, evidence record, acceptance condition, and disposition route. The customer’s requirements determine the actual population — there is no universal pilot quantity.

The useful deliverable is not a pile of samples. It is a traceable matrix connecting each open question to the right production condition, sample population, result, and next step.

What must the pilot validate before any sample is made?

When "validate the part" is the only objective, teams collect unrelated results without knowing which decision they support. Gaps appear after the sample population has been consumed.

Convert every open risk into a specific pilot question and classify it as product, process, assembly, packaging, or decision evidence. Define the requirement, method, population, owner, and pass or disposition rule before scheduling the run.

Identify destructive work first, because it fixes the allocation: parts consumed by testing cannot also become retained masters or assembly-build stock.

Begin with the latest design, process, and program risk records, then interview the functions that will use the output — design, manufacturing, quality, the customer plant, logistics, and purchasing — and do not combine tests merely to reduce sample count when conditioning or destructive work makes the populations incompatible.

Use an objective register as the planning tool, with columns for objective ID, decision question, revision, characteristic, sample source, cavity and lot coverage, preconditioning, method, quantity basis, destructive status, owner, evidence, acceptance authority, and fallback action. For example, 40 clips for mating evaluation and 30 for aged pull testing need separate populations, because aged samples cannot serve as untouched assembly references.

Product evidence

  • Dimensions and geometry; appearance and boundary condition; assembly fit and interface; functional and environmental performance

Process evidence

  • Cavity and cycle stability; material and process traceability; inspection readiness; downstream work and packaging

Decision evidence

  • Issue disposition; deviation authority; retained reference set; named release approval

What are the intended conditions, and what deviations are allowed?

A pilot made with prototype fixtures, extra inspection, different resin, or an alternate press can answer selected questions but may conceal risks in the serial route.

Freeze the intended conditions before the run, compare them line by line with the actual run, document every substitution and temporary control, restrict the conclusion each deviation supports, and plan closure under serial conditions where equivalence is not demonstrated.

A production-representative run should exercise the intended tool, equipment, environment, operators, and cycle. Volvo Group’s public supplier quality manual uses those conditions for its significant production run and says sample quantity depends on the equipment, tooling, and process; the customer’s plan sets the actual quantity and approval route.

Record drawing and CAD revision, tool and cavity IDs, press and auxiliaries, resin grade, color, and lot, drying and regrind rule, process and program revision, operators, fixtures, inspection method, assembly components, and packaging, and freeze those conditions before selecting samples. Keep setup pieces, purges, and short shots traceable but outside the accepted counts.

The full condition-comparison method — classifying each difference as equivalent with evidence, more favorable than serial, less favorable than serial, or not assessed, with the reason, risk, owner, and closure event for every deviation — is set out in Automotive Molding Capacity: What a Run-at-Rate Trial Should Demonstrate. Do not repeat that sheet inside the pilot plan; reference it and complete it once. A temporary 100% visual sort can protect a customer build, but it does not validate a future sampling plan.

How should pilot samples be allocated — and how does the 240-piece example scale?

Sample counts become unreliable when one part is promised to multiple users, destructive tests are not identified, or cavity coverage is decided after the run.

Allocate accepted samples before the run using unique IDs and a ledger. Tie each population to its objective, cavity and lot coverage, conditioning, destination, destructive status, reserve rule, and evidence owner; keep setup and rejected pieces outside accepted allocations.

Illustrative example — assumptions: a four-cavity tool, 240 accepted and traceable pilot pieces after documented setup and stabilization, one material lot, and customer-defined tests. The quantities below demonstrate allocation logic only. They are not PPAP, OEM, or industry minimums.

Sample group Purpose and quantity basis
Dimensional layout — 20 Five identified pieces per cavity. Evidence: report to released drawing and measurement method.
Assembly evaluation — 80 Mating build across agreed part variation; customer build plan. Evidence: fit and issue log and assembly disposition.
Functional and environmental — 60 Preconditioned test groups and controls; test matrix and method. Evidence: sample IDs, conditions, results, and acceptance decision.
Destructive work — 40 Sectioning, force, or other consumed tests; replicates and invalid-test allowance. Evidence: raw data, failure mode, and disposition.
Packaging trial — 20 Pack orientation, handling, and transport simulation; pack quantity and route. Evidence: pack instruction and post-test condition.
Retained set — 20 Controlled reference and issue recheck; retention plan. Evidence: sealed IDs, storage condition, custodian, and expiry or review date.

Use the table by asking whether each row has a justified quantity basis, not whether 240 is appropriate for your program. Five pieces per cavity illustrates a dimensional layout, but a released drawing, customer plan, risk, and statistical method must determine actual coverage.

How to scale the 240-piece allocation to a real program

The 240-piece table is a worked allocation, not a recommended quantity. Scale it by rebuilding each row from its own quantity basis — never by applying a single multiplier to the total.

First, count the decisions, not the parts: every objective needs its own population unless two can demonstrably share the same samples.

Second, scale the dimensional row by cavity. Five pieces per cavity is a coverage choice, not a rule: if the tool has eight cavities, the dimensional population grows if per-cavity evidence is still required, in proportion or by a sampling scheme as the customer plan decides. A single-cavity tool does not need a four-cavity allocation.

Third, scale by variant. Each color, material lot, insert variant, or mating-part combination that must be evidenced is a separate population for the objectives it affects. Two colors do not double every row, but dimensional and appearance rows cannot be shared across a color change, nor functional rows across a material change, unless the customer plan explicitly permits it.

Fourth, let the test method set the functional and destructive rows: replicates, control groups, conditioning batches, and the invalid-test allowance are fixed by the method and the laboratory, not by the pilot total. Fifth, treat assembly and packaging as build-driven — assembly by build combinations and failure-learning allowance, packaging by pack quantity and handling route.

Finally, hold a visible reserve under the same ledger instead of padding every row; drawing on it needs the same authorization as the original allocation.

What does the pilot plan record for each objective?

A calendar and sample total do not define a pilot plan. Without owners, methods, evidence, and release conditions, finished tests can still leave the program unable to decide what happens next.

Build a decision matrix in which every objective has controlled inputs, sample use, quantity basis, method, evidence record, owner, acceptance authority, and release or escalation condition.

Write the plan so every objective has an owner and a decision rule before samples exist, and use the plan table at three reviews: readiness, execution (actual conditions and sample IDs against the planned rows), and closeout (results attached, every exception dispositioned). A row is not complete because samples were shipped; it closes only when the intended evidence exists and the named authority has dispositioned it.

Sequence the populations carefully: capture as-molded dimensions before destructive sectioning, preserve control samples before conditioning, and confirm whether assembly parts will be returned.

Pilot objective Evidence and release condition
Dimension and appearance Released geometry and visual baseline; identified cavity and lot distribution. Evidence: raw data, report, boundary records. Release: disposition of every nonconformance.
Assembly and interface Mating stack and installability; representative build combinations. Evidence: build record, force and fit observations, issues. Release: interface owner accepts or assigns correction.
Functional and destructive Named requirement after conditioning; control and exposure groups. Evidence: traceable laboratory and test record. Release: result meets criterion or approved deviation exists.
Process and traceability Intended route creates identifiable output; full pilot population. Evidence: process, material, cavity, inspection records. Release: unresolved deviations closed.
Packaging and delivery Part condition preserved to use point; complete pack and handling path. Evidence: approved instruction and inspection. Release: damage, contamination, label risks accepted.
Retained references Comparison set; untouched identified parts. Evidence: storage log, photographs if authorized. Release: custodian, condition, replacement rule defined.

How are issues closed without mixing revisions or sample populations?

Pilot results are easily contaminated when failed samples disappear, replacement tests are undocumented, or corrections create a new revision pooled with the original population.

Control every issue and replacement through sample IDs, revision impact, root cause, containment, correction, repeat scope, and authorized disposition. Preserve failed and invalid records, and never combine pre-change and post-change evidence without an approved rationale.

Give every issue an ID, affected sample IDs and cavities, requirement, evidence, containment, owner, due date, and disposition authority. When a correction changes tool steel, process, resin, component, or drawing, state which pilot evidence remains valid and what must be repeated. Do not replace failed data with unplanned "good" samples; if a test is invalid, preserve the invalid record, explain the cause, and authorize the replacement sample set.

Keep retained parts subordinate to released data: a retained sample can clarify appearance or a physical condition, but it cannot authorize an out-of-tolerance dimension or an undocumented design change. Use an issue log linked to the objective register, recording requirement, observed condition, affected cavities and sample IDs, date, material lot, method, containment, cause, corrective action, owner, due date, and authority. Distinguish a true nonconformance from an invalid test; both records remain part of the history.

Perform a change-impact review before rerun: a local steel correction may need only targeted dimensions and mating checks, while a gate, cooling, process-window, or material change can affect warpage, appearance, strength, cycle, and multiple cavities. Update drawings, risk analysis, process documents, inspection instructions, and sample labels. An illustrative scenario: an insert is corrected after the first 120 samples. The remaining 120 are post-change samples under a new tool state and must be evaluated against a revised plan.

Disposition choices

  • Accept to requirement; rework or retest under approved method; correct tool or process and repeat affected evidence; approve time-bounded deviation; reject and reopen design or process decision

Revision firewall

  • No mixed CAD or drawing revisions; no unrecorded material substitution; no pooled unidentified cavities; no reused destructive samples; no changed acceptance rule after seeing results

How does the pilot hand off to a run at rate?

A pilot and a run at rate answer different questions, and the most common planning error is treating one as the other. The pilot proves the right questions were answered under the intended conditions; the run at rate proves the full route can deliver good units at the required rate, through inspection, assembly, and packaging, for a defined scheduled window. Neither substitutes for the other.

Hand the pilot over as evidence, not as a rate claim. Transfer the frozen baseline, the process window, the cavity-level record, the open deviations, and the sample disposition — and let the run at rate be judged on its own capacity math.

The handoff package should contain the baseline sheet, the dispositioned objective register, the sample ledger, the issue log, the process window, and the retained-sample custodian. What it should not contain is a capacity statement: the pilot was not run to demonstrate a scheduled-window rate.

The run-at-rate planning then starts from the demand question in Automotive Molding Capacity: What a Run-at-Rate Trial Should Demonstrate: the required good delivered units per scheduled hour, the demand period, the shift pattern, and the process boundary — molding, inspection, packaging, or assembly. Its arithmetic is the capacity math, not the pilot math: reconcile scheduled time, running time, completed shots, active cavities, gross pieces, holds, rejects, and downstream accepted units, and compare the demonstrated rate with a demand model that uses the same units and applies each loss exactly once. An observed good rate across the scheduled window already contains the observed downtime and rejects, so it must not be multiplied by uptime or yield again.

Three handoff rules keep the boundary clean: no pilot deviation carries forward silently, no open pilot issue is closed by a good rate, and if the tool, process, material, or route changes between pilot and run at rate, the change-impact review decides what pilot evidence remains valid.

What does a bounded pilot decision record?

The phrase "pilot passed" can be misread as approval for production or shipment even when only an assembly build succeeded and process, capacity, packaging, or customer records remain open.

Issue a bounded closeout that identifies represented conditions, completed objectives, sample populations, results, deviations, open actions, and the next activity authorized. Keep pilot acceptance separate from formal customer or production release.

The closeout should state what passed, what remains open, which revision and conditions were represented, which populations were used, and whether the decision releases another validation step, a customer build, limited production, or nothing further. Use the customer’s actual submission and release rules rather than calling an internal pilot "PPAP approved." PPAP is defined by the AIAG Production Part Approval Process (PPAP-4), the industry standard for demonstrating that engineering design record and specification requirements are consistently met during an actual production run. For submission scope and responsibilities, see PPAP for Automotive Molded Parts.

The full release-evidence method — one row per gate, with linked evidence, status, deviation, owner, due date, and approval authority — is set out in T1 Sample Approval vs. Production Release: What Still Needs to Be Closed?. This article does not repeat that matrix; the pilot closeout should point to it. Production release occurs only when all blocking rows are closed or formally bounded, and that decision is recorded there, not in the pilot report.

Prepare a closeout table with one row per objective — condition, sample IDs, evidence, result, exception, disposition, owner, release effect — and a decision statement naming part and revision, tool and cavities, material lot, process state, and pilot dates, and stating what the evidence releases.

Scope boundary: this article is a planning aid, not an OEM approval rule. The released drawing, contract, customer-specific requirements, and agreed validation plan control the actual project.

Pilot Production Run Review

Review area What to confirm before the run
Objectives Every open risk as a question: requirement, method, population, owner, disposition rule
Conditions Intended conditions frozen; deviations recorded with reason, risk, owner, closure event
Allocation Samples allocated by objective, cavity, lot; destructive and retained never shared
Scaling Each row rebuilt from its own quantity basis, not a multiplier on 240
Plan Every objective: inputs, sample use, evidence, owner, authority, release condition
Issues Issue log linked to register; pre- and post-change populations separate; firewall observed
Handoff Baseline, window, cavity record, deviations, disposition transferred; capacity shown separately
Closeout Bounded decision: revision, conditions, populations, results, next activity — not "pilot passed"

Worked Decision Scenario (Illustrative)

An illustrative scenario, with no numerical acceptance value implied beyond the allocation already shown: a Tier 2 supplier plans a pilot for a four-cavity interior trim clip — dimensional layout, assembly build at two mating variants, conditioned functional test, pack trial — allocating 240 accepted pieces as in the table above, then the customer adds a second color. The team does not add a round number: dimensional and appearance populations are duplicated for the new color, the functional row is extended only where the test method requires it, the packaging row is unchanged, and the retained set gains a second-color reference.

Questions to Ask the Supplier

  • Which decisions must this pilot close, and which objective in the register serves each one?
  • What are the frozen intended conditions, and which deviations are already known?
  • How are samples allocated by objective, cavity, and lot, and what does the ledger show for destructive versus retained stock?
  • How was each row’s quantity derived — and what would change it if cavities, variants, or test methods change?
  • What is the stabilization and sampling rule, and are setup pieces outside the accepted allocation?
  • How are issues logged, and what repeat scope follows a tool, process, or material change?
  • What exactly does the pilot closeout authorize, and what remains open for the run at rate and production release?
  • What is in the handoff package, and which pilot deviations carry forward into that trial?

Information to Submit for a Project-Specific Review

  • Released part CAD and drawing, with revision, and the risk and test requirements the pilot must serve
  • Tool and cavity plan, including variants, colors, and material lots in scope
  • Intended production route: press, auxiliaries, operators, fixtures, inspection, and packaging
  • Assembly interfaces, mating parts, and the customer build date the pilot must support
  • Test matrix: methods, conditioning, controls, replicates, and the customer sampling plan
  • Required approval stage and PPAP submission level, where applicable
  • Annual volume and order pattern, so the run-at-rate handoff can be planned from the real demand question

For the wider RFQ inputs around a pilot, see the Automotive Injection Molding RFQ Checklist. For how pilot evidence carries into repeat production, see Keeping Repeat Automotive Molding Orders Consistent with Approved Samples, and for sample report versus first article versus PPAP, see FAI vs. PPAP vs. a T1 Sample Report: What Should an Automotive Buyer Request?. AutoMoldingPro is operated by C.K. MOLD & ENGINEERING LIMITED, which is IATF 16949 certified and ISO 9001 Certified; the IATF 16949:2016 overview describes that framework. For the control plan that carries characteristics, frequencies, and reaction rules into production, see Control Plans for Automotive Molded Parts.

Conclusion

Plan the pilot from decisions backward, allocate every traceable sample once, scale each row from its own quantity basis, and close results against named acceptance authorities. Then hand the evidence — not a rate claim — to the run at rate, and let production release be decided on its own matrix. Provide released CAD and drawings, risk and test requirements, cavity plan, intended route, mating parts, packaging, build date, and approval stage.

References

Facebook
X
LinkedIn

Wait, We Have Something Special for You!

Join our mailing list and receive a 10% discount on your next mold or CNC project.

Request a Quick Quote

Send your drawings and detailed requirements via:
Email: jerry@ckmold.com

Or fill out the contact form below:

We will contact you within one working day. Please pay attention to the email with the suffix “@ckmold.com”