Why automotive audits are different
An IATF 16949 plant does not run "an internal audit." It runs a layered programme of audits — several distinct types, at several frequencies, across every process and shift — because the automotive standard, and every OEM customer-specific requirement sitting on top of it, demands defence in depth. A defect that reaches a vehicle is a recall; the whole point of the audit stack is to catch the drift long before the part leaves the plant. For an Indian auto-component supplier in the Pune, Chennai or NCR belt, this is the daily reality of holding an OEM's business.
The good news is that every one of these audit types runs on the same machinery: a reusable clause- or control-plan-mapped checklist, a plan by frequency, a competent and authorised auditor, conformance recorded on the floor, and findings driven to closure. That is why an ISO 9001 & IATF 16949 audit software can carry the whole stack rather than needing a different tool per audit type — the engine is one, described in the audit-management pillar; only the checklist and cadence change.
The four-layer audit stack
Four audit types make up the core of an automotive quality-audit programme. Each answers a different question, and a mature plant runs all four in concert.
| Audit type | What it checks | Typical cadence |
|---|---|---|
| System audit | The QMS against IATF 16949 clauses and your own procedures | Annual, full coverage across the cycle |
| Process audit | Each manufacturing process against its control plan, setup and parameters | Planned rotation, risk-weighted |
| Layered process audit (LPA) | Key controls on critical processes, by several management layers | Daily / weekly / monthly by layer |
| Product audit | The finished part against specification — parameters, samples, defects | Per part family, scheduled |
The distinction that trips teams up is between the process audit and the product audit. A process audit asks whether the process is being run correctly — is the control plan followed, are parameters within limits, is the setup verified. A product audit asks whether the output is actually conforming — it measures the part. Both are essential, and in a good system they are different audit types because the product audit records data a process audit does not: parameter checks, multiple sample readings and defect categories per requirement.
Layered process audits (LPA)
The layered process audit is the automotive world's answer to the fact that a once-a-year audit cannot keep a process under control. Instead of depth, LPA uses frequency and layers: the same short checklist of the most critical controls is audited by a team leader daily, a supervisor weekly and a manager monthly — so leadership stays physically close to the floor and drift is caught within hours, not months.
Operationally, an LPA is just an audit with a short checklist, a high frequency and an assignment that rotates by management layer. On an audit system that means a compact reusable template, a plan that generates the daily, weekly and monthly occurrences automatically, and mobile checklist entry so a supervisor can complete the audit at the machine on a phone rather than carrying a clipboard back to a desk. Any non-conformance an LPA raises enters the same closure loop as a system-audit finding, which is what stops LPAs becoming a tick-box ritual.
Tracking LPAs, process audits and product audits in separate files?
See the whole IATF audit stack — system, process, LPA and product — on one plan and one NC register, live in 30 minutes on your own control plans.
Product audits — parameters, samples, defects
The product audit is where automotive auditing gets quantitative. Rather than a conformance verdict against a clause, the auditor measures the part against its control plan and records real data per requirement. A capable product-audit type captures exactly the fields the shop floor needs:
Parameter checks
Each characteristic checked against its specification, with the control-plan reference, so the audit ties directly to the part's controls.
SpecificationSample readings
Multiple sample measurements per characteristic, so variation across a small batch is visible rather than a single go/no-go.
Samples 1–5Defect grading
Defects categorised A, B or C with a remark, so severity is captured and a critical defect is unmistakable in the report.
Defect A/B/CA product audit also carries header context a system audit does not — department, cavity or mould numbers, sample reference and control-plan number — so the report is unambiguous about exactly what was audited. The result is a formatted product-audit report showing each requirement with its parameter checks, specification, sample readings, defect categories, compliance and remark. For the full method, see the dedicated product and process audit software page.
Auditor competency the IATF way
IATF 16949 is explicit that internal auditors must be competent, and that competency must be demonstrated — knowledge of the standard, of the core tools, of the process being audited and of customer-specific requirements. That is not a certificate in a drawer; it is a maintained record. A serious programme scores each auditor against criteria, attaches the evidence, records which audit types they are authorised to conduct, and refuses to assign an unqualified person. So a product audit that needs measurement competence, or a system audit that needs clause depth, only ever goes to someone the record shows is qualified for it — and when the registrar asks how you qualify your auditors, the answer is one screen, not a scramble.
Hosting OEM customer audits
Not every automotive audit is one you conduct. When an OEM customer audits your plant — or your registrar runs the certification or surveillance audit — you are the auditee, and the challenge flips from finding issues to producing evidence on demand. A good system hosts these audits as their own types, so the findings raised against you are logged, graded and driven to closure with the same discipline as your internal findings, and your NC register, closure history and audit evidence are ready to show without a fire drill. This hosting discipline is covered in depth in hosting customer and certification-body audits, and it is the difference between a calm OEM audit and a panicked one.
One engine behind the whole stack
Picture a Tier-1 supplier certified to IATF 16949 across two plants. One set of clause-mapped templates drives the annual system audits; process-audit templates tied to each control plan drive the process rotation; a compact LPA template generates daily, weekly and monthly layered audits; and a product-audit template captures parameter checks, samples and defect grades on the floor. Every finding — internal, LPA or product — lands in one NC register, graded and flagged fresh or repetitive, and drives through auditee, coordinator and auditor sign-off to closure. When the OEM customer audit arrives, the same system hosts it and produces the evidence. All of it rides one shared document, party and user engine.
How Fast Audit runs the stack
Fast Audit Software carries the entire automotive audit stack on one platform, so a plant does not stitch together separate tools for system, process, LPA and product audits. Mapping the stack to the product:
Because it rides the shared platform, the automotive stack sits alongside your supplier audits and your EHS audits, and a corporate quality function can run it across a group of plants from one instance — one programme, one NC register, one source of truth for every OEM and every registrar.
Frequently asked questions
What audits does an IATF 16949 plant have to run?
IATF 16949 requires a layered internal-audit programme rather than a single annual audit. A certified plant runs quality management system audits against the standard's clauses, manufacturing process audits of each process against its control plan and customer-specific requirements, and product audits that verify finished parts against specification. Many plants add layered process audits (LPA). All are internal audits and must be planned, conducted by competent auditors and closed with corrective action.
What is a layered process audit (LPA)?
A layered process audit is a short, frequent audit of the same critical process controls, conducted by several layers of management — team leader daily, supervisor weekly, manager monthly, for example. Instead of one deep audit a year, LPA applies many shallow, high-frequency checks to the controls that most affect quality, so drift is caught early. LPAs run on the same audit engine as system and product audits: a reusable checklist, a plan by layer and frequency, conduct on the floor, and findings driven to closure.
What is the difference between a process audit and a product audit?
A process audit examines how a manufacturing process is run — whether it follows its control plan, work instructions, setup and control parameters — and is conducted at the process. A product audit examines the output — a finished or in-process part checked against its specification, with parameter measurements, sample readings and defect grading against a control-plan reference. In an audit system the product-audit type records parameter checks, multiple sample readings and defect categories per requirement, which a process audit does not.
How do OEM customer audits fit into the programme?
When an OEM customer audits your plant, you are the auditee rather than the auditor. A good system hosts that customer audit as its own audit type, so the findings the customer raises against you are logged, graded and driven to closure with the same discipline as internal findings — and the evidence, closure history and NC register are ready to show the OEM on demand. The same applies to the certification-body audit run by your registrar.
Why do automotive plants need audit software rather than spreadsheets?
An IATF plant runs system, process, layered and product audits across many processes and shifts, with auditor competency to evidence, findings to grade and corrective actions to close on due dates — more than a spreadsheet can keep current. Audit software generates the annual plan automatically, restricts assignment to authorised auditors, records product-audit parameter and defect data, flags repeat NCs, chases overdue actions, and produces the NC register and dashboards an OEM customer or IATF registrar will ask to see.
Can Fast Audit record product-audit parameter and defect data?
Yes. The product-audit type records parameter checks against the control-plan specification, multiple sample readings per characteristic, and defect categories A, B and C with a remark, plus header context such as department, cavity or mould numbers, sample reference and control-plan number. It produces a formatted product-audit report per audit, and non-conformances flow into the same graded, multi-role closure workflow as every other audit type.