Modules · Audits and management system
In developmentQWorks Audit
From management review to verified closure.
Your audit programme starts with management review decisions; planning, execution, findings, actions and verification move on the same backbone, and the results return as input to the next review. Every step with its owner, due date and evidence.
One backbone
An audit is not a calendar; it is a loop that closes.
QWorks Audit runs the management-system loop end to end in one place: the review’s decision sets the programme, and the audit’s result feeds the next review.
- 1Management reviewRisk, objective and resource decisions are recorded; they are the programme’s input.
- 2Audit programmeThe annual programme is built on risk and objectives, and updated when decisions change.
- 3PlanTeam, scope, date and checklist; the process owner is notified.
- 4ExecutionEvery question is answered; a non-conforming answer becomes a finding with its evidence.
- 5FindingMajor, minor, observation or opportunity for improvement; each assigned to an owner.
- 6ActionRoot cause and corrective action run on the same 8D/CAPA engine as Complaint.
- 7VerificationOnce effectiveness is verified with evidence, the finding closes and the result becomes review input.
Audit types
Six audit types. One engine.
Question sets and participants change; the logic of planning, findings, actions and closure is the same for all.
System and internal audits
Run management-system internal audit programmes with clause-based checklists, findings and closure evidence.
Process audits
Question sets per line and process; findings tie to the process owner and related records.
Product audits
Checks per product and characteristic; a non-conformity can become a case when needed.
Supplier audits
The on-site audit, findings and corrective action request in the same supplier history.
Customer audits
Preparation for audits your customers carry out, follow-up of findings and evidence-based responses.
Layered process audits
Short, frequent checks across shift and management layers; a deviation opens as work at once.
See the operation at work
One review decision; to verified closure.
The demo audit below moves through the loop on its own. At every step you see who worked, which decision was taken and what state resulted. Hover to pause; click a step to jump.
The review records the rise in customer complaints and the recurring risk on the casting line as a decision. The decision becomes input to the audit programme.
How it works
Each scene shows one mechanism.
The scenes below show, in simple form, how QWorks Audit works. Under each we note what you are looking at and which risk it controls.
Scenes are conceptual; record numbers and values are representative.
The same backbone as Complaint
Findings and complaints on one action engine.
An audit finding and a customer complaint often point to the same process. In QWorks both use the same 8D/CAPA engine and the same work and evidence backbone.
- From finding to caseA major finding starts a root-cause and corrective-action chain, as in Complaint.
- From case to auditA recurring complaint can become an audit proposal for the related process.
- One historyA process’s complaints, findings and actions appear in the same history.
Roles
One loop, different responsibilities.
Everyone sees only their own work and permissions; the loop stays one.
- Quality managerBuilds the programme from review decisions and watches the whole loop.
- Lead auditorPlans the audit, classifies and assigns findings.
- AuditorRuns the checklist, gathers evidence, verifies closure.
- Process ownerResponds to the finding and runs the corrective action.
- SupplierProves the corrective action on findings at its own site.
- ManagementDecides in the review; sees late and recurring findings.
Shared platform capabilities
On the same operations backbone.
QWorks Audit runs on the work, due-date, evidence, permission and data backbone QWorks Complaint uses today. When it is switched on, the same capabilities come with it.
See how the platform is builtBusiness modules+ Platform vision
- Work Orchestration
- SLA & Escalation
- Identity & Access
- Problem Solving
- Evidence
- Reporting
Start with QWorks Complaint and every shared capability comes with it.Start with QWorks Audit and every shared capability comes with it.Start with QWorks Zero and every shared capability comes with it.
Scope we can share today.
- QWorks Audit is in development; no release-date commitment is made.
- Visuals on this page are conceptual, not product screens.
- QWorks does not issue certification or declarations of conformity; that decision belongs to the certification body.
Where you can start today.
QWorks Complaint is in use today; the action engine and backbone Audit will use are built with it. Organisations in the Design Partnership Programme get early access to evolving modules.
Questions about Audit.
What people ask before moving the audit operation onto one backbone.
Which audit types does it cover?
System and internal audits (IATF 16949, ISO 9001, AS9100D programmes), process, product, supplier and customer audits, and layered process audits (LPA). All work with the same logic of planning, findings, actions and closure.
Why does the process start with the management review?
Risk, objective and resource decisions in the management review set the audit programme; audit results become input to the next review. The loop closes in one place.
How do findings relate to actions in Complaint?
Both use the same 8D/CAPA engine. A major finding can start a root-cause and corrective-action chain; a recurring complaint can become an audit proposal for the related process.
Can we use our own checklists?
Yes. Checklists are defined with your organisation’s question sets, by audit type and process.
What happens to opportunities for improvement?
An opportunity for improvement is a finding type of its own; it is not lost, it is assigned to an owner and tracked as a proposal. Observations stay on record the same way.
Does it ensure conformity to standards?
QWorks does not issue certification or declarations of conformity. It lets you run your internal audit programme, findings and evidence in one place; the conformity decision belongs to the certification body.
When will it be available?
QWorks Audit is in development and we make no date commitment. Organisations in the Design Partnership Programme get early access to evolving modules.
Let’s map your audit loop together.
Let’s review today’s audit flow from management review to closure, see where it breaks and show how it fits one backbone in QWorks.