IATF16949 Practical Application (28) | Additional Management Review Inputs: 9.3.2.1 Data Sources, Criteria, and Decision Tracking Table
1. Scenario: Quality Department Can Only Provide Seven of the Twelve Inputs
A certain automotive parts company is undergoing an IATF 16949 recertification audit. The auditor sits down in the management review meeting room and, instead of looking at the meeting minutes, directly asks: "Tell me, for each of the twelve inputs listed in 9.3.2.1, where the data is and who provided it."
The quality manager opens the PPT, the first three pages cover customer satisfaction, goal achievement, and process performance. He stops at the fourth page. Nonconforming quality costs? "Finance has it, but they haven't given it to us." Customer scorecard? "It's in the customer portal, sales reviews it monthly." Warranty performance? "It's in the after-sales system." Actual field failures and their impact on safety? "We didn't have any recalls last year."
The auditor ultimately issues a minor nonconformity, clearly stating: a) Nonconforming quality costs, i) Customer scorecard review, k) Impact of actual field failures, not provided as management review inputs.
In the post-audit review, what truly alarmed the general manager was not this nonconformity, but another issue: the customer scorecard had been in the yellow zone for two consecutive quarters, with deductions mainly due to delivery delays and response times. However, neither of the two management reviews had any resolutions addressing this issue—because the scorecard had never been brought into the meeting.
This is the intent of 9.3.2.1: it is not about adding more PPT slides, but about consolidating data from finance, sales, after-sales, R&D, and planning, using a uniform set of criteria, to the desk of the top management, so they can make decisions during the meeting.
2. What Does 9.3.2.1 Add Compared to ISO 9001
ISO 9001's 9.3.2 c) includes seven vague sub-items (customer satisfaction, goal achievement, process performance and product conformity, nonconformities and corrective actions, monitoring and measurement results, audit results, external supplier performance). IATF 16949's 9.3.2.1 adds twelve items, divided into two directions:
- Breaking down vague items into quantifiable specific items: Process performance → broken down into "effectiveness" and "efficiency"; product conformity is listed separately; external supplier performance is supplemented with warranty, scorecard, and field failure.
- Items unique to IATF, not found in ISO 9001: Manufacturing feasibility assessment, maintenance target performance, warranty performance, customer scorecard, potential field failure identified through risk analysis (such as FMEA), actual field failure and its impact on safety and the environment, and design and development measurement summaries at specific stages.
The original text of the clause (including the l) item added by IATF's approved interpretation SI 16) is listed alphabetically below. This section lists them in the original alphabetical order without consolidation:
| Item | Key Points of 9.3.2.1 | Corresponding ISO 9001 Item |
|---|---|---|
| a) | Nonconforming quality costs (internal and external nonconformity costs) | No direct correspondence |
| b) | Measurement of process effectiveness | 9.3.2 c) 3) Process performance |
| c) | Measurement of process efficiency, if applicable | No direct correspondence (SI 10 explicitly states that not all processes require efficiency measurement) |
| d) | Product conformity | 9.3.2 c) 3) |
| e) | Manufacturing feasibility assessments for existing operations changes, new facilities, or new products (see 7.1.3.1) | None |
| f) | Customer satisfaction (see ISO 9001 9.1.2) | 9.3.2 c) 1) |
| g) | Performance review against maintenance targets | None |
| h) | Warranty performance (if applicable) | None |
| i) | Customer scorecard review (if applicable) | None |
| j) | Identification of potential field failures through risk analysis (such as FMEA) | None |
| k) | Actual field failures and their impact on safety or the environment | Partially corresponds to 9.3.2 c) 1) Stakeholder feedback |
| l) | Summary of measurements during specific stages of product and process design and development, if applicable (added by SI 16, derived from 8.3.4.1 Monitoring) | None |
Among the twelve items, the quality department can independently provide data for only b) and d), plus parts of f) and j), totaling about four items. The other eight items are owned by finance, sales, after-sales, R&D, equipment, and planning. This is the structural intent of the IATF clause: the management review is a comprehensive quality meeting, not a performance review for the quality department.
Two supporting clauses must be considered together to ensure a closed loop:
- 9.3.1.1 Management Review—Supplement: Management reviews should be conducted at least annually.
- 9.3.3.1 Management Review Output—Supplement: When customer performance targets are not met, the top management must develop and implement a documented action plan.
The second clause highlights a common weakness in many companies—scorecards dropping to the yellow zone, PPM exceeding standards, and delivery performance not meeting targets. If any of these "customer performance targets not met" conditions are true, there must be a documented, action-oriented, and implemented plan, not just a vague "continue to monitor" in the meeting minutes.
3. Deliverable One: Function Data Source Comparison Table for the Twelve Inputs
This table is the backbone of the entire implementation. The left column lists the clause items, and the right four columns answer "who provides, where the data comes from, what criteria are used, and what thresholds are watched." Companies can directly use this table as a division of responsibilities for management review inputs.
(1) Four Items in Financial and Operational Terms
| Input Item | Responsible Function | Data Source and Criteria | Threshold/Key Points | Common Errors |
|---|---|---|---|---|
| a) Nonconforming Quality Costs | Finance (Cost Accounting) + Quality Engineer Verification | Internal nonconformity costs = scrap + rework and repair labor hours + sorting + line stoppage for judgment + re-inspection + deviation concession handling; External = customer claims + return transportation + on-site service travel + warranty (if listed separately, avoid double counting) + customer fines/line stoppage loss allocation + third-party sorting. Only nonconformity costs are counted, not preventive or appraisal costs | Nonconformity costs as a percentage of sales, common range for automotive parts is 1.5% to 4%; a quarter-over-quarter increase of over 20% must be attributed | Using the quality department's budget as nonconformity costs; mixing preventive/appraisal costs; double counting warranty in after-sales and finance |
| d) Product Conformity | R&D/Process (characteristics criteria) + Laboratory (data) | Conformity items/inspected items, statistics divided into three layers: customer special characteristics, internal key characteristics, and routine characteristics; data sources are PPAP full-size reports, annual full-size and functional tests, COP tests | Special characteristics conformity rate must be 100%, any nonconformity enters the review agenda | Reporting only the total number without layers, special characteristics deviations are averaged out |
| b) Measurement of Process Effectiveness | Process Owners (R&D, Procurement, Planning, HR, Customer Service, Finance report individually) | Effectiveness = target achievement rate. Each process must have at least one effectiveness indicator, such as procurement = supplier on-time delivery rate, HR = key position staffing rate, customer service = 24-hour response rate | Achievement rate <90% or a consecutive two-period decline is listed as an agenda item | Quality department filling in all processes; reporting only achievement without trend |
| c) Measurement of Process Efficiency (if applicable) | Process Owners + Finance | Efficiency = resource input per unit output, such as labor hours per piece, processing days per purchase order, processing cost per work order. SI 10 explicitly states that not every process requires efficiency measurement; the organization should determine which processes need it | Selected processes must provide a "why it was chosen," and unselected processes must have a justifiable reason | A blanket requirement for efficiency indicators across the entire company, leading to fabricated data |
(2) Four Items in Customer and Market Terms
| Input Item | Responsible Function | Data Source and Criteria | Threshold/Key Points | Common Errors |
|---|---|---|---|---|
| f) Customer Satisfaction | Sales/Customer Service | OEM satisfaction scores + number and categories of complaints, trends divided into product, delivery, service, and price | Focus on trends and sub-items, not the overall score; a consecutive two-period decline in any sub-item is an agenda item | Reporting only a single comprehensive score of 92, unable to identify where the decline occurred |
| i) Customer Scorecard Review | Sales (data retrieval) + SQE (quality items) | Original scorecard from the customer portal, list each deduction point, deduction score, responsible department, and consecutive periods | Yellow zone for two consecutive periods or red zone for one period, a documented action plan as per 9.3.3.1 must be formed | Focusing only on the overall score ranking; deductions not assigned to responsible departments; treating the yellow zone as "okay" |
| h) Warranty Performance | After-sales/Customer Service | Claim rate, IPTV (failures per thousand units), cost per unit warranty, top 3 failure modes; view separately for 3/6/12 MIS windows | 12 MIS IPTV year-over-year increase of over 15%, or a single failure mode exceeding 30% is an agenda item | Reporting only the total amount without failure modes; mixing old and new batches, making it impossible to identify deterioration |
| k) Actual Field Failures and Safety/Environmental Impact | After-sales (collection) + R&D (analysis) | Field failure list: failure modes, batches, traceability intervals, whether they involve safety characteristics, and whether customer notification is required; linked with 8D and recall assessments | Any failure involving safety characteristics, even one, is an agenda item, with no threshold set | Counting only the number without assessing safety impact; failure items not entered into the analysis ledger |
(3) Four Items in R&D and Operations Terms
| Input Item | Responsible Function | Data Source and Criteria | Threshold/Key Points | Common Errors |
|---|---|---|---|---|
| e) Manufacturing Feasibility Assessment | Process/Manufacturing Engineering + Planning | Trigger conditions: new project quotation, engineering changes leading to cycle time changes, order volume exceeding approved capacity by 15%, new shifts or facilities, key equipment failure and resumption. Output three numbers: available capacity (units/shift), peak demand, and capacity margin = (available - demand) / demand | Capacity margin <10% is yellow, <0 is red and must be addressed in the meeting (investment, subcontracting, or order rejection) | Only done during new project quotations, no re-evaluation after production starts |
| g) Performance Against Maintenance Targets | Equipment/Process | MTBF, MTTR, planned maintenance completion rate, unplanned downtime hours; compared against the maintenance targets set at the beginning of the year | Planned maintenance completion rate <85% or a year-over-year increase in unplanned downtime of 20% is an agenda item | Reporting only the number of maintenance work orders, no targets for comparison |
| j) Identification of Potential Field Failures | R&D (DFMEA) + Process (PFMEA) | Items in FMEA with severity (S) ≥9 and occurrence (O) ≥2, list failure modes, detection methods, and on-site detectability (whether the customer can detect it during use) | Items with S≥9 and undetectable on-site, all listed for review | Directly exporting a 600-row table from FMEA, equivalent to not reporting; should prioritize the top 20 items based on S×O |
| l) Design and Development Stage Measurement Summary | R&D/Project Manager | Three sets of numbers for each stage: time (on-time milestone achievement rate), cost (development budget execution rate), feasibility (stage gate re-evaluation conclusion); data source is APQP stage review records | Milestone achievement rate <80%, or any stage gate conditionally passed, is an agenda item | Reporting only "project on schedule" without data support |
After compressing the twelve items into one table, the division of labor in the meeting can be as follows: finance handles a, R&D handles d/e/j/l, sales handles f/i, after-sales handles h/k, process owners handle b/c, and equipment handles g. The role of the quality department (or system engineer) shifts from "preparing all materials" to "setting criteria, verifying consistency, and compiling the input package"—this is the most critical change needed for the implementation of 9.3.2.1.
4. Deliverable Two: Compilation Rules and Timeline for the Input Package
The twelve items are not twelve PPT slides. Follow the timeline and four-part template below to keep the entire input package within 6 to 8 pages.
(1) Timeline (with Review Day as T)
| Node | Time | Action | Responsible Person |
|---|---|---|---|
| T−20 | Working Day | Issue input notification, attach annual criteria explanation and template (once criteria are set, they cannot be changed privately within the year) | System Engineer |
| T−12 | Working Day | Data freeze day: finance closes accounts, current scorecard from customer portal, current data from warranty system are based on this day's snapshot | Functional Data Owners |
| T−8 | Working Day | Each function submits the input package, overdue submissions are recorded as "missing" in the completeness rate | Functional Heads |
| T−5 | Working Day | Reconciliation: cross-departmental verification of the same indicators (nonconforming costs vs. financial accounts, PPM vs. customer data), differences >10% must be explained in writing | System Engineer + Finance |
| T−3 | Working Day | Draft decisions: write each agenda item as "what to decide + three options + cost/resources," with a maximum of 8 items | Management Representative |
| T−1 | Working Day | Send the input package and draft decisions to attendees; lack of a record of sending one day in advance is considered incomplete input | System Engineer |
(2) Fixed Four-Part Template for Each Input
- Current Value and Trend: Current number + last three periods' numbers, one line graph is enough, no need for detailed charts.
- Comparison with Targets and Previous Periods: Achievement rate, year-over-year, quarter-over-quarter, use three colors to highlight (green = achieved and trend is flat or rising, yellow = not achieved but trend is improving, red = not achieved and trend is declining).
- Deviation Attribution (one sentence): Do not write "multiple reasons," it must be a verifiable cause, such as "A customer orders concentrated from September, changeover frequency increased from 4 times per week to 11 times."
- Suggested Decision (three options + cost): For example, "① Add an online inspection device for 1.8 million yuan; ② Add one final inspection personnel for 120,000 yuan annually; ③ Negotiate with the customer to relax appearance judgment, risk: increased complaints." Inputs without the fourth part are considered invalid.
(3) Three Characteristics of Invalid Inputs
- Numbers without judgment: A fully green table means no issues, turning the review into a clapping session.
- Issues without options: Presenting "we need to pay attention" without options is equivalent to pushing the decision back to the boss.
- Criteria inconsistent with previous periods: Changing the statistical scope distorts the trend, which is worse than not reporting.
5. Deliverable Three: Decision Tracking Table (14 Fields)
The most expensive cost of a management review is not the half-day meeting, but the resolutions that remain unimplemented in the minutes. The table below turns "resolutions" into verifiable items, with 14 fixed fields, consistent format throughout.
| # | Field | Filling Rules | Example |
|---|---|---|---|
| 1 | Decision Number | Annual-sequential number, e.g., R-2026-03, continuous with the previous period | R-2026-03 |
| 2 | Source Input Item | Must fill the letter item from 9.3.2.1 to ensure traceability | i) Customer Scorecard |
| 3 | One-sentence Issue | Clearly state the gap, no emotional language | A customer's delivery performance has been in the yellow zone for two consecutive periods |
| 4 | Decision Type | Choose one: Resource / Procedure Document / Organizational Capability / Technical Product | Resource |
| 5 | Decision Content | Start with a verb, must be actionable | Add a second shift logistics scheduling position |
| 6 | Responsible Position | Specify the position, not the department | Planning Department Supervisor |
| 7 | Deliverables | Must be tangible items | Job description + scheduling table + launch notification |
| 8 | Completion Deadline | Specific date, no "as soon as possible" | 2026-12-15 |
| 9 | Required Resources/Cost | People, money, equipment, specify the source | 1 person at 120,000 yuan annually, budgeted for 2027 |
| 10 | Verification Method | Data to prove effectiveness | Delivery performance monthly achievement rate ≥95%, for two consecutive months |
| 11 | Verifier | Separate from the responsible person | Customer Service Manager |
| 12 | Status | Not started / In progress / Pending verification / Closed / Overdue | In progress |
| 13 | Closure Date | Actual closure date, leave blank if not closed | — |
| 14 | Recurrence Mark | Whether it is a recurring issue, fill in the original number if yes | No |
Three Hard Conditions for Closure (all must be met):
- Deliverables Exist: The items listed in field 7 must actually exist and be retrievable.
- Evidence of Effectiveness: Field 10's indicators must have at least one complete measurement cycle's data to support effectiveness. Claiming effectiveness on the day of document change does not count.
- Verifier's Signature: The verifier and the responsible person must not be the same, to prevent self-verification.
9.3.3.1's Red Line for a Specific Item: Any issue related to "customer performance targets not met" (scorecard yellow/red, PPM exceeding standards, delivery performance not meeting targets) must result in a documented action plan and implementation. These items are marked with "CP" in the tracking table and are prioritized during audits. The assignment logic mentioned in the previous article for resolving red/yellow scorecards is reflected in fields 2, 6, and 10 of this table—without these fields, the red/yellow scorecards cannot be resolved.
6. Effectiveness Measurement: Four Indicators to Quantify the Usefulness of the Meeting
The management review itself needs to be reviewed. Use the following four indicators to calculate trends annually and include them in the first page of the next year's input package.
| Indicator | Formula | Target | Red Line | Data Source |
|---|---|---|---|---|
| Input Completeness Rate | Actual timely submissions / Required submissions (12 items as a base, adjusted for applicability) | ≥95% | <85% indicates a failure in the system's input mechanism | Input notification recovery records |
| Decision Closure Rate | Number of closed decisions / Total decisions from the previous period | ≥80% (within 6 months) | <60% indicates a lack of resource support for decisions | Decision tracking table |
| Recurrence Rate of the Same Issue | Number of issues that reappear in consecutive periods / Total issues from the previous period | ≤10% | >25% indicates a failure in root cause analysis | Field 14 of the tracking table |
| Resource Fulfillment Rate | Actual allocated amount / Approved amount | ≥90% | <70% indicates that review decisions lack budgetary constraints | Financial budget execution table |
Add one observation value, no target set: Decision Density = Number of effective decisions / Meeting hours. Industry practice typically sees 2 to 4 effective decisions per hour; fewer than 1 decision per hour suggests the meeting is just reading reports. This number should not be used for performance evaluations but to assess whether the meeting format needs to be changed.
Among the four indicators, the most revealing is the Recurrence Rate of the Same Issue. The same failure, the same customer complaint, the same delivery delay appearing year after year indicates that decisions are made annually but never translated into deliverables and verifiers—fields 7, 10, and 11 remain empty, making the table useless.
7. Audit Evidence: How 9.3.2.1 Will Be Questioned
IATF auditors typically do not check whether a meeting was held but instead trace 3 to 4 input items. The following five questions cover most on-site inquiries.
| Audit Question | Desired Evidence | Typical Reasons for Not Answering |
|---|---|---|
| How are nonconforming quality costs calculated? What is the difference with the financial report? | Calculation criteria document + reconciliation table with financial accounts | Only a self-estimated number from the quality department |
| Which resolution did the last customer scorecard deductions lead to? | Original scorecard + corresponding row in the tracking table + deliverables | Scorecard only in sales, not brought to the review |
| How do you decide when capacity is insufficient? | Manufacturing feasibility assessment records + decision items (investment, subcontracting, or order rejection) | Only done once during the quotation stage |
| How many items in the FMEA with S≥9 have resulted in actual field failures? | Potential failure list + actual failure analysis report + safety impact assessment | Each table in a different department, no one has combined them |
| How many decisions from the last review were closed? Why were the others not closed? | Tracking table + closure evidence + overdue explanation | Minutes only state "continue to monitor" |
A practical approach: make this table the cover page of the input package, and annotate the corresponding evidence file numbers behind each input. When the auditor asks the first question, you open the evidence directory, not the PPT.
8. Implementation Points and Common Errors
Implementation Points:
- Change the division of labor first, then the template. Eight of the twelve items are not owned by the quality department; without changing the division of labor, no matter how beautiful the template, it cannot be filled out.
- Set criteria once a year. The criteria for nonconforming costs, IPTV, and process effectiveness must be set and published at the beginning of the year; changing criteria mid-year destroys trends.
- There must be a data freeze day. Without a freeze day, each department will refresh data in the week before the meeting, leading to inconsistencies.
- Each input must include decision options. Three options + cost is the most effective way to turn "reporting" into "requesting."
- Separate the verifier from the responsible person. Self-verification is the primary cause of loop failure.
- 9.3.3.1 should have a separate register. The action plan for customer performance targets not met should have a separate number and management, which is a mandatory audit item.
Common Errors:
- Treat 9.3.2.1 as "adding twelve more PPT slides." The result is double the number of pages, but no additional decisions.
- Uniform efficiency measurement. SI 10 clearly states that not every process requires efficiency indicators; forcing all to compile data will lead to data quality collapse.
- Focus only on the total score of the scorecard. A total score of 85 may seem good, but all deductions are in delivery, leading to lost orders next year.
- Double-counting warranty and nonconforming costs. The same claim counted in both finance and after-sales inflates nonconforming costs and misguides decision-making.
- Confuse potential failures with actual failures. The former comes from FMEA analysis, the latter from returned field items; they must be reported separately.
- Evaluate capacity only during quotations. A 30% increase in orders after production starts, with no re-evaluation, leads to negative capacity margins and delivery failures.
- No maintenance targets set for the year. Without targets, there is no "comparison," and item g) is directly void.
- Resolutions only state "strengthen/attach importance/continue to monitor." These terms cannot pass the deliverables check in field 7 of the tracking table and should not be included in the minutes from the start.
The output of the management review is not a set of minutes but a series of verifiable decisions. The value of the twelve inputs in 9.3.2.1 lies not in meeting the clause requirements but in bringing the financial accounts, sales scorecards, after-sales failure items, and R&D feasibility conclusions to the same table on the same day—only then can the top management see where to allocate resources.
Twelve inputs, eight functions, one table to close the loop
Knowledge code: 2.1.2
Version: v20261009
Author: QTank QTank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.