These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Automotive QMS
- Process
- Audit and findings
Audit and findings
Plan scoped audit work, retain each finding and review reporting before closing the audit.
Step by step
-
Plan audit Audit Lead
Audit Lead records an audit number, scope, planned date and auditor. The Planned state places the work in the open audit queue.
- Establishes scope, date and auditor
- Updates Audits, People
-
Conduct audit Audit Lead
The auditor reviews the agreed scope and moves the audit to in progress while evidence is gathered. Findings are linked to this audit rather than held in an isolated list.
- Shows active work against the agreed scope
- Updates Audits
-
Record findings Audit Lead
For each finding, the auditor records the requirement, observed issue, severity, owner and due date. Observation, Minor and Major distinguish the agreed follow-up priority.
- Links requirements and owners to the audit
- Updates Audit findings, Audits, People
-
Review reporting Audit Lead
Audit Lead moves the audit to Reporting and checks that the recorded scope matches the linked findings. Missing context is resolved before a closure decision.
- Checks scope against recorded findings
- Updates Audits, Audit findings
-
Close audit Audit Lead
Audit Lead approves the reporting result and moves the audit to Closed. Finding owners can still use their own due and closed dates to show the state of specific follow-up items.
- Records the reviewed audit closure
- Updates Audits, Audit findings
ApprovalA person approves before the work moves on.
Who does what
Roles and permissions- Audit Lead
- Plans, records and reviews the audit.
- People identifies the assigned auditor and finding owners.
- Admin
- Maintains their access.
Set up Automotive QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.