Prototype, Pilot, Mass Production — Can One Control Plan Last All the Way? — Five Steps for CP Three-Stage Evolution

1. A CP Used from Prototype to Mass Production, Resulting in Nonconformity During Factory Audit

A certain automotive parts company compiled a control plan (CP) for a new energy motor bracket project. To save effort, the process engineer created one version during the prototype stage and then only changed the version number and date for "pilot production" and "mass production," keeping the content unchanged. In the third month of mass production, the customer conducted an audit and found a problem: the CP still listed "100% CMM measurement" for critical dimensions, which was impractical for mass production. The production line had to secretly switch to sampling inspection—when the auditor checked the records against the CP, a nonconformity was immediately issued. Even more troublesome was another issue: the press-fit parameter window, which should have been verified during the prototype stage, was not included in the prototype CP because it only copied the inspection items from the mass production mindset. As a result, press-fit defects emerged in the first month of mass production, leading to a batch rework.

During the post-mortem, the quality manager discovered that the team was not incapable of writing a CP; rather, they did not understand one crucial point: there are actually three separate control plans, one for each stage—prototype, pilot production, and mass production. The content of each CP should evolve with the stage, with additions, deletions, and adjustments, rather than being the same document with a different version number.

2. Three CPs, Each Addressing Different Questions

The prototype CP serves "design verification": it uses a small number of prototypes to answer whether the product, as designed, can meet functional requirements. Therefore, it is comprehensive, focusing on design characteristics, functional tests, and 100% measurement. The target audience is the laboratory and the sample line.

The pilot production CP serves "process verification": it uses a pilot production batch to answer whether the process, equipment, and tooling can consistently produce conforming products. It shifts the focus from the product to the process, with equipment parameters, process parameters, and incoming material characteristics gradually being introduced. Special characteristics (SC) and key characteristics (CC) are transmitted from design characteristics to process characteristics, and SPC and poka-yoke are tested in this stage.

The mass production CP serves "daily control": it answers how to maintain quality over the long term at the lowest cost. It retains only the critical few items that have been proven necessary by data, reducing inspection frequency. Poka-yoke and SPC take over daily monitoring, and the reaction plan becomes a commonly used part of the production floor.

In summary: the prototype CP addresses whether the product is correct, the pilot production CP addresses whether the process is stable, and the mass production CP addresses how to maintain quality over the long term. Confusing these three questions can easily result in a CP that is a "mishmash."

The sequence of the three CPs is essentially a step-by-step risk confirmation: design risks not fully verified during the prototype stage must not flow into pilot production; process risks not confirmed during the pilot production stage must not be carried into mass production. The issues left unresolved in the previous CP must be the first items addressed in the next CP.

3. Five-Step Method for CP Evolution Across Three Stages

Step 1: Determine the Stage, Then the Content. Before starting to write, confirm which stage the CP belongs to and write down the questions it needs to answer. All project inclusions and exclusions should revolve around this. The time boundaries should follow the project: the prototype CP should be released before prototype production, the pilot production CP should be released during pilot production preparation, and the mass production CP should be finalized before PPAP submission and mass production start. Do not switch stages based on personal preference.

Step 2: Use Characteristic Lists to Drive Additions and Deletions. What to add and what to delete should be based on characteristic classification rather than personal experience. The prototype CP should cover all design characteristics and functional verification items; during pilot production, use the PFMEA to transmit process-sensitive SC/CC into process parameters and inspection items, refining the "broad and shallow" list from the prototype stage into a "narrow and deep" one; the mass production CP should retain only the critical few. Each addition and deletion should be documented in the change log for traceability.

Step 3: Gradually Upgrade Control Methods and Frequencies. For the same project, the prototype stage uses 100% measurement and functional testing; the pilot production stage uses intensified sampling inspection and SPC trial runs; only in the mass production stage can "reduced frequency" be discussed. Reducing frequency must be supported by data: process capability and measurement system data accumulated during the pilot production stage must prove that the process is stable and the measuring instruments are accurate before 100% inspection can be reduced to sampling inspection based on frequency. For example, a critical dimension is fully measured during the prototype stage, with 5 pieces sampled per batch for monitoring during the pilot production stage. Only when the Cpk is consistently above 1.33 and the control chart is under control can the frequency be relaxed to one piece every 4 hours during mass production. Conversely, new failure modes and added poka-yoke devices identified during pilot production must be included in the mass production CP—this is the easiest part to overlook.

Step 4: Stage Gate Transition Review. Transitioning between stages is not just a matter of changing the version number; it requires a formal transition review. The prototype CP to pilot production CP transition should be reviewed during the prototype summary meeting, and the pilot production CP to mass production CP transition should be reviewed before PPAP submission. The review should focus on three questions: have the issues from the previous stage been closed? Are the additions and deletions supported by data? Have the inspection work instructions, work instructions, and on-site tooling and equipment been updated accordingly? The review conclusions should be documented, so that during future customer audits, a complete chain of evidence can be provided to explain why full inspection was changed to sampling inspection.

Step 5: Controlled Versions, Only the Current Stage Version on the Floor. Each of the three CPs should have its own independent numbering and control, rather than a sequential V1.0, V2.0, etc. Auditors and on-site workers should be able to immediately see which stage's CP is currently in use. When transitioning stages, the old version should be removed, the new version distributed, and training completed. The version hung on the floor must match the controlled version, which is a critical check during factory audits.

4. Three Common Pitfalls

The common root cause of these three pitfalls is treating stage evolution as a document management task rather than a risk management process—no matter how frequently the document is updated, if the risks are not managed, the CP is just a piece of paper.

Pitfall 1: Using the Same Document Throughout. Bringing full inspection items from the prototype stage into mass production can lead to bottlenecks and high costs. The production floor will eventually "find a way around it," and the CP will lose its authority, as seen in the initial case.

Pitfall 2: Only Reducing, Not Adding. When discussing stage evolution, the focus is often on reducing inspection frequency, but new risks and poka-yoke devices identified during the pilot production stage are not included in the mass production CP, thereby increasing the risk exposure.

Pitfall 3: Reducing Frequency Based on Feel. Reducing inspection frequency from 100% to sampling, or from every 2 hours to every 4 hours, without process capability, measurement system, and defect trend data, leaves the company unable to answer the customer's question, "What is the basis for this change?"

5. One-Sentence Summary

A control plan is not a single document with three version numbers but three separate documents that grow with the project stages: the prototype CP for verification, the pilot production CP for confirmation, and the mass production CP for maintenance. Every addition, deletion, and adjustment must be data-driven and reviewed.

A control plan grows with the project stages: the prototype CP for verification, the pilot production CP for confirmation, and the mass production CP for maintenance—every addition, deletion, and adjustment must be data-driven and reviewed.

Knowledge code: 8.3.2

Version: v20260903

Author: QTank QTank is dedicated to providing systematic professional knowledge, methodologies, and practical tools to quality management practitioners, helping companies continuously improve their quality capabilities.