What this is
What is a layered process audit?
What is a layered process audit?
A layered process audit is a short, standardised check of a small number of critical process steps, run by successive levels of management at successive frequencies against the identical checklist. A supervisor might run it daily, a manager weekly, and the site manager monthly, all checking the same items at the same process. The point is not any one audit's findings; it is that every tier of management is regularly and visibly present at the process.
How is it different from an internal audit?
An internal audit is periodic, broad and system-focused: it examines whether a management system conforms to a standard across many processes, typically annually or on a rolling schedule. A layered process audit is narrow, frequent and floor-focused: a fixed short checklist on a handful of process steps that matter most, checked far more often, by people who do not normally carry audit responsibility. The two are complementary, not substitutes.
Why does the same checklist have to be used at every layer?
Because the comparison across layers only means anything if the layers checked the same thing. If the supervisor's daily checklist and the manager's weekly one diverge, a pass at one tier and a fail at another cannot be reconciled, and the audit stops being able to show whether a control that held on the floor also held under scrutiny from higher up.
Scope
When is a layered process audit required?
This audit is the tiered, high-frequency floor check, and it sits alongside deeper single-topic audits and less structured management walks rather than replacing either.
Use this template when
- A critical process step is on its layered schedule and due at the supervisor, manager or site leadership frequency
- A finding elsewhere, a complaint or a quality escape suggests a control that should be holding at the floor is not
- A new or recently changed process needs frequent verification while confidence is being built that it holds under normal operation
- A customer-specific requirement names layered process audits as a condition of supply for a given process or product line
- Site leadership needs a structured, scheduled reason to be seen checking the same critical steps as the floor
Do not use it for
- Standard Work Verification (OPS-021), which does the deep, single-topic conformance check of one process against its full standard rather than a short cross-tier checklist
- Gemba Walk Record (OPS-015), which records an open-ended observational walk with whatever is raised, not a fixed checklist repeated identically at every tier
- 5S Audit (OPS-019), which checks workplace organisation and visual standards rather than whether a specific critical process step is being done as specified
- Internal Audit, the periodic, system-wide audit against the management system standard itself, which this record's frequent floor checks feed into but do not replace
- Tier Board Review (OPS-014), which records the daily management meeting's agenda and decisions, not a physical check carried out at the process
Compliance mapping
Which IATF requirements does this satisfy?
IATF 16949 requires the internal audit programme to prioritise processes based on risk and to address customer-specific requirements; it does not mandate a layered process audit by that name. The method reaches most automotive suppliers through OEM customer-specific requirements built on top of that clause, and has since spread into food and general manufacturing as a daily-management practice in its own right.
| Clause | Requirement | Where it lands |
|---|---|---|
| IATF 16949 cl.9.2.2.3 | Internal audit programme to prioritise manufacturing processes by risk and customer impact, and to address applicable customer-specific requirements | Header |
| IATF 16949 cl.9.1.1.1 | Monitoring and measurement of manufacturing processes to confirm they continue to meet product and process requirements | Findings |
| IATF 16949 cl.8.5.1.1 | Verification of job set-up and adherence to the control plan whenever a process is run | Findings |
| IATF 16949 cl.10.2.3 | Problem solving to address recurring nonconformities, distinguishing systemic causes from isolated ones | Outcome |
| IATF 16949 cl.9.2.1 | General internal audit requirement to determine whether the process conforms to planned arrangements | Conduct |
| ISO 9001 cl.9.1.1 | Monitoring, measurement, analysis and evaluation of process performance and effectiveness | Outcome |
| Customer-specific requirement | Named layered process audit obligation, frequency and escalation route as specified by the customer | Header |
What it does not cover
- Standard Work Verification, which examines one process in full depth against its documented standard rather than a short checklist shared across tiers.
- Internal Audit, the periodic, certification-scope audit of the management system as a whole, which a passing run of layered process audits does not substitute for.
- Root cause analysis of a repeat finding, which belongs in a dedicated investigation once an issue has escalated, not in the audit record that raised it.
- The corrective action itself, which belongs in the CAPA record referenced by the CAPA ID field, tracked to verified effectiveness rather than to a completed audit.
- Training or competency evidence for the operator, which belongs in the training record the finding may trigger, not in the audit that observed the gap.
Global
Layered Process Audit requirements by country
Layered process audits are not a government-mandated instrument in any jurisdiction; they are an industry and customer-driven method built on top of a certifiable management system standard. What differs by region is which scheme actually requires the practice and by what name.
IATF 16949 cl.9.2.2.3; OEM customer-specific requirements (General Motors, Ford, Stellantis)
Several major OEM customer-specific requirements name layered process audits explicitly, with defined frequencies and escalation routes for their supply base.
For suppliers to those OEMs, LPA is effectively mandatory: the CSR, not IATF 16949 itself, sets the detail.
VDA 6.3 process audit (Germany); IATF 16949 for suppliers into German OEMs
VDA's process audit is a related but distinct methodology, deeper and less frequent than an LPA, used alongside customer-specific LPA requirements where the OEM sets them.
A supplier can be compliant with VDA 6.3 process audit expectations and still be separately required to run layered process audits by an OEM CSR.
IATF 16949 for automotive suppliers; BRCGS internal audit programme expectations for food manufacturers
Automotive suppliers inherit the same OEM CSR-driven LPA obligation as elsewhere; food manufacturers adopt the method voluntarily to satisfy a general internal-verification expectation.
Outside automotive, using LPA is a choice of method to meet a broader audit-programme duty, not a named requirement in itself.
IATF 16949; North American OEM customer-specific requirements shared with the US
Integrated automotive supply chains mean Canadian suppliers face the same CSR-driven LPA obligations as US-based ones.
The obligation travels with the customer relationship rather than with the country.
ISO 9001 cl.9.1.1; no domestic OEM automotive scheme of comparable scale
With limited local automotive manufacturing, LPA is adopted voluntarily in food and general manufacturing as a daily-management discipline under the general monitoring requirement.
Adoption is a management choice about how to satisfy ISO 9001's monitoring clause, not a customer mandate.
IATF 16949:2016 cl.9.2.2.3; AIAG Layered Process Audit Guideline
The AIAG guideline is the closest thing to a common international reference for how to design and run the method, regardless of which OEM's CSR is in play.
Where no specific CSR applies, the AIAG guideline is the default reference for frequency, checklist design and escalation.
How to complete it
How to complete a layered process audit, step by step
The template captures a pass or fail against each item. Whether the audit programme is actually functioning as a layered check comes down to judgement calls the form does not force.
Check the supervisor's, manager's and site leader's completed audits against each other, not just each against its own history. If the manager's version has drifted into a broader walk, or the site leader's has been abbreviated, the comparison across layers has already broken even if every individual audit looks complete.
An audit completed at a desk from memory or from the previous week's record is not a layered process audit, whatever the Carried Out At The Process field says. The operator being present and asked is what surfaces the gap between the documented method and the one actually being used that shift.
When Repeat Finding From A Previous Layer is answered honestly, the real question is whether it was then escalated, not whether it was noticed again. A programme where repeat findings are recorded but rarely escalated to the next layer has a reporting culture problem sitting underneath an apparently working audit schedule.
A high compliance percentage earned on a form where several items were marked N/A to avoid a No, or where completeness percent is low because the audit was rushed, is not a high score in any meaningful sense. Both numbers need to be read together, and a low completeness percentage should discount confidence in the compliance figure next to it.
What auditors find
Most common layered process audit findings
Layered process audit findings are less often about the process being checked and more often about whether the audit programme itself is still doing what it was designed to do.
| Finding | Clause | What fixes it |
|---|---|---|
| Checklist content differs between the supervisor, manager and site leadership tiers. | IATF 16949 cl.9.2.2.3 | Lock the checklist to a single version across all tiers; only the frequency and layer should change. |
| Audit completed away from the process, without observing it running. | IATF 16949 cl.9.1.1.1 | Require Carried Out At The Process to be Yes before the record can be marked complete. |
| Operator not present or not asked during the audit. | IATF 16949 cl.8.5.1.1 | Treat Operator Present And Asked as a precondition, not an optional observation. |
| Repeat finding from a previous layer recorded but not escalated to the next layer. | IATF 16949 cl.10.2.3 | Force an escalation record whenever Repeat Finding From A Previous Layer is Yes. |
| Items routinely marked N/A that plainly applied on the day. | Customer-specific requirement | Require a reason whenever N/A is selected, and review N/A rates by auditor and item. |
| High compliance percent alongside a low completeness percent on the same record. | ISO 9001 cl.9.1.1 | Discount or flag any compliance score where completeness falls below a set threshold. |
| Monthly site leadership tier of the schedule has lapsed for several cycles. | IATF 16949 cl.9.2.2.3 | Report each layer's on-schedule rate separately; a healthy supervisor rate can mask a lapsed site tier. |
| Finding recorded as an individual lapse where the same gap appears across several operators or shifts. | IATF 16949 cl.10.2.3 | Ask whether the same finding recurs elsewhere before classifying it as isolated rather than systemic. |
| On-the-spot correction not attempted before the item was simply logged as failed. | IATF 16949 cl.9.2.1 | Expect an attempt at immediate correction to be recorded before escalation for anything correctable at the floor. |
| Action Required marked Yes with no CAPA ID, owner or date populated. | IATF 16949 cl.10.2.3 | Make CAPA ID and Action Owner mandatory fields whenever Action Required is Yes. |
Case in point
Case in point: the finding that passed three layers
A meat processing site ran a layered process audit on metal detector sensitivity checks in the packing area. For six consecutive weekly manager audits, the sensitivity test piece passed on the second attempt rather than the first, which the checklist recorded but which nobody marked as a repeat finding, because each manager treated their own audit as the first time they had personally seen it.
The site leadership's monthly audit picked up the same second-attempt pattern and, likewise, recorded it as a fresh observation rather than checking whether it had appeared on the supervisor's daily and the manager's weekly audits before. It had, every time, for six weeks. A customer audit later found the same intermittent sensitivity issue and traced it to a detector needing recalibration that no internal record had ever escalated.
Every individual audit had been completed correctly and honestly. What failed was the comparison across layers: nobody had been checking whether this week's finding matched last week's, at any tier, so a genuinely repeat finding was recorded eighteen separate times as though it were new.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- OPS-016
- Archetype
- Audit
- Record ID
- LPA-2026-000
- Scoring
- Compliance by layer
- Direction
- High is good
- Singleton
- Yes
- Basis
- IATF
- Links
- Links Standard Work Verification and Internal Audit
- Tags
- Daily management, Audit
- Sections
- 5
- Fields
- 47
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
15 fieldsAudit ID*
Auto sequence. Format LPA-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Layer*
Supervisor, manager, or site leadership.
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Auditor*
Process Audited*
Questions In The Check*
Questions Passed*
Completed At The Required Frequency*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
The Layering Is The Point
The same short checklist run by a supervisor daily, a manager weekly and the site manager monthly. What it finds is less important than who is seen to be looking.
Conduct
6 fieldsCarried Out At The Process*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Operator Present And Asked*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Same Checklist As Other Layers*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Completed In Full*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Findings Recorded Honestly*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Corrected On The Spot Where Possible*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Findings
6 fieldsStandard Work Followed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Documentation At The Point Of Use*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Settings Match The Specification*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Controls Being Performed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Repeat Finding From A Previous Layer*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Systemic Rather Than Individual*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Related records
1 fieldStandard Work Verification ID
Verification of the same process.
Links to OPS-021 Verification ID
Outcome
19 fieldsCompliance Percent*
Findings Raised*
Repeat Findings*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Escalated To The Next Layer*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Finding ID
Links to FDN-015 Finding ID
Next Audit Due*
Items Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Auditor*
Signature*
Area Manager*
Second Signature*
OPS-016 · record IDs look like LPA-2026-000 · Links Standard Work Verification and Internal Audit
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The checklist itself is the easy part. What actually slips is whether every tier keeps to the same schedule, whether a finding that crosses tiers gets escalated, and whether the score reflects a rushed audit rather than a controlled process.
Tracks the layered schedule across all three tiers against actual completion, and flags where one layer has lapsed while another keeps running.
Links a repeat or systemic finding to the CAPA record it should trigger, so escalation produces a tracked action rather than a note on the form.
Connects a standard-work or competency gap found at the process to the training record it points back to, rather than leaving it as an isolated audit line.
Compares findings across tiers and across cycles to surface a genuinely repeat or systemic pattern that no single audit, read alone, would show.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Layered Process Audit definitions and key terms
- Layered process audit
- A short, fixed checklist covering a small number of critical process steps, run identically by successive levels of management at successive frequencies, where the layering is the control, not the checklist content.
- Layer
- The management tier running a given audit instance: typically supervisor at the highest frequency, manager at a lower one, and site leadership at the lowest.
- Customer-specific requirement
- An additional requirement an OEM customer imposes on its supply base beyond IATF 16949 itself, through which the specifics of many suppliers' layered process audit obligations are actually set.
- AIAG
- Automotive Industry Action Group, the body that publishes common reference guidance, including a widely used guideline for designing and running layered process audits.
- Systemic finding
- A finding whose cause is shared across operators, shifts or lines rather than confined to one instance, and which therefore needs a broader corrective action than a single retrain or fix.
- Repeat finding
- A finding that matches one already recorded at an earlier audit, at the same tier or a different one, indicating the earlier correction did not hold or was never made.
- Escalation
- Passing a finding up to the next management layer or into a formal corrective action, rather than re-recording it at the same level each time it reappears.
- Standard work
- The documented, current best-known method for performing a task, which a layered process audit checks is actually being followed at the process, not just held on file.
FAQ
Frequently asked questions about layered process audit
Does IATF 16949 require layered process audits?+
Not by that name. IATF 16949 clause 9.2.2.3 requires the internal audit programme to address customer-specific requirements, and it is through OEM customer-specific requirements, most notably General Motors', that layered process audits become a named, mandatory method for many suppliers. Treat the requirement as coming from the customer, not the standard, when deciding scope and frequency.
How many critical steps should be on the checklist?+
Few. The method depends on a short list being checked often and consistently, not on comprehensive coverage. A checklist long enough to take real time to complete at each tier is a checklist that will get compressed or skipped under time pressure, which defeats the frequency the method relies on.
What should happen when the same finding appears at two different layers?+
It should escalate, not simply be re-recorded. A finding that survives from a supervisor's daily audit into a manager's weekly one means the correction after the first observation did not hold, and that is a more serious signal than either audit's individual result suggests on its own.
Is a low score at the supervisor layer worse than one at the site leadership layer?+
Not necessarily worse, but it means something different. A supervisor failing daily suggests an immediate floor-level control gap. A site leader failing monthly, on a checklist the supervisor has been passing all along, suggests either the checklist has drifted between tiers or the senior audit is not being run with the same rigour.
Should N/A be used often?+
Rarely, and only when an item genuinely does not apply that day, such as a process not running. N/A removes the item from the compliance denominator, so frequent or convenient use of it inflates the score without the process actually being verified, which is exactly the outcome the audit exists to prevent.
Does a passing layered process audit mean the process is under control?+
It means the specific critical steps checked were being done as specified at the moment of that audit, at that tier. It is evidence, not proof of ongoing control, and it does not substitute for the deeper conformance check a standard work verification or internal audit provides on its own schedule.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Daily Management System
Audit Finding Record
Records a single audit finding with its evidence, clause reference and classification
Daily Production Report
Summarises the day across lines: output, attainment, losses, quality and the issues carried forward
Tier Board Review
Runs the daily management meeting against a fixed agenda and records what was agreed and by whom
Gemba Walk Record
Records a structured walk of the process by a manager, what was observed and what was raised
Meeting and Action Log
Holds the decisions and actions from any operational meeting, with an owner and a date on each
Daily Priority Plan
Sets the small number of things that must happen today and who owns each
More in Daily Management
Tier Board Review
Runs the daily management meeting against a fixed agenda and records what was agreed and by whom
Gemba Walk Record
Records a structured walk of the process by a manager, what was observed and what was raised
Meeting and Action Log
Holds the decisions and actions from any operational meeting, with an owner and a date on each
Daily Priority Plan
Sets the small number of things that must happen today and who owns each
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- IATF 16949:2016 clause 9.2.2.3, Internal audit programme
- AIAG Layered Process Audit Guideline
- VDA 6.3 Process Audit (Germany)
- ISO 9001:2015 clause 9.1.1, Monitoring, measurement, analysis and evaluation
- General Motors, Ford and Stellantis customer-specific requirements (automotive supply base)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.