Change Review as a Formality, Resulting in Failures? —— CCB Change Review Five-Step Method, Welding the Quality Gate onto the Change Process

In an automotive parts company, the customer's drawing changed the bracket installation hole from φ8.5 to φ9.0. Technician Xiao Wang initiated an engineering change according to the procedure. The review meeting lasted only 15 minutes: the design team said, "The drawing has been changed," the process team said, "Just adjust the drilling program," and the quality engineer asked, "Do we need to verify?" but was rebuffed with, "It's a minor change, no need to make it so complicated." The production and procurement teams remained silent throughout, and everyone signed off. Two weeks later, during batch installation, it was discovered that the stamping die's locating pin was still φ8.5, the supplier's welding fixture had not been synchronized, and the inspection gauges were still the old specifications—over a thousand work-in-progress items had to be reworked, nearly causing a production halt at the customer's end.

This scenario is not uncommon in manufacturing. Many companies do have change reviews, but these meetings often become mere "notification sessions" or "signing sessions": the process is completed, but the quality control is not. In well-managed companies, the review meeting is the most stringent quality gate in the quality management system (QMS); in poorly managed companies, it is just a piece of paper filled with signatures. This article will explain the five-step method for ensuring that every change truly "passes through the gate": how to classify changes, what to review, who should oversee, and how to track.

1. Change Review: The Easiest Quality Gate to Become a Formality

Design changes and process changes are the riskiest stages in the product lifecycle. The essence of a change is "one move, all affected": changing a hole diameter can impact the mold, tools, inspection gauges, suppliers, inventory, work-in-progress, and even delivered products. Failures typically occur in three areas:

1. Document Closure Break: The drawing has been changed, but the work instruction, control plan, FMEA are still the old versions, and the production floor operates according to the old documents.
2. Verification Closure Break: Design changes are made without verification, and process changes are made without first article inspection, leading to direct batch switching, where issues are only discovered by the customer.
3. Information Closure Break: Changes in one area are not communicated to others; design changes are not notified to procurement, and process changes are not communicated to suppliers, with each person only seeing their own part of the process.

Why is the review meeting a quality gate? Because it is the first place where change information is "centrally exposed" and the only time all stakeholders sit at the same table. Systems like IATF 16949 have clear requirements for change control: changes after production part approval must be notified to or resubmitted to the customer as required. The review meeting is the tool to implement these requirements. If the gate is not held firmly, changes become "implement first, review later," and problems seep into the production floor from the source.

2. CCB Change Review Five-Step Method

Step 1: Change Classification, Separate Minor and Major Changes

The first step in the review is not to hold a meeting, but to classify the change. The change request form should clearly state five elements: the object of change, the content of change (before and after comparison), the reason for change, the initiator, and the expected implementation date. Changes are then classified into three levels based on their impact:

• A Level (Major): Changes affecting product function, safety, regulatory requirements, customer-specified characteristics, or key interface dimensions. These must go through a full CCB review and be reported to or resubmitted for PPAP according to customer agreements.
• B Level (General): Changes affecting assembly, appearance, or process parameters but not involving key characteristics. These go through an internal CCB review and are filed with the customer.
• C Level (Minor): Changes that do not affect the product's form, fit, or function, such as drawing corrections or annotation improvements. These can be reviewed and filed within the department without much ado.

Misclassification can have serious consequences: over-classifying minor changes leads to resource waste and backlog, while under-classifying major changes can plant hidden risks. Xiao Wang's case is a typical example of "under-classifying a major change"—the hole diameter is an assembly interface dimension, involving fixtures, inspection gauges, and supplier coordination, but it was treated as a minor change and hastily approved. The basis for classification is not "how many words were changed," but "how significant the impact is."

Step 2: Impact Analysis, Thoroughly Check Each Affected Area

Impact analysis is the "ammunition" for the review meeting. If it is not thorough, the review is just a formality. It is recommended to use a "Change Impact Analysis Form" and check each area in two dimensions:

• Object Dimension: Drawing, BOM, DFMEA/PFMEA, control plan, work instruction, inspection specification, packaging specification—determine whether each is affected and how.
• Resource Dimension: Fixtures, molds, inspection gauges, equipment programs, materials and inventory, work-in-progress, suppliers, delivered products, customers—confirm each item.

The most common failures occur due to three items often overlooked in the list: inspection gauges—changes in the drawing often lead to overlooked adjustments in go/no-go gauges, inspection gauges, and coordinate measuring machine (CMM) programs; suppliers—changes in purchased parts are not communicated, leading to suppliers supplying parts according to the old drawings; work-in-progress and inventory—no clear breakpoint, resulting in a mix of old and new states, making traceability impossible.

