Turn an NCR into a CAPA / 8D draft — human approves disposition and closure

Problem

On a small shop floor an NCR is easy to open and easy to close. The part is out of tolerance, a customer sends a return, or incoming inspection stops a lot. Someone writes a line, picks rework or scrap from habit, and dates the record closed so the job can move. The requirement that failed, the reason the process made the part, and the reason inspection missed it stay in people's heads.

The same defect then returns with no earlier decision on file. A customer asks for an 8D and the team rebuilds the story from email. A supplier lot goes back with no request for a cause. Auditors find NCRs closed the day they were written. This pattern drafts the missing packet from a complete NCR. People still decide. It does not replace your quality procedure, and it has not been timed or tested in a shop.

When an NCR stays an NCR — and when it escalates

Not every nonconformance needs a second record. The NCR controls the output in front of you: what failed, what you held, and what an authorised person did with it. Add a later record only when the cause is unknown, detection missed it, a customer or supplier must answer, or the risk is too high for a local fix alone.

Open the smallest record that still owns the remaining work, and link it to the NCR number. A full 8D for a burr an approved rework step already covers is a packet nobody maintains. A customer return closed with no cause and no look at the escape leaves the next shipment exposed. NCR and 8D guidance published by the sources below makes this split. The table paraphrases it. It does not copy a vendor procedure or treat a vendor count as a fact.

Triggers that leave "close on the NCR" are a repeat, a customer complaint or return, a supplier-caused problem, an unclear cause, a detection failure or escape, and high risk. A minor isolated issue corrected immediately can close as a local correction. Where your procedure allows it, the NCR may close while a linked action stays open if the link, the owner, and the due date stay visible.

What the NCR must contain before anything is drafted

The draft can only restate facts the NCR already holds. Before n8n sends the row, a person checks that these are filled from the record, not from a hunch:

• NCR number, date, source, and owner.
• The requirement that was missed, cited, with its revision: drawing, specification, work instruction, purchase order, or procedure. On a drawing, follow drawing-to-inspection: controlled sheet and revision, not a remembered tolerance.
• The actual condition: what was measured, seen, or returned. This field does not guess a cause.
• Affected quantity and suspect quantity as two figures. Affected is what the evidence already shows is nonconforming. Suspect is what might be, until it is checked or cleared.
• Part, revision, lot, work order, and location.
• Containment already taken: what was held, stopped, or blocked, and who was told.
• Evidence references: a photo, an inspection row, a certificate, an email, a hold tag.

No cited requirement and no actual condition: do not draft. Send the NCR back. A model that fills those two gaps writes fiction into a quality record.

Fictional example, not a shop record. Each row shows a weak field the draft must not tidy up, and a strong field it is allowed to organise.

"Probably a worn tool" is already a cause claim with no evidence. It does not belong in the NCR, and it must not be copied into the draft as a finding.

How it works

Five steps, each ending with a person. n8n moves the text. Claude writes a draft and labels every block "draft", in the heading and the first line. Neither tool approves, closes, or names a cause. n8n sends the row only after a person marks it ready, then files the reply beside the NCR. It does not close the record. Keep the draft. Write the approved text back yourself.

1. Draft D1 through D3 from the NCR. D1 names only people already on the NCR. D2 repeats the cited requirement and the actual condition. D3 repeats containment already taken. Missing fields stay marked missing. No disposition and no cause are added. Human gate: the quality lead confirms the draft matches the NCR and that containment is still in place.
2. Ask for D4. Do not state a root cause. The draft asks and organises. It does not answer. A 5 Whys chain is blank questions. A 6M list (people, method, machine, material, measurement, environment) is questions by heading. Facts already on the NCR may be filed under a heading. The draft must not assert a root cause. Occurrence and escape stay separate. An escape is a detection gap. Shops that use cameras can set that gap beside visual defect detection without code or a DIY visual defect setup. The NCR needs the detection fact only. Human gate: the team verifies the occurrence cause and the escape cause against evidence.
3. Draft the D5 and D6 action table. Owner, due date, and the check that an action was done stay blank. Disposition options are listed and not chosen: rework, scrap, repair, return, use-as-is, and concession. Human gate: a named authority in your procedure approves the disposition and the corrective actions. This page does not name that person.
4. Prompt D7, the read-across. The draft asks where else the same requirement, tool, supplier, or inspection gap exists, and what would have to be checked before anyone claims the cause cannot happen there. It does not open those actions. Human gate: a person decides what, if anything, is in scope.
5. Draft the D8 closure checklist, unchecked. The questions are: product controlled, disposition recorded, actions done, evidence filed, effectiveness check scheduled, approver named. Human gate: the record closes only when the closure authority in your procedure says the list is met. Putting an action in place is not that gate.

Correction ≠ corrective action ≠ preventive action

These three get collapsed into "we fixed it". They are different records, and mixing them is how a closed NCR returns as a repeat.

Public summaries of ISO 9001:2015 clause 8.7 describe control of the nonconforming output: identify it, keep it from unintended use or delivery, and record the disposition. Correction is the action on those parts. Summaries of clause 10.2 describe action on the cause so the nonconformity does not recur or occur elsewhere, then a review of whether that action worked. Rework is not corrective action. The summaries leave the organisation to decide when a cause needs that action. Preventive action, in the shop language of the same summaries, is the read-across to similar parts, tools, or steps. Your procedure may use another name. This is general guidance, not certification advice.

The fictional bore, continued. Six pieces at 20.18 mm against drawing H-14 rev D. Still not a shop record.

• Correction. Rework the six pieces to the tolerance and inspect them again, or scrap them, and sort the lot on hold. The bad pieces can no longer ship. The process that made them is unchanged.
• Corrective action. From evidence, the team finds the boring insert ran past its change point and the offset was not checked at setup. The approved action changes the insert rule and adds the offset check to the setup sheet. That is about the next job, not the six pieces.
• Preventive action. The same insert rule is missing on the other two boring machines. A person adds those machines before they cut the same bore. That is read-across, not a second correction of lot B-19.

The effectiveness check is the closure gate

Marking an action done means a sheet changed, a tool was swapped, or a shift was told. It does not mean the nonconformity stopped. Close the corrective action only after you look again and see whether the requirement is being met. Schedule that look when the action is approved. Name who looks, at which feature, and what result would send the cause back. File the evidence with the NCR number.

Vendor write-ups of CAPA practice often mention a 30-, 60-, or 90-day check as a common interval. That is a description of what vendors write, not a result measured here, and not your interval unless your procedure adopts it. Set the interval in your own procedure.

A failed or overdue calibration can sit behind the NCR. Filing that certificate is a different job: calibration recall + cert filing. Link the certificate from the NCR. A filed certificate is not closure. Scrap is correction. Closure is the effectiveness decision your procedure names a person to make.

What to measure

Count on your own log before you start and again after people have used the pattern. This page supplies no baseline and no target.

• Open NCRs past the due date your procedure set.
• NCRs closed with no linked corrective-action decision, where your escalation rule required one.
• Repeats of the same part and defect inside 90 days. That window is for your own count. It is not a vendor figure and not a claim about how often defects return.
• The minutes your own people record to assemble an 8D packet, from a complete NCR to a draft a reviewer can mark up. Read the clock. Do not copy a duration from a vendor page.

If those counts do not move, the pattern is not helping. Do not publish a saving you did not measure.