Guidance · 9 min

From nonconformity to corrective action

How to analyse a finding, correct the immediate issue, address causes and demonstrate effective closure.

A nonconformity is a requirement-level conclusion supported by objective evidence. Closing it means more than repairing the sampled case: the organisation must understand the affected scope, address the cause and show that the revised control works.

Read the finding as three connected parts

Identify the exact requirement, the verified evidence and the conclusion explaining the gap between them. Confirm which sites, products, periods, records or people may be affected. If wording or evidence is unclear, seek clarification without arguing from intent or from evidence that was not available to the assessment.

Contain risk and correct the immediate case

Take proportionate action where learners, candidates, results, security, fairness or public claims may be affected. Correct the sampled error and check for similar cases in the relevant population. Record what was changed, by whom, when and with what authorisation. This correction controls the symptom; it does not by itself prevent recurrence.

Analyse causes at the level of the system

Ask how the control allowed the issue to occur and remain undetected. Test factors such as unclear ownership, unsuitable design, competence, workload, resources, interfaces, supplier control, data quality, change management and monitoring. ‘Human error’ or ‘staff reminded’ is rarely an adequate analysis unless the system conditions have also been examined.

Design action that changes the control

Link each action to a supported cause. Define the responsible owner, affected scope, required resources, dependencies, authorisation, completion evidence and method for checking effectiveness. Consider whether documents, systems, training, supervision, sampling, communications or public records also require controlled change.

Demonstrate implementation and effectiveness

Completion evidence shows that the action occurred: an approved revision, configuration record, training and competence result, corrected dataset or implemented review. Effectiveness evidence is different: a representative follow-up sample, monitoring trend, observation or test shows that the control now operates and the issue has not recurred within the period examined.

Close only on sufficient evidence

Submit a concise record connecting finding, affected scope, correction, cause, action and effectiveness evidence. A plan, future date, revised document without implementation or assertion that the matter is resolved is not closure. If the response is insufficient or the risk is wider than first understood, the finding can remain open and the assessment scope or recognition status may require further review.