A layered process audit (LPA) is a short, frequent check at the workstation that the process is being run to its standard, done by several layers of leadership, each at its own frequency. Team leaders audit every shift, supervisors daily, managers weekly and the plant manager monthly, so drift from standard work is caught in days and fixed before it becomes a defect.
LPA flowchartSet up an LPA programExample questionsProgram metrics
What Are Layered Process Audits?
Layered Process Audits are a system where multiple levels of leadership verify, at the process, on the floor, that standard work is being followed. Unlike product inspections that check the output, LPAs check the process: are the right steps being done in the right order with the right tools?
The "layered" part means the same kind of questions are checked by the team leader every shift, the supervisor daily, the department manager weekly and the plant manager monthly. Each higher layer also sees whether the layer below is actually auditing, which creates accountability from the floor to the front office. In the automotive supply chain the method is described in the AIAG guideline CQI-8, and several customers require it.
Why LPAs Work
Standard work decays. Over time, operators develop shortcuts, workarounds accumulate, and the documented method drifts from the actual method. LPAs catch this drift early, before it causes quality or safety problems.
| Without LPAs | With LPAs |
|---|---|
| Standard work followed for 2 weeks after training, then drifts | Standards verified daily: drift caught and corrected immediately |
| Leaders assume processes are followed because no one complains | Leaders verify at the gemba with their own eyes |
| Quality problems investigated after the fact | Process deviations caught before they create defects |
| Audits are annual, formal, feared events | Audits are daily, brief, constructive conversations |
The Layered Structure
| Layer | Who | Frequency | Scope | Duration |
|---|---|---|---|---|
| 1 | Team Leader / Lead Operator | Every shift | Their area (2-3 stations) | 5-10 min |
| 2 | Supervisor | Daily | Rotates across areas in their department | 10-15 min |
| 3 | Department Manager | Weekly | Rotates across departments | 15-20 min |
| 4 | Plant Manager / Director | Monthly | Random selection across plant | 20-30 min |
Layered Process Audit Flowchart
Every audit, at every layer, follows the same path. The branches matter more than the checklist: an audit that records a "no" and changes nothing is only measuring the decline.
How to Set Up a Layered Process Audit Program
Run the pilot for four to six weeks before adding areas. The pilot shows how long the audit really takes, which questions are always "yes" (and can be retired), and whether the higher layers keep their dates.
Designing LPA Questions
Good LPA questions are binary (yes/no), observable at the process, and focused on high-risk items:
Example LPA Questions
| Category | Question | Source |
|---|---|---|
| Quality | Is the operator verifying part orientation before loading per standard work? | Top defect: backwards installation |
| Quality | Is the torque wrench within calibration date? | FMEA: under-torque risk |
| Safety | Is the light curtain functioning (test button)? | Safety incident history |
| Process | Is the SPC chart current (within last 2 hours)? | SPC program requirement |
| Process | Is the correct revision of the work instruction posted at the station? | Document control |
| 5S | Are all tools in their designated locations? | 5S standard |
Responding to Findings
| Finding Type | Response | Timeline |
|---|---|---|
| Minor deviation (operator missed a step) | Coach on the spot. Reinforce why the step matters. | Immediate |
| Recurring deviation (same finding 3+ times) | Investigate root cause with 5 Whys: is the standard wrong, is the method impractical, is there a training gap? | Within the week |
| Safety or critical quality finding | Stop, contain, escalate. Root cause corrective action (8D or A3). | Same shift |
| System finding (standard work outdated, wrong revision) | Update the system. Retrain affected operators. | Within 48 hours |
LPA Program Metrics
Four numbers tell you whether the program is working. An illustrative month for one department with four layers:
| Metric | Formula | Example | Target |
|---|---|---|---|
| Completion rate | Audits done ÷ audits scheduled, by layer | 108 ÷ 120 = 90% | 90% or better at every layer |
| Conformance rate | Yes answers ÷ questions asked | 108 audits × 10 questions = 1,080; 1,026 yes = 95% | Rising; 100% for months means the questions are too easy |
| Repeat findings | Same question answered "no" 3 or more times | 2 questions | Each one has a root cause action open |
| Time to close | Days from finding to verified fix | Median 6 days | Set per finding type (see the table above) |
Look at completion by layer, not the average. If layers 1 and 2 are at 98% and layer 4 is at 50%, the floor has already noticed that the plant manager does not come.
LPAs Are Coaching, Not Gotchas
If operators see LPAs as a way to catch them doing something wrong, the system fails. The auditor's tone matters: "I am here to verify our process is working and help fix anything that is not." When a deviation is found, ask "what made it hard to follow the standard?" not "why did you skip the step?" Fix the system, not the person.
Effective LPAs
- Done at the process, watching actual work
- Questions linked to real failure modes and risks
- All layers participate consistently
- Findings lead to system fixes, not blame
- Completion rate tracked: 90%+ compliance
LPA Theater
- Checklist completed at a desk without going to the floor
- Generic questions not linked to actual risks
- Layer 1 does it, Layers 3-4 skip it
- Findings with no follow-up or corrective action
- "We do LPAs for the customer audit" (not for improvement)
Key Takeaway
LPAs are the mechanism that prevents standard work from decaying. Multiple levels of leadership verify the process daily, catch drift early, and fix system problems before they become defects. Design questions from your FMEA and failure history, keep audits to 10 minutes, treat every finding as a coaching opportunity, and track completion by layer. When LPAs run well, quality improves because processes are followed, not because inspection catches more defects.
Interactive Demo
Simulate weekly layered process audits. Track conformance trends and identify repeat findings.
Layered Process Audit Simulator
Conduct audits over 4 weeks. Mark items as non-conforming by clicking them, then submit each week's audit. Track conformance trends and identify repeat findings.
Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.
PlanTake the advanced knowledge checkLayered Process Audit FAQ
What is a layered process audit?
A layered process audit (LPA) is a short, frequent check, done at the workstation, that the process is being run to its standard. The same kind of questions are asked by several layers of leadership, from team leader to plant manager, each at its own frequency, so drift from the standard is caught in days instead of at the next quality escape.
How often should layered process audits be done?
The usual pattern is every shift for team leaders, daily for supervisors, weekly for department managers and monthly for the plant manager. The point is that some layer is auditing every area every day, and that the higher layers show up often enough for the floor to see it matters.
How many questions should an LPA have?
Eight to twelve, so the audit takes about ten minutes. Most should come from real failure history, the FMEA and the control plan, plus a few rotating questions that change monthly. A 30-question checklist will not get done every shift.
What is the difference between an LPA and a product audit?
A product audit checks whether finished parts meet specification. A layered process audit checks whether the process that makes them is being followed: the right revision posted, the torque check done, the gauge in calibration. One catches defects after they happen; the other prevents them.
What is CQI-8?
CQI-8 is the AIAG guideline for layered process audits, used widely in the automotive supply chain. It covers how to plan an LPA program, write questions, schedule the layers and react to findings. Several automotive customers require LPAs in their customer-specific requirements.
What metrics should an LPA program track?
Audit completion rate by layer (audits done divided by audits scheduled), conformance rate (yes answers divided by questions asked), repeat findings by question, and time to close corrective actions. Completion at the higher layers is usually the first number to slip and the best early warning that the program is dying.
What does a layered process audit flowchart show?
The path from a scheduled audit to a closed finding: go to the station, observe and ask each question, record conforming answers, correct what can be fixed on the spot, stop and escalate safety or critical quality findings, open a corrective action with an owner and date for the rest, and review results by layer so repeat findings get a root cause.