CQI-8 is the Automotive Industry Action Group (AIAG) Layered Process Audit Guideline, first published in 2005 and later revised. It defines a common framework for LPAs that any automotive OEM or supplier at any tier can adopt. The method is widely used outside automotive as well, because the logic is not industry-specific.

What should go on an LPA checklist?

A short list, usually five to fifteen items, of the highest-risk process controls, each written as a yes/no question an auditor can verify in seconds at the station. Draw items from past defect root causes, control-plan critical steps, error-proofing that must be present, and safety-critical actions. Every 'no' should trigger immediate correction.

How often should layered process audits be done?

There is no single mandated schedule; each plant sets frequencies to its risk. A common pattern is front-line supervisors auditing every shift or day, middle managers weekly, and senior leaders monthly, with all layers using the same core checklist. Frequency increases toward the floor.

How do layered process audits prevent improvements from eroding?

They check the standard so frequently that drift is caught while it is still small. Improvements usually leak away one shortcut at a time rather than failing all at once, and a daily layered audit is a tripwire on that slide. LPAs pair with standard work and visual management to keep the defined method in place.

Layered Process Audits (LPA)

Q: What is a layered process audit?

A layered process audit (LPA) is a system where multiple layers of management repeatedly verify the same high-risk process steps against short checklists on a set cadence. It checks how the work is done rather than inspecting finished parts, so process drift is caught before it turns into defects.

Q: What does 'layered' mean in a layered process audit?

Layered means several levels of the organization audit the same critical controls at different frequencies, for example a supervisor daily, a department manager weekly, and a plant manager monthly. The overlap is deliberate: what one auditor misses, another catches, and senior involvement shows operators the standard matters.

Q: How is an LPA different from a regular audit?

An LPA checks the process as it runs, happens frequently (daily to monthly), and is done by line management. A traditional system audit checks the management system, happens annually or per certification cycle, and is done by trained auditors. LPAs catch process drift in near-real time; system audits catch systemic gaps at a point in time.

Multiple layers of management checking the same high-risk process steps on a cadence, catching drift before it turns into defects, and keeping standards from quietly eroding.

A layered process audit (LPA) is a system of frequent, short checks in which multiple layers of management verify that a plant's highest-risk process steps are being done exactly as specified. The same critical controls get audited over and over, by different people at different levels, on a set cadence. The aim is to catch drift before it becomes a defect.

An LPA is not a product inspection and not an annual system audit. It checks the process is the fixture seated, is the torque setting right, is the operator following the current method, and it does so often, by many eyes, so that a slow slide away from standard gets caught in days rather than at the next customer complaint. The method was formalized in the automotive sector but the logic travels anywhere. This guide covers how LPAs work, who audits at each layer, and how to build a checklist that actually catches drift. For the broader picture, see our overview of lean manufacturing.

What is a layered process audit?

A layered process audit is a recurring verification of high-risk process controls, performed by several layers of an organization at different frequencies, using short standardized checklists. The word layered is the whole idea: a supervisor might audit a station daily, a department manager weekly, and a plant manager monthly, all checking overlapping sets of the same critical items. No single layer carries the whole load, and the redundancy is deliberate. What one auditor overlooks, another catches.

The method was codified by the Automotive Industry Action Group (AIAG) in its CQI-8 Layered Process Audit Guideline, first published in 2005 and revised since. It grew out of automotive quality practice, where it is often expected by customers even when a standard like IATF 16949 does not strictly mandate it. But nothing about LPAs is automotive-specific. Any plant with critical process steps that must be done a certain way, a torque, a temperature, a seal, a cleaning step, can run them.

Higher layers audit less often but the same items. The overlap is what makes the system hard to fool.

How is an LPA different from a regular audit?

An LPA differs from a regular quality audit in three ways: it checks the process not the product, it happens frequently not annually, and it is done by line management not just auditors. A traditional system audit, the kind behind a quality audit checklist for a certification, is deep, infrequent, and run by trained auditors against a standard. An LPA is shallow, constant, and run by the people who own the area.

That difference in cadence is the point. A yearly audit tells you the system looked compliant on one day. A daily LPA tells you whether the critical steps are being followed today and the day after, and the day after that. Process drift, the slow substitution of "how we've been doing it lately" for "how the standard says", is invisible to an annual audit and exactly what a layered audit is built to catch. Where a system audit verifies that a procedure exists, an LPA verifies that the procedure is being executed on the floor right now.

	Layered process audit	Traditional system audit
What it checks	The process, as it runs	The management system, on paper and in practice
Frequency	Daily to monthly, by layer	Annually or per certification cycle
Who does it	Line management, all levels	Trained internal or third-party auditors
Depth	Short, focused on critical controls	Broad and deep
Catches	Process drift, in near-real time	Systemic gaps, at a point in time

