When to use it
Create a problem-solving process where the problem, analysis, cause, actions, verification and recurrence prevention are documented without skipping stages.
QAPP principle
The application structures the workflow, evidence, ownership and links. Engineering judgement and customer-specific requirements remain with the competent team.
Inputs and preparation
- Verifiable problem statement and impact
- Data and evidence to scope the problem
- Cause analyses and tested hypotheses
- Actions, owner, due date and success criteria
- Verification results and lessons learned
Workflow
- Define the problem before searching for cause.
- Protect the customer/process when needed.
- Test causes rather than selecting them by vote.
- Select and validate actions before standardising.
- Verify effectiveness and update systems that prevent recurrence.
How QAPP can digitise it
| Element | Digital implementation |
|---|---|
| Data | Structured fields, controlled lists, revisions and attached evidence. |
| Ownership | Owners, due dates, notifications, approvals and escalation. |
| Traceability | Links between records, actions, revisions and resulting evidence. |
| Review | Status, open risks, overdue actions and management dashboards. |
AIAG alignment
AIAG CQI-20 · 2nd Edition
CQI-20 supports a robust problem-solving process and emphasises problem description, team participation, prioritisation, analysis, step verification and avoiding skipped stages. QAPP can keep stages, evidence and approvals in one audited workflow.
Open official AIAG source →Interpretation limits
This page is practical guidance, not a replacement for the licensed AIAG publication, IATF/customer-specific requirements or competent engineering judgement.