A practical guide / ISO 9001
Non-conformance reports: how AI helps with ISO 9001 paperwork
A non-conformance report (NCR) records what went wrong, the immediate fix and the action that stops it happening again. Yes. Use AI to sort quality issues into an action log, draft work procedures from staff notes and prepare for internal audits. Start with one process your team can show, such as handling a failed batch of parts.
The aim is a record that explains what went wrong and what the team did next. ISO’s overview describes a system built around processes, records and improvement. The sources below provide that context. The log and headings here are draft formats to adapt to your own work.
Use the quality promptBuild quality records around the work people do.
Separate the correction from the cause and action
Take one quality issue and gather the fault report, immediate fix and follow-up notes. Ask AI to draft a nonconformity log. Use fields for the issue, requirement, affected work, correction, cause, corrective action, owner, due date and check that the fix held.
More on this step
Keep the immediate correction apart from the work to stop a repeat fault. Give the process owner space to explain the cause and link to the checks they made. ISO’s overview describes a process approach and improvement based on evidence. Use those ideas to shape the log, alongside the rules that apply to your system.
Read the source: ISO: ISO 9001 explained
Draft the procedure from a walk-through
Ask the person doing the work to show a recent job. Note what starts it, the inputs, steps, handovers and records produced. Use the notes to draft a procedure under purpose, scope, roles, method, exceptions and records.
More on this step
ISO’s committee provides guidance on documented information for the 2015 edition. Check which edition applies to your firm before using that guidance. Describe the work the team shows you. Put proposed changes in a separate list. The owner can then test those changes before adding them to the approved procedure.
Read the source: ISO committee: guidance on documented information
Prepare an internal audit evidence route
Choose one process and build a short audit sheet. Try these columns: work step, internal rule, record link, sample to inspect and question to ask. Sort the sources in the order the work happens.
More on this step
For a failed batch, begin with the test record. Move to the decision about what to do with the parts. End with the follow-up check. Ask how the team learnt about a changed work instruction. Use the sheet to find records and plan the audit. Add notes of what the auditor examined beside the planned sample.
Worked example
A rejected batch becomes a traceable action record
Example with made-up details: a parts maker finds a hole outside the stated position. The team sets the batch aside and reworks the affected parts. The owner checks the setup and changes the work instruction.
The log records the sorting and rework under correction. It links the cause to the owner’s setup note. The changed instruction sits under corrective action, with its version and staff training record. A final field asks for the next agreed batch checks. The log now shows work done and proof still needed to judge the fix.
Illustrative example.
Quality issue
Collect the fault and response records.
Action log
Separate correction, cause and action.
Follow-up
Record the evidence and owner’s decision.
Try a practical task
Build a quality action log from your records
Use sample records for one fault and the headings your team already uses.
Try this in your AI app
ChatGPT
Claude
Gemini
CodexUsing Gemini? The button copies the prompt. Paste it into the new chat.
Prepare a nonconformity log for a small parts maker. Extract the fault, batch, unmet requirement and immediate correction. Keep the cause review, corrective action and follow-up check in separate fields.
Keep record IDs and dates. Where proof is missing, add a question for the process owner. Leave the cause field open for the process owner’s review.
Draft an action log with owners and dates. Then prepare an internal audit sheet, following the process from the fault to the follow-up. Put proposed procedure changes in a separate list. Use only the firm’s stated rules and clause references.
A related public story about audit records
Iain Davidson audits health, safety and security at luxury hotels. With coaching, he built a Python app for evidence capture, issue scores and reports. He produced a 70-page client report and went on to use the system at other hotels.
For quality paperwork, his approach shows how to keep evidence connected to each step of a working process.
Read the source: Public story: Iain Davidson, hotel audit records and reporting
Keep approval and certification in the right hands
ISO explains that independent certification bodies carry out certification. UKAS CertCheck lets you check claims that a firm holds UKAS-accredited management system certification. Use these official routes when checking a certificate.
Your process owner and quality lead approve procedures and close actions using evidence that the fix worked. Use approved tools for client and factory records. Respect limits on licensed standards. Keep the source records with the agreed log. Ask your certification body which edition and transition plan apply to your firm.
Read the source: ISO: ISO 9001 explained; UKAS: check accredited management system certification
Questions about this task
Which quality document is a good first choice?
Choose a log for a fault with a clear follow-up. Use the fields to distinguish the immediate correction, the cause review and the corrective action.
How can we avoid producing an unused procedure?
Draft from a walk-through of real work, then ask the process owner to walk a recent job through it. Resolve differences before approving the procedure.