1---2name: assess-recall-and-reporting-obligations-for-product-safety-i3task_id: environmental-esg/assess-recall-and-reporting-obligations-for-product-safety-issue4description: Guides incident response analysis for a product safety issue by mapping recall and reporting obligations across regulatory reporting, public-company disclosure, supply-chain contract, and litigation-hold dimensions rather than treating the matter as a single-agency compliance question.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/assess-recall-and-reporting-obligations-for-product-safety-i8---910# Skill: Assess Recall and Reporting Obligations for Product Safety Issue — Incident Response Memorandum1112## 2. Failure modes the skill is correcting1314- Treating the incident as a single-agency compliance question instead of a coordinated response across product-safety reporting, recall actions, securities disclosure, contract notice, insurance notice, and preservation duties15- Failing to separate what is known from what is still unverified, which leads to overstatement of hazard scope, affected population, timing, or causal attribution16- Missing the different triggers, deadlines, and recipients that govern mandatory reporting, voluntary corrective action, and customer-facing recall communications17- Overlooking tiered responsibility across manufacturer, importer, distributor, retailer, and component supplier, including independent notice and cooperation duties18- Neglecting the immediate preservation duty once litigation is reasonably anticipated, even before liability is confirmed19- Ignoring insurance notice and cooperation requirements that can be forfeited by delay or incomplete reporting20- Presenting conclusions without identifying the governing authority, operative trigger, responsible party, and immediate consequence21- Collapsing multiple agreements or regulatory strands into one generic recommendation instead of tracking each obligation separately2223## 3. Legal frameworks / domain conventions that apply2425- Product-safety reporting regime: identify the governing statute, regulation, or agency rule for the relevant jurisdiction; determine whether the event is a reportable defect, hazard, nonconformance, or serious incident under the controlling standard26- Recall and corrective action rules: distinguish voluntary corrective action from mandatory recall, stop-sale, consumer notice, remedy, and remediation procedures under the applicable product-safety framework27- Public-company disclosure: assess materiality and disclosure timing under the applicable securities law and exchange-filing regime, including the duty to avoid misleading partial disclosure28- Supply-chain contracts: review notice, cooperation, inspection, quality assurance, traceability, indemnity, and recall-cost allocation provisions in the governing agreements29- Distribution and retailer obligations: assess notice, shelf-pull, quarantine, replacement, and customer-contact duties that may be triggered by downstream possession of affected units30- Litigation hold and preservation: once litigation is reasonably foreseeable, preserve relevant documents, test data, complaints, design history, communications, and supplier records under the applicable preservation doctrine and court-rule framework31- Insurance notice: review notice, consent, cooperation, defense, and coverage-allocation provisions; distinguish product-liability coverage from recall-expense coverage and exclusion issues32- Privilege and internal investigation: preserve the ability to investigate while maintaining legal privilege where available, and separate factual preservation from legal analysis33- Causation and scope assessment: use complaint volume, incident severity, batch or lot traceability, and distribution footprint to define the reporting universe and remediation priority3435## 4. Analytical scaffolds3637- Begin with source-document triage:38 - identify the product, defect mode, injury or hazard type, affected units, geography, and timeline39 - distinguish confirmed facts, allegations, testing results, and open questions40 - list the agreements, notices, reports, insurance forms, and internal materials that may be implicated41- Enumerate the relevant entities before analysis:42 - the primary operating entity43 - upstream suppliers or component providers44 - downstream distributors or retailers45 - any insureds, additional insureds, or notice recipients46 - any public reporting entity or parent entity47- For each entity and document set, identify:48 - the legal or contractual trigger49 - the governing authority or clause50 - the deadline or timing anchor51 - the responsible person or role52 - the practical consequence of compliance or delay53- Analyze reporting obligations separately from recall obligations:54 - reporting asks whether the incident must be notified and to whom55 - recall asks what corrective action, notice, replacement, repair, refund, stop-sale, or retrieval is required56 - do not assume that a reportable issue automatically requires the same form of recall57- Test whether the issue is likely to be treated as mandatory or voluntary:58 - mandatory pathways usually hinge on statutory thresholds, agency direction, or defined safety criteria59 - voluntary pathways still require disciplined scope control, regulator coordination, and consumer messaging60- Assess securities disclosure with caution:61 - determine whether the incident is likely material in context62 - check whether the disclosure duty arises from periodic reporting, current reporting, antifraud concerns, or an existing public statement that must be corrected63- Assess preservation immediately:64 - preserve complaint data, design files, test protocols, supplier communications, batch records, corrective-action deliberations, and insurance communications subject to privilege planning65 - identify custodians and implement a litigation-hold notice before routine deletion cycles resume66- Assess insurance and indemnity in parallel:67 - notice to insurers can be required even when liability is disputed68 - indemnity and reimbursement rights against counterparties may coexist with insurance recovery69- For each issue, close the analysis by stating:70 - the governing authority71 - the party that must act72 - the deadline or urgency trigger73 - the downstream operational, regulatory, litigation, disclosure, or cost consequence7475## 5. Vertical / structural / temporal relationships7677- Supply-chain hierarchy matters:78 - reporting and recall duties may run independently at multiple tiers79 - a retailer’s shelf-pull obligations do not eliminate the manufacturer’s reporting duties80 - upstream indemnity rights do not suspend immediate notice duties downstream81- Temporal sequencing matters:82 - preservation duties can arise before any external notice is filed83 - insurance notice may be due before internal causation analysis is complete84 - public disclosure may need to be coordinated with, but not delayed by, regulatory submissions if materiality is present85- Scope must be dynamic:86 - initial scope may be based on a limited lot, model, or shipment87 - later testing or complaint data may expand the affected population88 - the memorandum should reflect that scope can change as evidence develops89- Multiple obligations can coexist:90 - a single incident may trigger reporting, corrective action, consumer notice, contract notice, insurance notice, and legal hold at the same time91 - analyze them as parallel tracks, not as alternatives unless the source materials clearly require a choice92- Where the documents show more than one affected product line, geography, or contract set, analyze each separately rather than using one representative path9394## 6. Output structure conventions9596- Draft as a formal incident response memorandum in an industry-conventional structure, using headings that cover:97 - Executive Summary98 - Facts and Scope of the Incident99 - Regulatory Reporting Analysis100 - Recall / Corrective Action Analysis101 - Contractual and Supply-Chain Obligations102 - Securities Disclosure and Public Statements103 - Insurance Notice and Recovery104 - Litigation Hold and Preservation105 - Recommended Action Plan106- State the governing authority for every legal proposition relied on, by statute, regulation, rule, or recognized doctrine; do not state a conclusion without tying it to the applicable authority107- Where the source documents identify a clause, regulation, or form requirement, quote or paraphrase it carefully without relying on unsupported shorthand108- Separate confirmed facts from assumptions, and identify any material information gaps that affect the recommendation109- For each obligation or issue, include:110 - severity using a consistent ordinal scale defined once at the top111 - legal basis112 - triggering facts113 - responsible role114 - timing anchor115 - consequence of delay or noncompliance116- If multiple parties, products, or periods are implicated, list them explicitly before analyzing them117- End with an explicit Recommended Action Plan that assigns each action to a role and ties it to a deadline, regulatory milestone, or immediate-risk urgency118- Keep the memorandum suitable for delivery as `incident-response-memorandum.docx`