Time to read: 13 min

The gap between a qualified prototype and a production-ready process is larger than most programs anticipate. A prototype part can pass DVT with flying colors, assemble cleanly at the bench, and clear all functional requirements. Yet it can still generate a yield disaster when tooling runs at production cycle time—when operators follow a work instruction rather than tribal knowledge, and you’re making hundreds of units instead of ten. Pilot production exists to close that gap in a controlled, measurable way before you commit to full production volumes.

Skip or rush the pilot run, and the consequences are often costly and slow to emerge: tooling failures that weren’t visible at low quantities, scrap rates that destroy unit economics, quality escapes that reach customers before incoming inspection catches them. This guide is for engineers and program managers who are serious about reducing that risk—covering how to plan a pilot build, what it needs to validate, and how to define success before results are in.

Manufacturing engineers evaluating pilot run quality
Pilot run quality evaluation


What Is a Pilot Production Run?

A pilot production run is a limited-quantity manufacturing run conducted with full production parameters. It uses production tooling and processes to validate process capability, yield, and documentation completeness before committing to full production volumes.

The distinction from a prototype run is meaningful. Prototype builds, including EVT and DVT runs in consumer electronics programs, are primarily design validation events. Their goal is to confirm the product works. A pilot build (during PVT, or Production Validation Test, in the EVT/DVT/PVT stage-gate sequence) is a process validation event. The design is already approved. What you’re evaluating is whether your manufacturing process can produce conforming parts repeatably, with acceptable yield at rate. Full production is not a validation event—it operates against a baseline the pilot should have established.

A pilot run is also referred to as a pre-production build, pilot lot, or golden lot. In automotive programs, the pilot feeds directly into PPAP. In aerospace, it generates the data required for FAI in accordance with AS9102. The nomenclature varies; the validation logic is consistent.

PrototypePilot ProductionFull Production
PurposeValidate design intentValidate manufacturing processBuild to demand
Typical quantity1–2530–300 (process-dependent)Per forecast
Process parametersDevelopment / approximateFull production parametersFull production parameters
Documentation requiredBOM, drawingsFAI, PPAP or equivalent, process FMEA, control planPer approved control plan
Pass criteriaFunctional and design specsCpk ≥ 1.33, target yield, documentation completeOngoing SPC against control limits


When Do You Need a Pilot Production Run?

A formal pilot is warranted whenever you are introducing meaningful process risk that hasn’t been validated under production conditions. That includes:

New tooling being used for the first time at production parameters. A tool that produced acceptable parts at low pressure and slow cycle time may flash, warp, or hold dimensions outside spec when it runs at full production settings.

A new supplier or manufacturing site, even for an existing design. Process capability is specific to a machine, operator, and facility. Moving production to a new site resets your capability baseline.

Design changes after the last validated production run. Even a minor ECO can affect form, fit, or process yield in ways that don’t appear at prototype quantity.

Regulatory submissions requiring production-process parts. FDA submissions for Class II and above, AS9100-governed aerospace programs, and similar contexts require that qualification samples be built using validated production processes—not from prototype tooling or manual overrides.

Complex multi-component assemblies where interface fits must be validated at production tolerances. Nominal parts assemble. Parts at the edges of their individual tolerances may not—especially across multiple mating features.

High-volume programs where a yield problem at scale is financially catastrophic. A 2% scrap rate is a footnote at 500 units and a budget crisis at 500,000.

A pilot can reasonably be scaled down or skipped for simple machined parts with no design changes being reordered from a qualified supplier with documented process history, or for commodity components where capability data already exists. The question to ask is: where does unvalidated process risk actually live in this program?

What a Pilot Build Should Validate

Process Capability

Cpk and Ppk are not interchangeable. Cpk measures process capability relative to the process mean using short-term variation—it answers whether the process could hold the tolerance if it were centered. Ppk measures overall performance, including mean shifts over time—it’s closer to what a customer will actually see. Both matter in a pilot validation.

For most production applications, a minimum Cpk of 1.33 is the accepted threshold. For safety-critical characteristics—anything that affects product safety, regulatory compliance, or field failure risk—1.67 is the appropriate target. A single FAI measurement tells you what one part looked like; Cpk tells you whether the process that made it is capable of doing that repeatedly.

Identify your critical characteristics and key characteristics before the pilot runs and measure each one across the full pilot quantity. Any characteristic below threshold is a corrective action, not a judgment call.

