Supplier Quality Improvement Project (QIP) Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: A supplier quality improvement project (QIP) page is not the slogan "we help suppliers improve quality". The page should state: how QIP differs from 8D/SCAR, scorecards, supplier development, COPQ and VA/VE; how a project is selected and chartered (problem statement, scope, baseline, target, business case, sponsor/team, supplier commitment); how baseline and target are defined (metric definition, data window, PPM/FPY/scrap/line stop/warranty, capability, target and deadline); how root cause and actions are verified (stratification, 5Why/fishbone, process audit, error-proofing, process/tooling/inspection change); how investment/resources/benefits are calculated (tooling/equipment/training/testing, cost sharing, COPQ reduction, avoiding double counting with price/VA/VE); how to validate and close (run-at-rate, capability, 3–6 months of data, audit, PPAP/PCN, sustainment); governance, ethics and public boundary. On the rules: the CPC Central Committee and State Council's Quality Power Construction Outline calls for stronger total quality management, improved industrial-chain/supply-chain quality and quality improvement/reliability; MOF Internal Control Application Guideline No. 7 (Procurement) requires supplier selection/evaluation, acceptance, payment and records; No. 16 (Contract Management) requires quality/breach/claims/change/archive handled per contract and authority. This article is current to 2026-11-10 and is a summary of public rules and page method, not quality/procurement/audit advice; the company's quality system, supplier agreements and project data control.

This article is for quality, supplier-quality (SQE), procurement, R&D, production, finance and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a supplier quality improvement project (QIP) page. The usual gap is "8D treated as QIP, cherry-picked baseline, arbitrary target, actions that only add inspection, unclear investment and benefit, validation on one batch, rebound after closure", ending with a page that only says "continuous improvement, quality enhancement", while customer audits/supplier reviews/cost accounting still disagree.

How does this page relate to 8D/SCAR, scorecard, supplier development, COPQ, VA/VE and contract pages?

The QIP page answers "how to turn a quality issue into an improvement project with target, investment and validation"; the 8D/CAPA page answers "containment, root cause, corrective action and report for a complaint/nonconformity"; the supplier scorecard page answers "QCDS scoring, rating, allocation and improvement trigger"; the supplier development/sourcing page answers "new supplier development, audit, trial production and nomination"; the COPQ page answers "how quality loss is classified/collected/calculated"; the VA/VE page answers "design/process cost reduction"; the contract/quality-agreement page answers "quality responsibility, claims and change". QIP is the main page for "improvement projects" and cannot be replaced by 8D or a scorecard.

Common breaks: 8D treated as QIP; cherry-picked baseline; arbitrary target; actions only add inspection/sorting; unclear investment and benefit; validation on one batch; rebound after closure; supplier does not invest; cost sharing unclear. The page separates "relationship—selection—baseline—actions—investment—validation—governance—boundary" so quality/SQE/procurement/R&D/production/finance share one vocabulary.

Page relationships are editorial; the company's quality system, supplier agreements and project data control.

How should QIP selection and chartering be accepted?

Selection sources should include at least: COPQ/scrap/rework/line stop/warranty, customer complaints/returns/audit findings, PPM/FPY/first-pass yield, supplier scorecard, process capability/process audit, major change/new-project ramp-up. The charter should state at least: problem statement (what/where/when/how much), scope (product/line/supplier/boundary), baseline, target, business case (quality/cost/delivery/risk), sponsor, project manager, team (SQE/procurement/R&D/process/supplier/finance), timeline, resources, supplier commitment. Select by impact × feasibility, not "whichever supplier is easiest".

Acceptance checks: selection source; prioritisation; problem statement; scope; baseline/target; business case; sponsor/team; timeline/resources; supplier commitment; charter approval. Common gaps: no data-based selection; scope too broad; vague problem; no sponsor; supplier does not agree; no resources.

Selection/chartering are editorial; the company's quality system, supplier agreements and project governance control.

How should baseline and target be defined to be reproducible?

