8D report with AI: template, disciplines and who decides

An 8D report documents how a supplier solves a quality problem in eight disciplines, from forming a team through containment and root cause analysis to corrective action, prevention and closure. Producing an 8D report with AI starts with splitting those disciplines into gathering work, which an agent can prepare, and decisions, which stay with the quality team.

The method comes from the automotive industry and goes back to Ford. Ford now works with a variant called Global 8D, which adds a D0 step for symptoms and emergency response actions, and its customer-specific requirements ask suppliers to deliver an 8D in response to a quality concern. In Germany the automotive industry association VDA published its own 8D volume in November 2018, covering method, process and report.

ISO 9001 does not prescribe a format, but clause 10.2 requires an organisation to react to nonconformities, in the 2015 text explicitly including those arising from complaints, evaluate the cause, take action and review whether the action worked. In the automotive supply chain the 8D report is the usual document that carries this evidence from supplier to customer. IATF 16949 adds clauses on problem solving (10.2.3) and on customer complaints and field failure analysis (10.2.6), and carmakers such as Ford, GM and Stellantis add their own requirements to clause 10.2.

A usable 8D report template records four things per discipline: the content, the evidence, the support the system gives and the person who owns the decision. Customer formats differ in fields and order but not in the disciplines; Ford adds D0, and Stellantis requires suppliers to submit the 8D in its own tracking system.

The last column shows a common allocation of roles. Your quality manual and each customer's requirements take precedence.

An AI agent takes over five jobs that consist of searching, matching and copying between systems. The problem description follows the same rule for an agent as for an engineer: Germany's quality association DGQ advises against copying the customer's complaint text into D2, because the description has to rest on data and facts. The agent therefore builds D2 from system records and shows the source of each statement, such as the batch number from the delivery note or the reading from the inspection record.

Where evidence is missing, the agent drafts the request to the customer or to your own logistics team, for photos, returned parts or a delivery note number, and the request goes out only after release. A published case study at an automotive supplier describes an ERP set-up that would not let anyone start an 8D step before the previous one was complete; the agent enforces the same rule as a completeness check.

Containment (D3), root cause analysis (D4) and the choice and implementation of corrective action (D5, D6) stay with quality engineers and the 8D team. These decisions depend on part analysis, trials and conversations on the shop floor, they commit cost and capacity, and the customer reads them as the supplier's commitment.

A root cause counts in an 8D only once a trial or comparison has proven it. The DGQ describes two common weaknesses: corrective actions whose root cause was never verified, and reports filled in quickly at the end so that the complaint can be closed. An agent that writes fluent D4 text would accelerate exactly that failure. It therefore supplies hypotheses, data and proposed tests and leaves the root cause field empty until the team attaches the evidence.

The VDA states in its 8D volume that deadlines for handing over the report must not lead to an inadequate solution. The agent therefore flags approaching deadlines and prepares the interim status, but it never enters a cause to meet a date. The ISO 9001 Auditing Practices Group makes the same point in its May 2026 guidance for auditing organisations that use AI, which asks auditors to check whether the organisation has defined where AI outputs that affect product conformity need human review.

The customer sets the deadlines, in the supply contract or in its customer-specific requirements. The VDA's 8D volume states that complaint processes usually impose time limits that also apply indirectly to 8D problem solving, even though the disciplines take different lengths of time.

Ford's customer-specific requirements, effective 15 June 2026, ask for a response within 24 hours of the notification, containment at the Ford plant and an 8D covering D0 to D3. Within 15 calendar days the supplier delivers the 8D with a preliminary or verified root cause and a plan for corrective and preventive actions. Stellantis refers suppliers to its own supplier claim procedure and requires the 8D to be submitted in the group's tracking system.

A published case study at an automotive supplier shows a contractual schedule of one day for D1, two days for D2 and D3, 14 days for root cause and corrective action with D6 and D7 defined, and 60 days to closure. Because every customer sets its own values, the deadlines belong in the workflow as a rule per customer and discipline. The agent counts from the notification and escalates before a date is missed.

The 8D report is part of the complaint and belongs in its record in the ERP or quality management system, not in a file attached to an email. That record holds customer, order, delivery, batch and cost, and it keeps the history for the next audit and the next similar case.

The workflow follows the same five steps as any other: intake, context, proposal, release and write-back. The agent reads the notification from the inbox or customer portal, pulls context from the ERP, the quality system and document management, files its draft in the complaint record and, after release, writes back status and report. For data exchange between customer and supplier the VDA has defined QDX, an XML format that covers complaint notices, acknowledgements, 8D reports and warranty and goodwill data, among others; customer portals such as the Stellantis tracking system become one more target system.

Whether to accept, reject or offer goodwill is decided on the case file that the agent assembles in the complaint handling workflow; the 8D answers the technical question of cause and fix. Intake, assessment, KPIs and closure of the wider process are set out in the guide to the complaint management process.

A named person releases everything that reaches the customer, and every version of the report is logged with inputs, sources, changes and release. ISO 9001 clause 10.2 requires documented information on the nature of each nonconformity, the actions taken and the results of corrective action, and the workflow log provides that evidence per case.

In the case study cited above, the customer assistance lead, the quality director and the plant director signed every 8D report, later digitally in the ERP with automatic notifications. That chain stays, and the agent only shortens the way to the signature. The control set for an 8D agent settles five things.

An 8D agent starts in shadow mode: it drafts D2, the evidence pack and the customer letter alongside a team that keeps working as before. The comparison shows, per defect type and customer, where its drafts are accepted unchanged, and only for those defect types does it go on to prepare the full draft. Anything sent to the customer still needs release.

A Workflow Build puts this into production in 8 to 12 weeks in your own cloud tenant, connected to the ERP, the quality system and document management, with no Cortaris platform and no licence. The ten-question workflow check shows whether your 8D process scores well enough on value, feasibility and ownership to be the first workflow.