Layered Process Audits (LPA): What They Are and How to Run Them
.webp)
published
September 29, 2026
Key Takeaways
A layered process audit (LPA) is a short, frequent audit to verify that a standard is being followed correctly on the shop floor.
LPAs run far more often than a standard quality audit and focus on a handful of high-risk process steps rather than a full system review.
The Automotive Industry Action Group's CQI-8 guideline is the industry-standard framework for structuring LPA layers, checklists, and ownership.
A working LPA program typically runs 4 audit layers, with frequency dropping and scope widening as the audit moves from operator to site leadership.
Paper-based LPA programs tend to decay within months. Digital scheduling, checklists, and escalation keep the audits from quietly stopping once the novelty wears off.
Most manufacturers already have a documented standard for how a process should run. The harder problem is knowing whether operators are following it on any given shift, on any given line. A layered process audit (LPA) answers that question directly.
What Is a Layered Process Audit?
A layered process audit is a short, structured check that verifies operators are following a defined process. It's performed routinely by multiple levels of the organization, not just the quality department.
Where a traditional audit asks whether the documented process is sound, an LPA asks a narrower, more frequent question: Is the process being followed right now, on this shift, at this station?
The "layered" part refers to who does the checking. Operators audit their own station daily; supervisors, managers, and site leadership add their own layers, with less frequent audits.
{{callout1}}
LPA vs. Standard Quality Audits
A standard quality audit is comprehensive and infrequent: a quality team reviews documentation, procedures, and records a few times a year, often ahead of a certification renewal.
An LPA is the opposite on both counts. It's narrow, covering a handful of high-risk checkpoints identified through past defects or a failure mode effect analysis (FMEA), and it's frequent, with operators often running it daily.
The two aren't substitutes. A standard audit confirms the system is designed correctly; an LPA confirms people are running it that way today.
The 4 Layers of an LPA
Most LPA programs, including those built around AIAG's CQI-8 guideline, use 4 audit layers. Frequency drops and audit scope widens as the layer moves up.
- Operator (daily): Operators self-audit their station at the start of a shift, checking the same critical points every time.
- Supervisor (weekly): Supervisors audit their area on a rotating schedule, verifying operator self-audits are accurate and catching drift the operator might miss.
- Plant or department manager (monthly): Managers audit across multiple lines or departments, looking for patterns rather than isolated misses.
- Site leadership (quarterly): Plant or site leaders sample a handful of stations. Their real target is the audit program: Is it still running as intended, or has it stalled?
Each layer sees a different slice of the same standard, which is why LPA makes gaps hard to hide. An operator might not notice a small drift in their habits, but a supervisor auditing the same station with fresh eyes usually will.
How to Run a Layered Process Audit
Building an LPA program includes 5 steps:
- Identify high-risk process steps: Pull from past defects, customer complaints, and your FMEA to find the stations where a miss matters. Auditing every station and step equally spreads attention too thin to catch anything.
- Write specific checklist questions: A question like "Is the process being followed?" doesn't hold up under repetition. "Is the torque wrench calibration sticker current?" does.
- Assign layers and frequency: Use a RASIC (responsible, approve, support, inform, consult) chart to document who audits what, how often, and who's accountable when an audit gets missed.
- Train every auditor: Supervisors and managers need clarity on what a pass or fail looks like, just as operators do, since they run the weekly and monthly layers.
- Close the loop on every finding: A finding that never gets a corrective action is as bad as not auditing at all.
Benefits of Layered Process Audits
The core benefit is timing: An operator LPA catches a process drift while the line is still running, not after a customer complaint or a failed shipment forces the question.
There's a cultural effect too. When operators know a supervisor might check their station this week, and a plant manager might check it this month, the standard becomes something the whole team is accountable for.
Leader standard work built around this kind of routine verification tends to hold up better over time than audits that only happen from the top down.
{{callout2}}
How to Digitize Layered Process Audits
Paper-based LPA programs have a predictable failure mode: the checklists get filled out less carefully every month, findings stop getting logged, and the whole program stops within a couple of quarters.
Digital LPA tools fix the parts that decay fastest. A scheduling engine assigns each layer's audit automatically and reminds the right person when one is due. Checklists live in one place, built once and reused across every shift. When a finding comes in, it drops straight into a corrective action workflow with an owner and a due date attached, and the history is there whenever a recurring issue calls for root cause analysis.
Why Redzone for Layered Process Audits
Most LPA programs don't fail because of a bad checklist. They fail because nobody remembers to run it. Redzone automates the scheduling, reminders, and escalation that keep every layer running on its own cadence, and routes every finding straight into a corrective-action workflow with an owner and a due date attached.
See how Redzone's Reliability software keeps LPA programs running past the first quarter.
Frequently Asked Questions
What is the purpose of a layered process audit?
The first LPA layer catches process deviations while a line is running instead of after a defect ships. Subsequent layers verify that operators are following the standard on the floor.
What is the difference between a process audit and a layered process audit?
A standard process audit is a periodic, comprehensive review, usually run by quality staff a few times a year. An LPA is short, frequent, and conducted by multiple levels of the organization, from operators to plant leadership.
What are CQI-8 layered process audits?
CQI-8 is the Automotive Industry Action Group's Layered Process Audit Guideline. It's the industry-standard framework for structuring audit layers, building checklists, and assigning roles. It's widely used across automotive and adopted by other regulated manufacturers.
Who is responsible for conducting a layered process audit?
Responsibility spans every layer: operators self-check daily, supervisors audit weekly, plant or department managers audit monthly, and site leadership audits quarterly. A RASIC chart typically documents who owns each layer.
How often should a layered process audit be conducted?
Frequency decreases as audit level rises: daily for operators, weekly for supervisors, monthly for managers, and quarterly for site leadership. Higher-risk stations get audited more often than stable, low-risk ones.