The baseline should state at least: metric definition (PPM/FPY/first-pass yield/scrap rate/rework rate/line-stop minutes/warranty rate/COPQ), formula, data source (MES/QMS/inspection/finance/customer), statistical period, sample size, denominator, exclusion rules, measurement-system/basis changes. The target should state at least: target value, relative improvement, deadline, milestone targets, leading/lagging indicators, validation method. The baseline should be stable and comparable, not the best month; the target should combine history, benchmark, process capability/entitlement, not guesswork; if the metric changes, recalculate the baseline and document it.

Acceptance checks: metric definition; formula; source; period/sample; denominator/exclusion; measurement system; target/deadline; milestones; validation; change record. Common gaps: unclear definition; cherry-picked data; changing denominator; inconsistent measurement; unsupported target; no milestones.

Baseline/target are editorial; the company's metric basis, quality records and finance data control.

How should root cause and improvement actions be accepted?

Root cause should include at least: data stratification (product/batch/shift/equipment/material/people/customer), 5Why/fishbone/fault tree, process audit/flowchart, hypothesis testing (DOE/trial/comparison), root-cause confirmation (reproducible/closable). Actions should include at least: error-proofing/automation, process parameters/tooling/mould, material/supplier process, inspection/sampling optimisation, training/work standard, control plan/SPC; each with owner, deadline, validation method, risk/side effect. Prefer "eliminate root cause/error-proof" over "add inspection/sorting/rework"; containment may remain but cannot be the only action. Process/material/drawing changes follow PCN/PPAP/customer approval.

Acceptance checks: stratified data; root-cause tools; verification/reproduction; action type; error-proofing first; owner/deadline; validation method; risk; change approval. Common gaps: gut-feel root cause; inspection only; no owner; no validation; unapproved change; side effects ignored.

Root cause/actions are editorial; the company's quality tools, change control and customer requirements control.

How should investment, resources and benefits be accepted?

Investment should include at least: tooling/equipment/mould, testing/trials, training, travel/on-site support, systems/data, buyer support resources; state who invests, when, asset ownership, and what happens on failure/exit. Benefits should include at least: COPQ reduction (scrap/rework/line stop/warranty/claims), price/cost improvement, capacity/delivery improvement, reduced customer fines/audit risk; state formula, baseline, period and finance confirmation. Cost sharing should be fair and executable, not all pushed to the supplier; benefits must not double count with price negotiation/VA/VE/COPQ. Guideline No. 7 requires price/contract/acceptance/payment and records control; benefits need a finance basis.

Acceptance checks: investment list; investor; asset ownership; failure handling; benefit type; formula/baseline; finance confirmation; cost sharing; double counting; payback. Common gaps: unclear investment; all on supplier; arbitrary benefits; double counting; finance does not agree; no exit.

Investment/benefits are editorial; the company's budget, finance basis and supplier agreements control.

How should validation, closure and sustainment be accepted?

Validation should include at least: run-at-rate/small-batch/mass-production validation, process capability (Cp/Cpk), 3–6 consecutive months of data, audit/layered audit, customer complaints/returns, PPAP/PCN/customer approval (where change is involved), measurement system. Closure should include at least: target achieved, data validated, documents updated (control plan/FMEA/work standard/inspection spec), training, sustainment plan (SPC/error-proofing/layered audit/monthly review), owner, closure approval. Closure is not "the meeting ended"; it needs ongoing data and a sustainment mechanism; rebound needs a trigger/restart rule. Guideline No. 16 requires quality/breach/change handled per contract and authority; claims/chargeback follow the quality agreement.

Acceptance checks: validation plan; run-at-rate; capability; 3–6 months data; audit; customer confirmation; document update; sustainment; closure approval; rebound rule. Common gaps: one batch only; insufficient data; documents not updated; no sustainment; rebound after closure; no restart rule.

Validation/closure are editorial; the company's quality system, customer requirements and supplier agreements control.

How should governance, ethics and the public boundary be accepted?