Cpk values within the process capability limits
Cpk values within the process capability limits

Yield and Scrap Rate

Before the pilot starts, define what acceptable yield looks like. That number needs to be established based on program economics and quality requirements—not reverse-engineered from whatever the pilot produced. Track and categorize every defect during the run: cosmetic, dimensional, functional, assembly-related. Defect Pareto data from the pilot becomes the foundation for process FMEA updates and the incoming inspection plan.

What yield rate is acceptable depends on the program, but the pilot should have a documented go/no-go yield threshold that the team agreed to before the first part ran.

Cycle Time

Confirm actual cycle time against planned cycle time at full production parameters—not the pace the shop ran at during sampling. Cycle time drives unit economics, line capacity, and lead time commitments. A process that runs 20% slower than planned is a program risk that needs to surface at pilot, not after production ramp. If actual cycle time requires process changes, those changes need to be validated before production approval.

Tooling Condition After Pilot Run

Inspect tooling after the pilot run is complete, not just before it. Wear, flash, dimensional drift, and surface degradation that become visible after a few hundred cycles can predict problems that will show up at scale before your planned maintenance interval. Early tooling wear data sets a realistic preventive maintenance schedule. Discovering that a tool degrades significantly after 500 shots at production, when your maintenance plan assumes 2,000, is information you want before you’re at 1,800 shots in a live production run.

Assembly and Interface Fits

For multi-component assemblies, verifying that nominal parts assemble is not sufficient. Pilot validation should include assembly trials using parts from the edges of the measured distribution—parts near the high and low limits of each critical dimension—to verify that production-tolerance variation doesn’t create assembly failures. This is where the work done in statistical worst-case and RSS tolerance analysis pays off in practice: if the analysis was done correctly, the pilot should confirm it. If parts at the tolerance limits fail to assemble, you have a tolerance stack problem that needs to be resolved before production.

Quality Documentation Completeness

The pilot should close out all required documentation before production approval. For automotive suppliers or programs using the AIAG PPAP standard, that means a complete PPAP package at the agreed submission level. For aerospace, FAI documentation per AS9102. For other industries, whatever combination of dimensional reports, material certifications, process FMEAs, control plans, and work instructions is required by the customer or quality management system. “In progress” documentation at production approval is not acceptable. Part of what the pilot validates is whether your quality system is actually ready.

How to Define Pass/Fail Criteria Before You Start

Acceptance criteria defined after results are rationalizations, not acceptance criteria. Every pass/fail threshold for the pilot needs to be documented and approved before the first part runs.

That means critical and key characteristics are called out on drawings with tolerances, Cpk targets assigned by characteristic criticality (1.33 vs. 1.67), a minimum yield threshold for pilot approval, and a defined pilot quantity.

In terms of quantity, 30 parts is the widely cited practical minimum for a valid Cpk study. The reason is statistical—you need enough data points to estimate both the mean and the standard deviation with reasonable confidence, and the resulting capability indices with fewer than 30 parts have wide enough confidence intervals to be misleading. Running 10 parts and calculating Cpk produces a number, but it’s not statistically reliable. For high-risk characteristics or high-volume programs, 50 to 100 parts may be more appropriate. Define the quantity up front based on the statistical validity the program requires, not on what’s convenient or fastest to build.

Document the criteria in a pilot plan that is reviewed and signed before the build begins. When the results come in—good or bad—there is no ambiguity about whether the pilot passed.

Worker performing quality control of manufactured pilot run
Pilot production quality control


Common Pilot Production Failure Modes

  • Pilot quantity too small to surface yield or capability problems. Running 10 parts instead of 30–50 produces a Cpk that looks acceptable and hides the process variation that will appear at volume.
  • Production parameters not used during the pilot. Slower cycle times, manual operator interventions, and “helping” the process through marginal steps are common at pilot—and they invalidate the results. If the process can’t run at production parameters without assistance, that’s a finding, not a workaround.
  • Acceptance criteria are defined after the results are known. A Cpk of 1.28 against a 1.33 requirement is a failure. Deciding after the fact that 1.28 is “close enough” skips the corrective action that would have caught the root cause.
  • Skipping tooling inspection after the pilot run. The pilot run is part of the tool’s life cycle. Inspect after, not just before.
  • Missing corrective action closure before approving production. A CAR that opened during the pilot and was listed as “in progress” at the production approval meeting is an open risk carried into production. Close corrective actions, verify effectiveness, then approve production.
  • Treating a golden sample as a pilot (golden) lot. A perfect sample demonstrates that the design is achievable. It does not demonstrate that your process produces it repeatably. Customer-facing golden samples and pilot production runs serve different purposes and are not interchangeable.

