Layered Process Audits: How to Build an LPA Program, With a Flowchart

How to set up a layered process audit program: who audits at each layer and how often, a flowchart from audit to corrective action, and example questions.

13 min read 10 sections Guide 5 of 7, Quality & Measurement Updated

New to this topic?

Read these first to get the most out of this guide:

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

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?

STEP · KEY POINT · WHY
Standard workThe current best way, written down, so it can be improvedThe Standard work guide

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.

Gemba walkGo see the work where it happensThe Gemba walk guide
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

TIER 1TIER 2TIER 3
Daily managementTier meetings cascade: the floor board feeds the area board feeds the plant boardThe Daily management guide
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

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.

Layered process audit flowchart: scheduled audit, go to the station, observe and ask, conforming answers recorded, non-conforming answers corrected on the spot, escalated if safety or critical, or opened as a corrective action, then tracked and reviewed by layer Audit scheduled layer, area, date Go to the station use this layer's questions Observe the step, ask the question Conforms? Yes Record yes, next question No Fixed on the spot? Yes Correct and coach, record as corrected, next question No Safety or critical quality? Yes Stop, contain, escalate the same shift No Open corrective action owner and due date Track to closure verify the fix at the next audit Weekly review by layer 3+ repeats: root cause rotate the questions Corrected items still count in the weekly review.

How to Set Up a Layered Process Audit Program

S × OD
FMEARPN = severity × occurrence × detectionThe FMEA guide
Pick a pilot areaStart with one line or cell that has a known quality or safety history and a supervisor willing to lead it.
Build the question bankWrite 8 to 12 yes/no questions per area from failure history, the FMEA, the control plan and customer requirements. Each one must be observable at the station.
Define the layers and frequenciesTeam leader every shift, supervisor daily, department manager weekly, plant manager monthly, each with an area rotation.
Publish the scheduleA visible board or calendar that shows who audits which area on which day, so missed audits are obvious.
Train the auditorsTeach the questions, how to observe rather than ask, and how to coach when a step is missed.
Run, record and reactCorrect on the spot where possible, escalate safety and critical quality findings the same shift, and open a corrective action with an owner and date for the rest.
Review the results by layerEach week review completion rate, conformance rate, repeat findings and open actions. Three repeats of one finding trigger a root cause analysis.
Rotate and refresh the questionsRetire questions that are always yes, add questions from new failures, and rotate a few each month so the audit does not go stale.

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:

5SSort, set in order, shine, standardize, sustainThe 5S guide
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

A3The whole problem, story left to right, on one sheetThe A3 guide
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 with 5 Whys: is the standard wrong, is the method impractical, is there a training gap?Within the week
Safety or critical quality findingStop, 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:

TARGET
Improvement stepsSmall experiments step up toward the target condition, one rung at a timeThe Improvement steps guide
MetricFormulaExampleTarget
Completion rateAudits done ÷ audits scheduled, by layer108 ÷ 120 = 90%90% or better at every layer
Conformance rateYes answers ÷ questions asked108 audits × 10 questions = 1,080; 1,026 yes = 95%Rising; 100% for months means the questions are too easy
Repeat findingsSame question answered "no" 3 or more times2 questionsEach one has a root cause action open
Time to closeDays from finding to verified fixMedian 6 daysSet 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.

UCLLCL
Control chartA point outside the limits, or a run on one side, is a signalThe Control chart guide

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? Guided scenarios and data export. Included with every plan.

PlanTake the advanced knowledge check

Layered Process Audit FAQ

REF 25.000CAL OKDUE 04/27
CalibrationAn instrument is checked against a reference standard and gets its sticker with the next due date

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.

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn
Take the advanced knowledge check Plan Included with every plan.

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?