In most AS9100 organizations, the program owner for LPAs should be the quality function, with strong day-to-day sponsorship from operations leadership.
That means quality typically owns the framework: audit structure, question governance, revision control, training expectations, records, escalation rules, and linkage to corrective action. Operations should own execution discipline on the floor: participation by supervisors and managers, response to findings, and sustained adherence to standard work.
If one group must be named as the single owner, it is usually quality. If operations owns it without quality governance, LPAs often drift into inconsistent checklists, weak evidence, and poor follow-through. If quality owns it without operations sponsorship, LPAs often become a compliance ritual with low credibility and limited impact on actual process behavior.
What good ownership usually looks like
- Quality owns: program design, audit cadence rules, controlled questions, auditor qualification expectations, record retention, trend review, and connection to CAPA or other issue-management processes.
- Operations owns: leader participation, timely closure of shop-floor issues, reinforcement of standard work, and resourcing corrective actions.
- Site leadership owns: accountability when repeat findings persist across cells, shifts, suppliers, or programs.
This is usually better described as quality-governed, operations-executed, leadership-backed.
Why this matters in an AS9100 environment
In a regulated, traceability-heavy environment, LPA ownership is not just about who schedules audits. The owner has to maintain controlled revisions, evidence quality, escalation discipline, and consistency across shifts and sites. That is why the program cannot sit only with a continuous improvement coordinator or only with a production manager unless the supporting governance is already mature.
Also, LPAs should not be treated as a substitute for the internal audit program, process validation, training control, or formal corrective action. They are a reinforcement mechanism. Their value depends on whether findings are traceable, reviewed, and acted on through established quality and operational processes.
Common failure modes
- Quality-only ownership: good records, weak behavior change.
- Operations-only ownership: faster audits, but inconsistent standards and pressure to under-report.
- EHS or CI ownership without quality governance: overlapping checks, unclear escalation, and fragmented records.
- Corporate ownership without local accountability: standard templates exist, but plants treat the process as administrative overhead.
No org chart choice fixes weak management follow-through. If leaders do not review trends, remove barriers, and enforce closure, the program will decay regardless of where ownership sits.
System and process implications
In brownfield environments, LPA ownership also depends on where evidence and actions must flow. If findings feed a QMS, training system, MES, or ERP-linked nonconformance process, the owner needs enough authority to coordinate across those systems. That does not require replacing existing tools. In fact, full replacement is often unnecessary and risky in long-lifecycle, validated environments. A lighter approach is usually more realistic: keep authoritative records where they already belong, define clear interfaces, and control revisions and approvals carefully.
If your plant has mixed paper and digital workflows, ownership should be assigned to the function most capable of maintaining consistency across both. Otherwise, one part of the program becomes visible and controlled while the rest becomes informal.
Practical answer
For most AS9100 organizations, assign program ownership to quality, require co-ownership in practice from operations, and make site leadership accountable for response and sustained use. If your quality team is weak operationally, or your operations team is weak on control and evidence, address that gap directly rather than forcing sole ownership into the wrong function.