Governance should include at least: sponsor/project manager, stage gates (charter/root cause/actions/validation/closure), monthly/quarterly review, cross-functional team (quality/SQE/procurement/R&D/process/production/finance/supplier), escalation path, documents/version, lessons learned. Ethics should include at least: do not force unreasonable investment on the supplier, do not use QIP as a price-cutting pretext, do not fabricate data/benefits, do not unilaterally appropriate supplier improvements, respect IP/confidentiality. The public page explains method/process/roles/validation/boundary, and does not publish supplier/customer names, specific defects/batches, project benefits/investment, contracts/prices, audit reports or system screenshots.

Acceptance checks: sponsor/stage gates; review; cross-functional; escalation; documents; lessons; ethics; public boundary. Common gaps: no sponsor; no stage gates; no review; QIP as price cut; data fabrication; sensitive information published.

How should the website page be written, and what must not be published?

Suggested sections: (1) QIP positioning/relationship with 8D, scorecard, supplier development, COPQ, VA/VE; (2) selection/chartering; (3) baseline/target; (4) root cause/actions/change; (5) investment/benefits/sharing; (6) validation/closure/sustainment; (7) governance/ethics; (8) contact window/update date. The public page explains "method, process, roles, validation, boundary" and does not publish specific suppliers/customers, defects/batches, investment/benefits, contracts/prices, audit reports or system screenshots. The English page should use consistent terms (supplier quality improvement project, QIP, baseline, target, root cause, error-proofing, run-at-rate, process capability, cost sharing, closure, sustainment) and state the cut-off date.

Do not turn the QIP page into a "zero defect/quality up X%" slogan, and do not claim "supplier bears all/invests everything" if it is unproven or unfair. The page should let quality/SQE/procurement/R&D/finance judge "whether the project should be done, whether baseline/target are credible, whether actions are effective, whether investment/benefits are reasonable, and when it can close".

Go-live acceptance checklist

Ten checks: positioning/relationship; selection/chartering; baseline/target; root cause/actions; change control; investment/benefits/sharing; validation/closure; sustainment/rebound; governance/ethics; public boundary. Each needs evidence and a review date. The pass standard is not "there is a QIP template", but that quality/SQE/procurement/R&D/finance can judge whether the project is valid, the data credible, the actions error-proofing, the benefits finance-confirmed and the closure supported by ongoing data.

Before go-live, run a tabletop exercise on a real (redacted) project: selection → charter → baseline → root cause → actions → investment → validation → closure, simulating "metric basis change", "supplier unwilling to invest", "actions only add inspection" and "rebound after closure", to see whether the page and process work.

The acceptance list is editorial; the company's quality system, supplier agreements and project governance control.

Who should read it, who should not, and what decisions does it support?

For quality, SQE, procurement, R&D, process, production, finance and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "8D as QIP, cherry-picked baseline, arbitrary target, inspection-only actions, unclear investment/benefit, rebound after closure". Not for teams without supplier quality improvement management, or that want one page to replace quality/procurement/audit advice.

Read it if: building a QIP page; only "continuous improvement"; 8D as QIP; unclear baseline; unsupported target; inspection-only actions; unclear investment/benefit; no sustainment. Not suitable if: treating "QIP" as "8D"; "improvement" as "more inspection"; "benefit" as "price cut"; "page" as "quality system/audit conclusion". Supports: positioning/relationship, selection/charter, baseline/target, root cause/actions, investment/benefits, validation/closure and public-boundary self-checks.

FAQ

What is the difference between QIP and 8D/SCAR?

8D/SCAR handles a complaint/nonconformity that already happened: containment, root cause, corrective action, report and closure; QIP turns one or more quality issues into a project with baseline, target, actions, investment, validation and sustainment, with a longer cycle, cross-functional team and possibly supplier investment/process change. 8D can feed a QIP but cannot replace it; not every 8D needs a QIP.

How does QIP relate to supplier development and the scorecard?

