How do you stop corrective actions being marked closed when nothing was actually fixed?
In Inspecable, a failed inspection item raises an issue, a corrective action is raised from it, and the action cannot close without evidence, a signature and a verification method, from someone other than its owner.
Corrective Action Tracking: From Failed Inspection to Verified Close-Out | Inspecable
This web dashboard tutorial follows one defect through the issue register and the issue record, the escalations register, the CAPA register (fed by inspections, incidents, near misses, observations, audits and sign-offs), the action record with child actions and linked work, the Verify & close gate, which the database enforces, and the signed effectiveness review, where an ineffective result opens a follow-up action. Escalation follows the policy you set up; until a policy exists, nothing moves up the chain. Recorded in a live demonstration organisation.
The narration, word for word
Read the transcriptHide the transcript
Introduction
In this video you'll follow one problem from a failed inspection item all the way to a closed corrective action: the issue, its escalation, the CAPA register, and what it takes to close an action properly.
The issue register
Issues are defects and faults raised against assets. When an item fails on an inspection, an issue is raised on the spot. The register counts them by status: open with no owner, in progress, and resolved, with cuts for critical and repeat problems. Search by title, asset or reporter, filter the list, or export it to Excel. Let's follow one through: six broken fastenings at a turnout heel, found on a siding inspection.
The issue record
The issue page shows its stages: raised, triaged, escalated, resolved and verified. Quick actions let you mark it resolved, create a task, and on the Operations plan a work order or job. Or raise a corrective action straight from here. Triage needs a risk rating on your organisation's risk matrix, or a link to the risk it relates to. On the right is where it came from: the inspection, the asset and the site, and the corrective action raised from it.
Escalations
Escalations lists everything currently escalated: what it is, its level, who it sits with, how long it has waited and when it's due. Escalation follows the policy set up under Escalation policy. Until a policy exists, nothing moves up the chain.
The CAPA register
The CAPA register holds every corrective and preventive action in one place, fed by inspections, incidents, near misses, observations, audits and sign-offs. It shows the totals, what's open and overdue, and which causes keep coming back. Each action shows its state, its priority, the root-cause method used, or not analysed, and an overdue badge. Search, and filter by origin, type, state or owner.
The action record
Open an action to work it. The stepper runs plan, do, evidence, verify, close and effectiveness. Below are the source, the root cause, the action plan with its owner and due date, follow-on actions, its escalation and linked work. A big action can be broken into child actions, each with its own owner and due date, and each one an ordinary action in the register. Linked work attaches the work order, document or training course that discharges the action.
Closing an action
Close an action with Verify and close. It stays disabled until three things are there: evidence, a signature and a verification method. The database enforces the same rule, and the person who owns the action can't close it. Someone else verifies it. We'll cancel this one.
Effectiveness review
After closure comes the effectiveness review, on the After close-out tab. A reviewer records effective, partly effective or ineffective, with evidence notes and a signature. Choose ineffective, and it opens a follow-up action with the same source and root cause.
Recap
So: a failed item raises an issue, which you triage and escalate. Raise a corrective action and work it in the CAPA register. Close it with evidence, a method and someone else's signature, then review whether it worked. Next, see how to run an incident from the first report to close-out, with a root-cause analysis. Every tutorial is on our website, linked on screen now.
Safety and compliance tutorials
Fourteen days on the Safety & Compliance edition, no card
Or book a 30-minute walkthrough and we show this on your industry's checklists.