VDA 6.3 is the German automotive industry's process-audit standard, published by the VDA. It evaluates whether a supplier's manufacturing process is capable and stable across seven process elements (P1 to P7), scoring each question 0, 4, 6, 8, or 10 and grading the overall result A, B, or C. It audits the process, not the paperwork of a quality-system certificate.
An IATF 16949 certificate says a supplier has a quality management system. VDA 6.3 asks a harder question: on this line, for this part, is the process actually under control from the first inquiry to the last shipment? That is why customers in the German automotive supply chain run VDA 6.3 audits before they award business and again when a supplier is in trouble. This guide covers what the standard measures, the P1 to P7 structure, the turtle diagram it leans on, the 0/4/6/8/10 scoring, and the downgrade rules that can sink an otherwise strong score.
What is a VDA 6.3 process audit?
A VDA 6.3 process audit is a structured, risk-based examination of a supplier's product-creation and series-production processes, run against a fixed questionnaire and scored to a percentage grade. It was first published by the VDA in 1998, restructured in 2016, and updated again in the current edition (2023), which tightened expectations around embedded software, sourcing before start of production, and remote auditing.
The point is process capability, not documentation. A quality manual can be immaculate while the line still ships defects, so VDA 6.3 sends an auditor to the process itself: the machines, the operators, the control plans in use, the reaction when something goes wrong. It is used three ways, as a potential analysis before a supplier is awarded business, as a process audit of running series production, and as an escalation tool when field or line problems demand a hard look. It sits alongside IATF 16949 rather than replacing it: the certificate covers the system, VDA 6.3 covers the process.
The audit is not something anyone can run. The VDA requires auditors to be formally qualified, a mix of technical education, years of relevant industry experience, quality-method training, and a VDA 6.3 examination, because the scoring leans heavily on auditor judgment about risk. That qualification requirement is part of why a VDA 6.3 result carries weight across the supply chain: two competent auditors looking at the same weak reaction plan should land on the same score. The trigger for an audit is usually one of three things: a new sourcing decision, a scheduled surveillance interval, or a problem in the field that a customer wants explained at the process level rather than in a meeting.
What are the P1 to P7 process elements?
VDA 6.3 divides a supplier's whole value stream into seven process elements, so the audit follows the part from concept to customer rather than jumping around. P1 stands apart as a pre-award screen; P2 through P7 walk the flow.
| Element | What it covers |
|---|---|
| P1, Potential Analysis | Pre-award screen: does the supplier have the basic capability, capacity, and stability to be trusted with the work? |
| P2, Project Management | Is the launch project planned, resourced, and steered with clear milestones? |
| P3, Planning Product & Process Development | Are the design and process plans, feasibility, and required resources defined? |
| P4, Realization Product & Process Development | Were the plans executed, prototypes, validation, PPAP readiness, capable equipment? |
| P5, Supplier Management | Are sub-suppliers selected, developed, and monitored so incoming material is sound? |
| P6, Production Process Analysis | The core element: is the running series process capable and controlled? Audited with the turtle diagram, in sub-elements P6.1–P6.6. |
| P7, Customer Care / Satisfaction | Complaint handling, warranty, corrective action, and continuous improvement after delivery. |
How does the turtle diagram structure the P6 audit?
The turtle diagram is the framework the auditor uses to interrogate a process step from every side at once: the process sits in the middle, and six "legs" ask what feeds it, what it produces, and everything needed to run it. It keeps the audit from becoming a document review and forces attention onto how the step actually operates.
How is a VDA 6.3 audit scored?
Every question is answered with a fixed score of 0, 4, 6, 8, or 10 points, no in-between values, and the scores roll up to a percentage for each process element and for the audit overall. The bands are simple: A is at least 90 percent, B is 80 up to 90 percent, and C is below 80 percent. An A supplier is capable; a B has weaknesses to correct; a C is not yet acceptable and needs an action plan and re-audit.
The downgrade rules are what make VDA 6.3 unforgiving, and they are the part suppliers underestimate. A high average does not protect you if a critical question fails. In broad terms, the overall grade is capped or dropped when a starred question (a *-question, flagged for safety, regulatory, or customer-specific risk) is scored 0, or when a P6 sub-element falls below 70 percent of its possible points. In other words, you can average an A on paper and still be graded C because one safety-relevant question scored zero. Confirm the exact current rules against the standard itself before you rely on them, because the thresholds and starred-question list are defined in the VDA publication and have shifted across editions.
How do you prepare for a VDA 6.3 audit?
Preparation is mostly about making the process show its own control, not about assembling a binder. Work the value stream the way the auditor will.
- Map the audit scope to the process, not the plant. Fix which part, line, and process steps are in scope, and build a turtle for each major step so you know what each leg should show before the auditor asks.
- Walk P6 first and honestly. Production process analysis carries the most weight, so audit yourself there: control plan in use, gauges calibrated, operators qualified, reaction plans real. Fix weak legs before the external audit, not during it.
- Hunt your starred questions. Identify every safety-, regulatory-, and customer-specific requirement, and make sure each has hard evidence. A single 0 here can downgrade the whole result, so these get disproportionate attention.
- Confirm the flow-up and flow-down. Check P5 (are your sub-suppliers controlled?) and P7 (are complaints, warranty, and corrective actions closed with proof?). Auditors follow the chain in both directions.
- Tie findings to a corrective-action loop. Every gap you find should already be in a nonconformance and corrective-action system with an owner and a date, so the auditor sees a process that catches and closes its own issues.
- Rehearse the evidence, not the answers. The score comes from what the process demonstrates on the day. Make records retrievable at the station in seconds; an auditor who waits ten minutes for a calibration record has already formed an opinion.
Where VDA 6.3 sits and the numbers that anchor it
A few reference points keep the standard in proportion.
- VDA 6.3 is issued by the Verband der Automobilindustrie (VDA) through its Quality Management Center, which publishes the questionnaire, scoring model, and auditor-qualification requirements (VDA QMC).
- The overall grades are A (≥ 90%), B (≥ 80% to < 90%), and C (< 80%) with each question scored 0, 4, 6, 8, or 10 and downgrade rules that a high average cannot override (VDA QMC).
- The automotive QMS standard that sits above the process audit is IATF 16949 which requires suppliers to conduct manufacturing-process audits (customers often nominate VDA 6.3), maintained by the IATF (IATF Global Oversight).
VDA 6.3 is a process audit, and the companion tools around it decide whether it goes well. A layered process audit program keeps the P6 controls honest between formal audits, a quality audit checklist turns the questionnaire into a repeatable internal routine, and disciplined supplier quality management is exactly what P5 grades you on. What sinks scores in practice is not a missing procedure but a process that cannot show its own control quickly: records on a clipboard, evidence three departments away, a reaction plan nobody has read since launch. Digitizing station-level records and audit trails, the way Harmony's connected-worker tooling does, means the evidence is at the point of use and the corrective-action loop is visible, which is what the auditor is really testing. For a picture of a floor where that record-keeping is live rather than retrospective, see the CLS field story. VDA 6.3 rewards a process that governs itself; the audit just confirms it.