The pattern is stable across manufacturing, construction, and health. Events are typed into a form. Actions are typed into a spreadsheet. Email carries the chase. At quarter-end a patient person rebuilds a pack that leadership will believe for one meeting.

That is not a discipline problem. It is a split in the system of record.

Three files, three truths

Once CAPA leaves the incident, three documents start to disagree:

  • The register says the incident is closed, because closure was a status on the event.
  • The tracker still has open rows, or rows marked done with no evidence attached.
  • The board pack is a third narrative, assembled from whichever tab someone trusted this month.

Auditors and executives do not experience those as three tools. They experience them as one question: did the change hold? If answering that question requires a reconstruction, you do not have CAPA. You have a reporting project.

What a spreadsheet cannot keep

A well-kept workbook can list owners and dates. It cannot reliably keep:

  • The source incident as a navigable record — facts, attachments, containment, root cause.
  • Confidentiality — who may see a sensitive event — without teaching people to under-report in the description field.
  • Escalation when the date slips, on the same timeline as the incident, not in a forgotten conditional format.
  • Effectiveness review next to the action that claimed to remove the cause.
  • Print that matches the filter already on the register: this manager, this area, this date range.

Versioned filenames feel like control. They are how drift gets a name.

CAPA is the rest of the incident

Corrective action removes the cause of a detected problem. Preventive action reduces the chance it happens elsewhere. Both need evidence they were implemented and that they worked.

That work does not belong in a second product. It belongs on the incident and on linked actions with an owner, a due date, and a source link back. If “closed” is a dropdown and the proof is somewhere else, you will rebuild the story every time someone asks.

Intellilox Incident and Actions is built around that single history. The default CAPA form walks intake, assessment, respond and correct, and recover / review / close. Linked actions carry the accountable work. Effectiveness stays attached. Installing a framework does not create certification; it gives you a governed starting form you can localise.

A practical test

Pick one event from the last quarter. Without opening email, can you show: what happened, who owned the change, when it was due, what evidence was filed, and whether effectiveness was reviewed?

If that takes a hunt across files, the spreadsheet has already failed — quietly, every week, while the register looked complete.

A 30-day trial of Incident and Actions is for that test: capture one incident, assign one owned action, print the item and the filtered list. Other Intellilox applications are not included. That is deliberate.

Intellilox helps organisations operationalise CAPA on incident records. Using the software does not by itself create ISO certification or guarantee compliance.