Layered Process Audits: A Practical Guide With Examples

A layered process audit (LPA) is a short, frequent check that the critical controls on a manufacturing process are being followed, carried out by several "layers" of the organization, from shift supervisors up to plant leadership. Instead of inspecting finished parts, an LPA asks whether the process is running the way it is supposed to, so problems are caught before they turn into defects.

This guide explains how layered process audits work, when customers require them, how often each layer audits, how to set up a program and write good questions, and what to do when an audit finds a problem. It includes an example schedule and question bank you can adapt.

What is a layered process audit?

The "layers" in a layered process audit are levels of the organization. Each layer checks the same short list of high-risk process points, but at a different frequency: the people closest to the work audit most often, and senior leaders audit less often. Because many people check the same points, a step that gets skipped on one shift is likely to be caught on the next.

A typical LPA takes a few minutes and happens at the workstation. The auditor works through a short checklist of yes/no questions, talks to the operator, and corrects small deviations on the spot. LPAs are most closely associated with automotive manufacturing, but the method works in any operation with defined standard work, including aerospace, medical devices and food production.

Layered process audit vs. process audit vs. product audit

LPAs don't replace your other audits. They sit alongside them and answer a different question:

For more on checking parts rather than processes, see our guide to part and product inspection. For system-level audits, see mastering the internal quality audit.

Are layered process audits required?

IATF 16949 itself doesn't name layered process audits as a requirement. It requires an internal audit program that covers quality management system, manufacturing process and product audits, and it requires you to evaluate your customers' customer-specific requirements (CSRs) and include them in your quality management system.

That is where LPAs usually come from. Several automakers make them a customer-specific requirement. For example, GM's CSRs for IATF 16949 require suppliers to run an internal layered process audit process that checks compliance to standardized work, identifies improvement opportunities and provides coaching, and they specify that the audits are led by competent management. GM's current CSRs took effect on 30 October 2025, and OEMs revise their CSRs regularly, so always check the latest versions published on the IATF Global Oversight site.

The common reference for designing an LPA program is the Automotive Industry Action Group's CQI-8 Layered Process Audit Guideline, whose 2nd edition was published in 2014. Some customers require you to follow it.

Outside automotive, standards such as ISO 9001, AS9100 and ISO 13485 don't require LPAs, but many manufacturers still use them as a practical way to monitor that processes run as documented. For the wider automotive picture, see our automotive quality management system guide.

The layers and how often each one audits

There is no single correct structure, and your customer may set its own. This is a common starting point for a plant:

Rotate auditors across areas from time to time. A supervisor auditing a neighboring line sees things that someone who works there every day stops noticing.

How to set up an LPA program

1. Pick the processes. Start with the operations that carry the most risk: safety and special characteristics, high-severity failure modes in your PFMEA, and anything behind a recent customer complaint. Pilot on one or two lines before rolling out plant-wide.
2. Build the questions. Pull them from your PFMEA, control plan, standardized work and recent corrective actions. Every question should check a specific control that, if skipped, could produce a defect. Our guide to managing risks with PFMEA covers how failure modes are ranked.
3. Define the layers, auditors and schedule. Write down who audits, where, and how often, and make sure leaders are on the schedule, not just supervisors.
4. Train the auditors. Show them how to observe rather than just ask, how to talk to operators without making the audit feel like a test, and what they can fix on the spot versus what they must escalate.
5. Run the audits and react. Correct small deviations immediately, record every "no" answer even when it was fixed, and escalate anything that affects product.
6. Review results and rotate questions. Look at completion rates and failure rates by question each month. Retire questions that always pass, and add new ones when complaints, corrective actions or process changes call for them.

How to write good LPA questions

A good LPA question is specific, observable and answerable with yes or no at the workstation. If two auditors could look at the same station and reasonably answer differently, the question needs rewriting.

• Weak: "Is the operator following the work instruction?" Better: "Is the torque tool set to the value on the posted work instruction for this station?"
• Weak: "Is the area organized?" Better: "Are rejected parts only in the red, labeled reject bin?"
• Weak: "Is the gauge OK?" Better: "Does the go/no-go gauge have a current calibration label?"
• Weak: "Is error-proofing working?" Better: "Was today's start-of-shift verification of the presence sensor completed and signed?"

Keep each checklist short. A Layer 1 audit that takes half an hour won't get done every shift, and a list of 40 questions hides the few that matter.

Example LPA schedule and question bank

Here is an example question bank for an assembly line, showing where each question comes from and which layers ask it. Adapt the wording to your own control plan and work instructions.

Question 8 is a temporary question: it stays on the checklist until the corrective action behind it has been verified as effective, then comes off. Using LPAs this way turns them into a routine check that corrective actions are actually holding.

What to do when an LPA question fails

A "no" answer is only useful if something happens next. Set out the response in advance so every auditor handles it the same way:

1. Fix it on the spot if you can, such as replacing an outdated work instruction or moving a misplaced reject, and still record the finding.
2. Contain it if product could be affected. Hold suspect parts and log a nonconformance so the material is dispositioned properly.
3. Open a corrective action if it repeats or points to a system problem. Find the root cause through CAPA, and keep a question on the checklist to verify the fix.
4. Track the trends. Repeat findings on the same question or station are a sign the process, the instruction or the training needs to change.

This is where paper-based LPA programs tend to break down: the checklist says "no", but the finding never reaches the nonconformance log or the corrective action that should follow. An eQMS such as the Isolocity platform keeps nonconformances, CAPA, document control and training records in one place, so a problem found on the floor can be traced to the corrective action and the procedure or training change that closed it.

Common LPA mistakes

• Pencil-whipping: checking "yes" without looking. Spot-check audits and rotate auditors to keep them honest.
• Questions that never change: a checklist that always passes isn't telling you anything new.
• Leaders who delegate their audits: part of the value of LPAs is that managers see the floor for themselves.
• Findings that stop at the checklist: if a "no" doesn't lead to a fix, a nonconformance or a corrective action, the audit was wasted time.
• Checklists that are too long: long audits get skipped or rushed.
• Treating LPAs as inspection: LPAs check the process, not the part. Keep product checks in your inspection plan.

Layered process audit FAQs

What is a layered process audit?

A short, frequent audit in which several levels of the organization check that the critical controls on a manufacturing process are being followed, at frequencies that increase the closer the auditor is to the work.

How often should layered process audits be done?

A common pattern is every shift or daily for supervisors, weekly for area managers and monthly for plant leadership. Check your customers' requirements, since some set their own.

Does IATF 16949 require layered process audits?

Not directly. IATF 16949 requires manufacturing process audits and requires you to meet your customers' specific requirements, and several automakers, including GM, require LPAs through their customer-specific requirements.

What is the difference between an LPA and an internal audit?

An internal audit is a periodic, in-depth review of whether a process or system meets its requirements and is effective. An LPA is a quick, high-frequency check of a few critical controls. Most manufacturers need both.

What is CQI-8?

CQI-8 is the Layered Process Audit Guideline published by the Automotive Industry Action Group (AIAG). It describes how to design, run and improve an LPA program.

Conclusion

Layered process audits work because they are small, frequent and shared: many people checking a few critical controls catch drift long before it reaches a customer. The value comes from what happens after a "no", when findings are fixed, contained and fed into corrective action.

To see how the Isolocity platform connects nonconformances, CAPA, documents and training so findings don't get lost, book a demo.