Vda 6 3 Audit

Step 5 — Conduct the audit

Pre-audit:

• Request all relevant documentation: Process Flow, PFMEA, Control Plan, WIs, maintenance records, calibration records, training records
• Review and identify gaps before the site visit
• Confirm auditor qualification: VDA 6.3 audits require a trained, qualified auditor — internal auditors must hold a recognised VDA 6.3 auditor qualification (VDA QMC certification or OEM-equivalent). An unqualified person conducting the audit invalidates the result.
• Confirm auditor independence: the auditor must not have direct responsibility for the process being audited. Self-assessment by the process owner is not a substitute for an independent audit.

Opening meeting:

• Confirm scope, timing, and audit plan
• Introduce audit team and request the process owner to accompany

Process walk (the audit):

• Follow the process flow physically — start from incoming material, end at shipment
• For each step: observe, ask, verify records
• Ask: "Show me the record for this" — never accept verbal confirmation
• Score each question in real time; document evidence (positive and negative)

Findings classification:

• Score 6: Partial fulfilment — finding documented, corrective action required; deadline typically 90 days
• Score 4: Insufficient fulfilment — significant gap, represents active risk to quality; escalate deadline; customer OEMs often treat score-4 findings on critical questions (P6.4, P6.5, P6.6) as major deficiencies requiring immediate corrective action
• Score 2: Not fulfilled — systematic failure, high risk; corrective action with accelerated timeline required before next delivery
• Score 0: No evidence / not implemented — blocking; re-audit required before SOP release (if P1 applicable)

Closing meeting:

• Present scores and degree of fulfillment per element
• Confirm overall rating (A, B, or C)
• Agree on corrective action deadlines (typically 90 days for B-rating findings; accelerated for score-2 and score-4 findings)
• For B rating: schedule a follow-up audit or evidence review within 3 months to verify corrective actions are implemented — do not close the audit without this commitment in writing
• Confirm re-audit requirements if applicable (mandatory for C rating)

Step 6 — Audit report structure

The VDA 6.3 report must contain:

1. Audit information: date, location, auditor, auditee, scope
2. Degree of fulfillment per element (P1–P7 as applicable)
3. Overall rating (A, B, C)
4. Finding list: for each score ≤ 6 — question, observation, evidence, score, deadline
5. Positive findings: best practices worth noting
6. Corrective action plan (CAP): supplier-signed, with root cause and due date per finding
7. Re-audit requirement if C rating

Validation criteria

A VDA 6.3 audit is complete when:

• All applicable elements (P5, P6, P7 minimum for series) have been scored
• All findings (score ≤ 6) are documented with evidence
• Degree of fulfillment calculated and overall rating stated
• Corrective action plan signed by supplier quality management
• Re-audit scheduled if rating is C

Common mistakes

• Auditor accepts verbal confirmation as evidence — always request the record
• Skipping the process walk and only reviewing documents — P6 requires observation of the live process
• Not documenting positive evidence — the report must balance findings and strengths
• Calculating degree of fulfillment without applying question weights
• Not confirming error-proofing device checks are being performed at the required frequency
• Closing meeting without confirming the corrective action deadline in writing
• Rating B without scheduling a follow-up to verify corrective actions are implemented

Output Format

At the start of each use, ask the user:

"How would you like to receive the output? A — Structured Markdown (formatted tables and sections, ready to copy) B — Plain tables (simplified structure for Excel or Word) C — Narrative report (flowing text for a formal document or email)

Default: A."

Adapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.

Changelog