Layers
Multiple Leadership Levels
Daily
Not Monthly or Quarterly
Process
Not Product Inspection
Verify
Standards Are Followed

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 audit questions are checked by the team leader daily, the supervisor weekly, the manager monthly, and the plant manager quarterly. Each layer verifies that the layer below is actually auditing — creating accountability from the floor to the front office.

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 LPAsWith LPAs
Standard work followed for 2 weeks after training, then driftsStandards verified daily — drift caught and corrected immediately
Leaders assume processes are followed because no one complainsLeaders verify at the gemba with their own eyes
Quality problems investigated after the factProcess deviations caught before they create defects
Audits are annual, formal, feared eventsAudits are daily, brief, constructive conversations

The Layered Structure

LayerWhoFrequencyScopeDuration
1Team Leader / Lead OperatorEvery shiftTheir area (2-3 stations)5-10 min
2SupervisorDailyRotates across areas in their department10-15 min
3Department ManagerWeeklyRotates across departments15-20 min
4Plant Manager / DirectorMonthlyRandom selection across plant20-30 min

Designing LPA Questions

Good LPA questions are binary (yes/no), observable at the process, and focused on high-risk items:

Start from failure modesWhat defects or safety incidents have occurred? What process deviations caused them? These become your audit questions. Link to your FMEA — high-RPN items should be on the LPA checklist.
Keep it to 8-12 questionsAn LPA that takes 30 minutes will not get done daily. Keep it brief and focused on the vital few. Rotate supplemental questions monthly.
Make them verifiable"Is the operator following standard work?" is vague. "Is the operator performing the torque check at Step 3 per SWI-042?" is verifiable. The auditor watches the actual step.

Example LPA Questions

CategoryQuestionSource
QualityIs the operator verifying part orientation before loading per standard work?Top defect: backwards installation
QualityIs the torque wrench within calibration date?FMEA: under-torque risk
SafetyIs the light curtain functioning (test button)?Safety incident history
ProcessIs the SPC chart current (within last 2 hours)?SPC program requirement
ProcessIs the correct revision of the work instruction posted at the station?Document control
5SAre all tools in their designated locations?5S standard

Responding to Findings

Finding TypeResponseTimeline
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: Is the standard wrong? Is the method impractical? Training gap?Within the week
Safety or critical quality findingStop, contain, escalate. A3 on root cause.Same shift
System finding (standard work outdated, wrong revision)Update the system. Retrain affected operators.Within 48 hours

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.

⚡
Try It Yourself
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.
Week 1 Audit8/8 conforming
0
Audits Completed
0%
Avg Conformance
0
Total Findings
0
Repeat Findings
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check →
Free forever · Every feature included

Stop reading, start modeling

Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.

Open Workbench → Pro Knowledge Check

Take this to a room

The running order

For a plant starting LPAs. They should leave with 8 to 12 verifiable questions drawn from real failure modes.

7 beats · 10 min
  1. 1

    Auditing the process, not the product

    This is the distinction the name is trying to make, and it changes everything about how it feels.

    • Product inspection asks whether this part is good.
    • Process audit asks whether the standard was followed.
    • One catches defects. The other prevents them.

    Ask the room Do we currently verify our standards, or only our output?

  2. 2

    Layers means several levels, daily

    Team lead, supervisor, manager, plant leader - each auditing at their own cadence.

    • Daily, not monthly or quarterly. Drift is caught in days.
    • When only layer one participates, the message is that it does not matter above the floor.
    • Track completion by layer - that number is the first thing to go.
  3. 3

    Questions come from failure history

    Generic questions produce generic audits. Start from what has actually gone wrong.

    • What defects and safety incidents have occurred, and what deviation caused them?
    • Link to the FMEA - high-risk items belong on the checklist.
    • Rotate supplemental questions monthly so it does not go stale.
  4. 4

    Eight to twelve, ten minutes

    An audit that takes thirty minutes will not happen daily, and one that does not happen daily is not an LPA.

    • Keep it to the vital few.
    • Ten minutes is the design target.
    • Length is the most common reason these quietly stop.

    Ask the room How long would our checklist take?

  5. 5

    Make every question verifiable

    The wording decides whether the auditor can be honest.

    • Is the operator following standard work? - vague, and always answered yes.
    • Is the operator performing the torque check at step 3 per SWI-042? - verifiable, and the auditor watches it.
    • If you cannot observe it, it is not an audit question.
  6. 6

    Coaching, not gotchas

    The tone decides whether the system survives, and operators read it immediately.

    • I am here to verify our process is working and help fix anything that is not.
    • When a deviation is found: what made it hard to follow the standard?
    • Not: why did you skip the step. Fix the system, not the person.

    Ask the room How would our operators describe an audit today?

  7. 7

    Findings must change something

    An audit that records deviations and changes nothing is a measurement of decline.

    • Every finding leads to a system fix or a coaching conversation, same day.
    • Track completion rate by layer - target 90 per cent or better.
    • We do LPAs for the customer audit is the sound of a dead system.

    Ask the room Who owns the findings, and how fast do they close?