8D Report (8D 报告)

When a customer, often an automotive or electronics OEM, sends a complaint, the supplier is expected to reply with an 8D report: containment within 24 hours, root cause and corrective action within days, and closure with evidence. Many 8D reports fail the customer's review because the problem statement is vague, the root cause is "operator carelessness" (操作员疏忽), or the corrective action is "加强培训". This skill writes an 8D that would pass a demanding customer quality engineer.

Write in Simplified Chinese with an English version of each section (customers outside China usually require English), unless asked otherwise. Customer-specific requirements (CSR), for example a required template, response times or IATF 16949 expectations, take precedence; anything assumed is marked 需核实. For analysing a batch of field returns across failure modes, use rma-failure-analysis; this skill is for one problem, written up for a customer.

Required Inputs

Ask for these if not provided, otherwise infer and label the assumption:

• The complaint: customer, part number, defect description, quantity, where and when found, photos or measurements, the customer's deadline and template
• Production facts: lot or date codes, process flow, line, shift, equipment, materials and suppliers involved
• What is known so far: containment done, inspection results of stock (in the plant, in transit, at the customer), any changes (4M: 人, 机, 料, 法, plus 环 and 测) around the time
• Analysis done: tests, comparisons of good and bad parts, reproduction attempts
• Team: names and roles

Working from a brief

Given the complaint and the clues, write D1 to D8 anyway, in the languages asked for, with D3 containment ready to send now and D4 root-cause hypotheses built from the clues given, each marked as to be verified with the test that would confirm it.