Impact analysis should also be linked with FMEA: are the characteristics involved in the change covered in DFMEA/PFMEA? Have the severity and occurrence changed? Is it necessary to update the FMEA or adjust the control plan? Bringing FMEA into the analysis can reveal many hidden impacts. The analysis form should be distributed 24 hours before the review meeting, allowing each specialist to fill it out in advance rather than thinking on the spot.

Step 3: Conducting an Effective Review Meeting, Each Role Should Come with Conclusions

CCB (Change Control Board) members typically include: design, process, quality, production, procurement/SQE, equipment, project or sales, and sometimes the customer if customer requirements are involved. The review meeting is not a place for "on-the-spot thinking," but for "on-the-spot decision-making"—each specialist should come with their assessment conclusions, and the meeting should focus on three questions:

1. Verification: Have the verification tests for design changes been conducted? What about the sample data? Have the trial production and first article inspection for process changes been completed? Without verification data, the change is just a "gut decision."
2. Breakpoint: To which batch will the old state be consumed? From which batch will the new state be switched? How will work-in-progress, inventory, and in-transit materials be handled? Without a clear breakpoint, mixed batches are inevitable.
3. Synchronization: When will the files, fixtures, inspection gauges, programs, and suppliers be updated? Who is responsible for monitoring?

Quality should have a veto power in the review meeting: if verification has not been done, the breakpoint has not been set, or synchronization has not been arranged, quality can refuse to approve the change—this is the purpose of the gate. In Xiao Wang's review meeting, the quality engineer's question, "Do we need to verify?" was dismissed, indicating that the company's quality team lacks veto power, making the review meeting a mere formality. The meeting minutes must clearly state: conclusions, conditions, responsible persons, and completion deadlines.

Step 4: Approval and Issuance, Conclusions Must Be "Executable"

Review conclusions fall into three categories: approved, to be executed immediately according to the plan; conditionally approved, with a list of conditions that must be verified before approval; and rejected, requiring additional analysis or verification before re-evaluation. These three conclusions should be documented in a change notification (ECN), which includes: change content, effective breakpoint, list of affected documents, execution plan, and verification requirements.

The scope of issuance should be "all at once": internal departments, suppliers, and customers (as per agreement). Many companies only issue ECNs to design and process teams, leaving procurement, SQE, and warehouses unaware, and thus suppliers and inventory are neglected. After the notification is issued, the recipient must confirm receipt, not just assume they know.

Step 5: Tracking and Closure, Verification Loop Must Be Closed

Approval of a change is just the beginning; execution tracking is the main part. Create a change execution tracking form: document updates, fixture modifications, inspection gauge replacements, program changes, supplier synchronization, first article verification, and personnel training. Each item should have a responsible person and a completion date, and be checked off at each milestone.

Change closure must meet three conditions: 1) the first article or verification data is qualified; 2) all documents, fixtures, inspection gauges, and programs are synchronized; 3) the new state is confirmed to be in normal production on-site. If any of these conditions are not met, the change cannot be closed. During the initial period after batch switching (usually 1-2 weeks), stricter monitoring should be implemented to ensure the new state is stable before returning to normal control. After closure, the impact analysis form, review minutes, verification report, and ECN should be archived for future traceability and audits.

Xiao Wang's company later rebuilt its process using this method: the hole diameter change was reclassified as a B-level change, and the impact analysis form listed 12 affected items, including inspection gauges, molds, supplier fixtures, and inventory breakpoints. The quality team exercised its veto power at the review meeting, requiring 50 pieces to be trial-produced before batch switching. The ECN was sent to procurement and suppliers with individual confirmations. The second similar change, from initiation to batch production, took only ten days, with no rework required.

3. Five Common Misconceptions

• Misconception 1: Implement first, review later. The change has already been made, and the review meeting is just a formality, making the gate ineffective. The correct approach is "review first, implement later," even for urgent changes, which should follow a fast track and be fully documented afterward.
• Misconception 2: Review only what has been changed, not the impact. An empty impact analysis form is equivalent to no review.
• Misconception 3: Inspection gauges and suppliers are always overlooked. These two items contribute to the majority of change failures, and the impact analysis form must have fixed sections for them.
• Misconception 4: Conditional approval without tracking. Conditions listed in the meeting minutes are not followed up, leading to "default satisfaction." The condition list must be included in the tracking form.
• Misconception 5: First article qualification means everything is fine. Without tracking and reporting to the customer after batch switching, small batch issues can escalate into major customer complaints. Verification should cover "first article + initial batch period," and reports should be made to the customer as per the agreement.

4. In a Nutshell

Change review is not a signing ceremony but a quality gate—classification, analysis, review, issuance, and closure. Completing these five steps ensures that every change is truly controllable.

Change review as a formality, resulting in failures—classification, analysis, review, issuance, and closure, five steps to ensure the quality gate for changes is firmly held.

Knowledge code: 8.4.1

Version: v20260828

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