Operations celebrate near-miss volume and then cannot say what changed. The usual cause is architectural: near misses were given a lighter form, a lighter tracker, and no effectiveness review, because “nobody was hurt”.

Hurt is not what makes CAPA necessary. Recurrence is.

Same path, different outcome

In Intellilox Incident and Actions, outcome includes fatality, serious injury, serious-injury risk, and near miss. That is a classification on the incident, not a ticket to a different product. Contributing factors — machinery, chemical, procedural, LOTO, guarding, competency, exclusion zone — still have to be recorded if you want the executive pack to mean anything.

Construction and OHS sites feel this immediately: plant interaction, working at height, exclusion zones. Manufacturing feels it on LOTO and guarding. Health feels it on harm level that did not become harm this time. The form labels change. The path does not.

What “reporting” has to include

  • A first save under pressure — facts, where, when, attachments. Capture-only mobile so the frontline is not waiting for a desk.
  • An owner for the change — a linked action with a due date, not a comment that “we should look at this”.
  • Escalation if the date slips — near misses go quiet faster than injuries because nobody is chasing a claim.
  • Effectiveness — did the guarding, the brief, the lockout change actually hold?
  • Confidentiality when needed — some near misses still name people. The register must not teach under-reporting.

Side logs fail in a predictable way

They inflate counts (easy to type, no follow-up). They hide duplicates (second shift, second reporter). They never appear in the filtered print leadership actually reads. Then someone concludes “near miss reporting does not work here”. The reporting worked. The work after the report was never in the system of record.

How to use a 30-day trial on this

Do not start with a lost-time case if you want to test leading indicators. Pick two near misses from last month. Capture both on the CAPA form. Assign one owned action each. Print the register filtered to those dates. If the pack still looks like “nothing happened”, the outcome field or the print layout is wrong — not the philosophy.

Frameworks can deploy an OHS starting form; Form Designer names the fields for the site. Installing a template does not create certification.

Near-miss programmes are an operational choice. Intellilox records the outcome and the CAPA path; it does not by itself satisfy a regulator’s reporting duty.