LayerAudit / Help
Layered process audit resources

What Is a Layered Process Audit? A Manufacturing Guide

Learn what LPA means, how management layers participate, and how to start a process audit routine with a checklist, schedule and follow-up.

A layered process audit (LPA) is a recurring check of how a work process is performed against its defined requirements, carried out by people from different levels of the organization. It brings supervisors, managers and plant leaders into the verification of important process controls.

For a manufacturing team, the practical question is specific: are the controls intended to prevent an error actually being followed at the point of work? The program needs a clear question, an assigned auditor, a planned time and a way to follow up when the answer is No.

What does “layered” mean?

Layers describe organizational responsibilities. People close to daily production perform frequent checks, while managers and senior leaders participate on a cadence appropriate to their role and the process risk. Each layer observes the process and contributes to follow-up. A management review of a dashboard alone does not provide the same evidence as a visit to the process.

  • Frontline leaders or supervisors verify selected controls during routine production.
  • Department or area managers check whether controls work consistently and whether recurring findings receive action.
  • Plant leadership examines process discipline, removes obstacles and supports action on issues that cross departments.

Your organization defines the number of layers, auditor qualifications and frequency. Role names and example schedules in online guides vary. Base the final plan on process risk, customer obligations, operating patterns and the time needed to perform a meaningful check.

A layered process audit example

Imagine a fictional assembly line that uses two visually similar components. The approved work instruction identifies the component for the job running now. A checklist asks the auditor to compare the material ID at the point of use with that instruction and record the observed IDs.

A supervisor finds the wrong component container at the station. The team follows its local containment procedure and records a finding. The action owner investigates how the container reached the station and implements the agreed correction. A manager later verifies the revised control during production and checks for recurrence.

The next leadership visit can inspect the same control and ask whether other shifts or lines face the same risk. All layers contribute to one process question. The value comes from the observation and response, rather than the number of completed forms. This is an illustrative example, not a LayerAudit customer result.

How LPAs relate to other quality activities

  • Product inspection examines a product or its characteristics. An LPA checks whether selected process controls are being followed.
  • A quality management system audit examines the management system against its audit criteria. An LPA is a narrower, recurring check at the point of work.
  • A gemba walk can explore how work happens more broadly. An LPA uses defined questions and acceptance criteria for the controls in its scope.
  • Corrective action addresses an identified issue and its causes. The LPA supplies observations and can later verify that an agreed control remains in use.

These activities can support each other. A product defect may identify a process control worth adding to the LPA checklist. Repeated failed checks may show that a control needs redesign. Passing an LPA does not by itself establish that every product conforms or that the management system meets every requirement.

Start an LPA program in five steps

  • Choose a pilot process. Review recurring defects, customer concerns and process risks with the people who own the work. Define the control you need to verify.
  • Write observable questions. Give each question an expected condition, a process reference and an evidence method. Test whether two auditors interpret it consistently.
  • Assign layers and a schedule. Name primary and backup auditors, include relevant shifts, and reserve realistic time for each check.
  • Practice at the workstation. Run a joint audit, compare results and clarify ambiguous wording before expanding the program.
  • Close the loop. Give findings an owner and due date, verify completed actions and review recurring failures with the responsible managers.

Get the editable layered process audit checklist

Set up a schedule with layer and shift coverage

Review results without rewarding box ticking

Review completion, findings and follow-up together. A high completion rate can coexist with weak observations. A low finding rate may reflect a stable process, unclear questions or audits that miss the work being performed. Review a sample of evidence before drawing a conclusion.

  • On-time completion: audits completed by their planned deadline divided by the audits due in that period. Define how cancellations and rescheduling are treated.
  • Repeat findings: issues that recur at the same control after an action was recorded as complete.
  • Overdue actions: open actions whose agreed due date has passed, reviewed with the responsible owner.
  • Coverage: which processes, shifts and layers were actually observed compared with the intended plan.

Use these measures to direct attention and improve the routine. Avoid setting a target that pressures auditors to record only passes or to close findings before the control is verified.

Where CQI-8 fits

AIAG publishes the CQI-8 Layered Process Audit Guideline. Automotive teams can consult the current publication and their customer-specific requirements when establishing a program. This article is an introduction and does not reproduce the paid guideline or establish a customer compliance requirement.

When LPA software becomes useful

A small pilot can start with a spreadsheet and a shared follow-up log. As the program covers more shifts, layers or plants, the coordination work grows: maintaining checklist revisions, assigning recurring checks, collecting findings and reviewing closure.

LayerAudit brings audit scheduling, digital checklists, findings and corrective-action tracking into a manufacturing LPA workflow. Use the pilot to define what you need before selecting software or expanding the rollout.

Explore LayerAudit for manufacturing teams

See layered process audit software capabilities

Further reading

L2L: layered process audit framework and implementation overview

Tervene: planning and implementing a layered process audit program

AIAG: CQI-8 publication information

On this page