How to use this page
How to read these LPA examples
Each scenario uses the same frame so you can compare processes quickly: the setting, why the control matters, Layer 1 checks, an example observation or failure, how follow-up could work, and what higher layers might look at. For the overall method, start with the Layered Process Audit guide.
Process + control
What is being audited and which process controls the example targets.
Direct observation
What the auditor actually sees, measures, compares, or asks to be demonstrated.
Fail + follow-up
What is recorded when the control is not holding and how the issue becomes owned work.
Layer perspective
How a supervisor, area manager, and leadership level may look at the same risk differently.
The checks are compact by design. For detailed question-writing rules, see the Layered Process Audit checklist guide.
Hypothetical example
Final Assembly
Setting
A small manufacturer of mechanical subassemblies. The final assembly cell has a torque station, a presence sensor for a seal, and a build record at the station.
Why it matters
Assembly depends on controls that are easy to drift: settings get changed, instructions age, the wrong component can reach the station, and mistake-proofing can stop working.
What to adapt
Challenge method, reference parts, instruction references, containment rules, and which controls matter most.
Example Layer 1 checks
Is the posted work instruction the current released revision?
Posted revision vs. released revision list
Does the torque driver setting match the current instruction?
Displayed setting vs. process requirement
Is the torque driver within its required verification status?
Tool ID and verification status
Do component containers match the part and lot required for the job?
Container labels vs. build record
Was first-piece verification completed for the current run?
Current-run first-piece record
Using the approved challenge method, does the presence sensor respond correctly?
Approved challenge result
Are traceability fields complete for the most recent units?
Build record
Is nonconforming material segregated from normal production flow?
Tagged container and production area
Example observation · Pass
The torque driver display matches the value in the current work instruction. The auditor records Pass and, where useful, the observed value.
Example Fail
The approved challenge piece is accepted by the presence sensor instead of being rejected. The auditor records the exact observation, station, shift, and challenge used.
Example follow-up
The supervisor follows the plant's containment or reaction process where required. A finding is created with an owner and due date. After corrective work, verification confirms the control is working again.
Layer 2 perspective
An area manager might repeat the critical challenge check and then review whether similar sensor findings have appeared recently and whether prior actions held.
Layer 3 perspective
Plant or quality leadership might review recurring mistake-proofing failures, overdue findings, and whether lower-layer audits are being completed as designed.
Hypothetical example
CNC Machining
Setting
A machining cell producing housings on a CNC machining center with a fixture, tool-life counter, first-piece approval, and defined measurement controls.
Why it matters
A machine can appear to run normally while the wrong program, fixture, tool status, or measurement control is in use.
What to adapt
Which controls live in the machine, tool-life rules, setup controls, measurement method, and critical features.
Example Layer 1 checks
Does the loaded program and revision match the setup requirement?
Machine control vs. setup sheet
Does the installed fixture ID match the job?
Fixture ID vs. setup sheet
Is the tool in use within the plant-defined tool-life limit?
Tool-life screen or tool log
Is first-piece approval recorded for the current setup?
First-piece record
Is the specified gauge in use and within its required status?
Gauge ID and verification status
Does the sampled critical feature meet the defined requirement?
Specified measurement method
Does material identification match the traveler or production record?
Material tag vs. traveler
Is the reaction plan available where the process requires it?
Point-of-use process reference
Example Fail
The finishing tool is beyond the plant-defined tool-life limit and is still running. The auditor records the tool, counter state, and the relevant limit rather than only writing 'tool issue.'
Example follow-up
The plant applies its own reaction and containment process. A finding is opened. Investigation may identify a reset or replacement-control issue; later audits verify the corrected control remains in place.
Layer 2 perspective
An area manager can check the same tool-life control and then review recent machining findings and open actions for the cell.
Layer 3 perspective
Leadership can look for recurring tool-life or setup issues across machines rather than treating every failure as an isolated operator event.
Hypothetical example
Injection Molding
Setting
A molding press running a production job with controlled material, mold identification, a defined setup, and first-piece approval.
Why it matters
Molding depends on the right material, tool, and process settings being used together. A mismatch can continue through many cycles before someone notices.
What to adapt
Material controls, drying needs, approved parameters, sample method, and traceability requirements.
Example Layer 1 checks
Does the recipe or program ID match the approved setup?
Press screen vs. setup requirement
Does the installed mold ID match the scheduled job?
Mold ID vs. production record
Does material identification at the hopper match the job?
Material label vs. production record
Where drying is required, is the dryer in the defined condition?
Dryer display vs. setup requirement
Do selected machine parameters match the approved setup?
Selected parameters on the control screen
Is first-piece approval recorded for the current run?
Approval record
Does the sample meet the plant's defined reference or check method?
Sample vs. approved method
Are rejected parts separated from normal packing flow?
Rejected-part container and area
Example Fail
The material lot at the hopper does not match the lot scheduled for the job. The auditor records both identifiers, the press, and the time.
Example follow-up
The supervisor applies the plant's material and containment process. A finding follows the mismatch to the staging or loading control, then a later audit verifies that the corrected material-control step is holding.
Layer 2 perspective
An area manager might review material-related failures across several presses and confirm that staging controls are being followed.
Layer 3 perspective
Leadership might review whether material mismatches recur and whether the LPA question set still targets the right stage of the process.
Hypothetical example
Welding & Fabrication
Setting
A fabrication area welding sub-frames in a fixture using controlled drawings, work instructions, material identification, and defined inspection or rework steps.
Why it matters
Fabrication depends on the right drawing, fixture, material, and process references being used together, with rework controlled rather than blended into normal production.
What to adapt
Applicable procedure references, traceability, consumables, rework controls, and customer or product-specific requirements.
Example Layer 1 checks
Are the drawing and work instruction at the station current?
Posted revisions vs. released versions
Is the installed fixture the one specified for this part?
Fixture ID vs. job requirement
Does material identification match the traveler?
Material tag vs. traveler
Where the process requires a weld procedure, is the correct reference available?
Procedure reference vs. job
Are specified consumables correctly identified?
Consumable labels vs. instruction
Was the required first-article inspection completed?
Inspection record
Is required part identification or traceability applied?
Part and traveler
Are repaired or reworked parts routed according to the plant's process?
Rework area and identification
Example Fail
A superseded work instruction is posted and the fixture at the station belongs to another variant. The auditor records the old revision, current released revision, and fixture ID.
Example follow-up
The supervisor follows the plant's reaction and containment process. Separate findings can track document-distribution and fixture-control failures, with later verification confirming each control has been restored.
Layer 2 perspective
An area manager might review whether similar document or fixture issues exist at adjacent fabrication stations.
Layer 3 perspective
Leadership might look for a recurring document-control or fixture-management pattern rather than a one-station event.
Hypothetical example
Paint & Coating
Setting
A finishing line applying a coating and curing parts through a controlled process with defined recipes, materials, and verification records.
Why it matters
Coating quality can depend on conditions that are not obvious by looking at the finished part and can be changed at a controller or during material preparation.
What to adapt
The actual process parameters, approved ranges, verification method, material controls, and product requirements.
Example Layer 1 checks
Does coating material and batch match the production record?
Container label vs. job record
Was surface preparation performed as defined?
Preparation step and record
Does the selected recipe or program match the part being run?
Controller vs. job
Where applicable, is mixture condition within the plant-defined range?
Recorded condition or approved check
Is the oven setpoint within the approved process range?
Controller display vs. process requirement
Was coating-thickness verification completed for the run?
Verification record
Are parts identified through the process as required?
Tags, racks, or travelers
Are defective parts identified and segregated?
Defect area and labels
Example Fail
The oven setpoint is outside the approved range for the current product. The auditor records the displayed setpoint, the required range, oven, and time.
Example follow-up
The plant's own response process governs product hold, process correction, and disposition. The finding tracks why the setpoint changed and whether the corrective control remains effective.
Layer 2 perspective
An area manager might verify start-of-shift process checks and review recent oven or recipe findings.
Layer 3 perspective
Leadership might review repeated setpoint or recipe issues and whether change controls are working across the finishing area.
Hypothetical example
Packaging & Final Release
Setting
A packaging station applying customer labels and packing finished parts into approved containers before final release.
Why it matters
A product can be physically correct and still create a customer problem through the wrong label, lot code, quantity, or packaging configuration.
What to adapt
Customer-specific label and pack requirements, release method, traceability, quantities, and obsolete-label controls.
Example Layer 1 checks
Does the product in the container match the label part number?
Product vs. label
Is the label the current released revision for the job?
Label revision vs. released list
Does packed quantity match the defined pack requirement?
Container contents vs. packing instruction
Do lot and date-code details match the production record?
Label vs. production record
Is the specified packaging material in use?
Packaging material vs. instruction
Are customer-specific packing requirements followed where applicable?
Pack instruction
Was required final inspection completed and recorded?
Inspection record
Are obsolete or incorrect labels removed from normal use?
Station and label storage
Example Fail
The label loaded at the station is a superseded revision. The auditor records the revision seen, the current released revision, and the station or printer involved.
Example follow-up
The supervisor follows the plant's label-control and containment process for affected packed product. A finding then tracks why the obsolete label remained available and how the release control was improved.
Layer 2 perspective
An area manager might review label-related findings and whether the release process is being followed consistently.
Layer 3 perspective
Leadership might review recurring label failures, overdue actions, and whether related customer complaints point to the same control.
Layer comparison
Same process, different audit layers
Using final assembly again, the same process risk can be viewed at different levels. This is one possible design, not a mandatory three-layer hierarchy.
| Layer | Example auditor | What they observe | Example question | What a Fail can signal |
|---|---|---|---|---|
| Layer 1 | Supervisor / team lead | Direct station conditions | Does the approved challenge produce the expected reject? | The control is not working now. |
| Layer 2 | Area / production manager | Critical controls + recent drift | Did the previous mistake-proofing action hold, and is the control working now? | The area may be repeating a known failure. |
| Layer 3 | Plant / quality leadership | Patterns, overdue work, execution | Are mistake-proofing findings recurring or overdue, and are lower-layer audits happening? | The gap may be systemic or managerial, not only station-level. |
Higher-level items such as recurrence and overdue findings can also be reviewed through reports rather than placed directly on a line-side checklist.
Worked lifecycle
Example of a failed LPA question from start to closure
Hypothetical final-assembly failure
Question: Using the approved challenge method, does the mistake-proofing device produce the expected reject?
Observed: the device accepted the challenge. Answer: Fail.
- 01
Record the exact observation
Capture which station, shift, approved challenge, and behavior were observed.
- 02
Follow the plant's reaction process
Containment or product disposition follows the organization's own procedure where required.
- 03
Create a finding
Keep the changing follow-up lifecycle separate from the historical audit answer.
- 04
Assign an owner
The accountable owner may be different from the auditor.
- 05
Set a due date
Make expected follow-up visible.
- 06
Complete corrective work
Handle cause and corrective work under the plant's own process.
- 07
Resolve the finding
Record what was done without rewriting the original audit.
- 08
Verify the control
Use an appropriate verifier or later audit to confirm the control holds.
- 09
Reopen if needed
If the control fails again, return the finding to active follow-up.
Audit record
Fail · device accepted the challenge
Historical observation. It does not turn into Pass after the fix.
Finding record
Open → resolved → verified → reopen if needed
This record carries the changing lifecycle after the audit.
Learning from failures
Example of a checklist revision after a real problem
Suppose Revision 2 of a machining checklist has no changeover-verification question. A production issue later shows that a recurring check on changeover confirmation would be useful. The plant adds the new question in Revision 3 and gives it an effective date.
REVISION 2
Earlier audits
No changeover question. Historical audits stay attached to this version.
REVISION 3
After the effective date
A new changeover-verification question applies to future audits.
This lets the program learn without rewriting history. For the data structure behind revisions and audit records, see the Layered Process Audit template guide.
Compact reference
Examples of good LPA questions by process type
These are examples of structure, not a second universal checklist. Each names an item, a requirement, and something observable.
| Process | Example question | Control verified |
|---|---|---|
| Assembly | Does the torque driver ID match the tool listed on the current work instruction? | Correct tool in use |
| Assembly | Does the component-bin part number match the current build record? | Material identification |
| Machining | Does the loaded program revision match the setup requirement? | Correct program |
| Machining | Is the specified gauge in use and within its required status? | Measurement control |
| Molding | Does the installed mold ID match the scheduled job? | Correct tool for job |
| Molding | Are rejected parts segregated from normal packing flow? | Rejected-part control |
| Welding / fabrication | Does the fixture ID match the current job requirement? | Correct fixture |
| Welding / fabrication | Are repaired parts routed according to the defined rework process? | Rework control |
| Paint / coating | Is the oven setpoint within the approved range for the selected recipe? | Process parameter |
| Paint / coating | Was required coating verification completed for the current run? | Verification step |
| Packaging | Does the loaded label revision match the released label list? | Label control |
| Packaging | Does the lot code on the label match the production record? | Traceability |
For the full question bank and wording patterns, use the Layered Process Audit questions guide. For checklist structure, acceptance criteria, and Pass / Fail / N/A design, use the LPA checklist design guide.
Shared pattern
What these examples have in common
Real process control
The check points at something the process actually depends on.
Observable condition
The auditor can see, measure, compare, or ask for a defined demonstration.
Defined expectation
There is a setup, instruction, range, record, or reference to compare against.
Clear answer
Pass or Fail is based on the observed condition rather than a general impression.
Meaningful response
A Fail has an owner and follow-up rather than disappearing on the form.
Repeatability
Another auditor should be able to perform the same check later.
Historical traceability
The record retains what was checked and which checklist revision was used.
Use examples carefully
What you should — and should not — copy from an example
Copy the pattern
- • Point at a real process control.
- • Make the observation direct and repeatable.
- • Define the expected condition.
- • Make a Fail lead somewhere visible.
- • Preserve the historical audit record.
Do not copy as-is
- • Exact questions or question count
- • Layer titles or number of layers
- • Frequency or recurrence
- • Process setpoints, limits, or tolerances
- • Finding and escalation rules
These examples are not presented as requirements of AIAG, ISO, or IATF. Formal requirements and customer-specific expectations should be read from the applicable source documents. Your LPA design should reflect your own process and risk.
From example to pilot
How to turn one of these examples into your own LPA
- 01
Choose one process
Start where a lapse matters and the team can support a pilot.
- 02
Identify the controls that matter
Use your process documentation, setup controls, and failure history.
- 03
Write a small set of observable questions
Keep the first version focused rather than copying a long generic list.
- 04
Define acceptance criteria
Give each question an actual reference, condition, range, or approved method.
- 05
Decide which layer checks what
Match checks to the perspective each layer can realistically provide.
- 06
Define recurrence
Choose a cadence based on risk and what the organization can sustain.
- 07
Define the response to Fail
Set ownership, due dates, containment references, and verification expectations before launch.
- 08
Pilot with real auditors
Watch how the questions work on the floor rather than only reviewing them in a meeting.
- 09
Remove confusion and low-value checks
Rewrite items that create inconsistent answers or no useful signal.
- 10
Control revisions
Publish changes deliberately and retain the revision used by each historical audit.
Tooling choice
How the same examples look in Excel vs. LPA software
Any of the six scenarios can be run in Excel. For a small program, that can be a sound choice. The difference is mainly how much coordination your team has to maintain manually.
| Area | Excel | LPA software |
|---|---|---|
| Checklist | Stored in a sheet with revision discipline | Controlled checklist published as a revision |
| Schedule | Tab or calendar maintained manually | Recurring audit obligations generated from schedules |
| Assignment | Names and rotation tracked manually | Fixed or round-robin assignment |
| Responses | Rows in a response table | Recorded inside the audit with notes and private evidence |
| Findings | Separate table with owners and dates | Findings linked to failed checks with lifecycle tracking |
| Reminders | Manual email or calendar follow-up | Reminder workflow and overdue visibility |
| Reporting | Formulas, pivots, or manual consolidation | Dashboard, reports, and exports |
| History | Archive discipline and controlled files | Audit and finding history retained |
If you want the spreadsheet architecture in detail, see the LPA template guide. If coordination is already the hard part, see the Layered Process Audit software page.
When coordination grows
When does LPAWorks help?
LPAWorks is built for small manufacturers moving from Excel, paper, email, or shared folders to a focused LPA workflow. It does not invent process-specific questions for you; the controls still come from your plant.
Focused LPA workflow
Import the checklist, schedule the work, and keep findings connected to the audit
LPAWorks supports CSV/XLSX checklist import, controlled published revisions, recurring schedules, fixed or round-robin assignment, Pass / Fail / N/A execution, notes and private evidence, finding ownership and due dates, resolution, verification, reopen, history, dashboards, reports, and PDF/CSV exports.
Historical audits remain tied to the checklist revision used at the time. LPAWorks is deliberately focused on the LPA workflow and is not positioned as a broad QMS, ERP, MES, document-control suite, or LMS.
Current access
30-day free trial
No card is required for the 30-day trial. After the trial, the workspace is read-only until you subscribe.
Try your own checklistFrequently asked questions
Layered Process Audit examples FAQ
What is an example of a Layered Process Audit?
A supervisor may walk to a final assembly cell and verify a short set of defined controls such as torque setting, first-piece completion, material identification, and mistake-proofing response. The exact controls should come from that process, not from a generic list.
What are common LPA questions in manufacturing?
Common patterns include checking the current instruction, correct program or recipe, fixture or mold, gauge status, material identification, first-piece records, mistake-proofing response, traceability, and nonconforming-material controls. The right questions vary by process.
What does a Layer 1 LPA look like?
Layer 1 often focuses on direct process conditions close to daily operations, such as current settings, materials, work instructions, error-proofing, and required records. Titles and frequency vary by organization.
What does a Layer 2 LPA look like?
Layer 2 may repeat core process checks and add broader follow-up on recent findings, repeated drift, or whether controls are holding across an area.
What does a Layer 3 LPA look like?
Higher leadership may focus on recurring failures, overdue findings, and whether lower-layer audits and follow-up are happening. Some organizations review these items from reports rather than as line-side checklist questions.
Can the same LPA checklist be used for every process?
A common format can help reporting, but the questions and acceptance criteria should reflect each process's actual controls and risks.
What happens when an LPA question fails?
The auditor records the observation, the plant follows its own containment or reaction process where needed, and a finding can carry ownership, due date, resolution, verification, and reopen status. The original audit answer remains historical.
Can Layered Process Audits be managed in Excel?
Yes. Excel can be entirely adequate for a small, simple program. Coordination becomes harder as schedules, auditors, revisions, reminders, findings, and reporting multiply.
How often should an LPA be performed?
There is no universal cadence. Frequency should reflect process risk, operational needs, customer-specific expectations where applicable, and what the organization can execute consistently.
Are these examples required by AIAG, ISO, or IATF?
No. These are hypothetical illustrations, not a claim about any standard requirement. Formal or customer-specific requirements should be read from the applicable source documents.
Should old audit records change after a checklist revision?
No. Historical audits should remain tied to the checklist revision used at the time so the record shows what the auditor was actually asked to verify.
How do I create an LPA for my own process from these examples?
Choose one process, identify the controls that matter, write a short set of observable checks with acceptance criteria, define layers and cadence, define the response to Fail, pilot with real auditors, and revise from what you learn.
The takeaway
Copy the pattern, not the exact questions.
Select a real process control, verify it directly, record what happened, act on failure, and repeat the check often enough to know whether the control is holding. Then adapt the questions, layers, frequency, and follow-up to your own plant.