Supplier development/sourcing manages "how a new supplier/category is developed, audited, trialled and nominated"; the scorecard manages "QCDS scoring, rating, allocation and improvement trigger" for existing suppliers; QIP manages "an improvement project for a specific quality issue". Scorecard/COPQ/audit findings can trigger a QIP; QIP results feed back into the scorecard and allocation. They are not the same table.

How should baseline and target be set credibly?

The baseline states metric definition, formula, data source, statistical period, sample size, denominator, exclusion rules and measurement system; choose a stable, comparable period, not the best month. The target combines history, benchmark, process capability/entitlement and customer requirements, with target value, improvement, deadline, milestones and validation method; if the metric changes, recalculate the baseline and keep a record.

How can actions be validated as more than temporary sorting?

First confirm the root cause (stratified data, 5Why/fishbone, process audit, trial/comparison), then select actions, preferring error-proofing/process/tooling/material over inspection/sorting; each action has owner, deadline, validation method and side-effect assessment. Validation uses run-at-rate/small-batch/mass production, process capability, 3–6 months of data, audit/customer confirmation; changes follow PCN/PPAP/customer approval.

How should investment and benefits be calculated and shared?

Investment lists tooling/equipment/testing/training/on-site support/systems, stating who invests, asset ownership and failure/exit handling; benefits list COPQ reduction, price/cost, capacity/delivery and risk reduction, with formula, baseline, period and finance confirmation. Cost sharing should be fair and executable, not all on the supplier; benefits must not double count with price negotiation/VA/VE/COPQ.

When can a project close, and how is rebound prevented?

Closure requires target achievement, 3–6 consecutive months of data, process capability/audit/customer confirmation, document updates (control plan/FMEA/work standard/inspection), training and a sustainment plan (SPC/error-proofing/layered audit/monthly review), plus closure approval. Closure is not "the meeting ended"; it needs ongoing data and a rebound trigger/restart rule, with escalation on rebound.

Should the website publish QIP projects/suppliers/benefits?

Usually not specific suppliers/customers, defects/batches, investment/benefits, contracts/prices, audit reports or system screenshots; it can publish QIP method, process, roles, baseline/target principles, validation/closure requirements, governance/ethics and update date. The goal is to let customers/suppliers understand the improvement method, not to disclose supplier issues and company benefits.

One-sentence takeaway

The supplier quality improvement project (QIP) page on a Changzhou manufacturer's website is not a "continuous improvement" slogan; it is about turning the relationship with 8D/scorecard/supplier development/COPQ/VA/VE, selection/chartering, baseline/target, root cause/actions, change control, investment/benefits/sharing, validation/closure/sustainment, governance/ethics and public boundaries into a checkable list, so quality/SQE/procurement/R&D/finance can judge whether the project is valid, the data credible, the actions error-proofing, the benefits confirmed and the closure supported by ongoing data.

Research method and limitations

This article is a summary of public rules and page method, not quality/procurement/audit advice. It uses no unpublished company supplier/customer names, defects/batches, investment/benefits, contracts/prices, audit reports or system screenshots; the tables and acceptance items are editorial and not quality/procurement/audit conclusions. The CPC Central Committee and State Council's Quality Power Construction Outline, MOF Internal Control Application Guideline No. 7 (Procurement) and No. 16 (Contract Management) are public sources; the company's quality system, supplier agreements and project data control. This article does not decide whether any specific baseline/target/benefit is reasonable, and does not promise "zero defect/quality improvement percentage"; companies should set them item by item based on product, supplier, customer requirements and finance basis.

Sources and basis

Current to 2026-11-10; the official pages below control.

1. CPC Central Committee and State Council, Quality Power Construction Outline (6 February 2023): The State Council of China. Stronger total quality management, improved industrial-chain/supply-chain quality, quality improvement and reliability; used for the QIP policy context and improvement direction.
2. MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Supplier selection/evaluation, acceptance, payment and records; used for QIP supplier evaluation, acceptance and records requirements.
3. MOF Internal Control Application Guideline No. 16 — Contract Management (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Contract performance, change, disputes and archive; used for handling quality agreements, changes and claims/chargeback in QIP.