The Pilot-to-Production Transition

A successful pilot doesn’t automatically approve production—it generates the data package that supports a formal production approval decision. Define who has sign-off authority before the pilot begins: typically quality engineering, manufacturing engineering, and program management at a minimum, with customer approval required in some industries.

Pilot data feeds directly into the production control plan and process FMEA. Control limits on SPC charts, inspection frequencies, and reaction plans at production start should all be informed by what the pilot measured. First-off inspection requirements at production start should be defined in the control plan—what gets measured, by whom, and what constitutes a hold condition.

When pilot results are marginal—a Cpk at 1.30 against a 1.33 target, or yield that cleared the threshold by a narrow margin—conditional production approval is sometimes the right call. That means a defined monitoring period, increased inspection frequency, and specific metrics that trigger a production hold if performance degrades. Marginal pilot results are not a reason to ignore the data. They are a reason to approve production with explicit controls and a defined response plan.

A successful pilot also doesn’t guarantee sustained production quality. It validates process capability at a point in time. Production monitoring, SPC, and regular process audits continue after pilot approval because processes drift, tooling wears, and suppliers change things.

How Fictiv Supports Pilot Production Programs

Fictiv’s platform is built to support the full NPI-to-production continuum without a re-sourcing event between phases. DFM feedback is available before tooling is cut, which is where pilot failure risk is most cost-effectively reduced—a tolerance stack or draft angle problem caught in DFM review doesn’t become a pilot failure.

For pilot builds, Fictiv provides platform-integrated quality documentation, including FAI reports, dimensional inspection, material certifications, and PPAP-aligned documentation packages. Suppliers in the Fictiv network have documented process capability, meaning the baseline data required for a valid pilot is available rather than being established from scratch.

When pilot results support production approval, the same supplier and process can scale without the qualification overhead of a new manufacturing partner. That continuity—from prototype through pilot into production—reduces the transition risk that re-sourcing events introduce.

If you’re planning a pilot build or preparing to transition a program into production, get a quote on Fictiv’s platform or talk to a manufacturing expert about your program requirements.

Talk to a Fictiv expert about your project, or upload your parts to start a free quote.

FAQs About Pilot Production

What is pilot production in manufacturing?

Pilot production is a limited-quantity manufacturing run conducted at full production parameters to validate that a process is capable of producing conforming parts repeatably before committing to full production volumes. It uses production tooling, production cycle times, and production operators, and results in a documented pass/fail determination based on pre-established acceptance criteria.

What is a PVT in manufacturing?

PVT stands for Production Validation Test and is the term used in consumer electronics programs for the final stage of the EVT/DVT/PVT development sequence. PVT is the equivalent of a manufacturing pilot: it runs at production parameters using production tooling and is intended to validate process capability and yield rather than product design. A successful PVT is the gate between development and production.

How many parts do you need for a pilot production run?

Thirty parts is the widely cited practical minimum for a statistically valid Cpk study, and therefore the minimum for a meaningful pilot. With fewer than 30 parts, the confidence interval around a capability index is wide enough that the result can be misleading. For high-risk characteristics or high-volume programs, 50 to 100 parts is more appropriate. The right quantity depends on the statistical confidence the program requires and the criticality of the characteristics being validated.

What is the difference between a prototype and a pilot production run?

A prototype build validates design intent—it confirms that the product meets functional and performance requirements. A pilot production run validates process capability—it confirms that the manufacturing process can produce conforming parts repeatably at production parameters. Prototypes are often built with temporary tooling, manual processes, or at reduced cycle times. A pilot uses production tooling and production parameters, and the pass criteria are process-focused: Cpk, yield, cycle time, and documentation completeness.

What should a pilot production run validate?

A pilot production run should validate process capability on critical and key characteristics (Cpk and Ppk against defined targets), yield and scrap rate against a pre-established threshold, actual cycle time versus planned cycle time, tooling condition after the pilot quantity, assembly and interface fits using parts from the edges of the measured tolerance distribution, and completeness of all required quality documentation including FAI, PPAP or equivalent, material certifications, and the production control plan.