Closing the quality ticket is not the same as fixing the cause
For Quality managers and laboratory leads · Understand the problem
TL;DR — what you’ll learn
- Separate the observed issue, immediate containment and investigation of its cause.
- Assign actions to owners with evidence that explains what changed.
- Define how effectiveness will be reviewed before closing the case.
- Use AI to organise records and draft summaries while retaining evidence and accountable judgement.
The same label-selection error appears three times in a month. Each ticket closes with operator retrained. The training happened, but the line still stores nearly identical rolls together and the issue screen does not check revision. The completed action explains the closed ticket; it does not explain why the error keeps returning.
What should a food business record in a nonconformance and CAPA workflow?
A nonconformance record describes an observed departure from an applicable requirement. A CAPA workflow connects that evidence to containment, investigation, approved action and an effectiveness review. The record should distinguish a completed task from evidence that the underlying problem has been addressed.
- 01Record the eventObserved facts and affected scope
- 02Contain and investigateQualified owners and evidence
- 03Review the proposed actionCause, responsibility and verificationIs the proposed action supported?YesVerify effectivenessNoContinue investigation before accepting a convenient explanation.
- 04Verify effectivenessRetain the closure decision
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
Write the observation before writing the explanation
Record what was found, when and where, the affected item or process, the applicable requirement and supporting evidence. Keep the initial observation distinct from an inferred cause. A statement such as wrong revision issued is different from operator carelessness; the second asserts an explanation that needs evidence.
Define the affected scope under the site's approved process. Link relevant lots, orders, equipment or documents rather than copying their details into an unconnected note. Where the scope is still being established, show that uncertainty and the person responsible for resolving it. Do not narrow it simply to make the case easier to close.
Containment answers what happens now
Immediate actions may control affected work while the investigation proceeds, according to the authorised quality process. Record the action, scope, owner and evidence. Keep any inventory hold or production restriction connected to the authoritative status record so the CAPA note cannot conflict with the operational screen.
Containment is not proof of the cause or a permanent correction. For the illustrative label issue, controlling the affected material may be necessary while the team investigates selection, storage, identifiers and work-order checks. The investigation can continue even after the immediate operational state is stable.
Investigate the process that allowed the event
Use the actual sequence: how the requirement reached the operator, how material was selected, which checks applied and what evidence remains. Compare expected practice with observed records. A cause statement should identify the supported mechanism, not merely name the last person who touched the material.
Several contributing conditions can exist. Similar roll appearance, unclear revision identity and a missing issue check may each matter. Distinguish confirmed findings from hypotheses still being tested. AI can help organise interview notes or group repeated descriptions, but a fluent summary does not establish causation.
Choose an action with an observable result
An action needs an owner, due date and a description of the changed process or control. The evidence should show implementation: a revised approved instruction, a tested issue check or a corrected storage arrangement, as appropriate. Attendance at a briefing alone may not establish that the changed process works.
Frappe's quality-action documentation provides an example of recording corrective or preventive actions and status. The operating workflow still needs the evidence and review criteria appropriate to the case. Software completion fields should not be treated as proof that a regulatory or quality requirement has been satisfied.
Source: Frappe / ERPNext · Quality action records, proposed resolution and status. Reference details
Agree the effectiveness check before closing
Define what future evidence would support the conclusion that the action worked. For the illustrative label issue, the review might inspect relevant subsequent issue events and deliberately test wrong-revision selection under controlled conditions. The quality owner determines the suitable scope and review period; a universal number of days would not fit every process.
Keep action implementation and effectiveness review as separate states. If the event recurs, link the new evidence to the earlier case and assess whether the cause or action was incomplete. Do not delete the earlier closure. That history helps the business learn which types of action have failed repeatedly.
| Stage | Question |
|---|---|
| Containment | Was the immediate scope controlled under the approved process? |
| Action implementation | Was the agreed change actually put in place? |
| Effectiveness review | Does the reviewed evidence support the intended outcome? |
Keep the queue focused on decisions
A useful view separates cases waiting for scope review, cause evidence, action implementation and effectiveness assessment. Each needs a different person or next step. A single overdue count can identify pressure but does not explain what will unblock the work.
Start by reviewing a small set of repeat cases. Check whether the observation, cause and action form a coherent explanation and whether closure has supporting evidence. Automating reminders around a weak case structure will make the reminders more frequent without improving the quality of the decision.
Summary
A useful CAPA record connects the observed problem to an evidenced cause, a deliberate change and a review of its effect. Those stages should remain distinct. The system supports continuity and accountability; the responsible quality team determines the scope, actions and adequacy of the evidence.
What to do next
- Review three recurring cases and separate observations from assumed causes.
- Check whether each action has an owner and implementation evidence.
- Define the effectiveness review for an open case before setting its closure condition.
Recognise this problem in your operation?
Tell us where the records or handovers break down. We can discuss the process, data and software questions worth examining first.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Quality ActionFrappe / ERPNext · Online product documentation, accessed October 2026
Example of recording proposed corrective or preventive action and its status. A software record alone does not establish regulatory compliance or action effectiveness.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
