product-safety-incidentlisted

# Product Safety Incident Response Step-by-step protocol from detection of a product safety issue to case closure. Time-critical: missed notification deadlines = criminal liability in most jurisdictions. ## Incident Response Flow ```dot digraph { rankdir=TB; node [shape=box style=rounded fontsize=10]; detect [label="1. DETECT\nCustomer complaint, QC fail,\nauthority notice, media report"]; triage [label="2. TRIAGE (24h)\nIs this a safety issue?\nSeverity assessment"]; contain [label="3. CONTAIN (24-48h)\nSales stop, quarantine stock,\nwarehouse hold"]; assess [label="4. RISK ASSESS\nSeverity x Probability\nmatrix"]; notify_auth [label="5. NOTIFY AUTHORITIES\nCPSC 24h / Safety Gate 10 days\n/ OPSS"]; notify_chain [label="6. NOTIFY SUPPLY CHAIN\nDistributors, retailers,\nmarketplaces"]; action [label="7. CORRECTIVE ACTION\nRecall / repair / refund /\nwarning / modification"]; notify_consumer [label="8. NOTIFY CONSUMERS\nDirect + public notice"]; rca [label="9. ROOT CAUSE ANALYSIS\nWhy + how to prevent"]; close [label="10. CLOSE\nEffectiveness check +\nfinal report"]; detect -> triage -> contain -> assess -> notify_auth -> notify_chain -> action -> notify_consumer -> rca -> close; } ``` ## Step 1: Detection Sources | Source | Typical Signal | Urgency | |--------|---------------|---------| | **Customer complaint** | Injury report, burn, allergic reaction, electric shock, choking near-miss | IMMEDIATE if injury | | **Quality control** | Batch test fail