VDA 6.3 Audit Preparation: Managing Readiness Across Every Plant


VDA 6.3, an automotive process audit standard once rarely seen outside of Europe, is making its way to plants worldwide as suppliers are diversifying and looking for projects with German OEMs.
That means a company in Ohio that’s completely unfamiliar with VDA 6.3 may find it in scope at four plants because a customer two tiers up won a Mercedes program.
A poor result may put you on the OEM’s red supplier list, or even end with business on hold.
We sat down with Daniel Castilla, a former quality director at Tenneco and founder of Ollin.One to talk about how to avoid these outcomes, and what VDA 6.3 audit preparation actually takes across a multi-plant footprint.
Download a free white paper to learn How to Improve Production Quality with Layered Process Audits
What Is VDA 6.3?
VDA 6.3 is a process audit standard published by the German Association of the Automotive Industry (Verband der Automobilindustrie, or VDA). German OEMs and their suppliers use it to determine whether a specific manufacturing process reliably delivers conforming product.
The scope of the standard covers seven elements:
- P1: Potential analysis, used to assess a supplier or site before award.
- P2: Project management.
- P3: Planning the product and process development.
- P4: Implementation of the product and process development.
- P5: Supplier management.
- P6: Process analysis and production, covering the plant floor itself.
- P7: Customer care, customer satisfaction, and service.
Preliminary self-assessments require a lead auditor with formal VDA 6.3 qualification, who grades each question and attaches supporting evidence, pulling in subject matter experts across the business. Anything graded red or yellow needs either a corrective action or an explanation. That package goes to the customer, who reviews it and decides whether to dig further or come on site.
A poor result can put you on that customer’s red supplier list and escalates risk on the program. From there, the problem can widen.
“If it’s truly a red that can’t be solved, then business goes on hold until you fix it. That impacts business with that customer, plus whoever else requires VDA, so it becomes quite a situation,” says Castilla.
Why Non-European Suppliers Struggle with VDA 6.3
For most plants, the first big challenge around VDA 6.3 is working out which parts apply to them in the first place. Familiarity with the standard varies sharply by region, a key concern for companies managing VDA 6.3 compliance across a global footprint.
Castilla saw that gap firsthand across four regions:
- Europe is strongest, which makes sense given the standard originated with Mercedes and the other German OEMs.
- Teams in the Americas may grasp the assessment without fully understanding what it was driving at.
- Asia is weakest, with India and China furthest behind.
While most OEMs have their own version of a supplier process assessment, VDA 6.3 is the most mature of them.
“VDA 6.3 is a very mature assessment, so complying with it actually makes it way easier to comply with most American OEM requirements, and even Asian OEMs like Toyota and Hyundai,” says Castilla, who managed VDA 6.3 compliance across four regions at Tenneco.
What Do VDA 6.3 Auditors Look For?
VDA 6.3 auditors want to see more than what’s happening on your best line. Rather, they look for uniformity across all of your production lines in scope.
“It’s not about showing the auditor one instance of doing things right. It’s about showing them that you are doing it consistently everywhere,” says Castilla.
He says it’s common for a supplier to walk the auditor to its newest and most automated line, where every requirement is visibly in place. But when the auditor checks the other three lines, it’s not consistent.
From a preparation standpoint, a self-assessment on your strongest line to increase the score you submit isn’t particularly useful. Instead, you want to walk the footprint the way the auditor will:
- Pick the line you’d least want them to see: Start the internal assessment where findings are most likely to occur.
- Check older and less automated areas: Where controls depend on people rather than equipment, standardization is more difficult and harder to evidence.
- Compare sites against each other: Look for instances where two or more plants score themselves differently on substantially the same process, which can highlight underlying problems or even difficulty understanding the standard itself.
- Assume every green will still be checked: Castilla notes that customers will still check even an all-green submission, meaning an unsupported green is a finding waiting to happen.
The Biggest Gap Isn’t Where You Think
Ask most pros which VDA 6.3 element causes the most trouble and they’ll say P6 (process analysis). It’s the factory floor, it’s observable, and an auditor can walk up and see it. Castilla called it the easy route from the auditor’s perspective.
Where he says the bigger gaps are, however, is P5 (supplier management).
“Visiting your vendor’s supplier isn’t something auditors can do as easily, so they rely more on the paper records and audit reports provided,” says Castilla.
He adds that while plants often claim their suppliers meet standards, the evidence often shows the exact opposite after a quality problem leads the customer to investigate deeper.
What auditors look for here is a traceable chain of evidence including prints and material specifications linked to PFMEAs and control plans, all the way down to shop floor measurement and machine capability.
“If you’re supposed to hold a diameter, you should be able to show the measurements are in place and the machines are capable of running to it,” Castilla says.
So, how far should you go in verifying your own supplier’s operation? Ultimately, the depth of verification depends on risk and on available resources. For instance, a low-risk part from a supplier with a good track record might be verified on paper, versus a safety component requiring physical evidence or firsthand observation.
“If your supplier says they have vision systems checking every single part, maybe you put a known bad part through a machine to see if it’s rejected or accepted.”
One Lead Auditor, Sixty Topic Areas, Three Continents
Preparing a VDA 6.3 self-assessment across multiple plants is a coordination problem that many companies underestimate.
For starters, the assessment requires a formally qualified lead auditor. The certification process itself is rigorous, involving prerequisite auditor and core tools training, five years of industrial experience, and a five-day course ending in an oral exam.
That person then pulls in subject matter experts across roughly 50 to 60 topic areas, spanning sales, program management, design, and manufacturing.
Castilla describes a hypothetical example of how this plays out in a multi-national company:
“Let’s say in India you have the manufacturing setup, purchasing is in America, and design and testing is in Europe. Doing all of this in spreadsheets becomes a nightmare.” .
Castilla points to several problems with this approach:
- Central-person bottleneck. Everything flows through the lead auditor, who becomes the single point of consolidation for the whole assessment.
- No visibility. Until the file comes back, you can’t tell whether a contributor is nearly finished, stuck, or working from a misunderstanding of the assignment.
- Questions that need multiple inputs. A plant may measure every 10 parts locally but send one part monthly to a European tech center for measurement against a tougher standard. Answering that question correctly needs both the Indian and the European input.
- Template drift: Contributors modify the template, or point to an attached document instead of answering the question, which leaves the lead auditor reassembling a puzzle.
- Language. Contributions in multiple languages compound every one of the problems above.
Where SharePoint and Excel Break Down in VDA 6.3 Self-Assessments
SharePoint and Microsoft 365 make it possible to share files, but a shared folder still can’t assign questions to owners or tie each answer to its evidence. Other gaps show up as the assessment comes together:
- No question-level change log. Version history shows when a file changed, though not who changed a grade on a single question, or why.
- No cross-site view. Comparing how two plants scored the same process means opening their workbooks side by side.
- Broken spreadsheets. Co-authoring lets every site edit the same workbook at once, which gives every site a chance to break it.
Part of the problem is the VDA 6.3 workbook itself. “Everybody complains about the current VDA solution, because it’s an Excel file with funky formulas,” Castilla says. “If you touch something by mistake, it breaks the formulas.”
Collaborative audit solutions, by comparison, assign each section to its SME owner and roll up results as each one is submitted, so the lead auditor can see progress in real time.
VDA 6.3 Audit Preparation: Where to Start
Asked what a quality director inheriting a multi-plant footprint should tackle first, Castilla points to two key priorities.
First, start with making sure you have qualified internal auditors. Scarcity of this credential is a real problem outside of Europe, as is making sure credentials are current. A VDA 6.3 qualified auditor certificate lasts five years, and renewing it requires ten audits across at least twenty audit days.
That means a plant that runs assessments only occasionally can find an entire year’s worth of audits invalidated due to lapsed credentials, a core argument for using audit tools that verify auditor qualifications at the time of scheduling.
Second, Castilla recommends mapping VDA requirements onto standards your team is already familiar with, such as ISO 9001 and IATF 16949. The reason is that VDA 6.3 terminology is specific and distinctly German, making them somewhat difficult to understand for those who are new to the process.
Note here that VDA 6.3 is weighted toward evidence and observation rather than procedure. Castilla’s read is that quality teams in the Americas, shaped by ISO habits, lean too hard on showing a document that describes the process. VDA 6.3 starts there, then asks to see it happening through records, measurements, and photos. Audit systems that capture that evidence like images and video, make the second half easier to satisfy.
Why VDA 6.3 Readiness Takes Longer Than You Think
VDA 6.3 readiness comes down to numerous factors, not least of all the challenge of demonstrating standardization across production lines and sites.
The plants that perform well on the European standard are those that leave plenty of lead time for preparation, including securing qualified auditors.
While the process is complex, the effort invested pays back beyond the business relationship with German automakers. Standardization to meet VDA 6.3 compliance makes most other OEM requirements easier to satisfy, while also helping prevent quality failures in the long term.
See how EASE Auditor Qualifications connects qualification to audit scheduling to prevent VDA 6.3 compliance surprises