Automotive Process Audit Checklist: IATF 16949 and VDA 6.3
Build a process audit checklist that answers IATF 16949 and VDA 6.3 questions, scores findings and keeps your automotive quality management program ready.
Contents
- What a process audit checklist does
- IATF 16949 questions to include
- VDA 6.3 questions and scoring
- Lay out the checklist sections
- Gather the evidence before the walk
- Score findings and set actions
- Keep the checklist current
- Questions about process audit checklists
- What should a process audit checklist for the automotive industry contain?
- Is there a process audit checklist IATF 16949 PDF I can download?
- How does a VDA 6.3 process audit checklist differ?
- Who should carry out the process audit?
- How often should the checklist be reviewed?
An automotive process audit checklist is a structured set of questions that follows one process from its inputs to its outputs and checks it against IATF 16949 and VDA 6.3 expectations. The checklist pairs each process audit question with the evidence an auditor asks to see, such as the control plan, the APQP record and the PPAP file. Scoring then turns those answers into findings a team can act on.
- Build the checklist around one process at a time, not around the whole quality manual.
- Tie every question to a document or record, because an answer without evidence cannot be scored.
- Use VDA 6.3 for a scored process walk and IATF 16949 for the management system requirements behind it.
- Keep the questions in a shared template so scores from different audits can be compared.
- Close each finding with an owner, a correction and a check that the correction worked.
What a process audit checklist does
A process audit checklist guides an auditor through a single process and records what was seen against defined requirements. The checklist turns a broad standard into process audit questions that a team can answer on the floor with documents and observation. Automotive quality management relies on this approach because a document review alone does not show whether a process is controlled.
The checklist sits inside your internal safety and process audit program and gives each audit the same shape. Audit scoring starts from the answers, so a consistent checklist keeps results comparable across shifts, lines and sites. A checklist written for one process also makes it easier to train a new internal auditor on that process.
Structure matters more than length for a working checklist. Each row should name the requirement, the evidence to look for and the place to record the result. Rows grouped by process step let an auditor follow the product flow instead of jumping between clauses.
IATF 16949 questions to include
IATF 16949 asks whether the process meets customer requirements and whether the supporting records exist. A process audit checklist for IATF 16949 covers the control plan, the APQP record, the PPAP file and the reaction plan for nonconforming output. The checklist should also confirm that process owners know their targets and what triggers corrective action.
Risk thinking belongs in the questions, not in a separate chapter. Ask how the process team identified risk, how that risk shaped the control plan and how the team reviews it after a change. Questions on competence and calibration fit the same section, because a trained operator with an uncalibrated gauge is still an uncontrolled process.
Many auditors search for a process audit checklist IATF 16949 pdf, but a fixed file ages quickly. Build the checklist in a shared document with clause references and an owner for each question. Review it when a customer requirement, a process change or an audit finding affects the section.
VDA 6.3 questions and scoring
VDA 6.3 is a process audit method that scores each question on how well the process meets the requirement. Its process audit checklist follows the product from potential analysis through series production, with questions grouped by element. A VDA 6.3 process audit checklist therefore needs a scored row for every question, not a simple pass or fail.
The method weighs elements differently, so the checklist should show the element each question belongs to. Scoring rewards a process with evidence of control and lowers the score when a requirement is partly met. The auditor writes down the evidence behind each score, because the score without the observation cannot be defended later.
VDA 6.3 and IATF 16949 work together rather than compete. IATF 16949 sets the management system requirements that a process must satisfy, and VDA 6.3 provides the scored walk through that process. Use one checklist that shows both references so the audit answers both needs.
Lay out the checklist sections
A checklist should open with identification, then follow the process in the order work happens. Identification covers the process name, the audit scope, the date and the auditor. The process steps that follow mirror the flow of product and information from receiving to release.
Each process step section repeats the same pattern of question, evidence and result. A repeated pattern lets the auditor work quickly and keeps the record readable for the person who closes the findings. Keep a final section for findings, owners and dates so the audit ends with actions.
A short table can hold the row structure, and the auditor fills it during the walk. The table below shows one way to arrange the columns for a scored audit.
| Column | What it records |
|---|---|
| Process step | The stage of the process being audited |
| Question | The requirement written as a process audit question |
| Evidence | The document, record or observation to check |
| Score | The result on the scoring scale you use |
| Finding | The gap and the action agreed with the process owner |
Gather the evidence before the walk
Evidence collection should happen before the auditor steps onto the floor. Ask the process owner for the control plan, the APQP record, the PPAP file, the latest internal audit and the current corrective actions. Reading these first lets the auditor form questions that the walk then confirms or contradicts.
Product and process documents show what should happen, and observation shows what does happen. The checklist should force the auditor to compare the two, because a control plan that no operator follows is a gap. Keep the evidence list close to the related question so the audit does not turn into a document hunt.
Sampling keeps the audit practical, and the checklist should state what was sampled. Note the part, the shift, the machine and the record reviewed so another auditor can repeat the check. Naming the sample in the record protects the audit score from being read as a judgment of the whole process.
Score findings and set actions
Audit scoring turns observations into a result the team can compare and track. Each question needs a defined scale, whether that is full, partial or no conformity, or the VDA 6.3 scale. Write the scale beside the question so every auditor applies it the same way.
A finding should name the requirement, the evidence and the effect on the process. The process owner then agrees a correction, a root cause analysis and a date. Close the loop by checking that the correction removed the gap and that the checklist question was answered again.
Actions belong in the same system that holds the audit record, not in a separate file. Linking the finding to the audit question makes the next audit faster and shows whether the process improved. A finding without an owner and a date stays open and weakens the whole program.
Keep the checklist current
A checklist ages when the process changes and nobody updates the questions. Add a review step to the audit program so the checklist is checked against the current control plan and customer requirements. Give each section a named owner who knows the process and can approve changes.
Track which questions produced findings over several audits and look at the pattern. Repeated findings on the same question suggest the process or the question needs attention. Remove a question only when the requirement it covered no longer applies to the process.
Version control keeps the scored record trustworthy. Store the checklist with a version and a date, and record which version was used for each audit. When a VDA 6.3 or IATF 16949 requirement changes, update the affected rows and note the change.
Questions about process audit checklists
What should a process audit checklist for the automotive industry contain?
A process audit checklist for the automotive industry contains the process steps, the requirement behind each question, the evidence to check and a place to record the result. It should reference IATF 16949 and, where you use it, VDA 6.3, and it should end with findings and actions. The checklist follows product and information flow so the auditor can walk the process in order.
Is there a process audit checklist IATF 16949 PDF I can download?
A ready-made process audit checklist IATF 16949 PDF exists in many places, but it ages as requirements and processes change. A checklist built in a shared document with clause references and a named owner stays current and can be scored the same way each time. Use any published file as a reference only and adapt it to the process you audit.
How does a VDA 6.3 process audit checklist differ?
A VDA 6.3 process audit checklist scores each question instead of recording only pass or fail. It groups questions by element and follows the product from potential analysis to series production. The same checklist can carry the IATF 16949 reference beside each VDA 6.3 question, so one audit serves both.
Who should carry out the process audit?
A trained internal auditor who does not own the process being audited should carry out the process audit. That separation keeps the score independent and lets the auditor ask hard questions. Where a finding touches a specialized area, bring in a qualified specialist rather than answering for them.
How often should the checklist be reviewed?
The checklist should be reviewed when the process, a customer requirement or an audit finding changes what the questions must cover. Set a review point in the audit program and give each section an owner. Version and date the file so every audit record shows which checklist was used.