Non-conformance reports: closing the loop on root causes
Admin · 22 October 2026
Illustrative image. Photo by Pedro Miranda on Unsplash. Unsplash License.
A non-conformance report should create a clear route from an observed departure to an authorised response and verified outcome. It loses value when it becomes only a label attached to a problem or a record closed as soon as someone reports that work has been corrected. The project needs to understand what was affected, who decided the response and whether the underlying cause requires further action.
For quality and package managers, the reporting workflow must preserve technical responsibilities. A form cannot decide whether work is acceptable or prescribe a remedy without the appropriate competent assessment. Its role is to make the evidence, status and actions traceable through the project’s actual procedures, with the people affected able to see what remains unresolved.
Describe the departure against a requirement
Identify the work, location and relevant requirement using current references. Explain what was observed factually and distinguish it from a proposed explanation. A broad statement that the installation is poor gives reviewers little basis for assessment. The responsible technical team needs a precise question and the evidence available.
Where the applicable requirement is unclear, record that issue and obtain the appropriate clarification. Do not invent a criterion to make the form complete. The project may need to resolve a design or information gap before it can determine the status of the work. Preserve that distinction rather than force every concern into the same conclusion.
Identify the extent for assessment
The observed instance may raise questions about related work, materials or records. The competent team should establish what investigation and coverage are needed. The coordinator can identify relevant locations and references without assuming that one example proves the condition of every similar item. Scope conclusions need an evidential basis.
Keep the work identity connected to photographs, results and other supporting material. A clear image without a location or date may be difficult to use later. Record the source and status of evidence through the project’s information arrangements. This helps reviewers distinguish what was actually observed from material gathered subsequently for another purpose.
Make the interim status clear
Use the established process to communicate the status while assessment continues. The appropriate people determine the implications for related work and the next activities. A report raised is not automatically a complete instruction to every affected trade. The coordinator should ensure the relevant decision and communication occur through the correct authority.
Identify the owner and timing of the next assessment. If the forecast depends on further information, say so. The planner and package leads need an honest account of what can be committed. Repeatedly assigning an unsupported closure date may create more disruption than a clear explanation of the outstanding evidence and decision.
Separate response options from approval
A contractor or supplier may propose a response, but the project must follow its actual review and authorisation arrangements. Record the proposal, supporting information and decision. A suggestion in an email should not be treated as an approved technical solution merely because the person writing it is experienced.
The APM change control overview provides general context for evaluating changes. If the proposed response affects approved design or scope, connect it to the relevant project process. The non-conformance workflow should not become an unofficial shortcut around requirements that apply to the change.
Verify the response against evidence
Agree what will demonstrate completion and who reviews it. The responsible competent team determines the checks and acceptance basis. A statement that the work is fixed may be insufficient without the evidence required by the project. Link the record to the actual work and any consequential revised information.
A hypothetical package corrects an installation and uploads a photograph. The image may help, but the reviewer still needs to establish whether it shows the relevant location and required condition. The lesson is not to reject photographs generally; it is to define the evidence needed before closure and assess what each record actually demonstrates.
Investigate causes without jumping to conclusions
Review the sequence leading to the departure with the relevant participants. Distinguish intended procedures from what happened in practice. Information, procurement, supervision and working conditions may all deserve questions, depending on the evidence. Avoid choosing a familiar cause simply because it fits a standard dropdown field.
Test proposed explanations against records and the accounts of those involved. Where uncertainty remains, retain it and assign further investigation where appropriate. A root-cause field containing communication failure is rarely enough to guide improvement. The report should identify the specific breakdown and the process that could be changed.
Distinguish correction from prevention
Resolving the affected work and reducing recurrence are related but different actions. The first may be complete while the second requires a change to information release or supplier review. Keep their owners and status clear. Do not imply that a physical correction alone proves the process that allowed the departure has improved.
Choose preventive actions connected to supported findings. Retraining may be appropriate for a defined learning need, but it should not be the automatic answer to every event. The actual problem may concern an unclear requirement or a control that could not function with the information available. The action needs to address that condition.
Close the record through the proper authority
Define what closed means under the project procedure and who can confirm it. The person administering the register may not hold the technical authority to accept the work. Preserve the distinction between administrative completion and the authorised conclusion. A signature should identify the purpose and scope of the review.
Where actions remain beyond the immediate correction, link them to a controlled process with owners and review dates. Avoid closing a report in a way that makes those commitments disappear. The final record should allow a new manager to understand the outcome, evidence and any continuing responsibility without reconstructing the entire correspondence.
Keep later evidence connected to the original event
Further information may arrive after the first report or corrective action. Record its source, date and significance through the appropriate process. If it changes the assessment, obtain the relevant review rather than silently rewriting the original description. The chronology should remain understandable so a later manager can distinguish what was known at each decision point.
Where a report is reopened, explain the reason and identify the authority and actions involved. This is more useful than creating an unrelated duplicate that fragments the history. Clear links help the project understand both the work’s current status and whether an earlier preventive action needs reconsideration in light of the new evidence.
Keep closed records searchable by location and issue type. This allows the team to identify recurring problems using evidence rather than recollection and helps future reviewers understand the accepted response without reopening unrelated correspondence.
Use trends carefully
Review patterns across packages using consistent definitions and suitable context. Counts alone may reflect different reporting practices rather than different quality performance. Ask whether similar departures share a supported cause and whether earlier actions were implemented and effective. A chart should prompt investigation, not substitute for it.
The CIOB’s 2019 quality-management code provides wider professional context. The workflow here is an editorial management approach, to be adapted to current project requirements. It does not establish universal technical criteria, remedial methods or contractual consequences.
A useful non-conformance process leaves a coherent trail from requirement to observation, competent decision and verified outcome. It keeps correction and learning connected without confusing them. That gives the project a stronger basis for closing the affected work and improving the processes that future packages will rely on.
Review the record format with users after early cases. If an important identifier or approval meaning is repeatedly unclear, improve the field and guidance before the same ambiguity spreads through the register.
