A supplier can say that a line stopped and a revised production date will follow. That update may be accurate, but it does not tell the buyer what actually happened to the order. Was the interruption limited to one machine or a full line? Which work order, product revision, lot, cartons, or in-process units were affected? Were units put on hold? Is the issue an equipment fault, material shortage, quality stop, utility event, or an unconfirmed problem? A structured incident record should come before a broad recovery promise.
China supplier production interruption incident record is a controlled record of an event that interrupts a defined supplier process and may affect a buyer order. It identifies when the event was detected, the affected supplier site, work order, line or process, product scope, quantity status, immediate containment, linked evidence, responsible owner, and next update point. It does not prove a cause, repair, product conformity, schedule outcome, compliance, insurance claim, technical suitability, or shipment release.
Current 21 CFR 211.192 requires, in its pharmaceutical context, review of production and control records before release and thorough investigation of unexplained discrepancies or specification failures. It requires a written investigation record with conclusions and follow-up.1 NIST describes maintenance work orders as records used to track equipment health status, capture faults and failures, and document repairs or solutions.2 NIST also describes its research on maintenance strategies as aimed at improving reliability and minimizing unplanned downtime in manufacturing systems.2 These sources do not prescribe an incident form for general China suppliers. They support a buyer practice: record known facts when the interruption is reported, identify the scope and containment status, preserve relevant production or maintenance evidence, and keep facts separate from a suspected or confirmed cause.
Define what triggers an incident record
An incident record should begin when an event may affect a buyer order, not only after the supplier has confirmed a delay. Define practical triggers in the supplier communication plan. The trigger does not decide the severity of the event. It tells the supplier when to create a factual record and notify the buyer contact.
| Trigger | Initial record should state | Do not assume |
|---|---|---|
| Equipment fault | Line or equipment reference, time detected, and work scope | The equipment caused a product defect |
| Material shortage | Material reference, affected work order, and current balance | The supplier cannot source replacement material |
| Quality stop or hold | Hold ID, quantity, product scope, and status | The goods are nonconforming |
| Utility interruption | Affected area, duration if known, and product status | The event has a fixed schedule impact |
| Data-system or record interruption | System or record function affected and manual control status | Data has been lost |
| Staffing interruption | Process scope and current operating status | Individual employment details are relevant |
| Tool or fixture issue | Tool reference, process, and affected units | Tool change or repair is approved |
| Supplier-defined line stop | Event description, scope, and owner | The event fits a preselected category |
Use a short definition: a production interruption is an event that stops, restricts, or places uncertainty around a defined production or packing activity. Keep safety or emergency response instructions in the supplier’s own safety procedures. The buyer record should focus on order scope and evidence.
Capture the incident header while facts are fresh
The initial report does not need a full root-cause analysis. It needs a stable identity and basic facts. A missing detection time, work-order reference, or product revision makes later review much harder, especially if the supplier updates the schedule several times.
| Header field | Example record | Buyer purpose |
|---|---|---|
| Incident ID | Supplier or joint reference | Connects later evidence to one event |
| Detection time | Date, local time, and time zone | Shows when the supplier identified the event |
| Reporter and owner | Supplier role and contact | Identifies who can update the record |
| Supplier site | Factory, building, or defined area | Locates the affected operation |
| Buyer order reference | PO, work order, or release ID | Connects incident to buyer demand |
| SKU and revision | Controlled product reference | Prevents mixing product baselines |
| Line or process | Assembly line, test station, pack-out area, or other scope | Defines where interruption occurred |
| Current status | Stopped, restricted, on hold, resumed with restrictions, or unknown | Distinguishes fact from forecast |
| Next update time | Supplier-stated checkpoint | Prevents open-ended status messages |
The record should preserve the first reported facts even if later information changes the story. Add a dated update rather than silently replacing the first version. This is especially useful when a line restarts while some in-process units remain under review.
Identify the affected product and quantity scope
A line stop can affect more than the quantity already produced. It may involve components issued to the line, in-process units, packed cartons, finished goods awaiting handover, or units already placed on a quality hold. Ask the supplier to define the category and unit of measure rather than send one unexplained total.
| Quantity category | Supplier evidence | Buyer question |
|---|---|---|
| Units in process | Traveler, work order, or station record | What phase were units in when work stopped? |
| Finished but not packed | Production or inspection status | Are units available, held, or under review? |
| Packed but not handed over | Packing list or carton record | Which cartons are linked to the incident? |
| Material issued | Kit or issue record | Is the material still identifiable and controlled? |
| Units on hold | Hold or nonconformance reference | What decision remains open? |
| Rework pending | Rework authorization and status | Has the buyer-approved path been defined? |
| Supplier-stated unaffected output | Separate production scope | What evidence supports the separation? |
| Shipment allocation affected | Partial-shipment or cargo record | Which current or future release may change? |
Do not use the incident report to decide whether a product is acceptable. The report should say whether the supplier has restricted a known scope and which evidence is linked to it. Inspection, engineering, quality, and release decisions remain separate.
Record containment before discussing root cause
At the beginning of an interruption, the buyer needs to know what the supplier did to control the affected scope. Containment can include stopping the line, placing identified goods on hold, preserving machine or process settings, separating cartons, pausing a shipment allocation, or keeping related records available. It does not require the supplier to claim it knows the cause.
| Containment item | Record request | Boundary |
|---|---|---|
| Line status | Stop time, restriction, or restart status | Does not establish a repair was successful |
| Product hold | Hold ID, quantity, and location or system status | Does not determine final disposition |
| Material or component control | Identified material or kit status | Does not prove material quality |
| In-process unit control | Traveler or station reference | Does not prove unit conformity |
| Carton or pallet segregation | Package range and location reference | Does not prove cargo count |
| Preservación de evidencia | Photo, controller log, work order, or record link | Does not verify authenticity alone |
| Shipment pause | Affected allocation or handover reference | Does not cancel a booking or release |
| Communication owner | Supplier role and next update time | Does not make a buyer decision |
NIST notes that maintenance work orders can track health status, capture faults or failures, and document repairs or solutions.2 When equipment is involved, the buyer can request the relevant work-order reference and status. A buyer should not diagnose the machinery or prescribe repair actions unless it has a qualified role and agreement to do so.
Separate facts, hypotheses, and confirmed conclusions
An incident report becomes unreliable when a supplier presents an early opinion as a confirmed cause. Use simple labels. The supplier can state what it observed, what it suspects, what is still being checked, and what it later confirms through its own process.
| Record layer | Appropriate content | Avoid |
|---|---|---|
| Observed fact | Machine stopped, power alarm appeared, product was placed on hold | Calling an observation a confirmed cause |
| Immediate effect | Defined line stopped; specified work order was affected | Claiming the whole factory is delayed without evidence |
| Containment | Supplier stopped line and recorded hold scope | Describing containment as final corrective action |
| Suspected cause | Supplier-stated hypothesis under review | Treating a hypothesis as fact |
| Investigation reference | Internal investigation or maintenance work-order ID | Copying unsupported conclusions into buyer records |
| Confirmed conclusion | Supplier’s documented conclusion when available | Technical validation by an unqualified buyer |
| Follow-up action | Supplier-stated repair, review, or record update | Assuming the action resolved product risk |
| Schedule effect | Current estimate and next review point | Promising a recovery date without evidence |
Section 211.192 illustrates this separation in a pharmaceutical setting by requiring written investigation conclusions and follow-up for unexplained discrepancies or failures.1 For general sourcing, the buyer can use the same practical idea without applying pharmaceutical requirements: keep the initial report factual, link later findings, and maintain a change history.
Link the interruption to related evidence
A production interruption may connect to several existing controls. A buyer should not ask the supplier to repeat every record in the incident report. Instead, use identifiers and links that connect the interruption to the relevant work order, quality hold, maintenance record, production traveler, packing record, or future recovery plan.
| Related evidence | Why link it | Do not replace it with |
|---|---|---|
| Production traveler | Shows process phase and unit or run context | A general chat message |
| Maintenance work order | Records equipment fault and repair activity | An unsupported statement that the machine is fixed |
| Hold or nonconformance record | Identifies restricted goods and status | A line-stop title alone |
| Rework authorization | Tracks any controlled rework path | An assumption that rework is acceptable |
| Inspection evidence | Shows a separate check or result | An incident record as proof of product conformity |
| Packing list or carton range | Connects packed goods to shipment scope | A total order quantity |
| Partial-shipment allocation | Shows release or cargo effect | A revised delivery date alone |
| Production schedule update | States revised milestone information | A substitute for immediate incident facts |
This linkage avoids a common mistake: treating a new date as the whole answer. A schedule update is useful after the supplier understands the operational event. It should not erase what goods, equipment, or records were affected at the time of interruption.
Set an update cadence without promising recovery
A supplier may not know when the line will resume. The buyer can still ask for a next update time, evidence expected at that update, and the owner responsible. This maintains communication without creating a false commitment.
| Update point | Supplier should provide | Buyer review focus |
|---|---|---|
| Initial notification | Incident header, affected scope, and containment | Is the order and process scope clear? |
| First evidence update | Maintenance or production-record reference and current status | What facts changed since initial notice? |
| Quantity update | Hold, good output, rework, packed, and open quantity scope | Does the quantity reconciliation remain coherent? |
| Schedule update | Supplier-stated milestone effect and assumptions | Is this a forecast or a committed agreement? |
| Closure proposal | Supplier conclusion, follow-up, and linked records | Are open issues identified rather than hidden? |
| Post-closure review | Recurrence or preventive action evidence where agreed | Does not determine supplier performance alone |
The cadence can differ by product risk, schedule urgency, and buyer agreement. The value lies in defining the next evidence point, not in requiring a universal number of updates.
Keep interruption records separate from recovery plans
A production delay recovery plan asks how the supplier intends to catch up. An interruption incident record asks what happened, what is affected, and what evidence exists now. Both may be needed, but they should not be merged.
| Incident record | Recovery plan |
|---|---|
| Identifies event, time, scope, containment, and owner | Identifies proposed capacity, milestones, backlog, and revised plan |
| Preserves facts and linked evidence | States forward-looking supplier assumptions |
| May remain open while cause is investigated | May change as production conditions change |
| Captures holds, in-process units, and package scope | Explains how supplier expects to meet future demand |
| Does not promise a new date | May include a supplier-stated target date |
| Supports a controlled history | Supports an operational planning discussion |
A buyer should request a recovery plan only after it has enough incident information to understand what needs recovery. Otherwise, a supplier may issue a date without a clear basis.
Supplier request wording and FAQ
For [PO or work order, SKU and revision, supplier site, line or process, incident ID, detection time, and affected shipment or allocation], provide a production-interruption incident record. State the observed event, current line status, known affected quantity and unit, product or carton scope, hold or segregation status, immediate containment, responsible supplier owner, linked traveler or work-order evidence, relevant maintenance or quality-record reference, and next update time. Keep observed facts, suspected cause, confirmed conclusion, repair action, rework decision, and schedule impact separate. Preserve record revisions and open exceptions. Buyer review does not establish root cause, engineering adequacy, product conformity, compliance, insurance, final schedule, or shipment release.
What is a China supplier production interruption incident record?
It is a controlled report of an event that stops or restricts a defined production or packing activity. It identifies the order scope, current quantity status, containment, evidence references, and next update rather than only providing a revised delivery date.
Is an incident report the same as a production delay recovery plan?
No. The incident record captures what the supplier knows about the interruption now. A recovery plan describes how the supplier expects to address backlog or revise milestones. Use both records when both questions matter.
What quantity should the supplier report first?
Ask for the quantity categories the supplier can identify at the time: units in process, finished but not packed, packed but not handed over, issued material, held goods, rework pending, and supplier-stated unaffected output. Keep unverified quantities visible rather than forcing a total.
Does an equipment work order prove the product is acceptable?
No. A maintenance work order can show that the supplier recorded a fault and repair activity. It does not establish product conformity or final release.
Should the buyer require a root-cause conclusion in the first update?
No. The first update should separate observed facts from any hypothesis. The supplier can link its later conclusion and follow-up record when its process provides them.
Make the operational event visible before the schedule changes
China supplier production interruption incident record gives buyers a factual starting point when a line stops or an order is restricted. The supplier identifies the event, order scope, affected quantity, containment, evidence references, and next update. Later maintenance, quality, rework, schedule, and recovery records can link back to the same incident without changing the first known facts.
Start with a short incident template for a production line, work order, and package or shipment scope. Agree the trigger, first-notice fields, evidence links, revision method, and update owner before an interruption occurs. This approach makes a supplier’s schedule update easier to assess because the buyer can review the operational record behind it.
Supplier Ally can help buyers organize incident records, supplier status communication, work-order and packing evidence, hold and rework follow-up, recovery-plan coordination, and cargo handover documentation. For engineering, safety, technical, legal, insurance, regulatory, product-compliance, or final release decisions, use the appropriate qualified owner before acting.
ES 
EN 