What is a layered process audit?

How does a layered process audit work?

Layered process audits (LPAs) are a quality assurance routine that verifies the process is being run the way it is supposed to be, rather than inspecting the product after the fact. Each audit is a handful of yes/no audit questions about the controls that matter most on that part of the shop floor: is the control plan being followed, are the work instructions current and in use, are the error-proofing devices working. A team member or leader answers them at the workstation in about ten minutes.

The word "layered" means several levels of leadership perform the same type of audit at different frequencies:

Because many people check the same few things often, drift is caught within a shift rather than at the next annual audit or the next customer complaint. It also puts senior leaders on the shop floor, asking about the process, on a predictable rhythm. The programme only works when it involves all levels of the organisation: once the plant manager's layer is skipped, the other layers soon follow.

Who uses layered process audits, and why?

LPAs started in automotive manufacturing, where they are a customer-specific requirement of several vehicle makers for suppliers certified to IATF 16949, with AIAG's CQI-8 as the published guideline. They have since spread to aerospace, food, pharmaceuticals and general manufacturing, and to safety, where the same routine is used for layered safety audits. The reasons are the same everywhere: fewer escapes and customer complaints, controls that stay in place after the improvement project ends, and quality and safety owned by line leaders rather than only the quality department.

What are the benefits of layered process audits?

Most quality assurance effort sits at the end of the line: inspection, testing and customer audits. Those checks find defects after they are made. LPAs move part of that effort upstream, to the conditions that make good parts in the first place.

• Drift is caught early. A manufacturing process rarely fails all at once. A torque setting is changed on night shift, a poka-yoke is bypassed "just for this batch", a work instruction falls out of date. A daily check by the team leader finds these within a shift, before they turn into scrap, rework or an escape to the customer.
• Quality becomes a line responsibility. When supervisors and managers check the same controls as the quality team, quality stops being something the quality department does to production.
• Improvements stick. A countermeasure from a corrective action or kaizen is added to the question bank, so it is checked until it becomes habit.
• Leaders learn the process. Senior auditors see the real operation regularly and hear about problems from team members directly, not only through reports.
• Evidence for customers. Completed audits, findings and closed actions show that process controls are verified, not just written down.

What goes on a layered process audit checklist or form?

Each layer of leaders audits the same process at a different frequency.

A good LPA checklist has 8–15 questions, each answerable yes or no, and each tied to a real risk:

• Is the current control plan followed for this operation?
• Are the work instructions posted, current and being used?
• Are error-proofing and poka-yoke devices verified at the start of the shift?
• Are critical process parameters (temperatures, torques, speeds) within limits?
• Are gauges calibrated and used correctly?
• Is the correct PPE worn and are safety guards in place?
• Is nonconforming product segregated and labelled?
• Have the issues found in the last audit been closed?

Choose questions from customer complaints, scrap and rework data, the process FMEA and recent near misses. Rotate a few questions each month so auditors keep looking rather than ticking. A ready-made layered process audit checklist template gives a starting question bank. Whether you call them LPA forms, audit sheets or checklists, keep one short form per station so any layer can complete it in about ten minutes.

How do you set up an LPA programme?

1. Pick the processes: start with one line or area and its highest-risk steps.
2. Write the audit questions: short, yes/no, tied to a control in the control plan or work instructions.
3. Set the layers and schedule: who audits at each layer, how often, and which areas rotate. A kamishibai board is a simple way to show that schedule where the work is.
4. Run the audits at the workstation, with photos and a note for every "no".
5. Fix on the spot or raise an action with an owner and due date, and escalate anything the area cannot close.
6. Review completion and findings in tier meetings each week, then refresh the question bank.

How do you conduct a layered process audit?

The steps above set up the programme. Conducting the audit itself is a ten-minute routine at the workstation, and it runs the same way for every layer.

Before the audit. Check which station and checklist you are assigned today and what the last audit found there. Open actions from that audit are the first thing to verify.

During the audit.

1. Tell the operator you are checking the process, not the person.
2. Answer each question by looking, not by asking "is this done?". Watch the operator verify the poka-yoke, read the parameter on the display, find the current work instruction.
3. Ask one open question, such as "what makes this step hard?". The answer often explains a "no" before you find it.
4. Record each answer as you go, with a photo for every "no".

What to do with a "no". A "no" is the point of the audit, not a failure of it. Contain first: if product is at risk, stop and segregate it, and correct the condition on the spot where you can. Record what you found and what you did. If the cause is not fixed there and then, raise an action with an owner and a due date, and escalate it if the area cannot close it. Thank the operator for raising issues; never blame them for a "no".

After the audit. Results feed the tier meetings. At tier 1 the team sees today's findings on the board; at tier 2 the supervisor reviews completion by layer, overdue actions and repeat findings; at tier 3 site leaders look at trends across lines. A question that keeps scoring "no" points to a systemic problem that needs root cause analysis, not more auditing. A question that has scored "yes" for months may be ready to rotate out.

What are the common LPA mistakes?

• Pencil whipping. Auditors tick "yes" without looking. Rotate questions, ask for photo evidence on key checks and have senior layers occasionally audit the same station on the same day.
• Checklists that grow. Thirty questions turn an LPA into a full audit that nobody finishes. Keep it short.
• Senior layers skipping their audits. This tells everyone the process does not matter.
• Findings without follow-up. A "no" that never becomes a corrective action teaches people that answering honestly is pointless.
• Audits that only find paperwork issues. If every finding is a missing signature, the questions are aimed at the wrong risks.

Paper or digital layered process audits?

Paper LPAs work for a pilot but break down at scale: schedules slip, completion is hard to see, and findings sit on clipboards. Digital checklists let you schedule each layer automatically, capture photos and signatures at the workstation, see completion in real time and turn a failed check straight into a tracked action. The aim is the same either way: the results should be visible at the daily meeting, so the people who can fix a problem see it the same day.

LPA vs gemba walk vs internal audit

A gemba walk is an open-ended, learning-focused visit. An LPA is a structured verification of a few critical controls against a checklist. An internal audit is a detailed, infrequent review of a whole system by a trained auditor. Many sites combine the first two: leaders complete a short LPA during their walk, then spend the rest of the time observing and asking questions. The internal audit then checks that the LPA programme itself is working: audits completed on time, findings closed and questions refreshed.