Protect the customer before debating the cause
Imagine a UAE precision-machining company discovering during final inspection that a component was produced to an obsolete drawing revision. The part is isolated and the delivery is held. Those steps protect the customer, but they do not yet explain why the obsolete file remained available to the CNC operator or how the same path will be prevented on the next job.
This is an illustrative scenario, not a claimed LETA client result. Record the immediate containment first: affected job, material, work in progress, finished stock, supplier or subcontract activity, and any customer communication. Then record the correction applied to the affected output. Keeping these decisions visible prevents an urgent repair from being mistaken for corrective action.
Write the problem so another person can investigate it
A statement such as 'operator used wrong drawing' already assumes the person is the cause. Start with observable evidence: which requirement was not met, which revision was used, where it was accessed, which jobs may be affected, when the mismatch entered the process and what consequence followed. The investigation can then examine engineering release, server permissions, ERP links, point-of-use access, change communication and production verification.
Use several evidence sources rather than one meeting opinion. Compare the current approved drawing, access logs or revision history, job traveller, machine file, interview evidence and earlier NCRs. A cause is useful when changing it would reasonably reduce recurrence and when the team can explain how the evidence supports that conclusion.
Choose an action that changes the failed control
If the only action is to remind the operator to be careful, the organisation remains dependent on memory while the obsolete route remains open. Depending on the confirmed cause, stronger actions might restrict point-of-use access to current released drawings, link the job to the approved revision in ERP, remove obsolete files from the production view, introduce a controlled change-release gate or require revision verification before first-off machining.
Do not copy those examples without checking your process. The action should be proportionate to the consequence, technically practical and owned by someone who can change the relevant system. Record what will change, who owns it, the due date, what evidence will show implementation and what unintended effects must be checked.
Define effectiveness before closing the NCR
Implementation evidence answers 'was the action installed?' Effectiveness evidence answers 'did it work?' Before closing, choose a later test that matches the cause: sample the next relevant jobs, verify that obsolete drawings cannot be selected, review access exceptions, interview operators on a different shift, or monitor recurrence over an appropriate production period. Define the sample and decision rule before the result is known.
The five-step loop—contain, correct, analyse, change and verify—is LETA's practical structure, not a mandatory ISO form or copied requirement. ISO's public 2026 material confirms that continual improvement remains fundamental and that the transition should strengthen how the system supports performance. The ISO 9001 Auditing Practices Group paper on reviewing and closing nonconformities provides useful older background, but it was written for the 2015 edition and is not ISO 9001:2026 transition criteria. Confirm exact requirements using an authorised copy of ISO 9001:2026. LETA supports implementation and readiness; an independent certification body decides certification.