Who is behind qportal

Audits from both sides

I have prepared and run audits, and I have been audited myself. Both perspectives shape this product more than any requirements list: the view of the auditor walking the plant floor and retyping notes in the evening, and the view of the auditee gathering evidence two weeks before the date that should have been accumulating all along.

What I kept running into was not a lack of knowledge of the standards. It was breaks in the toolchain: the audit plan in a spreadsheet, the question catalog in a document, the findings in a report, the actions in yet another list. Each individual step is fine — what is missing is the connection between them.

Technical background

Technical lead experience in SAP BTP projects with CAP, SAPUI5 and Node.js, plus project experience with well-known consumer-goods brands in Germany. That work sharpened what matters in enterprise environments: reliable processes, clear coordination, and software that holds up in daily use rather than only in a demo.

That is why qportal is built on SAP BTP with CAP and Fiori Elements — not out of enthusiasm for the stack, but because security, multi-tenancy and an established interaction model then do not have to be built from scratch.

Why I write what I write

The articles in this blog come out of the same practice. They cite their sources, because I regularly come across quality management texts that render requirements of the standards inaccurately. If you spot an error somewhere, write to me — I am glad to correct it.

Current status

qportal is in an open pilot phase. There is no company behind it, no price list and no sales team. If you work in quality management, own the audit programme, or work as an auditor, and you would enjoy shaping a tool before it is finished: I would welcome a conversation.