Audit management software
that does not stop at the root cause

The finding sits in the audit report. The root cause analysis lives in an Excel file. And whether the action actually worked — by the next audit, nobody knows. That's the gap this is about. And in about three minutes I'll show you how that gap can be closed. Hi, my name is Andreas Bauer. I've prepared audits, supported them, and I've been on the audited side myself. And I keep seeing the same pattern. It isn't the method that's missing. 5-Why, 8D and CAPA are in every QM manual. What's missing is the connection between them. Four tools, an Excel list in the middle — and the evidence of the chain only appears once the auditor asks for it. qportal starts exactly there. One data model for all four steps. I'll use a case everyone knows. Internal audit, goods receipt. A measuring instrument in use whose calibration has expired. The finding is recorded right at the audit point. With category, severity and the audit criterion it was assessed against. Here it's a major nonconformity. Inspection decisions were made with an instrument that was not under control. The evidence sits on the same record. Label, calibration certificate, inspection reports. And the audit context too. Which audit it came from, for which organizational unit. So the finding doesn't end in a report. It's an object you keep working with. From the finding I open the root cause analysis. And you see two separate chains. Why the failure occurred. And why the failure wasn't detected. That's the distinction where analyses so often fail in practice. The occurrence chain ends at a manually maintained list with no due-date check at all. And the detection chain ends where nobody ever updated the goods receipt checklist — because there's no process for it. The causes turn into actions. And within the same analysis. Immediate action, corrective action, prevention. Each with an owner and a due date. What matters is the link. It's documented which action addresses which cause. Not in the head of the person who was at the audit, but traceable for everyone in the system. And then the step that's missing most often in practice. This analysis is set to "in progress". Five of seven steps. It can't be set to "done" while the prevention step is still open. And now the point that matters in an audit. From the action I go back into the analysis, and from there to the finding that triggered it. The chain is provable backwards. That was the audit module. Audit is the start. Root cause analysis and actions are separate modules in the same portal. With shared master data and users. qportal runs on SAP BTP. Then the users and roles stay yours. Or qportal can be hosted as SaaS. If you'd like to see how qportal looks in your own processes, the contact link is right below this video. Write to me — tell me where your chain breaks. Then we'll look together at how the process could work in qportal.