Best software
CAPA and nonconformity software: inboxes, trackers or a full QMS?
Continual improvement remains at the heart of ISO 9001:2026. Compare inboxes, simple trackers and QMS modules for recording problems and following actions through — without inventing a required brand or a fixed clause number.

When something does not meet the requirement — a product, a process, a complaint, or a failed audit finding — the organisation has to record it, contain it where needed, understand why it happened, and follow actions through. ISO’s public summary of ISO 9001:2026 keeps continual improvement at the heart of the standard, and lists updating processes, documented information and governance where needed among typical transition steps.1 It does not require a named “CAPA module”.
The same discipline shows up in investigation practice. HSE’s HSG245 workbook treats the action plan and its implementation as a distinct step, and warns that dealing only with immediate causes may leave underlying and root causes in place, so that further adverse events remain likely.2 Whether you call the work CAPA, nonconformity control or complaint handling, the record has to support that follow-through.
Criteria for any tracker you use
- Can you describe the problem against a clear requirement, not only a vague complaint?
- Can you record containment separately from correction and from any action on the cause?
- Can you assign an owner, a due date, and evidence of what actually changed?
- Does the workflow make it harder to close a ticket with no evidence, or easier?
- Can you see repeats — the same process, the same customer issue, the same finding — or does each row live alone?
Three common approaches
Email, spreadsheets and shared inboxes
Many teams start here, and for a low volume of simple issues it can work. The risk is that the conversation becomes the record. Attachments sit in individual mailboxes, due dates live in someone’s head, and it is hard to show later what was decided and why a ticket was closed.
A spreadsheet is a little more visible, but it has the same limits as any shared workbook: competing versions, weak evidence, and no natural stop against closing a row because someone is tired of seeing it open.
A simple action or CAPA tracker
A dedicated tracker — sometimes a lightweight workflow tool — gives each issue a home, a status and a place for evidence. That is often enough if your main gap is lost actions rather than a missing quality system.
The limitation is isolation. If the tracker cannot point back to the inspection, audit, customer complaint or process document that raised the issue, you spend time reconstructing the story. A tracker also cannot force good cause analysis. People will still write “operator error” unless the method, and the competence of the reviewer, say otherwise.
A CAPA or nonconformity module in a QMS
When nonconformities, complaints, documented information and audits share a system, it can be easier to show the trail ISO 9001-style quality work depends on: the requirement, the evidence, the action and the updated document where needed.1
A full QMS is heavier to implement. If most of your issues are operational and already owned in another tool, duplicating them in a quality module creates two truths. Integration is only valuable if one record is the record.

Side-by-side comparison
| Criterion | Email and spreadsheets | Simple CAPA or action tracker | Module in a full QMS |
|---|---|---|---|
| A complete issue record | Often scattered across mail and files | One record, if people actually use it | One record, often linked to audits, documents or complaints |
| Cause versus quick fix | Easy to close after a temporary fix | Can separate containment, correction and cause, if designed that way | Same, with more chance to update documented information in the same system |
| Evidence of close-out | Hard to retrieve later | Typically a required attachment or note | Typically a required attachment, sometimes a linked change |
| Seeing repeats | Poor unless you analyse the sheet by hand | Better if you use consistent categories | Better if the same processes already live in the QMS |
| Effort to start | Low | Low to medium | Medium to high |
The official ISO film below introduces ISO 9001:2026. It is not a CAPA software demonstration. It is here because continual improvement remains central to that edition, and because a nonconformity process only helps if it changes how work is done.

For a structured walk-through of corrective and preventive action and complaint handling, see CAPA and Customer Complaint Handling. These are independent awareness and exam-preparation courses. They are not official IRCA, ISO, NEBOSH or IOSH awards, and they are not a substitute for a licensed standard or for legal compliance.
A practical way to decide
Count how issues reach you — audits, inspections, customers, process checks — and how you prove they were closed. If the trail already exists in a simple tracker, a full QMS is optional. If you cannot show the requirement, the cause and the evidence of the change, a clearer record will help more than a new logo on the same mailbox.
Closing a ticket is a workflow step. Correcting a problem is shown by evidence. Do not let software blur that distinction.
Frequently asked questions
Does ISO 9001:2026 require a CAPA software module?
No. ISO’s public summary keeps continual improvement at the heart of the standard and lists updating processes, documented information and governance where needed among typical transition steps. It does not require a named CAPA product.
What can investigation guidance teach a CAPA process?
HSE’s HSG245 workbook treats the action plan and its implementation as a distinct step, and warns that dealing only with immediate causes may leave underlying and root causes in place. The same discipline applies when you close a nonconformity or a complaint: record what will change, who owns it, and how you will check it worked.
Is closing a ticket the same as correcting a problem?
No. Closing a ticket shows a workflow step was completed. Correction is shown by evidence that the issue was addressed and, where needed, that the cause was tackled so it is less likely to recur.
Sources
Every factual statement marked with a number links to the source below. Sources were retrieved on 22 November 2026; check the publisher for later revisions.