LPAs and system audits are complements, not substitutes. One watches the process daily; the other checks the system periodically.

Who audits at each layer, and how often?

Each management level audits at a frequency that fits its role: the closer to the floor, the more often. There is no single mandated schedule, the CQI-8 approach lets each plant set frequencies to its risk, but a common pattern looks like this: front-line supervisors or team leads audit every shift or every day, middle managers weekly, and senior site leaders monthly. Every layer uses the same core checklist, though higher layers may audit fewer stations per visit.

The reason to pull senior leaders into hands-on auditing is not oversight for its own sake. When a plant manager stands at a station once a month and works through the same checklist an operator sees daily, three things happen: leadership sees the real state of the process, operators see that the standard matters to the top of the building, and the checklist itself gets pressure-tested by fresh eyes. An LPA where only supervisors ever audit loses most of its value. This is closely related to leader standard work the LPA is often one of the recurring checks written into a leader's daily or weekly routine.

What goes on an LPA checklist?

An LPA checklist holds a short list of the highest-risk process controls, each written as a yes/no question an auditor can verify in seconds at the station. Short is essential, an LPA that takes 40 minutes will not get done daily. Most effective checklists run five to fifteen items and take a few minutes. The items should come from where risk actually lives: the root causes of past defects, the critical steps in the control plan, error-proofing that must be confirmed present, and safety-critical actions.

Good LPA questions are specific and binary. "Is the process good?" is useless. "Is the torque wrench set to 12 Nm and within calibration date?" is auditable. "Is the current revision of the work instruction posted at the station?" is auditable. Each item should tie to a real failure mode, so a "no" answer means something concrete is wrong and triggers an immediate correction, not a note for later. The moment a nonconformity is found, the auditor acts or escalates; the finding is not filed away, it is fixed.

Every checklist item is binary, and every "no" forces an action, fix it now or escalate it. Nothing is left as a note.

How do you set up an LPA program?

Setting up a layered process audit program follows a clear sequence, and skipping the risk-selection step is the most common way to build one that wastes everyone's time.

Identify the high-risk process steps. Pull from control plans, past defects and complaints, safety-critical operations, and error-proofing that must stay in place. Audit the vital few, not everything.
Write short, binary checklists. Turn each risk into a yes/no question verifiable in seconds at the station. Keep each layer's list to a few minutes of work.
Define the layers and frequencies. Decide who audits at each level and how often, weighted toward the floor. Put it on a schedule so it is a routine, not a favor.
Train the auditors. Make sure every layer knows what "good" looks like for each item and what to do when they find a "no."
Audit, and fix findings on the spot. The value is in immediate correction. A nonconformity found in an LPA is a live problem to resolve now, not a data point to trend later.
Escalate and track what cannot be fixed immediately. Route findings that need more than a station-level fix to root cause analysis and track them to closure.
Review coverage and refresh the checklist. Rotate stations so all get covered, and update items as new failure modes appear and old ones are designed out.

Layered process audits: by the numbers

The method is documented in a recognized industry guideline, not invented for this article:

The AIAG CQI-8 Layered Process Audit Guideline defines the standard framework: multiple organizational levels verifying the same key process controls that ensure product quality, on a defined cadence.
CQI-8 was first published in 2005 and revised (the 2014 second edition is widely referenced), providing common definitions any automotive OEM or supplier at any tier can adopt, which is why the same method now appears well outside automotive.
The distinguishing principle is layering: the guideline calls for audits by several management levels rather than a single auditor, so the same critical controls are verified repeatedly by different people.

How do LPAs keep improvements from eroding?

LPAs keep improvements from eroding by checking the standard so frequently that drift is caught while it is still small. Most gains do not disappear in one dramatic failure; they leak away one shortcut at a time, an operator skips a step under time pressure, the next shift copies the shortcut, and within weeks the improved method is gone and nobody decided to abandon it. A daily layered audit is a tripwire on exactly that slide. It pairs naturally with visual management and the discipline of standard work: standard work defines the method, and the LPA verifies it is still being followed.

The limitation of a paper LPA is speed and visibility. If audits are recorded on clipboards and the results are keyed into a spreadsheet next week, the pattern in the findings, which step keeps failing, on which shift, at which station, stays hidden until someone tallies it, which often means never. The value of an LPA compounds when findings are captured digitally at the point of audit, escalations route themselves, and the trend is visible the same day, so a recurring "no" on one item becomes a signal instead of a statistic. That is the loop Harmony builds for plants, and the shift CLS made when it moved off paper. Run short checklists, audit at every layer, fix findings on the spot, and the standard you worked to set actually stays set.