CHANGE PATH / 01
Turn a proposed difference into an explicit decision, not an undocumented exception.
Once a quotation, approved sample, purchase order or quality plan exists, a late substitution can make earlier evidence ambiguous. A compact change-control record preserves the before-and-after versions and leaves the buyer’s permitted next action visible to both sides.
Identify the current controlled baseline
Start with the exact seller, production site, product or SKU, purchase-order number, specification or drawing revision, approved sample, packaging artwork, quality-plan version and delivery assumption now in force. Give the change request its own identifier and record the order quantities or lots it could affect.
Set the original controlled product definition before comparing any proposed change →
ISO 10007:2017 provides configuration-management guidance across a product or service lifecycle. This checklist uses that general control idea to organise buyer evidence; it does not claim that a supplier follows, is certified to or complies with ISO 10007.
Put the original instruction and revision hierarchy into the purchase order →
Classify what would actually change
Use separate fields for product and material changes; dimensions, tooling or process changes; packaging, artwork and labelling changes; factory or critical sub-supplier changes; quantity, timing or delivery-route changes; and changes to certificates, reports or inspection evidence. “No impact” is a conclusion that needs a stated basis, not a default selection.
Mark the proposed effective point: prototype, first production output, a named lot, a dated shipment, or all future orders. If the supplier cannot identify the affected scope, use a hold state instead of allowing the new version to enter production by assumption.
Issue one reviewable change notice
Ask for the current and proposed document IDs and revisions, reason, proposed effective point, affected orders or lots, supplier owner, date, supporting files and supplier acknowledgement. Keep the changed item separate from commercial requests or general progress messages so an approval can be tied to one precise scope.
Record open questions instead of converting them to a pass: whether the approved sample still represents the product, whether test or certificate coverage changes, whether a quality-plan checkpoint must repeat, and whether price or delivery commitments must be revised.
Review the impact before deciding
Compare the proposed version with the buyer’s product, contract and destination requirements. Decide which evidence must be rechecked: a new or retained sample, drawing, bill of materials, packaging proof, test report, inspection method, quality-plan checkpoint, price calculation, delivery point or shipment document.
The ISO committee guidance for ISO 10013:2021 explains the value of retaining documented information to support process operation. Here, the useful record is the evidence and decision trail for this change—not a claim that any particular form, platform or file hierarchy is mandatory.
Recheck whether the approved sample still represents the proposed version →
Map changed evidence to the existing quality-control checkpoints →
Record a buyer-owned decision and the permitted next action
Use a named authorised buyer role and one state: information requested, under review, rejected, approved with conditions, or approved as a new revision. An approval should name the new revision, affected scope, approved evidence, conditions, date and the exact work that may continue.
Supplier acknowledgement confirms receipt of the decision; it does not replace buyer authority. A blanket “approved” label should not silently approve a different material, another factory, new artwork, an additional lot or a later shipment.
Verify the new version at its first relevant checkpoint
Before the affected lot reaches the next hold point, confirm that the actual product, site, packaging and evidence match the approved revision. Preserve the original baseline and change trail; do not overwrite it with the new file or replace an unresolved difference with a revised filename.
Use the defined inspection or evidence event for the specific decision. A change approval does not automatically release production, shipment, payment, contractual delivery or destination-market compliance.
Use an in-process checkpoint for a continue, correct, reinspect or hold decision →
CONTROL TABLE / 02
Minimum fields for a reviewable supplier change notice
| Control area | Record before a decision | Evidence to compare | Hold when |
|---|---|---|---|
| Current baseline | Order, seller, site, product, document IDs and current revisions | PO, approved sample, specification and quality plan | The version now controlling work cannot be identified |
| Proposed difference | Exact before/after field, reason and proposed effective point | Supplier notice, drawings, materials, photos or process records | The proposal is only described in an informal message |
| Affected scope | Orders, lots, products, factory sites and destination assumptions | Production plan, shipment schedule and order quantities | The supplier cannot name what may already be affected |
| Evidence impact | Sample, test, certificate, inspection, packaging and document questions | Current evidence and proposed replacement evidence | Existing evidence does not clearly cover the new version |
| Commercial impact | Price, timing, delivery point and payment implications | Approved quotation, PO and written commercial change | A revised invoice or promise silently changes the order |
| Buyer decision | Authorised role, state, conditions, date and new revision | Written decision and supplier acknowledgement | No authorised buyer decision exists for affected work |
| First verification | Next checkpoint, method, owner and release condition | First-piece, in-process, reinspection or document-review result | The new version cannot be tied to a defined evidence event |
DECISION STATES / 03
Keep proposed and approved changes visibly separate
| State | Minimum record | Permitted next action |
|---|---|---|
| Information requested | Current or proposed version, evidence or affected scope remains unclear | Provide the named information only; do not treat the change as approved |
| Under review | Notice and impact questions logged; buyer decision is pending | Hold affected work unless a separate written instruction permits limited work |
| Rejected | Buyer decision and the reason recorded | Continue only the existing approved baseline or propose a new notice |
| Approved with conditions | New revision, limited scope, evidence and conditions named | Perform only the stated work and complete the named checkpoint |
| Approved new revision | Authorised buyer, new baseline and effective point recorded | Use the new version only for the approved scope, then verify it |
| Hold | Reason, affected lots, containment and escalation owner visible | Do not continue affected work until a new buyer-owned decision is recorded |
METHOD / 04
How this checklist was prepared
Currawong Web’s China-side verification desk checked the official sources below on 2 August 2026. ISO 10007 supports the configuration-management framing across a lifecycle, and ISO 10013 supports retaining documented information to operate processes. The six checks, table and decision states are our buyer-evidence synthesis.
We did not inspect any reader’s supplier, product, contract, order, factory, sample, technical file, destination rules or shipment. This is general evidence-organising guidance, not legal advice, a contract clause, regulatory interpretation, supplier approval, certification, quality guarantee or production/shipment release.
PRIMARY SOURCES / 05
Official sources used for this guide
Links and page content were checked on 2 August 2026. Re-open relevant source material and obtain product-, contract- and jurisdiction-specific advice before a material decision.
- ISO 10007:2017Official ISO record for configuration-management guidance applicable to products and services across their lifecycle; used here only for the general controlled-baseline and change-status framing.
- ISO 10013:2021 — Guidance for documented informationOfficial ISO committee note describing guidance on retaining documented information to support process operation; used here only for the value of a traceable evidence and decision record.
COMMON QUESTIONS / 06
Keep the change record inside its decision boundary
- Does a supplier need buyer approval for every operational detail?
- No universal rule is supplied here. Define which changes require notice and buyer approval in the applicable contract, order and quality plan. This checklist helps make the chosen control point visible.
- Can a chat message approve a change?
- Only if the parties’ own process makes it a traceable authorised decision with the exact revision, scope and conditions. For material changes, a separate controlled record reduces ambiguity.
- Does an approved change prove the updated product is compliant or acceptable?
- No. It only records a decision about a defined change. Product testing, inspection, contractual acceptance and destination-market requirements need their own applicable evidence and review.
- What if production has already started before the supplier gives notice?
- Identify the potentially affected work, preserve the existing evidence, record the access limit and use a hold, containment, review or reinspection decision rather than silently treating the new version as the original baseline.