Create a quality-control issue response plan for [ISSUE DESCRIPTION]. The affected product, service, or process is [AFFECTED SCOPE], and the evidence currently available is [EVIDENCE]. The applicable requirements are [REQUIREMENTS]. Our operational constraints and risk factors are [CONSTRAINTS AND RISKS]. Do not treat an assumption as a finding. Start with a one-paragraph issue statement that separates verified facts, unknowns, and the customer, safety, regulatory, financial, or operational impact. Then produce these sections: 1. Immediate containment: actions for the next 24 hours, including segregation or hold status, traceability check, customer or downstream impact review, and who may authorize release. 2. Investigation plan: a 5 Whys or fishbone-style analysis covering people, methods, materials, equipment, measurement, environment, and supplier inputs. List evidence to collect for each plausible cause. 3. Corrective action plan: a table with action, accountable owner role, due date, required resources, and completion evidence. 4. Preventive controls: process, training, inspection, sampling, supplier, or system changes that address the root cause rather than only rework the affected unit. 5. Effectiveness verification: measurable acceptance criteria, review date, sample or audit method, and escalation trigger if the issue recurs. Mark any step that requires quality, safety, legal, regulatory, engineering, or customer approval. Do not invent specifications, test results, batch records, root causes, or deadlines. Before answering, check that containment comes before root-cause conclusions and that each corrective action has an owner, evidence of completion, and a verification method. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ISSUE DESCRIPTION] | Describe the observed defect, deviation, complaint, or inspection failure and when it was found. | Final inspection found 14 cartons with incorrect allergen labels on a morning packaging run; no injuries or customer complaints have been reported. |
| [AFFECTED SCOPE] | State the product or process, locations, dates, lots, orders, or customers potentially affected. | Ready-to-eat soup line 2, September 22 run, 1,180 cartons; 240 cartons remain onsite and 940 shipped to three regional distributors. |
| [EVIDENCE] | List verified records, observations, measurements, photos, or reports available so far. | Line clearance checklist, label-printer log, packaging count, retained samples, and photos of two incorrect labels; the cause is not yet known. |
| [REQUIREMENTS] | Provide relevant specifications, procedures, contract terms, standards, or regulatory requirements. | Approved artwork procedure QP-14, customer label specification LS-88, and the facility allergen-control plan. |
| [CONSTRAINTS AND RISKS] | Describe production, safety, customer, staffing, timing, and traceability constraints. | Potential undeclared milk allergen, distributors need instructions today, and lot traceability is available by pallet. |
How to use
- Paste verified facts and label assumptions clearly; do not ask the model to fill gaps in records.
- Have the accountable quality lead confirm containment and release authority before acting on the plan.
- Convert the action table into your controlled CAPA or deviation system, preserving its required approvals and records.
- Follow up with: “Turn the corrective actions into a weekly CAPA review agenda with evidence required for each owner.”
Variations
Supplier defect
Use this when incoming material or a supplier process may be involved.
Prepare a supplier quality issue report for [DEFECT] involving [SUPPLIER MATERIAL OR SERVICE]. Affected scope is [SCOPE], and verified evidence is [EVIDENCE]. Requirements are [SPECIFICATIONS]. Produce immediate containment, traceability questions, a supplier corrective-action request, owner roles, due dates, and acceptance criteria for future receipts. Do not assign supplier fault before evidence supports it. Flag any notification or disposition needing quality, contract, or regulatory approval. Check that each requested supplier response has objective evidence.
Customer complaint
Use this when responding to a reported customer quality problem.
Create an internal investigation and customer-response outline for this complaint: [COMPLAINT]. The affected order or service is [SCOPE], and known evidence is [EVIDENCE]. Relevant commitments are [REQUIREMENTS]. Include empathy without admitting unverified fault, immediate safety or service containment, records to review, owner roles, customer update milestones, and corrective-action verification. Do not invent facts, compensation, liability conclusions, or promises. Check that external wording separates confirmed information from investigation status.
Audit finding
Use this after an internal or external audit nonconformance.
Build a CAPA plan for this audit finding: [FINDING]. The cited requirement is [REQUIREMENT], and current process evidence is [EVIDENCE]. Produce a finding restatement, containment, root-cause questions, corrections, corrective actions, owners, dates, and effectiveness checks. Distinguish correction of the observed instance from corrective action against systemic cause. Do not claim compliance or root cause without records. Check every action has objective closure evidence and an effectiveness review date.
Tips
- Containment protects customers and evidence; do it before debating the most likely cause.
- Separate correction from corrective action: relabeling a carton fixes one unit, while a control that prevents label mix-ups addresses the system.
- Use objective closure evidence such as a completed training record, revised controlled procedure, or audit sample, not “owner confirmed.”
- An effectiveness check needs a pass criterion and a date; a closed action without recurrence monitoring is not proof the cause was addressed.
FAQ
What is the difference between containment and corrective action?
Containment limits immediate exposure, such as holding stock or stopping a line. Corrective action removes the verified cause so the issue does not recur.
Can AI determine the root cause of a quality issue?
No. It can organize an investigation, but root cause must be supported by records, observations, testing, and accountable review.
When should a quality issue be escalated?
Escalate promptly when it may affect safety, legal or regulatory obligations, customers, data integrity, or release decisions. Follow your organization’s approval and notification procedures.